How we work
A clear, low-risk path from idea to working software. You see progress every week or two, decisions are written down, and you own everything at the end.
- Fit conversation (free, ~20 minutes)
We listen to the problem, ask about users, data and deadlines, and tell you honestly whether we are a good match and what the sensible first step is.
- Discovery (paid)
Requirements, a data review, risks, integrations, acceptance criteria and a phased estimate. You can take this document to any developer, and its cost can be credited if we continue.
- Scope and agreement
A written statement of work: what is in the first release, what is not, milestones, payments and who provides what.
- Prototype
The main screens on realistic data, so the important decisions are made on something you can click, not on a description.
- Build in milestones
Working increments every one or two weeks, deployed to a staging address you can try. Tests are written alongside the code.
- Validation
We check the agreed acceptance criteria together, on phone and desktop sizes, with real or realistic data.
- Launch
Deployment to your hosting, monitoring, backups and a rollback path. For public sites, the technical SEO basics are included.
- Handover and care
Code in your repository, documentation and a walkthrough. Optional care plan with a bounded number of hours per month.
Who does what
You: a decision-maker available for short weekly check-ins, access to existing systems and data, feedback on each increment, and content such as texts and product data.
We: design, development, tests, deployment, documentation and clear written updates, including risks and anything that changes the estimate.
AI-assisted development, with guard rails
We use Claude (Anthropic) and Codex (OpenAI) to write and refactor code faster. Every change still goes through our review, runs the tests and follows a written list of project rules the tools must respect, for example which external APIs must never be called. Releases are gated by automated checks and can be rolled back.
Estimates come from the scope, not from a promised speed multiplier. AI tools shorten many tasks; integrations, data quality and decisions still take the time they take.
Commercial terms we usually propose
- Fixed fee, paid upfront, for small diagnostics and discovery.
- Milestone billing for builds, for example 40% at start, 40% at an agreed working milestone and 20% at acceptance.
- Written change requests when new requirements appear.
- Care plans as prepaid monthly hours with stated coverage, not unlimited support.
- Quotes in euro; hosting, AI usage, email volume and licences billed to your accounts.
A sample acceptance checklist
- The catalogue page loads its first products in under one second on a mid-range phone over 4G.
- Every product shown is in stock and was confirmed by a feed in the last three days.
- The assistant never names a product its tools did not return (checked on 40 scripted conversations).
- All pages pass the automated checks: one H1, canonical, language alternates, no broken links.
- A backup is restored on a clean machine and the site runs from it.
Request a scoping conversation
Twenty minutes is usually enough to know the right first step.