You're not underperforming.
Your system is.
Fix. Build. Scale.
If the growth you deserve isn't showing up — the answer isn't more effort. It's a better system behind the effort.
The Underlying Philosophy
The debate between hunting and farming is the wrong question. The strongest organisations build both capabilities — and connect them.
Hunters chase tenders, respond to contractors, and compete commercially. They win quarters. But hunters without farmers create volatility — every quarter starts from zero, margin is squeezed, and nothing compounds.
Farmers build architect relationships, earn technical trust, and get products specified at design stage — long before the tender is issued. But farmers without hunters create unrealised potential. Specifications without conversion are lost effort.
Neither creates growth alone. Growth happens when both work as one system — where early positioning creates value and late conversion realises it.
What Gets Built
Every programme is designed to build all six capabilities. They are not independent modules — a gap in one limits the return on all the others.
Project Lifecycle — Sequential (01 → 04)
Capabilities 01 to 04 follow the project lifecycle in sequence. Strength in each enables the next. A gap in 01 means 02 is applied too late. A gap in 02 means there is nothing for 03 to protect. A gap in 03 means 04 converts from a weaker position.
Your team sees the right projects at the right stage — before the specification window closes. Entering at Stage 01–02 means you influence. Entering at Stage 04+ means you compete on price.
Your team earns the specification by name — through SME-level technical consultation, not product presentation. Architects call your team for technical opinion. They do not call product reps.
Specification survives from architect's drawing to contractor's purchase order — through value engineering, procurement pressure, and substitution attempts across every stakeholder in the project ecosystem.
Three distinct conversion scenarios — specified to order, approved list, and late-entry VE. Each needs a different playbook. Your team negotiates from a position, not from fear of losing the deal.
Growth Engine — Parallel & Continuous (05 + 06)
Capabilities 05 and 06 run continuously — not as project lifecycle steps but as the growth engines that expand the pool of projects and relationships that 01 to 04 execute against.
New markets, new categories, new institutional relationships — developed with the same structured discipline as existing pipeline. SME-led BD generates inbound interest. Product-led BD generates polite rejections. The difference is what you offer in the first conversation.
Institutional accounts that compound — where each completed project accelerates the next, where the architect recommends your team to peer firms, and where competitive displacement becomes structurally difficult. Managed accounts, not maintained ones.
Follow the project from first intelligence to confirmed order. Weakness in one stage limits every stage that follows. This is where individual projects are won or lost.
Run continuously as growth engines — expanding the pipeline that the lifecycle capabilities execute against. This is where the organisation compounds rather than just repeating.
A direct, diagnostic conversation about your current project sales reality — where you win, where you lose, and where you are not even in the room when decisions are made.
If there is a clear fit, we outline what a structured engagement would look like. If there is not, we say so directly.
Where are you losing specifications?
At the design stage, through value engineering, or at the contractor's order?Is your pipeline an engine or a list?
Are you identifying projects at Stage 01–02 or reacting to tenders at Stage 04?Does your team present or position?
Are they showing product decks or earning authority as technical subject matter experts?Are your accounts managed or maintained?
Are you building institutional relationships that compound, or just chasing the next quote?A co-pilot engagement — one full day every week, embedded into your pipeline reviews, your stakeholder strategy, your commercial decisions, and your leadership rhythm.
Applied to live projects. Real accounts. Actual pipeline. Not consulting from the outside. Building from the inside — alongside your team, on your projects, in your market.
The partnership is structured around three progressive phases — Fix, Build, and Scale. Every organisation moves through all three. The pace and depth of each phase is determined by where the organisation currently sits — not by a programme schedule.
The partnership begins here — regardless of where the organisation is. Before anything is built, the full reality of the project sales system is mapped across all six capabilities. Not by Pragmatic Step. By the leadership team itself.
The Fix phase is a structured, facilitated experience in which the team maps their own position, names their own gaps, and agrees their own direction. The output is not a consultant's assessment. It is the team's shared understanding of where they are — and what they need to build first.
The Fix phase is complete when the leadership team has a clear, honest, agreed picture of their current position — and a shared conviction about what to change. That conviction is the foundation everything else is built on.
Once the direction is agreed, the system is built — applied directly to live projects, real accounts, and actual pipeline. Not in a classroom. Not on simulations. On the commercial reality the team is working inside right now.
The Build phase moves through four distinct focuses — each constructing a layer of the project growth system, each applied to live pipeline so the system is running before the phase concludes. The depth and sequence of these focuses is shaped by what the Fix phase revealed.
The base layer. Pipeline qualification discipline is established — the team shifts from chasing every enquiry to pursuing the right projects at the right stage. Business development strategy is designed around SME-led engagement, not product promotion.
The influence layer. Technical specifications are moved from 'product data' to 'specification authority'. We build the tools and the conversation frameworks that allow your team to lead the architect or consultant — rather than responding to them.
The alignment layer. Project sales involve multiple stakeholders — architects, consultants, contractors, and owners. We build the system to map these stakeholders and align your value proposition to each persona effectively.
The commercial layer. Three distinct conversion scenarios — specified to order, approved list selection, and late-entry value engineering — each get a structured playbook. Negotiation positioning is built per deal.
The Scale phase is where the system stops being an initiative and becomes the operating model. The Growth Partnership is fully embedded — into the weekly pipeline review, the stakeholder strategy decisions, and the leadership rhythm.
This is the commercially significant phase of the arc. It is where the compounding signals begin to appear — the observable moments that indicate the system has moved beyond installation into self-sustaining growth.
An architect calls your team before writing the specification — not for pricing, but for technical opinion.
A contractor flags a substitution to your rep before accepting it — because they know the conversation needs to happen first.
A key account recommends your organisation to a peer firm — unprompted, without being asked.
The pipeline forecast at the start of the month is within 15% of actual orders. Conversion is structural.
| Rhythm | Purpose |
|---|---|
| Weekly | Live pipeline review — every project, every conversion scenario, every next action. Commitments tracked and opened the following week. |
| As needed | Live deal strategy — specification at risk, negotiation support, value engineering response. Within 48 hours of a flag being raised. |
| Monthly | Leadership review — KPI dashboard, capability progress, strategic decisions, market intelligence. |
| Quarterly | Capability re-assessment — six-capability movement mapped against starting position. Direction confirmed. Next phase priorities agreed. |
One hour. No pitch. No deck. A structured conversation about where your operation currently sits across your project ecosystem — and what a systematic specification growth programme would look like for your product, your team, and your market.