Capture the live opportunity
Bring discovery, buyer requirements, deadlines, commercial limits and named owners into one accepted record.
Loading — one moment.
Skip to contentBuild n BloomApply for Fit Call INPUT EVIDENCE CONTROL OUTPUT BREAK / 01 BREAK / 02 BREAK / 03 BREAK / 04 BREAK / 05 BREAK / 06 01 02 03 04 05 DRIFT / 01 DRIFT / 02 DRIFT / 03 DRIFT / 04 CONTRIBUTOR PARTNER DELIVERY FIRM ACCEPT ACCEPT EXCLUDED NO FEE · 25 MIN CURRENT FIRST-COHORT PRICE · US$3,500 SEPARATELY SCOPED THE NEXT RESPONSIBLE STEP
Menu
Our current offer: AI-assisted client delivery. This page describes pursuit preparation as an adjacent workflow example.
AI proposal automation · service-led installation
Turn approved experience into review-ready pursuit work.
Find the right prior engagement with its context intact. Draft from sources your firm can inspect. Route every claim to the person authorised to decide it — and settle who keeps those claims current afterwards.
Human-reviewed workflowWORKFLOW / CONTROLLEDEvery transition keeps an owner.
- 01CaptureContext + owner
- 02RetrieveApproved sources
- 03PrepareLinked working material
- 04ReviewNamed authority
- 05RecordAccepted handoff
CONTROLLED CENTREAI prepares. A named person decides.
00 / Proposal automation defined
The draft is one step. The controlled workflow is the product.
A one-click proposal generator starts with a prompt and returns text. Proposal automation starts with the live opportunity: it retrieves approved precedent, records what is missing, routes expert review, and preserves the accepted promise for delivery.
Retrieve approved experience
Find the applicable projects, credentials and language — with source, date, owner and approval state still attached.
Route expert review
Send claims, assumptions, scope choices and unsupported gaps to the person authorised to approve or reject them.
Preserve the accepted promise
Write the approved commitments, exclusions and owners into the proposal and the delivery handoff.
01 / The real job
The proposal is the output. The firm's memory is the input.
The work starts before the drafting — and before the deadline. Claims lose their currency in the quiet months, then the opportunity arrives and senior people reconstruct what still holds.
Approvals decay between pursuits
A claim approved last year still reads as approved. The person behind it left, the certification lapsed, the reference withdrew consent—and nothing marked the change, because nothing was watching.
The brief splits on arrival
Calls, emails, requirements and commercial constraints reach different people in different forms. The pursuit begins without one agreed version of the problem.
Precedent depends on memory
Someone remembers a similar project. Someone else has the deck. Nobody can quickly establish which language is current and safe to reuse.
The draft outruns the evidence
Plausible language fills an open question. The source and the uncertainty disappear, so the reviewer has to rediscover both.
Partner review becomes rescue
Senior people repair structure, claims and scope, when their time should go to the client, the argument and the final call.
Delivery loses the context
The proposal is approved, but its assumptions, exclusions and commitments never reach the delivery team in a form they can trace.
02 / Installed workflow
Five controlled stages. One visible evidence trail.
The system prepares and routes work. A named person retains professional and commercial authority at every consequential boundary.
Capture
SYSTEM ROLE
Normalise intake, expose missing information and open the pursuit record.
HUMAN DECISION
Whether to proceed and who owns the next step.
Input: Opportunity context, discovery, deadlines, buyer requirements and named owners.
Retrieve
SYSTEM ROLE
Find relevant material while preserving source, date, owner and approval state.
HUMAN DECISION
Whether the precedent is appropriate for this buyer and context.
Input: Approved proposals, project records, credentials and firm knowledge inside an agreed boundary.
Prepare
SYSTEM ROLE
Prepare source-linked working material and flag unsupported gaps.
HUMAN DECISION
What the firm is prepared to claim, propose and commit to.
Input: Approved material, live opportunity facts and the firm's working structure.
Review
SYSTEM ROLE
Route each decision to a named reviewer and record correction, rejection or approval.
HUMAN DECISION
Final professional and commercial sign-off.
Input: Working material, uncertainties, evidence links, assumptions and exclusions.
Write back
SYSTEM ROLE
Preserve the accepted record in the agreed CRM, knowledge or operating path.
HUMAN DECISION
What becomes reusable precedent and who owns delivery.
Input: Approved commitments, decisions, evidence and next actions.
03 / Between pursuits
The five stages run on a deadline. Decay doesn't.
Claim custody is the work of keeping your firm's reusable claims true between deadlines. A pursuit workflow only touches those claims while someone is under deadline — the worst moment to discover one is no longer current.
Approved once
A finding, benchmark or method is approved for a defined use at a particular point in time.
Then, nothing
Between engagements, sources change, methods are revised and benchmarks are superseded.
The record still says yes
Nothing marks the change, because nothing is watching.
The deadline finds out first
Senior people reconstruct what still holds from memory, drives and past deliverables — under time pressure, at the worst possible moment.
Included in installation
Use-driven repair
Included in every installation. A deliverable cannot be accepted while it rests on a claim nobody has re-checked — so any claim the work touches is repaired as a condition of using it.
Assessed at Blueprint
Scheduled assurance
For firms whose facts change faster than their engagements use them. A recurring review reaches the claims that active work never touches.
Assessed at Blueprint
Carried operation
For firms with no internal owner who has real capacity, fast-changing sources, or a heavy exception load. The custody role is performed rather than handed over.
04 / The working difference
Give each person better work to do.
The value is not more generated text. It is a better starting point for contributors, a better decision surface for reviewers and a cleaner promise for delivery.
Start from the right example
See the applicable project, the approved language and the missing context before assembling the response.
Review the decision—not the archaeology
Inspect sources, uncertainty and proposed changes without reconstructing how the draft came together.
Receive the promise with its limits
Carry the approved assumptions, exclusions, owners and commitments from pursuit into delivery.
Keep what the pursuit taught
Accepted work becomes reusable precedent, so the next opportunity doesn't restart from one person's memory.
05 / Evidence ledger
“Generated” is not an approval state.
A claim is not ready because it reads well. Where it came from, who owns it, when it was last approved, whether it applies here, and what the reviewer decided — all of that stays attached.
Synthetic ledger example
Comparable project experience
Source-linked working language with named-client details withheld until the authorised reviewer approves their use.
Safe stop demonstrated
Unsupported outcome number
No current source exists inside the approved boundary. Preparation stops and routes the gap to the evidence owner.
06 / Acceptance boundary
Define “working” before the system is built.
Acceptance tests attach to the real workflow and the agreed systems. They prove observable behaviour — without pretending we control the market, the client or the final professional decision.
Traceability holds
Representative sources can be retrieved, links and ownership stay visible, and unsupported claims are flagged.
Authority holds
Reviewer decisions are required and recorded. Writeback follows approved fields, permissions and owners.
Outcomes stay honest
No guarantee of win rate, revenue, professional correctness, adoption or third-party uptime.
07 / Market contexts
Specialised first. Adapted only where the work is genuinely similar.
US management and advisory boutiques are where we sell today. Engineering work is explored but not yet proven. Private-capital work is deliberately limited to research preparation. A similar-sounding industry is not a substitute for workflow fit — or for customer proof.
WHERE WE SELL TODAY
US management and advisory
Proposal and pursuit work shaped by discovery, prior engagements, partner review and delivery handoff.
EXPLORED — NOT YET PROVEN
Engineering and environmental
A potential fit where approved project evidence, technical credentials and documented review matter. Domain fit is assessed, not assumed.
LIMITED SCOPE BY DESIGN
Boutique M&A
Research, sourcing and mandate preparation only. Investment, valuation and underwriting decisions remain with authorised professionals.
08 / Commercial path
Buy the decision before you buy the build.
The paid Blueprint can recommend installation, a simpler configuration of a tool you own, ordinary automation, self-implementation, deferral — or no action.
Workflow Fit Call
Application-gated triage of the situation, the consequence, the access, the risk and the probable next step. No confidential material.
System Blueprint
One bounded baseline, workflow map, data and responsibility boundary, economic case, risk review and acceptance design.
Fixed installation
Quoted only where the Blueprint supports a responsible build. Security boundary, dependencies, price and acceptance plan come in their own document.
Is the next important proposal still starting from memory?
Use the Fit Call to test whether the repeated retrieval, preparation and review problem is important enough—and ready enough—for a paid Blueprint.