Format 01 bis · Fast track
A first AI tool in production in 14 days
We pick one task that costs you time every week. In 14 days, I build the tool that takes it on, and your teams use it on a real workflow, with your own data.
A plan changes nothing until something runs. The sprint skips the long study: one task, one tool, and after two weeks, real use inside your company.
On my side, several tools took only days to build: financial tracking and the appointment-setting agent in one day each, email triage in two, an automated recruitment firm in six. In your company, the 14 days leave time to scope, to test the tool on your data and to train the people who will use it.
| Duration | What you get | Fee |
|---|---|---|
| 14 days | One tool in production, used by your teams on a real workflow | Quoted and fixed before we start |
In production, not in a demo
At the end of the sprint, the tool:
- handles a real workflow in your company, with your data;
- runs on its own, on a schedule or whenever something new comes in: an email, an invoice, a request;
- is checked, and its anomalies are flagged to you;
- sends nothing to a client or supplier without a person's approval, unless you decide otherwise.
How we choose the task
We choose it together in a first working session. A good sprint task:
- comes back every day or every week;
- takes time from a named person, sometimes you;
- relies on data we can reach: an inbox, accounting software, a CRM, a shared file;
- produces a result someone can check;
- allows a before-and-after measurement.
If no task stands out, start with the audit. If the task is too big for 14 days, we split it at scoping, and I tell you before we start what will be live at the end and what comes next.
Two weeks, step by step
Week 1: scope and build
- Scoping: the real workflow, access opened by your team, a baseline (volumes, time spent, errors).
- Build: connection to your data, instructions, checks and approval messages.
Week 2: test and go live
- Parallel run: the tool works on live data alongside your team, so results can be compared.
- Go-live: fixes, launch, handover to the people who use it.
- Day 14 review: what runs, the first measurement, the next improvements.
Examples of first tools
These run today on my own job as CEO. In your company, the task will be chosen around your business.
| First tool | What it does | What runs on my side |
|---|---|---|
| Overdue-invoice reminders | Spots late invoices and drafts the reminder | Drafted from 7 days overdue, approved by me |
| Email triage | Sorts, summarizes and drafts replies | 4 inboxes sorted about 30 seconds after arrival; app built in two days |
| Meeting minutes | Follows the meeting, publishes minutes, creates tasks | Nora runs meetings; a 21-minute meeting costs about $2.45; 31 action items turned into tasks in one pass |
| Appointment setting | Answers requests and offers open slots | Runs every 15 minutes; built in one day, live the next; net effect still being measured |
| Overnight checks | Checks the figures and escalates only anomalies | 4 diagnostics and about 190 checks every night |
What stays with you
- the tool, in production, used by your teams;
- accounts and subscriptions in your company's name, paid by you, with access you control;
- the documentation: what the tool does, what it reads, what it writes, how to stop it;
- the baseline and the first post-launch measurement;
- a list of possible improvements, ranked by priority.
Nothing is resold: you are not renting software, you keep what was built.
A guaranteed, measured return
Before the sprint, we measure the chosen task as it runs today: time spent, delays, errors. After 14 days, we measure again on the same workflow. The gain target is written down before we start; if it is not met, I keep working at no charge until it is.
FAQ
How is this different from the audit?
The audit looks at your whole week and your teams' weeks, then ranks the projects. The sprint goes straight to one project and puts it into production. If you already know which task costs you time, start with the sprint; if not, with the audit.
What do you need from us?
One person who knows the task and can answer my questions during the two weeks, access to the tools involved, opened by your team, and someone to check results during the parallel run. You do not need an in-house technical team.
What happens after day 14?
The tool keeps running in your company. You can stop there, run another sprint, start the 3-month engagement to rebuild a whole function, or have me look after it as your fractional AI director.
30 minutes to see what can run without you
No commitment. You walk me through your week, I tell you what AI can take on, with a first estimate of the gain.
Or email me: thibault@vivasync.io