Discovery is the phase that decides whether a bid is priced correctly and whether delivery starts on time. For an integrator running it across a portfolio, that is a utilization problem before it is a methodology one.
01
On a $5M to $50M+ IAM program, a competitive pursuit is scoped before anyone has been paid. Solution architects spend weeks building an estimate against requirements that do not exist yet, on a bid the firm may not win. That cost is real, it is absorbed, and it scales with how many pursuits are in flight.
The usual response is to scope more cheaply — fewer interviews, more assumption, a bigger risk premium in the number. That protects pre-sales cost and moves the exposure into delivery, where it surfaces as a change order that the client experiences as your estimate being wrong.
For scale: a twelve-week discovery run by three consultants at a $175 blended rate is roughly 1,440 hours and $252,000 of direct labor. On a competitive bid, a meaningful share of the scoping behind that estimate is unpaid. Structured discovery changes what a pursuit costs to scope. The same questions get asked, of the same stakeholders, without an architect running the calendar — so the estimate rests on captured requirements rather than experience and hedging.
02
Two clocks matter in an alliance-led motion. The first runs from qualification to a proposal the client can act on. The second runs from award to the point where the delivery team has something to configure against.
Discovery sits inside both. Compressing it from roughly twelve weeks to under ten days moves the proposal earlier in the buying cycle and removes the dead period after award when the delivery team is staffed but blocked. On a portfolio of engagements rather than a single deal, that is a utilization question, not a scheduling one.
03
Every integrator produces a requirements deliverable. The difference is whether it survives contact with the client's security review, the auditor, and the delivery team who inherit it.
A generated baseline carries what a hand-assembled document usually loses: which stakeholder answered, when, what they actually said, and where two answers conflicted. In a competitive bid that is a differentiator you can show rather than assert. In a regulated client's security review it is the difference between a document and evidence.
04
Identity CoAnalyst is not an IGA platform. It does not provision, certify, or govern anything, and it does not compete with SailPoint, Saviynt, Okta or CyberArk for the client's platform budget. It produces the requirements those platforms get configured against.
That matters commercially. An integrator's alliances are its route to market, and tooling that threatens a platform relationship is not worth the margin it saves. This sits in the phase before platform selection is final — which is also why it stays platform-agnostic by design rather than by diplomacy.
05
A firm-wide license covers every engagement, with each client's data isolated from the others. There is no per-project purchase to justify and no procurement cycle between qualification and using it on a live pursuit.
The isolation is the part that gets examined. Multi-tenancy here means a client's stakeholders, answers and generated documents are separated at the tenant boundary — which is what a regulated client's security questionnaire is actually asking about when it asks how their data is kept apart from your other clients'.
06
It does not reduce license cost, connector development, or the certification effort that continues after go-live. It does not make an access model correct — it makes the decisions behind one explicit and traceable.
And it is a poor fit where discovery is genuinely trivial: a single-application rollout with three stakeholders does not need structure, and the overhead will exceed the saving. The economics work on the engagements where discovery is a phase rather than a meeting.
Most accelerators are downstream: connector libraries, role-mining utilities, deployment templates and workflow packs that speed up configuration once requirements exist. Identity CoAnalyst sits upstream of all of them, on the requirements phase itself. The two are complementary — an accelerator makes the build faster, structured discovery makes the build correct, and a fast build against wrong requirements is the most expensive outcome on the list.
The compressible time is almost never in configuration. It is in the discovery phase — typically eight to twelve weeks of stakeholder scheduling, workshops, follow-up and document assembly before a platform is touched — and in the rework that follows when a stakeholder who was never interviewed surfaces in month four. Structuring discovery addresses both: the phase itself shortens to days, and the change orders that originate in missed requirements largely disappear.
They solve different problems and most programs need both. A platform vendor's accelerator is optimized for its own product and starts once you know what you are building; it will not tell you that Finance and HR define "contractor" differently. Third-party discovery tooling is platform-agnostic by necessity, runs before selection is final, and produces a requirements baseline you can configure any platform against. If the platform is already chosen and the requirements are settled, the accelerator is enough.
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