The number is not a discount
When we say our agentic platform arrives eighty percent pre-built for your cost center domain, people hear "eighty percent done." That is not what it means. It means eighty percent of the work that is the same at every organization has already been solved: intent classification for a helpdesk, escalation logic for a contact center, the orchestration layer that lets an agent call four systems in sequence and recover when the third one times out.
The remaining twenty percent is the part that is unique to you. It is also the part that decides whether the system works.
What the twenty percent contains
Integration surface. Which systems the agent is allowed to read from, which it may write to, and what the authentication path looks like when a request crosses from your ITSM into your HRIS.
Workflow truth. Not the documented process, the actual one. Every operations group has a documented escalation path and a real one, and the gap between them is where automation quietly fails.
Escalation thresholds. The point at which the agent stops and hands to a person. Set it too high and trust collapses on the first bad answer; too low and you have automated nothing.
Content. The knowledge the agent answers from. This is consistently the largest item in the twenty percent, and it is the one clients underestimate most.
Why content dominates month one
A pre-built agent with a broken knowledge base is a confident wrong answer machine. Before the platform is useful, someone has to decide which of your four overlapping password-reset articles is authoritative, retire the other three, and structure the survivor so retrieval can find it.
We budget real time for this in Phase 1 and we do it with your team, not for them, because the person who resolves the conflict between two policy documents has to be the person who owns the policy.
What good looks like at day 30
A named workflow with volume attached to it. A documented map of the systems the agent will touch. An agreed escalation threshold. A cleansed, structured content set for the top request types. And a named owner on your side who will still be there in month four.
If those five things exist at the end of Phase 1, Phase 2 produces a working system. If any of them is missing, month two becomes a second month of Phase 1, which is a fine outcome, as long as everyone knows that is what is happening.
Takeaways
- Eighty percent pre-built means the common problems are solved, not that the engagement is short.
- Content quality is the biggest single variable in the remaining twenty percent.
- Phase 1 succeeds when a named owner, a named workflow, and a cleansed content set all exist.