Up and running in 14 days: the agent sets it up, you approve

Why implementation scares people, and why that’s fair

Most business owners aren’t afraid of the software. They’re afraid of the project. A consultant promises a month, then comes discovery, a requirements document, change requests, and hourly invoices. Six months later, your sales reps still message customers from their personal phones, and the sales script still lives in one person’s head.

The numbers back up the fear, though they don’t justify panic. According to Panorama Consulting’s 2026 ERP Report (170 organizations, 2025–2026), the median ERP implementation takes 9 months. More than a quarter of companies go over budget, and almost a quarter miss their deadlines. Large migrations are harder: ASUG (2024) found that moving to SAP S/4HANA takes about a year and a half on average, and Horváth (2025) reports that fewer than 10% of those projects finish on time.

The more important finding is this. Panorama names organizational issues, not technology, as the main reason projects run late: unclear ownership, slow approvals, resistance to change. Configuring software isn’t the real bottleneck. The bottleneck is people’s decisions and the endless prep work: the org chart, the permission matrix, policies, scripts, the knowledge base.

We built implementation around that. An AI agent takes over the setup and the prep work. You keep the part nobody can do for you: approve it and start working.

How the 14 days go

Implementation is a conversation. The agent asks one to three questions at a time, each with suggested answers and its own recommendation. It accepts any file: a spreadsheet of employees, policies, contracts, meeting recordings, voice notes. Everything it learns goes into an implementation file: facts with their source (“who said it, which document”), open questions with an owner and a due date, decisions made, and a readiness map.

Every change comes as a single plan card: what the agent will do, what it affects, and how to undo it. You say yes, it applies the change and checks the result.

The order is flexible. If sales matter most, the agent starts with pipelines and channels. But the org chart and permissions always come first, because everything else depends on them.

What a single step looks like

Say it’s day two and the agent proposes an org chart. You see a card: seven departments, each with a manager and a one-line description, reporting lines, and roles. Below that, what it affects: who gets invited and which permissions each department receives. You reply, “Merge warehouse and logistics into one department.” The agent revises the plan, shows the difference, and you say yes. A minute later the chart is live, and the implementation file records who made the decision and when.

If a week later the merge turns out to be a mistake, you roll it back in one click. The agent shows what will change in tasks, deals, and channels, and suggests who should pick up any loose ends.

Who the 14-day timeline fits

Two weeks is realistic for a company whose sales, services, or trading follow clear rules, and where the owner or an executive can answer questions within a day, not a week. Faster decisions mean faster implementation: the agent doesn’t wait for meetings, but it does wait for your approval.

For a large company or a group of companies, we don’t promise everything in 14 days. In that time, the first setup goes live, for example management, sales, and support. Other departments and legal entities follow in waves using the same playbook. The org chart and permissions are already in place, so each wave goes faster than the last.

What the agent does and what we need from you

The agent handles:

• interviewing you and keeping the implementation file, so nothing gets lost between conversations;
• building the org chart, assigning permissions, and inviting employees;
• setting up pipelines, tasks, document templates, and messaging channels;
• reading your documents and conversations to build the knowledge base and draft scripts;
• checking every change it makes and showing what it affects.

We need from you:

• Executive time. Plan on 4 to 6 hours a week, mostly in the first three days. That means answering questions and approving plans, not sitting in workshops with consultants.
• Documents. An employee list, any policies and procedures you have, contract and proposal templates, a price list, and access to the accounts where your team talks to customers.
• One point person. Someone inside the company who stays in touch with the agent and closes open items. It can be the owner, a COO, or an executive assistant.
• Employee input. Each person answers only their own part: the accountant covers accounting, the sales lead covers the pipeline.

What’s ready after 14 days

Not “everything is implemented,” but a first working setup your team uses every day:

1. An org chart with departments, managers, and descriptions, live in TEAMUS.
2. Access permissions by department across every service, so each person sees exactly what they should.
3. Employees invited and signed in.
4. Sales pipelines with stages and rules in CRMUS.
5. Tasks, stages, and hand-offs between departments in TASKUS, with a clear view of whose turn it is.
6. Customer conversations in one CONNECTUS inbox, with automatic routing.
7. A knowledge base in MEMUS built from your documents and conversations, answering with a link to the source.
8. Draft sales scripts: how a sale goes, common questions, objection handling.
9. Contract and proposal templates in DOCUS.
10. Support and sales AI agents that suggest replies for people to approve.
11. The CHATUS team messenger with a Questions board, where the agent sends anything it couldn’t find in the knowledge base.
12. A readiness map and a list of remaining items with owners and due dates.

What comes next: separate phases

Some things honestly can’t be done in two weeks, and we don’t pretend otherwise:

• Integrations with your bank, phone system, e-invoicing, accounting software, and industry systems. Each one is its own phase with its own timeline.
• Manufacturing in OPTIMUS: routings, cost of goods, inventory. The agent builds a profile of your industry and requests any missing features from DEVUS.
• Accounting migration from your old system, with balances and history.
• Custom work that goes beyond the standard product.

Your first setup is already running, so each next phase builds on a live system instead of replacing it.

Why it’s free

Implementation is free with an annual contract. A consulting partner sells people’s hours, so their implementation costs money, sometimes more than the license itself. With PRANUS, the agent does most of the work, and our cost is a fraction of what this service usually sells for.

Here’s how it works:

• Before you sign, we run a demo on your own tasks. A sales manager opens access after a short call. We build the demo around your company instead of handing an empty sandbox to everyone.
• In the contract, implementation is listed at market price with a 100% discount, so you can see what you’re getting.
• The scope is set upfront: org chart, permissions, the services in your plan, imports from spreadsheets and supported CRMs, the knowledge base, and training. Integrations, custom development, and accounting migration with balances are paid phases.

Cloud prices are on the pricing page. For large companies and installations on your own servers, we quote on request. See cloud, self-hosted, or air-gapped for the options.

Objections we hear, and honest answers

Want to see how this would work for your company? Request a demo. A sales manager will reach out, walk through your use case, and open a demo built around your business.