Frequently asked questions.

  • Citizen Consulting turns messy initiatives into clearly defined outcomes, requirements, and delivery frameworks you can buy as a product.

    Instead of open-ended hourly consulting, you buy fixed-scope consulting packs that produce board-ready documents, models, and plans your PMO, vendors, or internal teams can execute—plus a private AI partner trained on your project.

  • Traditional firms typically sell people and time: teams, workshops, and open-ended phases of work.

    Citizen sells defined outputs:

    • clearly scoped analysis-and-delivery packs,

    • a structured, largely asynchronous online intake, and

    • a fixed set of management-grade deliverables.

    Delivery is driven by a standardized execution model and AI workflows, not by which individual consultant you happen to get. You still get consulting-grade structure and analysis, but at a fraction of the cost and coordination overhead of a full consulting engagement.

  • Citizen is designed for organizations that need serious structure around specific initiatives, without hiring a large consulting team.

    Typical buyers include:

    • Executives and sponsors who need an investment-ready case and clear definition of what they’re funding.

    • PMO leaders and program managers who want consistent artefacts they can plug into existing governance.

    • Business owners and product leaders who need a rigorous requirements and benefits blueprint before engaging vendors.

    • Public-sector and regulated organizations that need traceable, defensible documentation without a year of workshops.

    If you’re accountable for turning strategy into delivered outcomes on a specific initiative, Citizen is built for you.

  • Citizen works well for medium-to-large initiatives where documentation quality matters, such as:

    • New or redesigned services, programs, or products.

    • Technology or platform changes with significant process and stakeholder impact.

    • Multi-stakeholder internal initiatives (operating-model changes, modernisation, compliance or audit programs).

    • Projects that must withstand challenge, audit, or formal approvals.

    The core requirement: you’re willing to provide context and data, and you care that the initiative is properly defined before major spend.

  • The Core Analysis & Delivery Pack is the foundation. It clarifies the problem, defines outcomes, and designs a delivery structure your team can actually run.

    You get an initiative definition + delivery blueprint, typically including:

    • Executive case and context.

    • Outcome and success definition.

    • High-level scope and constraints.

    • Stakeholder and impact view.

    • Requirements and rule library at the right level of detail.

    • Risks, dependencies, and readiness view.

    • A delivery framework: major workstreams, phases, and checkpoints.

    It’s the set of artefacts you use with leadership, PMO, procurement, and vendors so everyone can see the same picture.

  • Add-ons layer extra depth on top of the Core Pack where you need it most:

    • Change & Adoption Pack – stakeholder view, change story, and adoption plan.

    • Value & Benefits Pack – benefits catalogue, measurement model, and tracking view.

    • Risk & Controls Pack – detailed risk register, control framework, and decision gates.

    • Governance & Operations Pack – governance map, operating model view, and run-state handover.

    Each add-on reuses the same intake and core model, then extends your pack with focused artefacts in that area. You only pay for the extra depth you actually need.

  • No.

    Each purchase is scoped and priced as a single, self-contained product. When you buy the Core Analysis & Delivery Pack, it runs end-to-end on its own configuration and intake. Add-ons (Change & Adoption, Value & Benefits, Risk & Controls, Governance & Operations) need to be selected at the same time so the system can build one integrated model and delivery bundle.

    If you decide you need additional depth later, you’d start a new engagement (for example, a new Change & Adoption Pack) using your existing artefacts as inputs, rather than “topping up” the original order.

  • Deliverables vary slightly by pack, but typically include a document bundle plus working assets:

    • Core blueprint document (PDF + editable format)

      • Executive case, context, outcomes, requirements, and risks.

    • Structured registers and matrices (spreadsheet format)

      • Requirements catalogue, traceability views, risks/assumptions, and other supporting tables.

    • Diagrams and models

      • Process maps, outcome maps, and dependency views where helpful.

    • Pack-specific assets

      • For example, change plans, benefit models, control frameworks, or governance maps based on the add-ons you select.

    • Usage notes

      • Short guidance on how to read, maintain, and plug the artefacts into your PMO or vendor processes.

    Everything is designed so executives, PMO, internal teams, and vendors can use the outputs directly—without translation.

  • High-level:

    1. Select a product and initiate the engagement.
      You choose your pack(s), confirm scope and commercial terms, and receive your intake link.

    2. Complete the guided intake.
      A structured online questionnaire (about 60–120 minutes of focused effort) plus document uploads: strategy decks, org charts, process maps, risk logs, business cases, etc.

    3. Analysis and build.
      Your inputs run through Citizen’s execution model and AI-assisted workflows, followed by built-in quality checks.

    4. Delivery and clarification.
      You receive draft deliverables, can flag clarifications or corrections within the agreed scope, and then receive a final pack.

    By default, the process is asynchronous—no recurring workshops are required. For a deeper walkthrough, see the How it Works page.

  • Most clients can complete the intake and uploads with:

    • ~60–120 minutes for the primary sponsor / initiative lead; and

    • some additional time from subject-matter experts to gather existing documentation.

    You may occasionally receive a short follow-up questionnaire if something is ambiguous, but you are not expected to rewrite everything from scratch. Rough material is fine; the system is designed to extract and structure the signal.

  • Timelines are confirmed on the product page and in your engagement confirmation. As a baseline assumption:

    • Core Analysis & Delivery Pack: typically within 1 week of receiving a completed intake.

    • Core + add-ons: typically within 1–2 additional weeks, depending on how many add-ons you select and the complexity of the initiative.

    If demand is high, timelines may be adjusted or new intakes temporarily paused to avoid over-committing.

  • No.

    Templates are part of the delivery, but they’re the last mile, not the product:

    • Your inputs are analysed, structured, and challenged using Citizen’s execution model.

    • The deliverables are assembled to reflect your strategy, constraints, and governance environment.

    • You receive a coherent, initiative-specific package—not a blank framework.

    You can reuse and adapt the templates internally, but what you’re buying is an analysis-grade pack, not a folder of generic forms.

  • Every pack comes with a private AI business partner configured specifically for your initiative.

    • It is powered by your pack’s deliverables and context, not by other clients’ data.

    • It lets your team query the plan in natural language, generate derivative views (briefing notes, checklists, RAID updates), and explore “what-if” scenarios inside the structure of your pack.

    • It is scoped to your initiative; it doesn’t have access to other clients’ projects.

    The AI partner is there so the plan doesn’t freeze in a PDF—it stays interactive and explorable as your initiative moves forward.

    (For more detail, see the Data & Security page.)

  • No.

    Citizen is intentionally designed as a productized, mostly asynchronous service:

    • No recurring workshops or steering-committee meetings.

    • Communication is handled through structured intake, written clarifications (if needed), and document delivery.

  • No.

    Citizen is built to complement internal capacity, not replace it:

    • If you have a PMO or BA/PM function, they get a consistent, high-quality starting point.

    • If you lack capacity, the packs give you structure you can maintain without building an entire function first.

    • Vendors still deliver the work; Citizen gives you the blueprint, requirements, and governance scaffolding they plug into.

    You stay in control of execution; Citizen provides the model and artefacts.

  • Client information is treated as confidential and used only to deliver your packs and AI partner.

    • We support NDAs and data-processing agreements where required by your organisation.

    • Data is transmitted over HTTPS/TLS and stored in encrypted-at-rest systems.

    • Raw inputs are not used to train public, general-purpose AI models.

    • We follow least-privilege access principles and defined retention/deletion windows.

    For full details, see the dedicated Data & Security page, which explains ownership, storage, retention, and third-party services in plain language.

  • Once delivered and paid in full, you have the right to:

    • use, modify, and extend the documents and models; and

    • share them internally or with vendors and partners working on the initiative.

    Citizen retains ownership of the underlying playbooks, templates, models, and internal methods used to produce the work, but the outputs specific to your initiative are yours to use.

  • Because each pack results in customized documents, we don’t offer refunds once work has started.

    If something in the final deliverables is unclear or incomplete relative to the scope described on the product page, we’ll make reasonable revisions so the outputs match the agreed engagement.