Approach
We can't show you the work. So we show you the process.
Everyone claims to be rigorous. Here is exactly what happens between the day you sign and the day you stop needing us — with timelines, deliverables and guarantees.
Values
Six rules we don't negotiate.
- 01
Honesty
We say no to a request that will cost you money without returning any, to a technology we know will give you headaches, and to projects we're not the best people for. A vendor who says yes to everything is a vendor who isn't thinking.
- 02
Clarity
Every decision lands in a shared document you can read at three in the morning, written in plain English with no technical jargon serving as a curtain. Meetings only when there's genuinely something to decide — and with an agenda sent beforehand.
- 03
Transparency
Starting prices are published on this site. The quoted amount is the invoiced amount. Scope changes are presented and approved in writing before work begins, never discovered at the end of the month.
- 04
Independence
Repository in your organization, servers on your account, domains in your name. If you ever want to fire us, you change vendor without asking us for anything and without losing anything.
- 05
Accountability
Performance, security and accessibility aren't extras to be billed separately. A slow site or an app that breaks is work done badly, not an upsell opportunity.
- 06
Simplicity
Every library you add is one more thing that can break in two years. We write what's small, install what's large and well tested, and resist the temptation to complicate things to look sophisticated.
Process
Six phases, from the first email to post-launch.
- 01
Discovery
3 to 5 days
We understand the business before the software: who buys, what stalls the sale, where the team loses time, and what systems already exist. Out of this comes a scope document with what's in and — more importantly — what's out.
- Scope document
- Map of what exists
- Fixed quote
- 02
Structure and content
1 to 2 weeks
Designing the process or the page architecture, the information hierarchy and the real content. We never design over lorem ipsum — the reality of the operation determines the form, not the other way around.
- System map
- Real workflows
- Success criteria
- 03
Design
1 to 3 weeks
Two distinct directions for you to choose from, then one all the way to the end. Real screens, with your data, on phone and desktop. No theatrical presentations.
- Two directions
- Final screens
- Design system
- 04
Build
2 to 8 weeks
A staging environment you can reach from day one, updated with every change. You see progress whenever you want, without waiting for a weekly presentation.
- Staging environment
- Weekly status update
- Your repository
- 05
Go live
2 to 5 days
Data migration, verification, monitoring, backups and a recorded training session for your team. We stay on watch for the first 72 hours.
- Signed checklist
- Recorded training
- Documentation
- 06
Afterwards
ongoing
Either you move to a retainer and stop thinking about it, or we go our separate ways — with everything documented and handed over, leaving you dependent on us for nothing.
- Handover documents
- Performance report
- Retainer proposal
Tools
What we use, and why so little.
A short, boring list is a good sign. It means we chose tools that will still exist in five years, and that somebody else can pick up the work if you ever need them to.
Automation
- n8n
- Node.js
- Python
- Webhooks and queues
AI
- OpenAI
- Anthropic
- Local models
- Vector stores
Frontend
- Next.js
- React
- TypeScript
- Tailwind CSS
Mobile
- React Native
- Expo
Backend and data
- Node.js
- PHP / Laravel
- PostgreSQL
- Prisma
Infrastructure
- Vercel
- Cloudflare
- Docker
- GitHub Actions
Guarantees
The risk is ours, not yours.
No surprises on the invoice
The amount contracted on the retainer is the amount on the invoice, every month. No extras, no overage, and no work reclassified as out of scope.
Problems fixed, full stop
All problem-solving on anything we implemented is included in the retainer. We don't raise a quote to fix what we built — not today and not in two years.
No lock-in
Code, access and domains in your name. Everything we implement ships with documentation and handover documents for whoever takes over the work.
NDA by default
We sign a confidentiality agreement before the first technical meeting, without you having to ask.