Voice & messaging
The voice of a senior developer who has actually built with this generation of AI tooling, talking to another senior person wrestling with the same questions. Not anti-AI, not pro-vibe-coding. Somewhere none of the competitors are standing.
Personality
Four traits, one register
The reader should come away thinking: these people get it, and I can talk to them the way I'd talk to a friend who runs an eng team and just survived a year of vibe-coding cleanup.
Proof
The six mechanics
These are the only delivery claims allowed in copy. Specific enough to be checkable, modest enough to be deliverable, identical on every surface. Anything stronger is a promise we can’t keep. Never invent a seventh.
- One flat subscription
- No hourly billing. The model.
- Pause anytime
- 7-day notice. The contract.
- First code in 48h
- First working code. The start.
- Weekly demo
- On a fixed slot. The rhythm.
- Monthly report
- Written. The accountability.
- You own the code
- Yours to keep. The ownership.
The hard-won rules
Say this, not that
Each row is a lesson codified through a cleanup pass. The left column is banned in marketing copy. The right column is concrete, checkable, and on-voice.
One more, always: no em dashes. Use commas, colons, semicolons, periods, or parentheses.
Self-description
How we name ourselves
We sell an outcome, not headcount. The developers and the seniority are how; the software and brand are what. Three names, three jobs.
Nederlands
The Dutch site is not a translation
It is the same position written in Dutch software-company voice: informal throughout (je / jij / jouw, never u), simple spoken words, no English calques. It should sound like qlic.nl or kyano.digital, not like an English deck wearing Dutch suffixes.