Analyse the ask.
Mandatory requirements, scoring points, risks and open questions are pulled into a working bid record.
BidFoundry
BidFoundry turns supplied bid material and existing human-created content into a controlled workspace, requirements matrix, evidence loop and reviewable proposal pack. It moves the bid forward quickly without removing the human approval gates around claims, commercials, commitments or release.
| Project | BidFoundry |
|---|---|
| Status | In development |
| Visibility | Public summary / private build |
| Boundary | No external release without approval |
| Updated | 27 May 2026 |
Current use
Local bid/proposal build support
Outputs
Markdown, Word, optional PDF
Human gates
Bid owner, solution, commercial, release
Boundary
No submission, pricing or commitments
The job
Bids need controlled momentum, not blank-page heroics.
BidFoundry starts from material that already exists: a brief, ITT, RFP, tender pack, question set or proposal request. The point is to compress the early grind while keeping the approval gates visible.
Build the context.
Customer, opportunity and response context are assembled before drafting gets serious.
Check the evidence.
Approved libraries and capability sources are used to support the response, not make things up.
Create reviewable outputs.
Markdown and Word outputs give the bid owner something structured to amend, approve or stop.
BidFoundry is not autonomous bid submission. It is a controlled way to analyse, evidence, draft, validate and improve bid responses.
The model
The workflow does the prep work. The human signs it off.
The public version only needs to explain the idea. The working system keeps source material, capability checks and approval gates under control.
Bid material becomes a workspace.
Supplied files are registered, extracted and shaped into a controlled working pack before drafting starts.
The response has context.
Needs, scoring, constraints and assumptions sit beside the draft instead of being buried in notes.
Evidence needs a source.
Corporate libraries are searched and capability gaps are flagged before the answer hardens.
The next bid gets better.
Reviewer changes, missing proof and reusable answers feed the improvement mechanism for the next bid.
Operating loops
The system runs three loops, not one linear draft.
BidFoundry moves the response forward while repeatedly checking requirements, evidence and approval readiness. Each loop makes the pack more reviewable without turning the system into autonomous submission.
01
Control loop
The supplied pack is turned into a controlled requirement set before drafting starts.
- Intakesupplied pack
- Analyserisks and asks
- Matrixcontrolled scope
02
Evidence loop
Every useful claim is checked against approved sources so confidence is visible.
- Claimdraft answer
- Sourcelibrary proof
- Gapopen evidence
03
Approval loop
The response can progress only when the right human gate has reviewed the output.
- Draftproposal pack
- Reviewowner checks
- Gaterelease decision
Review feedback returns to the start.
Reviewer changes, missing evidence and reusable answers feed the next intake, so the loop tightens with each bid.
Evidence surface
Editable, auditable output.
BidFoundry should produce response packs that a human can inspect, edit and trace back to supplied material. The public page should show that outputs are controlled and reviewable without exposing private customer, pricing or bid content.
| Area | Current state | Public signal |
|---|---|---|
| Intake | Supplied brief, ITT, RFP, tender pack, question set and existing human-created content | Starts from provided material and approved human source content only |
| Control | Requirements, risks, open questions and evidence gaps visible | Reviewable before drafting hardens |
| Outputs | Markdown and Word as standard proposal outputs | Human-editable pack, not autonomous release |
| Boundary | Submission, pricing and commitments are approval-gated | Fail closed unless a human releases it |
Project state
A working tool before a public product.
BidFoundry is already working as a local tool. It can create a bid workspace, register source material, structure requirements, draft a response, render Word/PDF outputs and produce validation scorecards. Anything customer-facing still needs human approval.
Controlled bid workspace.
The current build can structure bid material, requirements, draft responses, readiness checks and local dashboard views.
Better libraries and proof.
The next stage strengthens extraction, approved content sources, capability evidence, reviewer feedback and output polish.
No automatic external action.
Submission, pricing, commitments, customer messaging and workflow triggers remain human-approved.
Controlled boundary
Drafting support, not autonomous release.
Reviewable output
BidFoundry produces an editable response pack based on supplied material and existing human-created content, with requirements, assumptions, evidence gaps and approval points visible before the answer hardens.
Human release
The system can prepare the work, but pricing, commitments, customer messaging and submission remain controlled decisions for the bid team.
[ Human approved ]
Fast first draft. Human final approval.
BidFoundry is built to move bid work forward quickly while keeping pricing, commitments, submission and release decisions under human control.
Bid owner
Solution owner
Commercial
Legal where needed
Final release