First automation live within a month.
AI projects do not need six months. The first useful automation in a small company is usually running within a month of the first call, and the ones that take longer are slowed by access and decisions, not by technology.
Here is the calendar as it actually happens, step by step, with the things that make it slip.
Week 1: quick-check and note
A 30-minute call, in person in the Principality or by video. Within two working days you have the note: the two or three tasks to start with, the hours each takes today, what each would take to build, and a fixed price for the prototype. If your company has several teams, the seven-minute questionnaire goes to the employees the same week and the note draws on their answers.
Weeks 2 and 3: the prototype
Two weeks, on a sample of your real data: last month’s emails, invoices or bookings. At the end you see the automation do the job on your cases, with the log, and you decide on the build with a fixed price in hand. What slips this step: access to the data arriving late. We ask for it on day one.
Weeks 4 to 8: the build, then it runs
Two to six weeks depending on the tools and the controls needed, with the automation running in parallel to the manual process until you are satisfied. Then the monthly run: we watch it, count the hours, and line up the next task. What slips this step: a decision nobody owns. We ask for one person accountable on your side; it is the single best predictor of a project finishing on time.
What we do for it.
Why Monaco projects can go faster
Small teams decide quickly, the decision-maker is usually in the room, and we are twenty minutes away for anything that needs a visit. The things that slow Monaco projects are specific: an IT provider in Nice who holds the passwords, a parent company abroad that must approve, a regulated activity that needs the processing documented. We have met all three and plan for them in the note.
Questions.
Can it go faster than a month?
For a single, simple automation with the data at hand, yes: we have gone from call to production in under three weeks. We do not promise it, because the slow part is usually not ours.
What do you need from us to start?
Thirty minutes of the person who does the task, a sample of the real data, read access to the tools in scope, and one person who can say yes.
How long does a full audit take?
Two to four weeks for a company with several departments, including the seven-minute questionnaire for every employee and the conversations with the people who run the processes.
Does the team need training time?
An hour, usually, because the automation lives in the tools they already use. For a wider rollout we run a half-day session; see the training page.
What happens after the first automation?
The next task from the note, usually a month later, with what the first one taught us. Most clients add one every one to three months.
Related.
How much does an AI project cost in Monaco?
Nobody can quote an AI project from a web page without guessing, and a guess is a lie with a currency sign. Here is what actually drives the price, how we fix it before each step, and what you get for it.
AI audit in Monaco
Before anyone builds anything, you should know which tasks are worth automating, in what order, and what each would give back. That is the audit. It comes in two sizes, and both end with a document you keep.
How we work
Small steps, each one paid back before the next: a free 30-minute quick-check, a two-week prototype on your real data, a build into your tools, then we run it and count the hours. Fixed prices per step, code you own, one person accountable.
Start with a 30-minute call. Keep what it finds.
You tell us where the hours go. We tell you which two or three tasks to automate first, in a short written note. Free, in English or French.