Kjak.design — landing pages & workshops for AI startups
Kjak turns complex AI products into landing pages that convert — and teams that agree on what they're building.
◦ Scene II — Two clearings
What we do
For teams whose product is better than their page.
For founders who each describe the product differently.
Wall textMost engagements begin in the second clearing and end in the first — the workshop decides what the page will say, the page proves the workshop was right.
◦ Scene III — The lit path
Process
We read your docs, sit in on sales calls, and interview each founder separately. We're listening for the gap between what you say and what your users actually buy.
OutputWhat we heard — a one-page evidence brief
The workshop. Scattered opinions become one thesis: who the page is for, what it claims, and what proves it. Everyone signs the same sentence before anyone opens Figma.
OutputPositioning statement, message map, page blueprint
Type, layout, and copy built around that thesis. You review real pages, not moodboards — two rounds, decisions made in the file, in daylight.
OutputFinal page design with every state and breakpoint
Production-ready code, handed to your repo with analytics wired in. We set the conversion baseline, watch it for a month, and make one measured iteration.
OutputLive page, baseline report, iteration one
◦ Scene IV — The specimen board
Field notes
Buyers don't pay for the model — they pay for what changes in their day. Name the outcome; let the architecture stay backstage.
Try itDelete "AI-powered" from your hero. If nothing is missing, it was noise.
Before anyone reads a word, the typeface has already said careful or careless. A confident display face buys your claims a hearing.
Try itSet your one true sentence at three times the size you find comfortable.
Every extra call to action splits attention. A page that asks for three things gets none of them. Here, the job is booked demos.
Try itCount the links above the fold. Keep two: the demo and the proof.
Three founders, three products — until the sentence is written down. The workshop's real output isn't a document; it's agreement.
Try itAsk each founder for the product in one sentence. Diff the answers.
Animation should explain — where things came from, what changed, what matters. Decoration fatigues; explanation guides. Every effect ships with a reduced-motion fallback.
Try itRemove any animation that doesn't answer "what just happened?"
Screenshots of interfaces sell software. Output sells intelligence. The instant your product makes something a human couldn't — that's the shot.
Try itPut your product's output above the fold, not its dashboard.
◦ Scene V — Plaques in the grass
Selected work
◦ Scene VI — Constellations
The count
◦ Scene VII — The clearing
One call. We'll tell you honestly whether the page is the problem.