The pursuit problem
A single-person software company pursued a requirement beyond its standalone systems, policies, accreditations, financial profile and delivery capacity while competing against substantially larger organisations.
Case study · Software, SaaS and cloud
£1m software-development award for a sole trader
The sole trader secured a £1m, three-year software-development contract as the sole and primary supplier.
- Contract
- Public
- Buyer
- Contracting authority
- Contract value
- £1m
- Result
- Sole-supplier contract secured
- Route
- Three-year single-supplier software procurement
Client confidentiality Client identity and sensitive details are withheld; project facts are generalised only where needed to keep the case useful without identifying protected parties.
What changed
Bid Champions’ team designed and coordinated a capability-matched consortium, brought together partners and candidates, developed compliance files, policies and insurance arrangements, held and negotiated with more than 20 parties, planned delivery and maintenance, and produced a 100-page tender response excluding supporting compliance documents.
The result
Sole-supplier contract secured. Contract value: £1m. The client retained a reusable consortium architecture, role and partner records, compliance pack, insurance position, delivery plan and detailed software tender response.
Work carried out by Bid Champions
The work behind this £1m software, saas and cloud pursuit.
The pursuit moved through five connected stages, with each decision tied to a practical output and the final submission.
Decision to unlock
The response had to prove current partner commitments, solution ownership, financial resilience, insurance, governance authority, delivery capacity and performance after award.
- 01
Capability-gap mapping
Started with what the contract required beyond one person
Broken the requirement into software, policy, accreditation, insurance, financial and delivery capabilities to reveal every gap that the proposition had to close.
Project output A contract capability matrix showing gaps, owners and remedies.
- 02
Consortium architecture
Designed a team around the requirement
Partners and candidates were brought together against the capability map, with the sole trader retained as the primary supplier rather than hidden behind an informal referral network.
Project output A capability-matched consortium and role structure.
- 03
Commitment negotiation
Turned interest into usable tender commitments
More than 20 parties were engaged and negotiated with so roles, availability and contribution could be translated into a credible submission.
Project output Partner commitments, interfaces and responsibility records.
- 04
Compliance construction
Built the missing proof environment
Compliance files, policies and insurance arrangements were developed alongside the bid so the response could evidence readiness instead of promising future completion.
Project output A submission-ready compliance, policy and insurance pack.
- 05
Integrated solution writing
Wrote one delivery and maintenance system
Delivery and maintenance were planned and expressed through a 100-page tender response, excluding the supporting compliance documents, so the consortium read as one accountable supplier.
Project output A 100-page response with an integrated mobilisation and delivery model.
Project control spineCapability gap → partner architecture → negotiated commitment → compliance proof → integrated delivery response
Why it mattered
The core technique was not to disguise the bidder’s size. It was to convert a genuine network of capability into one assessable operating model with clear roles, compliance and delivery ownership.
Inside the buyer decision
Four shifts in the buyer’s risk picture.
Each card follows the same route: the risk, the work completed, the proof created and the effect on the decision.
-
01 Buyer decision
Started with what the contract required beyond one person
- 01 · The risk
- A single-person software company pursued a requirement beyond its standalone systems, policies, accreditations, financial profile and delivery capacity while competing against substantially larger.
- 02 · Work completed
- Broken the requirement into software, policy, accreditation, insurance, financial and delivery capabilities to reveal every gap that the proposition had to close.
- 03 · Proof created
- A contract capability matrix showing gaps, owners and remedies.
- Outcome · Decision effect
- A contract capability matrix showing gaps, owners and remedies gave Contracting authority a concrete basis for judging buyer decision.
-
02 Operating reality
Designed a team around the requirement
- 01 · The risk
- The response had to prove current partner commitments, solution ownership, financial resilience, insurance, governance authority, delivery capacity and performance after award.
- 02 · Work completed
- Partners and candidates were brought together against the capability map, with the sole trader retained as the primary supplier rather than hidden behind an informal referral network.
- 03 · Proof created
- A capability-matched consortium and role structure.
- Outcome · Decision effect
- Contracting authority could test operating reality against a capability-matched consortium and role structure rather than relying on an unsupported claim.
-
03 Commercial pressure
Turned interest into usable tender commitments
- 01 · The risk
- The Contracting authority decision brought software expertise, partner choices, commercial decisions, solution approval, presentation and contractual delivery commitments into one award decision.
- 02 · Work completed
- More than 20 parties were engaged and negotiated with so roles, availability and contribution could be translated into a credible submission.
- 03 · Proof created
- Partner commitments, interfaces and responsibility records.
- Outcome · Decision effect
- Partner commitments, interfaces and responsibility records made commercial pressure visible and reviewable for Contracting authority.
-
04 Stakeholder fit
Built the missing proof environment
- 01 · The risk
- The software, saas and cloud proposition had to hold together from capability gap → partner architecture → negotiated commitment → compliance proof → integrated delivery response.
- 02 · Work completed
- Compliance files, policies and insurance arrangements were developed alongside the bid so the response could evidence readiness instead of promising future completion.
- 03 · Proof created
- A submission-ready compliance, policy and insurance pack.
- Outcome · Decision effect
- The submission connected stakeholder fit to a submission-ready compliance, policy and insurance pack so Contracting authority did not have to infer how it would work.
Professional controls applied to the problem
Professional practice and relevant key drivers.
These examples are tied to the work and outputs above, within the wider assurance approach used across the project.
APMP practices used on this project
These three APMP proposal-management practices shaped the requirement, evidence and release work for £1m software-development award for a sole trader.
- 01
Assembling resources
Partners and candidates were brought together against the capability map, with the sole trader retained as the primary supplier rather than hidden behind an informal referral network. A capability-matched consortium and role structure.
- 02
Proposal management plan
More than 20 parties were engaged and negotiated with so roles, availability and contribution could be translated into a credible submission. Partner commitments, interfaces and responsibility records.
- 03
Colour-team reviews
Broken the requirement into software, policy, accreditation, insurance, financial and delivery capabilities to reveal every gap that the proposition had to close. A contract capability matrix showing gaps, owners and remedies.
Relevant key drivers for this pursuit
These are three relevant examples from the broader project assurance—not the full set of controls applied.
- 01
ISO 9001 · Quality management
For this £1m software, saas and cloud pursuit, a key driver was requirement ownership, evidence traceability, staged review and release control. It governed A submission-ready compliance, policy and insurance pack and directly addressed current partner commitments, solution ownership, financial resilience, insurance, governance authority, delivery capacity and performance after award.
- 02
ISO/IEC 27001 · Information security
For this £1m software, saas and cloud pursuit, a key driver was information ownership, secure handling, access, supplier dependencies and incident response. It governed A contract capability matrix showing gaps, owners and remedies and directly addressed current partner commitments, solution ownership, financial resilience, insurance, governance authority, delivery capacity and performance after award.
- 03
ISO 31000 · Risk management
For this £1m software, saas and cloud pursuit, a key driver was risk identification, owned mitigations, dependencies and decision-stage review. It governed A capability-matched consortium and role structure and directly addressed current partner commitments, solution ownership, financial resilience, insurance, governance authority, delivery capacity and performance after award.
Control sequenceShape → Deliver
This sequence connected the buyer’s concern to owned work, reviewable evidence and the final release decision.
- parties brought together
- 20+
- tender pages stated
- 100
- consortium formation period stated
- 7 days
- contract term
- 3 years
How Bid Champions applies APMP and APM practiceHow standards support the pursuit
Why the bid won
The response made the delivery decision easier.
The core technique was not to disguise the bidder’s size. It was to convert a genuine network of capability into one assessable operating model with clear roles, compliance and delivery ownership.
The approach worked because the consortium structure, explicit roles, completed compliance position and detailed delivery case converted a one-person bidder into a proposition the buyer could assess as credible for a larger contract.
- Result
- Sole-supplier contract secured
- Contract value
- £1m
What remained after submission
Capability the client could use again.
The client retained a reusable consortium architecture, role and partner records, compliance pack, insurance position, delivery plan and detailed software tender response.
Decision room · Software, SaaS and cloud · 3 decisions · About 60 seconds
Take the decisions behind this £1m software, saas and cloud pursuit
Solve three connected pieces of the pursuit. Choose a route, then reveal what happened on this project.
The starting position
A single-person software company pursued a requirement beyond its standalone systems, policies, accreditations, financial profile and delivery capacity while competing against substantially larger organisations.
Decision 1 of 3
Decision 01
The buyer had to resolve capability-gap mapping. What happened first?
What happened on the project Started with what the contract required beyond one person. A contract capability matrix showing gaps, owners and remedies.
Decision 02
With £1m at stake, which move made consortium architecture credible?
What happened on the project Turned interest into usable tender commitments. Partner commitments, interfaces and responsibility records.
Decision 03
What created a defensible release decision for this software, saas and cloud response?
What happened on the project Wrote one delivery and maintenance system. A 100-page response with an integrated mobilisation and delivery model.
What happened
The software, saas and cloud proposition became easier to trust.
The core technique was not to disguise the bidder’s size. It was to convert a genuine network of capability into one assessable operating model with clear roles, compliance and delivery ownership.
Sole-supplier contract secured. Contract value: £1m. The client retained a reusable consortium architecture, role and partner records, compliance pack, insurance position, delivery plan and detailed software tender response.
Result£1m · Sole-supplier contract secured
Facing a similar constraint?
Give Bid Champions the target. Keep the approvals. Hand over the pursuit work.
We can test the buyer route, strengthen the bidder and offer, build the evidence and commercial case, write the response and control it through submission.