How we work
Our philosophy: deliver fast, iterate often. We don't believe in 6-month projects where you only discover the result at the end. We would rather show you something concrete within the first few weeks.
Discussion & Scoping
1-2 daysWe talk through your project, your goals and your constraints. We ask the right questions to understand the real need.
Rapid prototype
1-2 weeksWe build a first working version of your application. No static mock-ups: real code, a real app you can test.
Iterative development
2-8 weeksWe move forward in short cycles. Every week you see the progress and can adjust. No nasty surprises at the end.
Launch & Support
OngoingDeployment on your domain, training if needed, and post-launch support. Our team remains available for further developments.
"No pointless meetings, no PowerPoint slides, no jargon. We talk about your project, we build, we move forward."
Why a prototype before a full specification?
Most failed web projects have one thing in common: weeks were spent describing on paper a tool nobody had used yet. Once built, it didn't match what actually happens on the ground. We do the opposite: a short specification, then a working prototype that you and your teams test with real data.
Within two weeks, that prototype reveals what a document never shows: the screen nobody uses, the missing feature, the journey that takes too long. Fixing it at this stage costs a few hours; discovering it at delivery costs weeks. It is also what makes it possible to launch an MVP on a controlled budget, then invest at the pace of real usage.
What you see, week after week
During development, you have a test address that is updated continuously. Every week, a fifteen to thirty minute catch-up (video call or email) covers what has been delivered, what comes next and the decisions to be made. You can reorder priorities at any time: what hasn't been built yet hasn't been billed yet.
One main contact, involved in both design and development, answers your questions and coordinates the team working on your project. No salesperson, no middleman, no ticket sitting in a queue for three days.
After launch
Going live includes the domain name, the HTTPS certificate, backups, registration with Google (Search Console, sitemap) and training for the people who will use the tool or update the site. You receive the source code and all the credentials: the project belongs to you.
After that, two options: one-off developments on quotation, or a monthly support plan (monitoring, security updates, small improvements, SEO follow-up). No fixed-term commitment in either case.
What we expect from you
- 1. A decision-maker available one hour a week for the duration of the project.
- 2. Your existing content (text, logo, photos, business documents) from the scoping stage, even if imperfect.
- 3. Frank feedback on the prototype: it is made to be criticised.
To prepare for the first conversation: Website specifications: how to write them and MVP: launch your web app with a minimal version.