The offer
One subscription, three stages
The model is built the opposite way from agencies: every sprint ends in usable production, you stop when you want, and everything is in your name from day one. Your real risk is never more than one month.
- 1 1 to 2 weeks
The mapping
We map today's system: tools, how data moves, re-entry points, manual follow-ups, blind spots in steering.
In practice
The target system diagram and the sprint-by-sprint roadmap, costed. It has value on its own — and it qualifies the project.
- 2 2-week sprints
The construction
Every sprint ends in a real production release — not a demo. One hour of arbitration per sprint: the business facts come from you, the organisation from us.
In practice
Commitment limited to the current month: you can stop after any sprint and keep everything that runs.
- 3 Monthly, cancellable
The run
Daily supervision, fixes when a link between your tools breaks, backups tested by real restores, support within 24 business hours, an allowance for adjustments.
In practice
Cancellable in writing with 30 days' notice: maintenance must be bought because it is worth its price, not because you are stuck.
The comparison is never an agency — it is a hire. An ops manager costs €6–9k a month fully loaded, takes four months to recruit, and leaves with their knowledge. The system costs less, runs within two weeks, and stays. Pricing on quote, after the mapping.
A sprint, concretely
Two weeks. One hour of your time. A real production release.
-
Day 1
One hour of arbitration: you describe the business facts, we propose the organisation, you decide.
-
Days 2 to 12
We build, test on a copy of your system, document.
-
Day 13
Production release. Whatever changes for your team ships with its two-minute video, not a PDF nobody reads.
-
Day 14
You decide: next sprint, pause, or stop. You keep everything that runs.
What you own
We have no way to hold you — which is exactly what makes our clients calm.
- The server, code, accounts and data are in your name from day one — not handed over at the end.
- Documentation and walkthrough videos ship with every sprint, not at the end.
- The system is built with standard technologies: any developer can take it over tomorrow. Any independent technical opinion can verify it.
- Your system runs on your server, in France, for the price of two restaurant meals a month — and that price does not move when you hire or when your volume doubles.
Hire or systemize?
The question every owner who runs the shop by hand asks.
A person organises, they don't build — and the knowledge leaves with them. The system stays, trains the next hires, and costs less. Sometimes the right answer is to hire: we will tell you.
| Hire or systemize? | Hire an ops manager | Build the system |
|---|---|---|
| Monthly cost | €6–9k fully loaded | Less than a hire — and the same at 8 people or 40 |
| First result | 4 months to recruit, then onboarding | In production within 2 weeks |
| What stays if it stops | The knowledge leaves with the person | The system stays, in your name, and trains the next hires |
| What it does | Organises, frames, follows up — by hand | Moves the data, sends the follow-ups, consolidates the numbers — on its own |
| Commitment | Permanent contract, probation, notice | The current month. Stop after any sprint |
| When it is the right answer | When every file needs judgement | When it is the same file, file after file |
The questions we get
In the order they come up in meetings
A monthly subscription — that is a salary.
Exactly — that is the right comparison. An ops manager costs €6–9k a month fully loaded, takes four months to find, and one day leaves with everything they know. Here: no recruiting, first result in production within two weeks, commitment limited to the current month — and the system stays.
We already paid an agency, or a CRM, for nothing.
That is the case for almost all our clients, which is why the model is built the opposite way from agencies: every sprint ends in usable production, you stop when you want, and everything is in your name from day one. Your real risk is never more than one month.
My team won't follow.
They have nothing new to learn: they keep their current tools — the system works underneath. At our training client, the team works in the tools they already knew; what disappeared is the re-entry in between. And when a detail changes in their day, it comes with its two-minute walkthrough video — not a manual.
I don't have time for a project right now.
We do not take your operational time: the organisational work is prepared on our own, and you arbitrate in one hour per sprint. One hour of decisions rather than a half-day workshop.
We were thinking of hiring someone for this.
A person organises, they don't build — and the knowledge leaves with them. The system stays, trains the next hires, and costs less. And if you hire later, that person inherits a clean machine instead of a building site.
What if it breaks?
Anything can break — the difference is that nothing breaks in silence: every task leaves a trace, a failure triggers an immediate alert, and maintenance covers the fix with support within 24 business hours. The danger is never the outage; it is the outage nobody sees.
Why not Zapier or Make? They are cheaper.
For three isolated automations: yes, take Zapier — we will tell you so ourselves. The difference shows when the system becomes vital: those tools bill per execution, so they tax your growth, cap the calls between your tools, and when a scenario breaks nobody knows where or why. Our system costs the same at 8 people or 40, and every action leaves a trace.
What if Zippytal disappears tomorrow?
Everything is already yours: the server, the code, the accounts and the data are in your name from day one — not handed over at the end. Documentation and videos ship every sprint. And the system is built with standard technologies: any developer can take it over, which any independent technical opinion can verify. Ask your CRM vendor the same question.
Next step
One hour of decisions per sprint. Zero operational time taken from your team.
Thirty minutes to describe the life of one file, end to end. If a system is not the right answer, we will say so.