Assembly precedes volume.
A 90-day advisory install that industrialises the reusable 70% of every public-sector bid, so senior judgment concentrates on the 30% that wins. Built to raise bid volume without ever dropping below the functionality gate.
Nosto's advantage is structural, not effort-based. Level 1 B-BBEE, 100% Black female-owned, a senior bench with real public-sector pedigree. On almost every public-sector tender, Nosto walks in with a preference-point edge before a line of the proposal is written.
A preference-point edge only pays off across volume. One bid at a time, the edge is invisible. Run it across enough qualified bids and it compounds into a win rate the firm could not reach by quality of writing alone.
So the rational strategy is maximum qualified volume, on one condition: every bid clears the functionality gate. In South African public procurement, functionality is a threshold you pass before price and preference points are even counted. Fail it, and the structural edge never gets scored.
Keep every bid above the functionality threshold by default. The gate is designed for, not discovered at submission.
Lift bid volume without dropping below the gate. The preference edge compounds only across qualified volume.
Volume at a stable win rate, not win-rate improvement on a fixed number of bids. The OS exists to make that lever pullable.
You cannot bid more while every bid is written from scratch by senior people. A public-sector bid is roughly 70% reusable and 30% tender-specific.
Company profile, team CVs, comparable-projects record, methodology frameworks, compliance returnables, pricing logic. Drawn from the library, never re-authored per bid.
The judgment that actually wins. This is where senior time concentrates.
The OS industrialises the 70% so senior judgment concentrates on the 30% that actually wins. Reuse clears the gate. Volume wins the engagement.
Four patterns recur across firms that have the structural edge but never convert it to volume. The OS is designed against each one.
Senior people re-writing the same methodology and CVs each time.
No self-scoring against the evaluation criteria before sending.
No debrief, no scorecard pulled after a result.
Naming inconsistency across profile, bid, and snapshot. Personnel listed in one section who are absent from the presentation team.
The pipeline is gated. Each stage produces the input the next stage needs. You do not assemble before you decode. You do not submit before you self-score. Nothing is skipped.
The standing library every bid draws from. Nosto's equivalent of the Client BOS Portal. Not a per-bid step, the precondition that makes volume possible. It holds the standardised company profile and capability statements, team CVs in one format, a comparable-projects matrix tagged by sector and method, the methodology module library, the compliance and statutory returnables pack, B-BBEE and ownership documentation, and the pricing model template.
A tender is published or spotted via the eTenders portal, departmental sites, SETAs, development-sector bodies, or network referral. The Go / No-Go scorecard runs the volume funnel: mandatory eligibility, sector fit, capacity, win probability, value against effort. The OS lets Nosto look at more tenders and say no faster, so the yeses are the right ones.
Tear the tender apart. Build the compliance matrix: every mandatory returnable, every functionality criterion, the scoring weights, the price-versus-preference split, the submission format and deadline. This is the highest-leverage step and the one most often rushed. A bid that decodes the scoring map wins on points it knew were there.
Decide how this specific bid clears functionality and where it earns points. Map Nosto's proof assets to the evaluation criteria. Set the pricing posture: where to compete on price points, where the preference edge carries the load. Isolate the 30% that is bid-specific.
Draw the 70% from the library. Write the 30% that is specific. Methodology tailored to the terms of reference, team allocated, comparable projects selected for relevance, pricing built. This is where the system carries the load.
Score the bid against the evaluation criteria as the panel would. Compliance-check every returnable. Consistency-check across naming, personnel, and version. Run the functionality-gate self-test: would this clear the threshold as written?
Final compliance pass, format, deadline, channel. Log the bid record.
Win or lose, request the official scorecard and evaluation feedback. The highest-value free move available, and most firms never make it. Diagnose the result. A functionality failure is a proof or methodology problem, fixed in the asset library. A price or preference loss is a pricing-model problem, fixed in the pricing template. Feed both back into Stage 0. Each bid makes the next bid faster and better. This loop is the compounding asset, the equivalent of skills capture in a BOS install.
Time concentrates in the judgment layer. The system carries everything else. The same split as a BOS install, ported to bids.
Triage decisions, win strategy, pricing posture, final technical authority, sign-off. Owned by Tebogo and the senior team, with advisory input from Base X.
The asset library, the compliance matrix template, assembly from boilerplate, the self-scoring rubric, the bid record, and the AI-assisted drafting of the reusable sections.
Clear ownership across the install. The senior team holds judgment, Base X installs the system and runs the discipline, the system does the assembly.
Own judgment-layer decisions, technical authority, client relationships, and final sign-off.
Builds the templates and asset foundation, runs the Decode, Strategy, and Score discipline through the install, and drives the debrief loop. Success fee at 5% of contract value excluding VAT on any bid materially worked during the 90-day run. Uncapped for the founding client, six-month sunset.
The boilerplate assembly, the scoring rubric, the bid record, and the reusable drafting.
The advisory window is the install. The OS gets stood up and proven inside it.
Build Stage 0. Standardise the profile, CVs, comparable-projects matrix, methodology library, compliance pack, and pricing template. Fix the naming and identity inconsistency now. Pull every available past-bid scorecard and read it. Diagnose whether historical losses were functionality or price. That diagnosis sets the priority for everything that follows.
The scanner is a software build with its own lead time, so it runs alongside the foundation work rather than after it. Ingestion and classification stood up first, dashboard and decision capture next, live and feeding the queue by the time the volume run starts. Full build sequence in the scanner spec.
Build the operating templates: triage scorecard, compliance matrix, Win Plan, self-scoring rubric, bid record. Run the first live tender through the full pipeline as the proof case.
Every bid runs the pipeline. Every debrief feeds the library. This is where the fee accrues and where the volume lever is actually pulled. Hold a weekly pipeline review across all open bids.
Debrief the run. Tighten the templates against what the scorecards taught. Hand over the operating cadence so Nosto runs the OS after the sunset.
Two rituals hold the pipeline. One weekly review across every open bid, one per-bid gate that nothing skips.
What sits in source, triage, decode, assemble, score, submit. One board, one glance.
No bid moves to Assemble without a Decode output. No bid moves to Submit without a Score & QA pass.
The first three prove the OS is working. The last two prove it is not working at the cost of quality.
Three to lock before the run starts.
This sets the success-fee math and the capacity plan. Pick a number of materially-worked bids and build toward it.
Tool-backed in Notion or Drive, or structured documents in a shared folder.
A lightweight scoring instrument, the way the Gap Finder works for BOS, versus a rubric document.