How long AI implementation takes.
For the work Ortelian takes on, plan about two weeks for an on-site audit, then build in two-week cycles until the first job meets a written standard. There is no fixed total length. What drives the calendar is how clear the sources and the standard are, and how much of the process has to be redesigned.
This page is an honest range for buyers, not a promise. For the step by step method, see how to deploy AI agents in an enterprise. For how an engagement is structured, see how we work.
The short answer
About two weeks to audit, then two-week build cycles.
Ortelian's cadence is public and fixed in shape, not in end date. The audit takes about two weeks on site, depending on company size and how many people and systems the work touches. Delivery then runs in two-week cycles: scope, build with the team, evaluate on real examples, deploy what meets the standard, review and set the next scope. Cycles continue until the first job passes. After that, the platform keeps running and the next piece of work can start.
A narrow first build can be much shorter when the sources and the standard are already clear. In one public sales example, a ranked account list, a daily refresh and meeting prep shipped about a week after the first call. That week is the first build, not the whole engagement. The write-up is one week at one company.
What the calendar looks like
Three phases, with honest ranges.
- Audit: about two weeks
Time on site with the people who do the work, plus reading the systems and procedures. Output: a map of the work, the constraint, a redesigned process, the first build scope and a benchmark to measure against. The audit is a fixed fee and is credited against the first build if you go ahead.
- First build: one or more two-week cycles
Each cycle has a written scope and a pass bar on real examples. A narrow job with clear sources can land in a single focused week, as in the sales example above. Broader jobs, messy identity across systems or a process that still needs redesign take more cycles. There is no fixed engagement length.
- Run: ongoing
After launch, your team runs it or we keep running it. Either way we host and operate the platform in the EU, evaluations keep running on live work and the world model carries into the next job.
What actually drives duration
Clarity of sources and standard, not model choice.
The calendar stretches or shrinks with the work, not with which language model you prefer. The drivers we see most often:
For the redesign step, see redesign the work before you automate it. For the standard, see agree the standard before you build. For why pilots die without those, see why AI agents fail in production.
- Sources and identity
If the facts the work needs already live in joinable systems, with one customer or order meaning the same thing across them, the first build moves. If the territory lives in spreadsheets, registries and three CRM spellings of the same company, identity work comes first.
- A written standard on real examples
Agreeing what good looks like, including the messy cases, before code starts is what keeps cycles short. Without it, every demo restarts the debate. More in agree the standard before you build.
- How much redesign is needed
An agent on the current process makes waste faster. The first weeks often redesign what belongs to software, agents and people. That time is not optional if you want a lasting result.
- Access and an internal owner
Agreed access to systems, time with the people who do the work and an owner who can decide. Missing any of these pauses the calendar more than any technical choice.
- Scope of the first job
One clear job (daily account list, invoice matching, planning prep) beats a company-wide assistant. Wide scope without a standard is why many pilots never end.
What this is not
Not a six-month transformation programme by default.
Industry surveys keep showing a gap between AI use and business result. In McKinsey's 2025 survey, 88% of companies use AI in at least one function and 39% report any EBIT impact. Long programmes that pick a tool first and define done later are a common way into that gap. Ortelian's answer is the opposite shape: start from one piece of work, audit it on site, agree done on real examples, then build in short cycles.
We are also not a self-service product with a setup wizard. Access to the platform comes with an engagement. There is no public API or public MCP server. Inside an engagement, your own agents can use the platform through scoped tools, and it can plug into tools your team already uses.
Examples of pace
What we can say from public Ortelian writing.
We do not invent case study durations. These are the timings already stated on ortelian.com:
See AI agents for sales and AI agents for operations for the kinds of jobs. See the platform for what agents run on after launch.
- Audit
About two weeks on site (how we work, deploy guide, llms.txt).
- Build cadence
Two-week cycles until the first job meets the agreed standard. No fixed total length.
- Narrow sales first build
About one week from first call to a live ranked list, daily refresh and meeting prep, when sources and standard were clear (one week at one company).
- Functions we write about
Sales and operations role pages describe the jobs we start with. The audit still decides which job comes first for you.
How to shorten the path
What you can do before the audit.
None of this replaces the on-site audit. It makes the audit faster to scope. Start from the AI readiness assessment if you want a checklist, or from what an AI deployment partner does if you want the engagement shape.
- Pick one piece of work
Name the job, the owner and what a correct result looks like on a few real cases, including awkward ones.
- List the systems of truth
Where do the facts actually live today, including spreadsheets and outside sources the CRM never held?
- Name an internal owner
Someone with authority to decide and clear blockers, ideally a founder or leadership sponsor.
- Check readiness early
If you want a structured self-check before a call, use the AI readiness assessment, then talk scope.
Where Ortelian fits
Where this timeline fits, and where it may not.
Ortelian fits mid-market and enterprise knowledge work where the constraint is context no single system holds: sales, operations and similar. We work on site not because our product needs it, but because your company does. After launch, your team runs it or we keep running it. Detail is on how we work.
Where it may not fit: if you need a multi-year transformation across dozens of teams with a global systems integrator, a different shortlist is better. If you only need a chat workspace for every employee, start with ChatGPT Enterprise or Copilot, not with us. If the work is a stable, high volume click path with little judgement, an RPA specialist may be the better first call. If nobody inside can own the work or grant access, fix that before any vendor starts a clock.
Questions
Questions buyers ask about AI implementation time.
How long does AI implementation take with Ortelian?
About two weeks for the on-site audit, then build in two-week cycles until the first job meets the standard agreed on real examples. There is no fixed total length.
Can a first AI agent go live in a week?
Sometimes, when the job is narrow and the sources and standard are already clear. One public sales example shipped a ranked list, daily refresh and meeting prep about a week after the first call. That is the first build, not the full engagement.
Why do AI projects take months or years elsewhere?
Often because done was never written down, the process was automated as it stood, identity across systems was left unsolved or the programme started from a tool instead of one piece of work.
What slows an Ortelian build down?
Unclear sources, no written standard, missing system access, no internal owner and a first scope that tries to take on the whole company at once.
Is the audit included in the timeline?
Yes. The audit is the first about-two-weeks. It is a fixed fee, credited against the first build if you continue.
Who runs the system after the build?
Your team or Ortelian. Either way we host and operate the EU-hosted platform and keep evaluations running.
Bring one piece of work and a rough clock.
On a call, we say whether an audit is worth it, what would drive the duration in your case and where Ortelian fits or does not.
