Turning a feasibility study into a procurement package clients can act on
A feasibility study becomes actionable when it is broken into procurement packages, each with a one-page design basis, a scope boundary, an evaluation basis and a documentation list. The conversion step — not the study itself — is what most clients are missing when a project stalls after feasibility.
- Split by interface, not by supplier catalogue; interfaces are what create risk.
- Each package needs a one-page design basis a supplier can price from.
- Sequence long-lead packages first even if the budget is not fully approved.
- Keep one master assumption register shared across all packages.
Step 1 — package the project
Typical splits: site and civils; tanks or ponds and liners; water treatment; aeration and oxygen; pumping; feeding systems; monitoring and control; harvest handling; chilling and cold chain; processing interface. Draw the boundary lines on a single diagram and have the client approve it.
Step 2 — write a one-page design basis per package
- Duty point or capacity, with the biological or hydraulic basis behind it.
- Interfaces in and out, with responsibility named.
- Site conditions relevant to that package.
- Standards and documentation required.
Step 3 — set the evaluation basis before issue
Decide how offers will be compared — total evaluated cost, technical compliance, schedule and support — and write it down. Where a private RFQ process is used, buyer identity can stay confidential while the technical package still carries everything a supplier needs to quote.
Step 4 — issue, clarify, normalise
Run a clarification window, distribute all answers to all bidders, then normalise the responses onto one table with assumptions and exclusions visible. The output is a decision document, not a pile of PDFs.
FAQ
Related
Hand a client project to the concierge
You keep the client and the technical mandate. FishMatch Group runs the private supplier outreach and returns normalised offers.
All consultant guides