FAQ
Partner questions, answered plainly.
How Aimspace helps implementation firms establish, assess, and maintain requirements. Understand the evidence, deliverables, scope, pricing, and decisions your team controls.
Fit and service
Choose the right starting point: establish, assess, or maintain requirements.
Choose the starting point that fits your project. Establish a requirements baseline through the Requirements Discovery Sprint. Use Requirements Assessment to review requirements you already have. Use Requirements Continuity to keep an agreed active baseline current as implementation changes. These are separate entry points, not a required sequence.
A US$2,500 fixed review of one identified version of an existing requirements baseline and agreed supporting evidence. Aimspace checks clarity, consistency, coverage, evidence, traceability, priorities, ownership, assumptions, acceptance conditions, and open decisions. You receive one coherent assessment package with findings, evidence-linked gaps and quality issues, traceability and coverage findings, prioritized recommendations, and next actions. One consolidated factual-correction round for the findings is included. We confirm fit for the published scope before work begins.
No. Assessment diagnoses the current requirements and recommends next actions. Its factual-correction round addresses the assessment findings. Correcting every underlying requirement, new full stakeholder discovery, rebuilding the complete package, architecture, implementation, and unlimited reassessment of new versions are outside the standard offer. Assessment is not certification or a guarantee of completeness. It does not automatically repair a baseline or guarantee Continuity eligibility.
A fixed-scope requirements-discovery service for implementation consultancies. Aimspace takes over discovery for one defined implementation project. Use AI discovery interviews, meeting transcripts, project documents, or any combination. Aimspace prepares one traceable requirements model, your team completes one review, and Aimspace applies one revision and returns eight connected deliverables only to your firm, without Aimspace branding by default.
Implementation consultancies, including AI and automation agencies, Microsoft and Power Platform consultancies, CRM and ERP firms, systems integrators, software implementation firms, and process digitization consultancies. Experienced independent consultants can also use it. The strongest fit is an implementation project that needs a reviewed requirements package, a known discovery cost, and a clear handoff into delivery.
Usually the person responsible for delivery capacity, project margin, and whether another business analyst is needed. That is often the founder, owner, Head of Delivery, Managing Partner, Practice Lead, or Delivery Director.
Yes. AI discovery interviews, meeting transcripts, and project documents are independent evidence channels. Any one can be used on its own, or you can combine them. A purchaser interview is optional when it helps establish broad project context. No fixed participant count is required.
Share the project context and sources, choose interview participants, and send the link. Your team then reviews the requirements once and manages client approval.
No. Aimspace establishes requirements baselines, assesses existing requirements, and maintains agreed baselines through Requirements Continuity. You keep architecture, configuration, development, integration, testing, deployment, and support.
Aimspace serves firms that implement technology for clients. Your firm is our customer; your client is not. Your firm owns the client relationship and receives the completed work.
White-label relationship
Who owns the implementation relationship, how branding works, and who manages formal approval.
Your firm sends the neutral AI interview link and handles client follow-up. Aimspace does not independently approach your client or its stakeholders.
Brand-neutral work comes only to your firm, without Aimspace branding by default. You decide how to present it to your client. Required privacy, security, contractual, and AI-transparency disclosures still apply.
When AI interviews are useful, your team shares one neutral AI interview link with as many relevant stakeholders as needed. Participants enter separate private resumable conversations, answer in their own words, receive adaptive follow-ups, and can confirm a recap. Interviews are unlimited for normal discovery within the defined initiative. Meeting transcripts and project documents can be used instead or alongside them.
Stakeholders who use AI interviews enter through the shared discovery link and receive a private resumable conversation. Meeting transcripts and project documents can be supplied without stakeholder interviews. The delivered requirements package is portable: your implementation team does not need an Aimspace portal after handoff.
Yes. Interviews are neutral and identify the AI interviewer. Brand-neutral outputs go only to your firm without Aimspace branding by default. You can add your own brand and client-facing formatting. Required privacy, security, contractual, and AI-transparency disclosures still apply.
Aimspace takes over the agreed requirements work through the chosen service. Your team keeps the customer relationship, business and solution decisions, project management, implementation, and formal approval process. Existing BAs can focus on those responsibilities while Aimspace establishes, assesses, or maintains requirements within the agreed scope.
Process and deliverables
How AI interviews, meeting transcripts, and project documents become one reviewed requirements model and eight connected deliverables.
AI interviews ask follow-up questions and gather project input. Aimspace brings that together with transcripts and documents, then prepares requirements for your team's review.
Aimspace AI interviews are asynchronous private conversations. Your team can still hold meetings and supply their transcripts. AI interviews, meeting transcripts, and project documents may each be used independently or together.
Yes. Keep the meetings you need and use private AI interviews for other input. Aimspace can use interviews, meeting transcripts, project documents, or any mix.
Yes, when you choose the AI interview channel. Each stakeholder has a private natural-language conversation with focused questions, adaptive follow-ups, and a recap they can confirm. The shared interview link supports broad asynchronous discovery. Meeting transcripts and project documents can each be used without interviews. Aimspace remains accountable for analysis, reconciliation, traceability, review, and the final package.
The Discovery Sprint returns eight connected deliverables: Business Requirements Document; Requirements Specification; Requirements Traceability Matrix; Data Dictionary & Glossary; RAID Log & Decision Register; Validation / Review / Approval Status Record; Build Team Backlog; Executive Summary. They are connected views of one reviewed requirements model, delivered for use in your own implementation workflow without an Aimspace portal after handoff. Assessment has its own findings package; Continuity updates the agreed baseline and package.
The partner receives stakeholder summaries, source-linked evidence, and confirmation status where applicable. Material findings and requirements can trace to AI stakeholder conversations, supplied meeting transcripts, project documents, or clearly labelled Aimspace-derived or recommended requirements. Raw evidence is handled according to the engagement and privacy terms.
Yes. Requirements include clear wording, reason, source, owner, priority, dependencies, acceptance criteria, and status so the delivery team can scope and build against the same baseline. The Build Team Backlog uses structured XLSX/CSV fields suitable for mapping/import into Jira, Azure DevOps, or another tracker. Your firm owns technical architecture, engineering decisions, and implementation planning.
Every material requirement is tied to its evidence and clearly labelled by provenance. You can distinguish what came from an AI stakeholder conversation, an uploaded meeting transcript, a project document, an Aimspace synthesis or inference, and a professional recommendation. Conflicts and uncertainty stay visible instead of being silently blended away.
Aimspace keeps different views visible and linked to their sources. Decisions that belong to your team or client stay yours.
Stakeholder-confirmed means an AI interview participant has confirmed their own recap. Transcripts and project documents remain source-linked unless separately verified. Partner-reviewed means your team has completed one structured review for factual corrections, missing context, boundaries, and decisions. Aimspace applies one revision and returns the package. Your firm manages the formal approval process; your client’s authorized approver makes the decision.
The process is informed by established business-analysis tasks and techniques, including planning, stakeholder engagement, interviews, document analysis, requirements analysis, verification, validation, traceability, prioritization, change assessment, and approval readiness. Aimspace is not affiliated with or endorsed by IIBA. See the IIBA business analysis reference for the industry reference.
Scope, timing, data, and continuity
Standard boundaries, purchase paths, pricing, data handling, and the two ways to begin Continuity.
The Sprint has a 1-week target. Time spent gathering project input and waiting for your review affects delivery. See timing details.
One Sprint covers one standard-scope implementation project and one requirements model. Scope is agreed around the project, intended outcome, and relevant evidence. No fixed stakeholder count or evidence channel is required. It does not include detailed requirements for every unrelated downstream project, department, workflow, or system.
One project, requirements analysis, one review from your team, one revision, and eight connected deliverables. Use interviews, transcripts, documents, or any mix. See included allowances and scope.
Unlimited AI interviews and relevant meeting transcripts cover normal discovery for the defined implementation project. They do not include unrelated material, large duplicate datasets, archival ingestion unrelated to active discovery, abusive use, excessive automated bulk processing, general-purpose API use, or workloads materially outside the agreed initiative. Aimspace may pause unusual processing or require expanded scope when use materially exceeds normal discovery. Meeting transcripts do not count against the 1,000-page allowance for other project material.
The Requirements Discovery Sprint costs $7,500 USD for one standard-scope client project. The partner may absorb it, bundle it, pass it through, show it as a paid discovery phase, or mark it up. Work outside the standard project, document, or review limits is quoted separately.
If the delivered requirements package is not usable for your build, notify Aimspace within 30 days of final delivery to receive a full refund of the Discovery Sprint fee.
Yes. You can buy the Sprint without a call when its fixed scope fits. Assessment and Continuity follow their own fit checks.
Your team uses the delivered requirements package in its own workflow for your client approval process, solution work, and implementation. An Aimspace portal is not required after handoff. Requirements Continuity is available when the active requirements model and traceability need to stay current as implementation changes.
Requirements Continuity keeps the active requirements model, traceability, decisions, and package current as implementation changes, for US$1,200/month. The standard month covers one active baseline, 24/7 Requirements AI Partner access, one change intake, one impact assessment, one updated package, one change brief, and one combined Partner Review. AI Partner access means browser-based software access at any time, subject to reasonable use, maintenance, outages, security controls, and technical limits. It does not mean 24/7 human support, unlimited automated/API use, or unlimited compute. New discovery rounds and implementation workstreams are outside the standard month.
Yes, subject to fit review. US$1,200/month includes routine onboarding of a usable external baseline: a supported, reasonably structured baseline, one source-of-record format and version, preserved IDs, an existing supported mapping, and identified ownership and approval status. Your original format need not match Aimspace templates. A clean baseline does not automatically need Assessment or a Sprint. Reconstruction, extensive cleanup or reconciliation, and custom connectors are outside routine onboarding. Check fit before starting the subscription.
Agree the baseline version, requirement IDs, supported files or exports, mappings, and how updates will be exchanged. Portable files do not imply a live integration, universal import, or automatic tracker sync. Proposed, hypothetical, accepted, and superseded changes remain distinct. Your team keeps the approval process, and a task marked Done does not by itself accept the linked requirement. The Requirements AI Partner works from supplied baseline information; it does not know tracker changes that have not been provided or approve changes on your behalf.
The standard service is designed for ordinary confidential business and project information, such as workflows, requirements, business rules, role information, non-sensitive system descriptions, redacted project documents, data definitions, risks, and constraints. Do not submit passwords, access tokens, production credentials, classified information, protected health records, payment-card data, government identifiers, unredacted identity documents, production customer datasets, or other highly sensitive or specially regulated information unless separate controls are agreed in writing.
Unless a different written term applies, Aimspace intends to delete raw AI-interview responses, uploaded meeting transcripts, and uploaded project files 90 days after final delivery and retain final deliverables and change records for up to 12 months. Requirements Continuity or legal obligations may require a different agreed period.
A browser-based planning tool that asks for stakeholder count, project-context volume, and discovery breadth. It estimates senior BA hours, estimated team cost, and an external consulting equivalent, then compares the result with one standard Aimspace Sprint. The default rates and optional workload assumptions can be changed before you calculate.
No. The result appears immediately in your browser. You can choose to email yourself a copy after you see it.
Still have a question?
Ask about your implementation project, or review the fixed Sprint scope before you start.