How we work
A person on every call. Agents on the build. Checks on every change.
The whole process, in the open: what happens from your brief to your users, who decides, what the AI agents do, and what every change has to pass before it ships.
01The stages
Six stages, from your brief to your users.
01
Brief
One call with the person who will build it: the product, the people it’s for, the date that matters.
02
Launch forecast
Before any design: what will have moved by launch day — technology, user habits, regulation — and what the product does about it.
03
Design
Every screen designed by the founder, on a design system whose tokens are the same in Figma and in code.
04
Build
Agents write the code under the founder’s direction. Every change is logged: what was built and what it touched.
05
Checks
Speed, accessibility and tests run on every change — and on contracts, tests, fuzzing and static analysis. A failed check stops the release.
06
Launch
The release goes out with every gate green — web, mobile or on-chain.
02Who does what
AI does the work. A person makes every call.
No account managers and no hand-offs between departments — the person you brief is the person who builds it.
Founder
Scope, forecast, design and every decision about the product. Reviews each change before it ships.
AI agents
Code, tests, documentation and research — the volume of the work, directed and reviewed.
Checks
Performance, accessibility, tests and contract analysis, on every change, without getting tired.
You
One person to talk to, a preview to click, and a log of what was decided and why.
03Quality gates
What every change has to pass.
The gates run on every change, not once before launch. If one fails, the release waits until it’s fixed.
Performance≥ 90
Lighthouse score on a phone, for every page that ships.
AccessibilityAA
WCAG 2.2 — keyboard, screen readers, contrast, motion.
LCP< 2.5 s
The main content on screen, on a mid-range phone.
Tests100%
Every test passing. One red test and nothing is released.
Smart contractsTested, fuzzed and statically analysed on every change. Before contracts hold real funds on mainnet, we recommend an independent audit — and prepare the code for it.
04The stack
Current tools, chosen to last.
Web, mobile and on-chain — the stack the product is built on, and the one your next team will already know.
- Web products
- Next.js · React · TypeScript · Tailwind CSS
- Sites & launch pages
- Astro — this site is built on it
- Mobile
- React Native · Expo — iOS and Android from one codebase
- Web3 front end
- wagmi · viem · WalletConnect
- Smart contracts
- Solidity · Foundry · OpenZeppelin — Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain
- Back end & data
- Node.js · TypeScript · PostgreSQL
- Quality
- Playwright · Vitest · Lighthouse CI · axe · Slither
- Design
- Figma, with design tokens synced to the code
05Dates & visibility
Dates come with the plan — and you see the work as it’s made.
Every product is different, so we don’t quote a timeline off a web page. After the brief you get the scope, the stages and the dates — before any work starts. From then on:
A preview
The product as it is being built, on a link you can click any day.
The decision log
Who decided what, and when — every call has a name on it.
Check results
Performance, accessibility and tests for each change, not a report at the end.
Next step
Let’s build it.
Tell us what you’re launching and when. You’ll talk to the person who builds it.
Replies within 1 business day