Websites that say what you do, in Hebrew and English

Designed, fast sites for a business that sells a service. Every page answers what a client asks first: what you do, what they get, and how to start. This site is the live example: designed, written, and built here, in both languages.

What I do

I design, write, and build each site myself, with AI tools; this site is the working sample.

  • Design and build the site. Structure, type, and copy that state your service plainly, built to load fast on a phone.
  • Write it in both languages. Hebrew and English, each written natively rather than translated word for word, with right-to-left layout done properly.
  • Prepare it for search. Every page set up for search engines and AI assistants: titles, descriptions, and a map of the site.
  • Hand it over. Visitor analytics and a written handover, so the site is not tied to me.

Where to start

A site starts as its own project, scoped in the call.

  • A fixed-price project

    Fixed scope · fixed price. One site, designed and built in Hebrew and English.

What you receive

  • The finished site

    Design, copy, and the code that runs it, live on your own domain.

  • Hebrew and English versions

    Every page in both languages, with a language switch that keeps the visitor on the same page.

  • Ready for search from day one

    Every page goes live with its own title and description, listed in a map of the site.

  • Visitor analytics

    Which pages people read, from the first day the site is live.

  • Handover

    A written guide to how the site is built, so any developer can change it.

How it runs

  1. Scope the site

    Which pages, which languages, which services, and what a visitor should do next.

  2. Structure and copy

    The words come first, in both languages; the design follows them.

  3. Design and build

    The site is built, with its search setup and analytics.

  4. Review and approve

    You read every page in both languages before launch; nothing goes live without your yes.

  5. Launch and hand over

    Your domain, the analytics, and a written handover.

How a site gets made

A simplified flow from a brief to a live site.

Brief to live
  1. Your briefservices · audience · languages
  2. Structure and copy
  3. Design and build
  4. Search setup and analytics
  5. Your approval
  6. Live in both languages

What stays with you

  • The words

    Every page is drafted for you; the final wording is yours.

  • The launch

    Nothing goes live until you have read it in both languages.

  • The site itself

    The domain, the code, and the content are yours; nothing is locked to the studio.

A site built here

The site you are reading, in Hebrew and English, designed and built in the studio.

  • Live

    This website

    The studio's own site, written and built in English and Hebrew side by side.

    • Bilingual website
    • Design system
    • Link preview image

All work

After the project

What the project delivered stays yours. When you want the studio to run your office's recurring work, that is the managed office.

  • What stays. The site, both language versions, and the code that runs it: yours, documented, and live.
  • What the managed office adds. The studio runs the day's recurring work, month to month: the morning briefing, triage, documents, and follow-up.
  • How it starts. A one-time setup, then month to month, scoped in one conversation. Nothing is sent or changed without your approval.

See the managed office

See what your site could say.

Ask for the scoping call and bring the site you have, or the one you don't. You get a written read of what it should say and how it should start.