More work from the same team.
The executive who owns the function asked how the team could increase output while improving quality and client experience, without scaling headcount. Twelve weeks later the answer came back sequenced, running as software on the team's own workflows, and in front of the board.
62
Stakeholders, every department in the function
9,918
Findings, every one traceable
119
Proposals, from 2,291 mapped opportunities
9
Working demos built during discovery
Construction and infrastructure · figures as at 9 September 2026, read from the client’s console
The knowledge exists. The business does not hold it.
The team was strong and the experience was deep, but it sat in people and in parallel personal systems rather than with the business. So every response spent its effort reassembling what the last one had already worked out. The constraint was retention, not capacity: adding headcount buys more of the redoing at a higher cost.
The seven themes, and where the heaviest pressure actually sits, are in the full case study.The whole function read, then specified as a system.
Not a sample interviewed and written up, and not screen activity inferred from clicks. Interview agents talked to every role in the function, including the verbal and judgement work no screen ever shows, and every proposal traces back to findings tagged real, assumption or placeholder. Nine of the proposals were built as working software during discovery, on the client's own workflows.
- Opportunity
- Proof
- Costing
- Solution design
- Response ops
- Quality
- Outcome
Seven workstreams, mapped one-for-one to the seven themes, under one orchestrator and one leadership interface.
A modelled 20% to 40% increase in completed proposal capacity, from the same team.
The figure is built from the programme, the programme from the proposals and the proposals from the findings, so a board can pull the headline apart instead of taking it on trust. Not a target and not a promise. A forward model on stated assumptions, handed over with the workings.
The traceability ladder, the nine demos and everything the client held at the end are in the full case study.How the discovery actually ran.
The challenge
A proposal function at scale, winning a minority of the opportunities it pursued and carrying several live opportunities per person. The brief: more output, better quality and a better client experience, without one more person.
The approach
Scout interviewed all 62 stakeholders across every department in the function. Lens read every phase of the response process through twelve swimlanes at once. Arc distilled 9,918 findings into 2,291 opportunities and 119 proposals, sequenced into three waves.
Outcome
The sponsor extended the discovery to further divisions.
Key findings
- Estimates were not benchmarked against final costs — independently confirmed by multiple stakeholders in different roles.
- Post-bid feedback was not systematically tracked, so knowledge was lost between tenders.
- No effort tracking per tender, making return on bid investment impossible to measure.
- Ownership gaps in key process steps, with several stakeholders each deflecting responsibility for the same deliverable.
Read the whole thing.
Twelve weeks, 62 stakeholders, 9,918 findings, the seven themes, the nine demos and what the client owns at the end of it. Send it to me.
Client anonymised at their request. Prepared by 1QLabs. Stakeholder, finding and proposal figures are as at 9 September 2026; discovery goals and documents analysed are as at 27 August 2026. Commercial figures are a forward model on stated assumptions, not a forecast or a promised return.