Make one pursuit worth a decision
Before you commit proposal time, you need a reason to pursue, evidence behind that reason, and a clear handoff to the person responsible for the response.
This is a plan for that evaluation, not a record of one. It uses a fictional opportunity and sample outputs.
This walkthrough sits inside Find → Win.
Choose a relevant opportunity
Evaluate Signals against one approved opportunity. Keep the source, selection criteria, and unresolved questions together.
Make the pursuit call
A capture owner reviews fit and gaps, then records pursue, hold, or pass with a reason.
Review one response step
Evaluate a bounded ProposalOS step against the same source. A proposal owner checks the evidence before accepting the work.
The example: a facilities maintenance pursuit
A fictional solicitation requests a staffing approach, a quality review process, and a mobilization plan. The team has a sample staffing record, but no verified past-performance evidence or named mobilization owner.
Illustrative decision record · SYN-001
Hold for evidence
- Why it may fit
- The synthetic staffing record describes relevant work. That alone does not establish eligibility or delivery capacity.
- What must be resolved
- Verify past performance against the actual requirement; name a mobilization owner; confirm staffing availability.
- Who decides
- The capture owner records the final pursuit decision after the gaps are reviewed. Software output is supporting material.
Carry the evidence into the response
| Requirement | Response preparation | Review gate |
|---|---|---|
| SYN-001 §1: staffing | Map the proposed roles to an approved staffing record. | Verify availability and remove unsupported qualifications. |
| SYN-001 §2: quality | Identify the reviewer, review frequency, and exception process. | Confirm the process exists and its owner accepts it. |
| SYN-001 §3: mobilization | List dependencies and the person responsible for each. | Resolve access and staffing assumptions before committing dates. |
What a useful evaluation should prove
Save and reopen the selected opportunity in Signals. Complete one agreed pursuit step in ProposalOS. Then have the responsible reviewer accept or reject it against the source, with the reason recorded.
The evaluation should also make the handoff visible: what moves between tools, what needs manual work, and which permissions apply. This example assumes no automatic cross-product transfer, completed proposal, award outcome, or reduction in labor.
Download the synthetic source and decision packet · See how to scope the implementation
Start with the problem you need to solve
A free, 25-minute founder conversation helps clarify fit and the next step. A detailed implementation plan belongs in separately scoped work.
AI Integration Assessment: $12,500, fixed scope, 4–6 calendar weeks. Credits in full against an implementation engagement. The conversation is free; it does not purchase the assessment.