The recovery
Method
Building is the easy part. The cost lies in staying: monitoring, fixing, evolving, responding.
The shock. The pulse restarts at 108, then settles. That is what we sell.
- Monitoring
- Fixing
- Evolving
- Responding
The process · 6 steps
Six steps,
from call to care.
At every step, you know where your project stands, what comes next and what is still to be decided. Nothing starts without your agreement.
- 01
You call us.
A first conversation to understand what you want to do, for whom, and under what constraints. We listen to your need before we talk about technology.
30 min free first conversation
- 02
We audit.
A written assessment of your digital assets: availability, security, mobile performance, content, search visibility. It says what should be kept, simplified, digitised or automated. The audit is charged for, and its cost is deducted in full from any project you commit to within 90 days.
3–7 days for a written, prioritised report
- 03
We quote.
Three clear options, never a single quote to take or leave. The option you choose is set out in writing: scope, schedule, responsibilities and acceptance criteria.
3 options never a single quote
- 04
We build.
The first drafts the day after you place your order, then a demonstration every week on a test environment. You see the work move forward, and your feedback goes into the next version.
Day 1 the first drafts
- 05
You approve.
Acceptance: you check that what was agreed is there and works. It comes with security tests, training for your teams and video documentation. Once you have paid in full, the code and the data belong to you.
90 days guarantee after launch
- 06
We stay.
Every delivered project includes 3 months of support (1 month for Essential). After that, you choose your support level, or you take sole responsibility for your system: you only need to confirm it to us in writing.
1–3 months of support included, depending on the plan
Step 04 · Speed
First drafts
the next day.
The day after you place your order, you can already see the first drafts and tell us what works and what does not. After that, frequent deliveries, each followed by your feedback.
- Order dayYou place your order.
- Day 1The first drafts, and your first feedback.
- Every weekA demonstration on the test environment, and your feedback.
- AcceptanceYou approve what was agreed, before launch.
This speed takes nothing away from our standards. Our procedures are written step by step, and every project we deliver shortens the next one: what shrinks is production time, never the care we take.
Steps 04 and 05 · Your feedback
Seen as it is built,
fixed with you.
You do not discover your project on delivery day: you follow it while it is being built, and you correct course along the way.
A demonstration each week.
The project as it stands, on a test environment: not a presentation, the system itself.
Your feedback, written and dated.
Every piece of feedback is recorded, with its date and what it decides, and the next version answers it. Previous versions are kept: a decision is never lost along the way.
Nothing outside the quote.
Any request made along the way that falls outside the scope is priced and approved by you before we start on it.
An exit point.
At the end of the design phase, once mock-ups and architecture are approved, you can stop and leave with everything that has been produced, without penalty.
Step 06 · After delivery
Delivery
is not the end.
It is where your system's life begins. Support comes in four beats, the ones at the top of this page: monitoring, fixing, evolving, responding.
Monitoring
Your system's availability, your domains and your certificates are monitored, and your data is backed up weekly or daily, depending on your support level.
99.5–99.9% target availability
Fixing
Security updates are applied. A defect within the agreed scope is fixed at no charge during the 90 days after launch.
90 days guarantee on fixes
Evolving
Hours of changes included every month, a strategic review of your system depending on your support level, and enhancements proposed when real needs appear.
1–12 hours of changes included per month
Responding
A blocking outage is acknowledged within a few working hours, or at any hour, 24 hours a day, depending on your support level.
2–8 hours of working time for a blocking outage
Every month, one page.
No technical jargon: figures. The availability of your system, the fixes applied, the interruptions resolved and, if you have any, what your automations and agents have handled. This document is what justifies your subscription, not our word.
And what we learn while supporting your system goes back to the start of the process: a real need, seen in live use, becomes the next enhancement.
Everything starts
with a call.
A first conversation of 30 minutes, free of charge, to understand what you need.