# ScopeGen AI

> ScopeGen AI turns a client conversation into a structured, estimated work breakdown. It is why we can price a scope before it is built.

Source: https://www.koombea.com/products/scopegen-ai/

---

ScopeGen AI converts a discovery conversation into a structured work breakdown with story point estimates against every item.


## Scope your project in about 15 minutes

Tell ScopeGen AI what you want to build. It asks the questions a scoping session would ask, then drafts your Project Brief and requirements. No call required to start, and you can close the tab and come back.

Start it here: https://www.koombea.com/products/scopegen-ai/#scopegen


## What the conversation turns into

Thirty-eight seconds, no sound. You pick a path, answer the questions, and add the detail; the Project Brief and the requirements come out of that.


## The problem it solves

Fixed-price software quotes are usually one of two things: a guess with a margin bolted on, or six weeks of unpaid discovery disguised as a sales process. Neither is good for the buyer.

The bottleneck is decomposition. Turning "we need a patient portal" into 140 estimable items is slow, and until it is done nobody can price anything honestly. ScopeGen AI compresses that step.

It takes the transcript and artefacts from a discovery conversation and produces a draft Work Breakdown Structure: items, acceptance criteria, dependencies, and a story point estimate on each. Our engineers then review and correct it, which is a far shorter task than authoring it.

- A draft Work Breakdown Structure from a discovery conversation
- Acceptance criteria and dependencies on each item
- Story point estimates our engineers review before anything is quoted
- The same structure becomes the delivery backlog, so nothing is retyped

## How it works

Five steps. The first three happen in the chat above, on your own time. The last two happen with our engineers.

Describe the build: Say what you want to build, in plain language. No template to fill in. (Minutes)
Answer the questions: ScopeGen AI asks about goals, priorities, users, and constraints. The same ground a scoping session covers. (About 15 minutes)
Add the detail: Features, integrations, and anything the build has to talk to. Your Project Brief and requirements are drafted from this. (Same session)
Review it with us: Our engineers walk you through the draft, correct the estimates, and add architecture and delivery sequencing. (One call)
Sign off a committed scope: You approve a Work Breakdown Structure priced in story points. That document becomes the delivery backlog. (Before any code)

What comes out is a document you can circulate. Your team, your board, and whoever has to approve the spend all read the same scope we quoted against.


## What you walk away with

The first two come out of the session itself. The rest are added on the review call, because they are judgments about your build rather than restatements of what you told us.

- **Project Brief**: Goals, context, and what success has to look like.
- **Requirements document**: Prioritized features, user stories, and acceptance criteria. The PRD.
- **Expert review**: Our engineers walk the draft with you and correct it. No estimate reaches you unreviewed.
- **Architecture outline**: System design, integrations, and the dependencies that drive sequencing.
- **Timeline and sequencing**: Phased milestones, and what lands in which two-week cycle.
- **Effort and resourcing**: A story point estimate on every item, role-based time ranges, and the team those imply.

## Why start here

- **No scope ambiguity**: Requirements written down and agreed before anyone commits. Rework is what ambiguity costs, and it is billed later at full rate.
- **Decisions in days**: Planning that conventionally runs to weeks of discovery starts in about fifteen minutes and reaches a reviewed scope in one call.
- **One document everyone reads**: Stakeholders, budget holders and engineers work from the same breakdown, so the argument happens over the scope rather than over whose version is current.
- **Risk found early**: The hard parts surface during decomposition, while moving them is still free, rather than in the sprint that discovers them.

## What it does not do

ScopeGen AI does not send you a quote. It produces effort and resourcing outputs; the dollar figure comes after the review call, from Koombea's pricing model, against the scope the engineers signed off.

An unreviewed AI estimate is exactly the kind of thing that makes fixed-price delivery fail. The tool removes the typing, not the judgment.

What you sign is one committed scope at one price. That is the thing you can hold us to, and it is the reason the review step is not optional.