The two-door apex: one front door for buyers, one for builders

I run Kynth alone. One person, a whole company's worth of production apps, all running on the same engine — Kynth Core. For a long time the apex domain, kynth.studio, was the hardest page I owned. Not technically. It's mostly static. It was hard because I kept writing it for two people at once, and it kept coming out as mush.

This is the note about how I split it.

The two people

The first person has a problem and a credit card. They landed because something was going wrong at work. Unpaid invoices piling up. A chargeback they didn't know how to fight. A phone that rang while nobody was there to answer it. They do not care that I'm one person. They do not care about the engine. They want to know: does this thing do the specific job, what does it cost, and can I see it working before I hand over an email address.

The second person is a builder. They found me through a post, or a repo, or someone else's link. They're curious about the shape of the thing — a solo operator shipping a fleet on shared infrastructure. They want the architecture, the tradeoffs, the parts that broke. They are not going to buy an invoice chaser. If I try to sell them one, I lose them.

Same domain. Opposite wants. Any single page that serves both serves neither. The buyer version reads like marketing to the builder. The builder version reads like an ego trip to the buyer — *why is this person telling me about their monorepo, I just want to send a reminder.*

What one door did to me

The symptom was copy drift. Every rewrite of the homepage pulled in one direction, then overcorrected. One month it was all product: verbs, outcomes, pricing. Then I'd feel like I'd erased the interesting part, so the next pass added a paragraph about the shared engine — and now the buyer's first scroll was about *my* infrastructure instead of *their* problem.

There was a worse symptom underneath. I started writing sentences that were true of nothing in particular. "Software for modern operations." That's what a page sounds like when it's trying not to exclude anybody. It's the average of two good pages, and the average of two good pages is a bad page.

So: two doors.

Door one, buyers

The buyer door is the apex itself and the product pages hanging off it. The rules I hold myself to there:

• Name the job in the first line. Not the category, the job. "Chase unpaid invoices" beats "AR automation."
• Show the app before asking for anything. Every product has a demo you can start without an account. If the demo is broken, the page is broken, and I treat it as a production incident.
• Say the price. On the page. Not "contact us."
• Never mention the engine. The buyer gets the benefit of shared infrastructure — I ship fixes across the fleet in one build — but that's my problem to have, not their reading assignment.

That last one was the discipline that took longest. The engine is the most technically interesting thing I've built. It is also completely irrelevant to somebody with sixty days of overdue receivables.

Door two, builders

The builder door is /writing and /shipped.

/writing is where the architecture lives. How one Vercel project serves every product on a wildcard domain. Why a host proxy routes each subdomain into a tenant subtree instead of each app being its own deploy. What it costs me when a shared primitive changes and every tenant has to keep compiling. The failures too — the deploy that silently no-op'd because I piped it through tail and never saw the error, and left the apex stale for a day.

/shipped is the other half: a running log of customer-facing changes, appended from real commits. It's the least glamorous page I own and probably the most convincing one. A builder skimming it can tell in thirty seconds whether this is a live thing or a portfolio piece. So can a buyer, incidentally — which is the one place the doors overlap on purpose.

What I don't do behind the builder door: sell. No "want this for your company." No consulting pitch at the end of a post. The moment a technical essay has a funnel stapled to it, the reader correctly discounts everything above the fold.

The part that isn't obvious

Two doors is not two brands. Both doors are Kynth. Same face, same palette, same voice. If the writing section looked like a different company, the credibility wouldn't transfer, and transfer is the entire point — the builder who reads about how the fleet is wired should recognize that competence when they land on a product page six months later with an actual problem.

The split is by what the reader came for, not by identity. Buyers get the job. Builders get the machine. Nobody gets a page that's been sanded down to please the other one.

What I'd tell someone else

If you're running something small and your homepage feels vague, check whether you're writing for two audiences in one column. You usually are. The fix isn't better sentences. It's admitting there are two readers and giving each one their own front door — then holding the line on what belongs behind which.

I still get it wrong. Occasionally a paragraph about Kynth Core sneaks onto a product page and I catch it a week later. But the rule is simple enough to enforce alone, which matters, because alone is the staffing situation.

The apex has two doors now. Both of them lead to the same building.