PRODUCT BUILDER · NARRATIVE ENGINEER
I hold the business model, the story and the code in one head, so nothing is lost in translation between them. What ships is what was promised, and it ships in weeks.
9
products built and running
3,000+
pages indexed across them
#1
worldwide for “narrative engineering”
Weeks
to launch, not quarters
THE PROBLEM
A strategist writes a deck. A copywriter writes words that do not quite match the deck. A designer designs around the words. A developer builds something that fits none of it.
Every hand-off loses a little fidelity, and no single person in that chain is responsible for the total. What arrives is a product where the homepage promises one thing, the interface implies another, and the search results describe a third.
That is not an execution failure. Everyone did their part competently. It is a coherence failure, and adding more specialists makes it worse rather than better.
THE ANSWER
The positioning decision and the technical decision are usually the same decision. What you call the thing determines your information architecture. Who you sell to determines your data model. How you want to be found determines how the pages connect.
When one person makes all of them, they get made together, and they do not end up contradicting each other. That is the entire advantage, and it compounds through everything downstream.
A whole greater than the sum of its parts is not a slogan. It is what you get when the parts were never separated.
WHAT I DO
Not a developer who also writes, and not a strategist who can prototype. Each of these constrains the others, and most of the job is knowing exactly where.
Business model, pricing, positioning, audience. All settled before anything is designed, because everything that comes later is built on top of it.
What the thing is called, what it claims, and the content architecture that makes the claim findable. Story as a system, not decoration.
Full-stack engineering, payments, admin panels, structured data, deployment and monitoring. Production software, not a prototype.
SELECTED WORK
Four written up in full, with the actual problem, the decision that changed the outcome, and the numbers.
HOW TO WORK WITH ME
You can commission the whole arc or a single piece of it. The difference between me and a specialist who does only that piece is that I can see where it breaks against the rest.
Zero to live. Positioning and business model, then narrative and content architecture, then the full-stack build and launch. One accountable person for the entire arc.
Weeks, not quarters
See what that looks like →What the thing is called, what it claims, and who it is for. Settled to the point where you can build from it, because a claim you cannot build from is a claim nobody has tested yet.
One to two weeks, decisions in writing
How I named a category and won it →The system a business actually runs on: customers, orders, permissions, payments and invoicing in one place, shaped around how the business works rather than how an off-the-shelf tool assumes it should.
Fixed project price after scoping
Two price tiers, one catalogue →Built so people can find it, so you can edit it without me, and so the forms on it do not quietly create a legal exposure. Design and engineering in one pair of hands, with no handover losing half the intent.
Two weeks to a month, typically
A full presence, rebuilt →For products that already exist and are invisible. Topical maps, entity graphs, structured data, internal linking, and the automated checks that stop the whole thing decaying six months later.
Measured in enquiries, not traffic
Architecture before the first article →Israel's Privacy Protection Law Amendment 13 requires many organizations to appoint a DPO, including foreign companies handling Israeli residents' data. A GDPR appointment does not satisfy it. I take the role, certified by Bar-Ilan University.
Standalone, or designed into a new build
Amendment 13 service →If you are reading this from outside Israel and the market itself is the problem you are solving, start here instead. Privacy law, Hebrew search and local positioning behave differently here, and they constrain each other.
WHAT CLIENTS SAY
He didn't just build a website. He understood my business and my clients, and built something that actually brings in leads. The speed was unbelievable.
From the first conversation he saw the full picture: the business model, the narrative, the technology. He delivered a product that felt like months of work, in two weeks.
HOW I WORK
01
We talk. I work out what you are actually trying to achieve, who has to believe it, and what success would look like if it arrived.
02
Business model, positioning, naming, content architecture, technical architecture. All settled before a line of code, because they are really one decision wearing different clothes.
03
Full-stack development with modern tooling. Clean code, fast pages, structured data and SEO from the first commit rather than bolted on at the end.
04
Deployment, analytics, payments, email. Then automated monitoring, because a site that was correct on launch day and wrong three months later is not an asset.
LET'S TALK
Whether you are starting from nothing or trying to rescue something that already exists, the first conversation costs nothing and usually clarifies more than it commits to.
I take a limited number at a time, because the whole thing only works if one person has enough room to hold all of it. If you have something you are serious about, let's talk.