A typical first system.
A free 30-minute call picks the process with the clearest payback.
Map the process with the people who do it, collect real examples, agree one target. For larger builds this is the AI Blueprint.
Agent, integrations, approval steps and logging, in your accounts.
Last month's messages or documents replayed; edge cases fixed.
Go-live with daily review in the first weeks, then weekly.
Dependencies to start early.
| Dependency | Why it takes time | What to do on day one |
|---|---|---|
| WhatsApp number | Moving a number from the WhatsApp Business app to the Platform, display-name review and Meta business checks. | Decide which number to use and who owns the Meta business account. |
| Microsoft 365 or Google Workspace | Mailbox or calendar access needs an admin to grant consent to specific permissions. | Name the IT admin and book 30 minutes with them. |
| CRM or ERP API | Some plans do not include API access, or need an add-on. | Check your plan, or let us check it in the audit. |
| Knowledge and policies | The agent only answers from approved content; someone has to approve it. | Name one person who signs off answers and tone. |
| Data quality | Duplicates, old prices or missing fields make the agent wrong. | Fix the top problems before the build, not after go-live. |
When it is more than a month.
Builds that touch money or regulated decisions take longer, because approvals and testing take longer. Partner portals with commission engines, or support with KYC follow-up for crypto exchanges, are planned as a first working module within 30 days of the build starting, with the full system on a timeline fixed in the Blueprint.
The same is true when three or more agents share data. That is usually phased: one agent live first, the next ones added under AI Ops.
Not legal advice.
This guide is general information, checked against the sources listed, and not legal advice. Rules change; check the current text or ask a lawyer before you rely on it. Checked November 2026.
Common questions.
Can it be done in a week?
Sometimes, for a simple agent with access ready on day one. The free 7-day pilot puts a starter agent on your website or WhatsApp in that time, but a production system with integrations and approvals usually needs longer.
What happens if it takes longer than 30 days?
For One System and AI Ops builds, if the system is not live within 30 days of the build starting, you get the setup fee back. Delays caused by waiting for access are agreed in writing in the plan.
How much of our time does it take?
A few hours from the process owner in the scoping week, short approvals during the build, and a review slot each week after go-live.
Should we automate several processes at once?
Usually not. One process live and measured teaches you more than three half-finished ones.
Want this in your business?
Tell us how you work today. We'll tell you honestly what AI can take off your team's plate, what it costs, and whether we are the right fit.