FAQ
Partner questions, answered plainly.
Fit, structured partner-branded interviews, project scope, timing, partner validation, data handling, and what happens after the Sprint.
Fit and service
What the Sprint is, who buys it, and when it is useful.
A browser-based calculator for one real client project. It estimates the senior hours, internal cost, unbilled discovery work, annual cost, and delivery risk in your current process, then compares the result with one standard Aimspace Sprint.
No. The result appears immediately in your browser. You can choose to email yourself a copy after you see it.
A fixed-price, fixed-scope requirements discovery and definition service for one implementation initiative or workstream. Aimspace prepares the partner-branded stakeholder surveys, reviews and reconciles the evidence, defines the requirements, completes one partner validation round, and returns the final package under your brand.
It is designed for AI implementation firms, including boutique firms and experienced independent consultants. The strongest fit is a client project that needs a repeatable first requirements baseline, 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.
No. Aimspace completes the discovery and requirements-definition phase and creates the first requirements baseline. You keep architecture, configuration, development, integration, testing, deployment, and support.
Selected direct work remains possible. The standard website offer is designed for implementation partners because the white-label workflow, repeat client projects, and partner ownership create the clearest fit.
White-label relationship
Who owns the client, how the branded interview experience works, and when disclosure may be required.
It describes the operating relationship, not only the logo. You own the client, price, solution, and implementation. The stakeholder experience and final files use your approved brand, while Aimspace completes the agreed discovery and requirements-definition work behind your team.
After the project brief and brand assets are complete, Aimspace prepares private structured online interviews for the agreed stakeholder roles. You send the links through your normal client channel. Stakeholders answer in their browser on their own time, and Aimspace reviews every response and follows up when more detail is needed.
No. Stakeholders use a private browser link. The partner receives status updates and the final requirements package through the agreed delivery channel. There is no client portal or software workspace to roll out.
Partner branding is the default. Aimspace is identified only when a client contract, privacy notice, security rule, data-access requirement, or transparency obligation requires it. White-label delivery does not remove legal data-handling or disclosure duties.
No. You own the client relationship. Invitations normally come from your team, and Aimspace does not market or sell services to your client. Any direct follow-up follows the contact rules agreed in the partner brief.
No. Your team keeps the client relationship, business and solution decisions, project management, implementation, and end-client approval. Aimspace provides one bounded way to create the first requirements baseline.
Process and deliverables
How stakeholder evidence, senior analysis, partner validation, traceability, and the final package work.
Usually no. Each stakeholder completes a structured online interview on their own time. Aimspace reviews the response and sends targeted follow-up only when an important answer is unclear, incomplete, contradictory, or unsupported.
The standard launch service uses structured partner-branded online interviews and human-led follow-up. Aimspace may use AI internally to assist organization and analysis, but a senior analyst remains accountable for the evidence, requirements, conflicts, traceability, and final package.
A Business Requirements Document, Requirements Specification, Requirements Traceability Matrix, Data Dictionary and Glossary, RAID Log and Decision Register, and Validation and Approval Record in practical PDF, XLSX, and CSV formats.
The partner receives structured stakeholder summaries and source-linked evidence by default. Material findings and requirements trace to a stakeholder response, document, or clearly labelled analyst inference. Full raw transcripts are provided only when agreed, appropriate, and permitted by 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.
Aimspace does not obtain formal approval from your end client. Your team receives the draft first and submits one consolidated validation response. Aimspace applies agreed factual and analytical corrections, records open exceptions, and returns the final baseline with an approval record your firm can use with the end client.
The process is informed by established business-analysis tasks and techniques, including planning, stakeholder engagement, elicitation, 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 BABOK Guide for the industry reference.
Scope, timing, data, and continuity
The standard boundaries, purchase path, pricing, security limits, retention, and what happens after the Sprint.
Aimspace normally prepares the intake within one business day after the partner brief is complete, produces the draft within three business days after stakeholder responses and source files are complete, and finalizes the package within two business days after one combined set of partner feedback. Stakeholder response time is separate.
One Sprint covers one defined implementation initiative or workstream, one primary business outcome, one accountable sponsor, one connected stakeholder group, and one requirements baseline. A broad initiative produces a broad baseline. It does not include detailed requirements for every downstream project, department, workflow, or system.
One defined client project, one short partner brief, private partner-branded stakeholder surveys, up to 15 completed stakeholder responses, up to 20 source documents or 500 pages, targeted follow-ups, six connected deliverables, one partner review round, and final files under your brand.
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 stakeholder, document, project, or review limits is quoted separately.
Yes. Use the Start a Sprint page to submit the short project-fit form and continue to the configured secure checkout when the standard scope fits. A free partner call remains available when you want to confirm fit before buying.
Your team receives the partner-validated baseline and takes it through the end-client approval process, solution work, and implementation. Requirements Continuity is available when the active requirements baseline needs controlled maintenance after handoff.
An asynchronous monthly maintenance service after the Sprint. The standard month covers one active baseline, one change intake, up to 10 material change records, one impact assessment, one updated package, one change brief, and one consolidated partner validation round. It does not include recurring meetings, a new stakeholder campaign, or a new implementation workstream.
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 stakeholder responses and uploaded source documents 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.
Still have a question?
Bring one AI implementation project, or start the fixed-scope Sprint online.