Every pursuit has an owner, a next action and a recorded decision
The capture pipeline turns a saved tender into a company pursuit: a card on a board with a stage, an owner, a dated next action, tasks, comments and a decision log that keeps who decided, why, and on which version of the documents.
In one paragraph
[ SUMMARY ]A spreadsheet can list pursuits. It cannot tell you why a tender was declined six months ago, who was supposed to chase the clarification, or that a hold has reached its review date. The pipeline is built for those.
- 01Board grouped by stage: Reviewing, Preparing, Submitted, Won, Lost, Declined.
- 02Card dialogs with owner, next action and due date, tasks, clarifications, comments with @mentions and activity.
- 03Append-only decisions: pursue, hold or decline, each with author, rationale and the versions used.
- 04A Today view for your own actions and a weekly review for the capture meeting.
- 05A calendar feed so deadlines and next actions appear in Outlook or Google Calendar.
How it works
[ MECHANICS ]A pursuit is created from any opportunity, from the watchlist or the notice itself, and starts in Reviewing. There is one pursuit per opportunity per company. Personal bookmarks stay separate, so saving something for later does not put it on the team board.
Stages and rules
Pursuits move Reviewing → Preparing → Submitted → Won or Lost. From Reviewing or Preparing a pursuit can be Declined. A declined pursuit returns to work only by recording a new decision. Won and Lost are terminal and only a company admin can correct them. Invalid moves are refused with the reason shown on the card.
Hold is a decision, not a stage
A hold needs a review date and a reason. It leaves the stage alone, shows a banner on the pursuit, and resurfaces in Today and the weekly review when the date arrives. Recording any other decision clears it.
Decisions keep their context
Decisions are never overwritten. A new one supersedes the previous one, which stays inspectable with its author, rationale, timestamp, the company-profile version and the document versions in force. If a material amendment lands later, the pursuit gets a recommendation to revisit the decision; the decision itself is not changed. See cited briefs for how amendments are detected.
Today and the weekly review
Today shows your actions with overdue ones flagged, undecided pursuits, holds that are due and deadlines in the next fourteen days. The weekly review groups what the capture meeting has to deal with, lets you record decisions and assign owners inline, and is closed at the end so the meeting itself is on record.
Reviewers and comments
Colleagues can comment with @mentions on a card and mark a pursuit reviewed, so engineers and commercial reviewers take part without a separate process.
Inside a pursuit
[ 06 TABS ]- 01Decision
Overview
Current decision with author, rationale, versions; earlier decisions; outcome; reviewed-by.
- 02Work
Tasks
Owned, dated tasks, including ones flagged for review after an amendment.
- 03Buyer
Clarifications
Questions to the buyer and their answers, tracked per pursuit.
- 04Team
Comments
Discussion with @mentions that notify the colleague named.
- 05Audit
Activity
Every change to stage, owner, decision and task, including writes made over MCP.
Record a decision from an assistant
[ MCP ]One of only two write tools on the [MCP server](/integrations/mcp/). It records a decision a person has made; the assistant must not invent the rationale.
{
"pursuitId": "uuid",
"decision": "hold",
"rationale": "Fits the radio product line; waiting on ISO 27001 renewal.",
"holdUntil": "2026-10-15",
"holdReason": "Waiting on the certificate renewal"
}What it does not do
[ LIMITS ]- +Keep one shared record per pursuit, with history
- +Enforce stage rules and require reasons for holds
- +Feed deadlines and actions into your calendar
- +Expose pursuits and decisions to the API and MCP
- –Sync natively with Salesforce or HubSpot (use the REST API)
- –Let an assistant move stages, send messages or approve evidence
- –Draft the proposal or manage response sections
- –Forecast revenue or win probability
Questions
[ 04 ANSWERS ]01Can we customise the stages?
No. Stages are fixed (Reviewing, Preparing, Submitted, Won, Lost, Declined) so that decisions, reports and the weekly review mean the same thing across teams. Hold is handled as a decision with a review date.
02Does it replace a CRM?
For the capture stage of public defence tenders it can. Teams that keep a CRM use the REST API to push pursuits and matches into it; there is no native CRM app.
03How does the calendar feed work?
Each user can subscribe to a private calendar feed from the Today view. It carries pursuit deadlines and next actions and works with any calendar that accepts .ics subscriptions.
04Can an AI assistant change our pipeline?
Only in two narrow ways over MCP: recording a decision a person has made, and acknowledging a detected amendment. Both are logged in the activity feed as MCP writes. An assistant cannot move stages, assign work or approve evidence.
See which defence opportunities fit your company.
Set up a company profile in minutes and get a ranked, explained shortlist today.