The whole product, surface by surface
BA SOW Maker is a working system rather than a document generator: a place to hold an engagement, a way to ground what is written in it, and the governance a firm needs around the result.
One pipeline, eight stages, nothing hidden
Each stage produces something you can open: a brief, an indexed source, a run, a version, a file.
- 01RequirementsThe brief, in the project
- 02KnowledgeClient documents, indexed
- 03DiscoveryClassified, questioned, checked
- 04AI analysisGrounded in all of it
- 05DeliverablesThe core eight, in order
- 06ReviewEdited by a person
- 07VersionsNothing overwritten
- 08ExportDOCX, PDF, Markdown
The brief is a record, not an attachment
An engagement starts with its requirements held in the project itself, where they can be edited as understanding improves. Every generation reads them, so improving the brief improves everything derived from it.
- Editable in place
- Rewrite the brief at any point; the next run uses it.
- Fed first
- Requirements are the first thing in a generation's context budget.
- Refused when empty
- A run with no brief is rejected rather than invented from nothing.
The client’s material, indexed against the project
Upload PDFs, Word files, text and markdown. Each is extracted, chunked, embedded and stored with its workspace and project, ready to be retrieved when something is written.
A document that cannot be processed is still stored, with the reason on the row and a notification — degraded, never silently missing.
| Source | Type | Chunks | State |
|---|---|---|---|
| Client brief.docx | DOCX | 38 | Indexed |
| Existing platform audit.pdf | 126 | Indexed | |
| API limits — vendor note.md | Markdown | 12 | Indexed |
| Kick-off transcript.txt | Text | — | Processing |
A production run, configured before it starts
Pick the engagement, the scope — one deliverable or the whole pack — the engine and the focus for the run. The studio states what the run will read and whether anything is missing before you spend a token on it.
- ReadinessSays plainly what is missing: no brief, an unindexed source, an absent dependency.
- Live progressPer-document status as the run walks the dependency graph.
- Cancel and retryStop a run mid-way; retry only the steps that failed.
- Engine choiceSeven providers; model selectable per run and remembered per project.
- Technical Questionsdone
- Product Requirements Documentdone
- Statement of Workdone
- Solution Architecturerunning
- Milestones & Delivery Planqueued
- Effort & Cost Estimatequeued
Three columns: outline, document, context
The document sits between its own outline and the material it was derived from, so checking a claim does not mean leaving the page. Read it as a screen document or as the page it exports to.
Ask the engagement, not the internet
A chat scoped to one project, answering from its requirements, its deliverables and its indexed sources — with citations, so an answer can be checked.
Scoped
Retrieval is bounded by the project and its workspace.
Cited
Answers name the documents they drew on.
Contextual
Separate conversations per topic, each with its own material.
An append-only record of how a document got here
Each version records what produced it — an engine and model, or a person — and what instruction was given. Restoring copies an earlier version forward rather than rewinding, so the record of what happened stays intact.
Any version can be exported on its own, rendered exactly as it was written.
- v4Regeneratedminimax · 10 min ago
- v3Hand-editedyou · 2 h ago
- v2Restored from v1you · 4 h ago
One document format, three renderers
DOCX, PDF and Markdown are produced from the same parsed document and the same workspace format, so a table that fits in Word fits in the PDF, and the preview matches both.
- Page furniture
- Size, margins, fonts, header and footer text, page numbers, watermark.
- Branding
- Header, footer and cover logos, set by the workspace rather than the exporter.
- Pack
- Cover, contents and every generated deliverable in document order.
- History
- Any single version, exported as it stood.
The engagement replaces the current storefront with a headless build. Success is measured against checkout conversion, not delivery dates.
- Lift checkout conversion by 15% within two quarters
- Cut publish time from days to minutes
| Item | Included | Notes |
| Catalogue migration | Yes | 4,200 SKUs |
| Payments | No | Existing gateway retained |
The engagement replaces the current storefront with a headless build. Success is measured against checkout conversion, not delivery dates.
- Lift checkout conversion by 15% within two quarters
- Cut publish time from days to minutes
| Item | Included | Notes |
| Catalogue migration | Yes | 4,200 SKUs |
| Payments | No | Existing gateway retained |
What the work cost, and where it went
Every generation records provider, model, tokens in and out, duration and cost. The same aggregate drives the spend screen, the workspace breakdown and the ceiling, so two numbers on one screen cannot disagree.
Generation is refused once the ceiling is reached.
- Delivery$104.1062%
- Presales$61.2031%
- Internal$17.107%
Organisations, workspaces, and who reaches what
People join an organisation once, by invitation, and are granted the workspaces they work in. Authorisation is membership and role — never who created a row.
Access is membership, never row ownership: a colleague in the same workspace reaches its projects, and a resource in another workspace answers 404 rather than 403 — a 403 would confirm it exists.
The controls a delivery lead is accountable for
Spend, access and history, visible without asking an administrator to run something.
Spend ceilings
A monthly limit per organisation that refuses generation once reached.
Billing
Plan, period and every payment on one page; upgrade, downgrade or renew by card.
Activity
A ledger of who did what, filterable by workspace and action.
Notifications
Runs that finished or failed; sources that could not be processed.
Attention
Deliverables now behind the document they were written from, derived rather than tracked.
See it against your own brief
The product is easiest to judge on an engagement you already understand. Bring one you have written by hand and compare.