What happens after you click Contact.
The biggest fear when trusting a small team with your project is silence. Here is, step by step, how a project runs with us — and when you will hear from us.
- 01
First conversation
Manon calls you back and listens. No thirty-minute sales pitch: questions about your business, your customers and what made you get in touch.
- 02
Scoping
Goals, users, features, constraints, budget and timeline. This is the step that prevents nasty surprises: anything not written here becomes a dispute later.
- 03
Proposal
A document describing the scope, the chosen solution, the detailed price and the schedule. You have time to read it and ask questions. No pressure to sign.
- 04
Design
Site structure, user journeys, designs for the key screens. You sign off how it looks and works before a single line of code is written.
- 05
Development
Christopher builds, in batches. At the end of each batch you get a version you can look at. You watch the project grow; you discover nothing at the end.
- 06
Testing & sign-off
Responsive on phone, tablet and desktop, browsers, full journeys, forms, performance. You test on your side too and report anything that feels wrong.
- 07
Launch
Deployment, domain name, mailboxes, final checks, baseline SEO. We stay available in the following days, when the real questions arrive.
- 08
Follow-up
Hands-on training, then maintenance and new features depending on what you chose. The project does not stop on delivery day.
We do not vanish.
You always know who to contact, where your project stands, what is done, what comes next and when your sign-off is expected.
Redesign — Dupont Real Estate
- DesignsDone
- DevelopmentDone
- Online paymentDone
- ResponsiveIn progress
- Browser testingUpcoming
- LaunchUpcoming
How we actually talk to each other.
Regular progress updates
At a frequency agreed during scoping — usually every two weeks. Short, with a demo of what has moved.
One channel
Email or phone, whichever you prefer. No extra tool to learn just to follow your own project.
Direct access to the developer
When the question is technical, you talk to Christopher. Manon stays informed; you repeat nothing.
Written sign-offs
Designs, features, launch: every approval is recorded. That protects you as much as it protects us.
Feedback in one place
You collect your corrections in a single document and we handle them in batches. Far more effective than ten separate emails.
Support after delivery
Hands-on training, documentation, and a period of fixes included after launch.
What if the need changes along the way?
It happens often and it is not a problem. A request outside the agreed scope is quoted separately and you decide: include it now, keep it for later, or drop it. What never happens is discovering it on the final invoice.
Describe it, Manon replies.
Within one working day. Then a free, detailed, line-by-line quote, with no commitment.