The task somebody redoes by hand every single day.
Re-keying an order into a spreadsheet, chasing unpaid invoices, assembling a weekly report, moving information from one tool to another. We take one process, we measure it, and we make it disappear.
- One process
- 990TND
- or
- 690€ excl. VAT
- Live in
- 2weeks
- Quote within
- 24hours
Nobody is counting the time these tasks take.
In almost every organisation we see, one or two people spend several hours a week on motions that add nothing: copying information from one screen to another, opening twenty emails to extract three figures, rebuilding the same table every Monday, chasing the same customers with the same wording.
That time appears nowhere. It is on no budget, it has no owner, and that is exactly why it lasts for years. Added up, it often comes to the equivalent of a part-time post.
So our first question is not "what can be automated" but "how long does this task actually take, and how many times a month". Without that figure, you end up automating things that were never worth it.
Half the cases need no artificial intelligence at all.
When the rule is clear — if payment has not arrived after thirty days, send this reminder — no AI is needed. A conventional chain does the work, costs less, never gets it wrong, and has no monthly consumption. We say so rather than selling AI because it is the word of the year.
AI becomes useful when something has to read unstructured text: pulling the line items out of an invoice received as a PDF, sorting incoming requests by nature, summarising a twenty-message thread, or spotting orders that fall outside the ordinary.
Most often an effective process combines the two: the AI reads and interprets, the rules decide and execute. And on any decision that commits you — a payment, a message to a customer, a deletion — we always leave a human approval in the loop.
What we automate most often.
The orders of magnitude below are the ones we observe; yours gets measured at scoping.
| Process | What happens | Time returned |
|---|---|---|
| Re-keyed orders | The order from the site lands straight in your back office, with no re-entry | 2 to 5 h a week |
| Chasing unpaid invoices | Overdue detection, graduated reminders, alert above a threshold | 1 to 3 h a week |
| Supplier invoices | PDF read, line items extracted, filed into the accounts | 3 to 8 h a month |
| Weekly report | Sources aggregated and sent automatically on Monday morning | 2 to 4 h a week |
| Incoming requests | Sorted by nature and urgency, routed to the right person | 1 to 2 h a day |
| Public tender monitoring | Watching the portals, filtering, alerting on relevant notices | 3 to 6 h a week |
Per process, and paid back in weeks.
- Tunisia, one process
- from990TND
- France, Europe, international
- from690€ excl. VAT
We bill per process, not as one global package: that is what lets you start small, check that it works, and continue only if the gain is real. The first process is the proof.
The arithmetic is done at scoping, in front of you. A task taking three hours a week is about a hundred and forty hours a year; if automating it costs the equivalent of a few days, it pays for itself in one to two months. If the arithmetic does not work, we say so and we do not build it.
Two weeks per process, and we measure first.
Measurement
We watch the process as it is done today, with the person who does it. How long, how often, which exceptions. An hour of observation is worth more than a scoping meeting.
Days 1 and 2Design
The new flow, written and agreed with you: what triggers it, what is automatic, what stays approved by a human, and what happens when it fails.
Days 3 to 5Build
Development and connection to your tools. It runs alongside the manual process for a few days, so results can be compared with no risk.
Days 6 to 12Switch-over
Into service, with failure alerts and a readable log. One hour of handover with the people concerned.
Days 13 and 14
What people ask before they sign.
Do we have to change our tools?
No, and that is a principle: we plug into what you already use. Changing tool at the same time as automating means running two projects at once and failing at both. If a tool is genuinely blocking — no export, no programmable interface — we say so at scoping, with the least costly option.
What happens if the automation breaks?
That is designed in from the start. A failure raises a named alert, the item concerned is set aside rather than lost, and the log says what happened. The task can always be picked up by hand: we never build a process you would be a prisoner of.
What if our rules change?
The rules live in a configuration file, in plain language, not buried in code. A reminder threshold or a delay can be changed without us. A genuinely new rule needs work, quoted by the hour.
Does our data leave for a third party?
Only if an AI model hosted by a provider is needed, and we tell you explicitly for each step concerned. On sensitive data — client files, accounting documents, public tenders — we prefer a self-hosted model or a solution with no AI at all.
How many processes should we automate?
One, to start, and the one that costs the most time. You will see the result in two weeks and decide what follows on facts rather than on a promise. Ten-process automation plans decided in advance do not survive contact with the ground.
Two ways to start.
You know what you want
Describe what you need in a few lines. You get a priced quote, with the scope and the dates.
Request a quote Answer within 24 business hoursYou would rather talk it through
Message us on WhatsApp or call. Fifteen minutes are usually enough to know whether your need fits the package — and we will tell you plainly either way.
Message us on WhatsApp TN +216 58 044 066 · FR +33 7 69 78 69 98