Speed is the obvious pitch, and every accelerator makes it. It is also not the thing that actually costs an identity practice money. These seven are — and none of them are solved by working faster.
01
A firm runs thirty identity engagements a year. Every one of them starts from a blank page — because the last one lives in a consultant's laptop, in a client SharePoint nobody has access to any more, and in a Word document nobody can find.
You have run PAM discovery forty times. You are not forty times better at it. You are exactly as good at it as whichever consultant happens to be staffed on Monday.
A practice does not have a methodology if it has twelve people who each remember a different one.
Every engagement runs on the same library — 500+ questions across 11 domains. Improve a question once and every future client gets the improved version. Question versioning deploys updates to live questionnaires, tracks their impact, and rolls back if needed. The practice compounds instead of resetting.
Felt by: Practice Lead · VP of Delivery · Head of Identity
02
Discovery does not take twelve weeks because of the number of questions. It takes twelve weeks because only two people in the firm can ask them well. Everyone else runs the workshop, writes down what the client said, and misses the follow-up that would have caught the problem.
That senior architect is simultaneously the bottleneck, the single point of failure, and the person you least want transcribing a joiner-mover-leaver workshop instead of designing the solution.
Two people who can run a real discovery, and a pipeline that needs six.
The senior architect designs the questionnaire once — roughly fifteen minutes with AI assistance. An AI that understands the domain then delivers it. Stakeholders click "help with this question" or "apply to my case" and get an expert answer without the architect in the room. The bench delivers senior-quality output.
Felt by: Practice Lead · Resourcing Manager · anyone who has lost a deal to availability
03
Half of discovery happens before the statement of work is signed. That is pre-sales cost, it comes straight out of practice margin, and on competitive bids you absorb it whether you win or lose.
A firm chasing twenty opportunities and closing six is funding fourteen free discoveries a year.
What did last year's scoping cost on the work you did not win?
A scoping pass that consumed two senior weeks becomes a stakeholder link and a generated document. Lower cost of sale on every bid, won or lost — and the bids you lose still leave you with a reusable artefact rather than nothing.
Felt by: the P&L owner
04
Every change order in month four is a question nobody asked in week two. The firm absorbs some of the cost, bills some of it, and pays for all of it in client trust.
The most expensive thing in an identity program is not the license. It is discovering during user acceptance testing that Finance and HR had different definitions of a contractor the entire time.
How many of your change orders were genuine scope changes, and how many were things you found out late?
Cross-stakeholder contradiction detection. Twelve people answer the same question and the platform flags where they disagree. Consensus scoring shows which domains are actually settled; gap analysis assigns risk scores per domain based on response completeness. The disagreement surfaces in week one rather than month four.
Felt by: the Delivery Manager who owns the change-order conversation
05
Clients cannot evaluate your methodology. They can evaluate the document you hand them. Most discovery output is a Word file assembled at eleven at night by whoever was available — and it reads like it.
The requirements document is the only thing the client actually keeps.
The output template is designed before a single answer arrives: answer placeholders, conditional sections, loops per role or application. When stakeholders finish, the document generates itself — with version history and Word or PDF export. Every answer traces back to who gave it. The same standard every time, on your template.
Felt by: the Partner · the Practice Lead
06
A requirements document records what was decided. It rarely records who decided it, or why, or what they were shown at the time.
Every pre-answer carries source attribution — analyst draft versus document extraction. Disagreeing with an analyst recommendation requires written justification. Full conversation history is retrievable through the API. When a regulated client asks "who told you to build it this way," there is an answer with a name and a timestamp.
The requirements trail becomes evidence rather than recollection — which matters most in financial services, healthcare, government, pharmaceutical and insurance engagements, and anywhere the client has an auditor.
Felt by: Compliance · the security reviewer · the partner signing the attestation
07
Identity CoAnalyst is licensed annually and company-wide rather than per engagement. Under a single license a firm stands up a separate company tenant for every client it serves — its own users, questionnaires, templates and data — with complete data isolation between engagements. The bank client and the hospital client never touch. Sub-companies mirror divisional structure.
You are not buying seats. You are buying the platform your practice runs client work on.
An enterprise runs discovery once every few years. A system integrator runs it on every client, every quarter. Per-engagement procurement is the wrong unit for that, which is why the license covers the practice rather than the project. A REST API and a first-party ServiceNow integration mean results flow into whatever delivery ecosystem already exists.
Felt by: Delivery Ops · the security reviewer
Summary
They are not equally true of every firm. The one worth acting on is usually the one that made you wince.
| The problem | What it looks like | Who owns it |
|---|---|---|
| No practice memory | Every engagement restarts from a blank page | Practice Lead |
| The senior bottleneck | Two people can run a real discovery; the pipeline needs six | Resourcing, Delivery VP |
| Unbillable discovery | Pre-sales scoping burned on bids you did not win | P&L owner |
| Late discovery | Change orders that are really questions nobody asked | Delivery Manager |
| Inconsistent deliverables | The document looks like whoever wrote it | Partner, Practice Lead |
| Weak audit trail | No record of who decided a requirement, or why | Compliance |
| Client data separation | Isolation you have to explain in a security review | Delivery Ops, Security |
08
A twelve-week discovery run by three consultants is about 1,440 hours. At a $175 blended rate that is $252,000 of direct labor before anything is configured — and on a fixed-fee engagement, most of it is yours to absorb.
The question is not whether those hours can be cut. It is which hours they are. Stakeholder scheduling, chasing non-responders, transcribing workshops and assembling the document are the bulk of the calendar and almost none of the expertise. Move those and the same engagement bills the same fee against a fraction of the cost — or the same hours go to implementation work you can actually charge for at a higher rate.
That is the whole commercial case. Not "faster", which every accelerator claims. Cheaper to produce, at the same price.
09
A specialist firm rarely loses on capability. It loses on the things scale buys — a bench deep enough to start next week, and a pre-sales function that can absorb the cost of scoping a bid it might not win.
Structured discovery closes both gaps. You can commit to a start date without holding an architect in reserve, and you can put a defensible requirements baseline in front of a prospect during the pursuit rather than promising one after award. Against a global integrator's proposal, a client who can see the actual requirements before signing is a client you are no longer competing for on brand alone.
10
Access is invitation-based and a no-cost pilot is available on an active engagement — not a sandbox, not a demo dataset, your real stakeholders on work you are already being paid for. If it does not shorten that discovery, you have lost nothing but the time it took to load the questionnaire.
Onboarding is handled directly. There is no partner portal to navigate, no tiering to qualify for, and no alliance manager between you and the answer.
Three things, in this order: a way to run discovery that does not depend on which architect is free, a deliverable that looks the same whoever produced it, and an audit trail your regulated clients can be shown in a security review. Platform tooling — SailPoint, Saviynt, CyberArk — solves none of those, because they all sit downstream of the requirements you have not gathered yet.
By moving the parts of discovery that do not require judgment off the senior architect. Stakeholder interviews, chasing non-responders, transcription and document assembly are the bulk of the calendar time and almost none of the expertise. When those are structured and delivered by the platform, the architect reviews and decides instead of collecting — which is the only part that genuinely needs them.
Blended rates for identity discovery commonly fall in the $150–$250 an hour range in the US market, varying by firm size and location — a global integrator sits at the top of that band, a regional specialist nearer the bottom. The rate is rarely the problem. A twelve-week discovery at three consultants is roughly 1,440 hours regardless of the rate, and most of those hours are coordination rather than analysis.
Identity CoAnalyst is generally available and running on live engagements. Access is invitation-based — Bill Leonard handles onboarding personally.
Request a Demo See the platform