Frequently asked questions

Identity CoAnalyst (ICA) is an AI-powered requirements gathering platform built for IGA (Identity Governance and Administration), IAM (Identity and Access Management), and PAM (Privileged Access Management) projects. It compresses the traditional 8–16 week requirements gathering process to under 10 days by replacing stakeholder interviews and spreadsheets with a structured, AI-guided conversational questionnaire experience. ICA is generally available (GA) and running live on real engagements today.

No. ICA does not compete with IGA platforms. It sits upstream — in the discovery and requirements phase that happens before vendor selection, before implementation scoping, and before any configuration work begins.

If your firm is implementing SailPoint, Saviynt, Omada, or any other IGA tool, ICA accelerates the work that determines what gets built. The implementation platform and ICA serve different purposes at different phases of the project.

ICA uses questionnaires as the mechanism, but it is not a general-purpose survey tool. The difference:

• Survey tools automate distribution. ICA automates expertise.
• Survey tools send a form. ICA sends an AI expert.
• Survey tools produce raw data. ICA produces structured, implementation-ready requirements documentation.

ICA includes 325+ practitioner-written questions, AI that explains terminology and adapts question flow based on actual answer content, and automatic requirements document generation. None of that exists in SurveyMonkey, Typeform, or Google Forms.

Requirements elicitation, also called requirements discovery, is the work of drawing out what a system must do from the people who will own, use, and support it. It goes beyond asking people what they want: it uncovers needs they have not put into words, such as an unwritten approval rule or a compliance obligation only one team knows about. For identity projects, ICA runs elicitation as an AI-guided conversation that probes for detail, explains terminology, and adapts follow-up questions to each answer.

In practice the three terms describe the same activity: getting requirements out of stakeholders and onto paper. Requirements collection and requirements capture put more weight on recording what people say. Requirements gathering is the broader term and usually includes elicitation, analysis, and documentation. ICA covers the full cycle, from the stakeholder conversation to a finished requirements document.

Requirements analysis is the step that turns raw stakeholder input into requirements that are clear, consistent, complete, and buildable. It means resolving conflicts between stakeholders, filling gaps, and removing duplicates. Functional requirements analysis focuses on what the system must do. In an IGA program, that means things like who approves access, how joiners, movers, and leavers are handled, and how often certifications run. ICA supports analysis with cross-stakeholder contradiction detection, consensus scoring per question, and gap analysis.

Business requirements gathering captures what the organization needs to achieve, such as passing an audit, cutting onboarding time, or reducing standing privileged access, before anyone decides how a system will deliver it. It is a core business analysis activity and comes before vendor selection and technical design. ICA is built for this phase of identity projects and is vendor-agnostic, so its output feeds any IGA platform.

A stakeholder needs assessment identifies everyone affected by a project and records what each group needs from it. In identity projects, that includes HR, IT operations, security, compliance, application owners, and business managers. User needs analysis is the same exercise focused on the people who will use the system every day. ICA sends each stakeholder a conversational questionnaire suited to their role, then compares answers across groups to show where needs agree and where they conflict.

Requirements definition is writing each requirement precisely enough that it can be built and tested. Requirements documentation is the deliverable that holds those definitions, along with the context, decisions, and open items the implementation team needs. Producing the document by hand is one of the slowest parts of a traditional engagement. ICA generates the requirements document from stakeholder answers using a reusable template, with export to Word or PDF and version history.

ICA replaces most of the scheduling and note-taking that requirements workshops and discovery workshops require, but not the decisions they exist to make. Stakeholders answer on their own time, and ICA flags conflicting answers before anyone meets. Teams that still hold workshops can use them to resolve the specific conflicts and gaps ICA surfaces instead of starting from a blank whiteboard. Traditional IGA requirements gathering runs 8–16 weeks; ICA's published claim is under 10 days.

Product discovery is a product management practice for deciding whether a product or feature is worth building and what problem it should solve. Requirements discovery assumes the project is going ahead and works out exactly what it must do. Identity programs need the second kind: the decision to modernize governance is usually made, and the open question is what the solution must cover. ICA is built for requirements discovery in IGA, IAM, and PAM projects.

With AI generation: approximately 15 minutes. Describe your goal in plain language — "I need a SailPoint role mining questionnaire" — and the AI generates a complete questionnaire including questions, branching logic, and a report template. You then refine it in the visual editor.

From scratch with the visual editor: longer, but still significantly faster than building a requirements document manually.

They ask the AI. Every question in the conversational interface has three help options:

• "Help with this question" — the AI explains the question in context, relevant to their specific project and environment
• "Rephrase this" — the AI restates the question in simpler terms
• "Apply to my case" — the AI tailors the question to the stakeholder's stated environment

This is why ICA can be completed without a consultant in the room. The AI plays the role of the business analyst explaining context.

Yes. The document upload pre-fill feature lets stakeholders drop in a spreadsheet, PDF, or Word document mid-conversation. The AI extracts answers, maps them to the right questions, and pre-fills the form. Stakeholders review and confirm before submitting.

Yes. The questionnaire designer supports full customization — add questions, remove questions, reorder, modify text, set branching logic. Pre-built questionnaires are starting points, not locked templates.

Administrators can also pre-answer questions with institutional knowledge before stakeholders see the questionnaire. Stakeholders then review and agree or disagree — with disagreement requiring written justification.

ICA detects this automatically. Cross-stakeholder contradiction detection flags conflicting answers, shows consensus scores per question, and surfaces the inconsistency before the requirements document is generated — not after implementation begins.

• Open text (free-form, with AI probing for detail)
• Single and multi-select (dropdowns, radio buttons, checkboxes)
• Dynamic matrix grids (rows generated from prior answers, cell types: text, boolean, dropdown, number)
• Horizontal groups (form-style layouts inline in the conversation)
• Conditional branches (content-aware skip logic)
• Question dependencies (chained question flows)
• Document upload pre-fill

Yes. A full REST API with OpenAPI 3.0 documentation and an interactive Scalar UI. 14+ endpoints covering questionnaire management, stakeholder assignment, response retrieval, and document generation. Bulk export of up to 50 surveys per request. A first-party ServiceNow integration is included.

Yes. ICA uses a multi-tenant architecture with complete data isolation between engagements. Each client lives in its own company tenant — its own users, questionnaires, templates, and data — and one client's data is never visible from another client's tenant. Isolation is enforced server-side from the signed login token, and cross-boundary access is re-checked against the database on every sensitive request.

ICA is sold as an annual, company-wide license, not per engagement. Under one license, a firm stands up a separate, data-isolated company tenant for every client it serves — each with its own users, questionnaires, and data — with no per-engagement procurement. Tenants can be organized into companies and sub-companies to mirror the firm's structure. This is what makes ICA fit the way system integrators and consultancies work: an enterprise runs discovery once every few years, but an SI runs it on every client, every quarter, and one license covers all of it.

Yes, via the Enterprise Private Label deployment model. Under this model, ICA is fully rebranded with your logo, colors, domain, and identity. Clients interact with it as your platform. The multi-tenant architecture ensures data isolation between all client engagements.

ICA is licensed as an annual, company-wide license rather than per engagement. That single license lets a firm run discovery across every client, standing up a separate isolated tenant per client with no additional per-engagement purchase. Final pricing depends on scope — seats, number of client tenants, and how you intend to use it — so the best next step is a short conversation with Bill for a quote that fits your practice.

ICA is generally available. Access is invitation-based — contact Bill Leonard directly and he handles onboarding personally:

William Leonard | Solutions Sales Consultant, CTI Global bill.leonard@cticorp.com | 732-673-4260

No stated limit. Multi-stakeholder deployment across simultaneous engagements is a core feature, not an add-on.

Yes. This is the primary partner model — integrating ICA into your delivery methodology so it becomes a billable accelerator for your practice. Contact Bill Leonard to discuss how this fits your firm's engagement model.

For boutique IAM/IGA specialists, a no-cost pilot on your next active engagement is available. Reach out directly to discuss.

Bill Leonard handles all partner conversations directly:

William Leonard | Solutions Sales Consultant, CTI Global bill.leonard@cticorp.com | 732-673-4260

"If you lead an identity practice at a consulting firm, SI, or boutique IAM shop, I would like 30 minutes to show you how ICA fits your delivery model. Not a demo. A conversation."

ICA is a product of CTI Global. It was built by William Leonard, a Solutions Sales Consultant at CTI Global with 20+ years on the implementation side of enterprise IT at AT&T and IBM.

"ICA was built for the hardest phase of every identity project: the one where you figure out what you actually need before anyone writes a line of code."

No. ICA is vendor-agnostic. The requirements it captures are input into whatever IGA platform the client chooses — SailPoint, Saviynt, Omada, Oracle, or any other. ICA accelerates the phase that precedes vendor selection, not the vendor-specific configuration work.