In two months an investment-grade business case was built for an agro-industrial complex in a Costa Rican free trade zone: three plants, two sub-plants, FDA and HACCP compliance, and a three-year roadmap with CAPEX and OPEX broken down.
An investment-grade business case is not a longer business plan. It is a document that withstands scrutiny from whoever is putting up the money, and that changes what it has to contain and at what level of detail.
What was the assignment?
An investor needed a business case that could withstand financier scrutiny: an agro-industrial complex integrating production, storage and innovation inside a free trade zone, while achieving FDA and HACCP compliance.
The complexity was real. Three plants plus sub-plants, each with unique process flows, compliance paths and market destinations, ranging from food and nutraceuticals to packaging inputs. The plan had to sequence construction and certification across three years without promising capacity it could not sustain.
An investor doesn't buy the idea: they buy the detail. CAPEX by category says more than any optimistic projection.
What makes a business case investment grade?
That every number traces back to an explicit assumption, and that the assumptions can be argued one by one. A document that shows only the result forces you to believe; one that shows the path lets you negotiate.
In practice, the difference between a business plan and an investment-grade case comes down to four things:
- CAPEX is broken down by category, not given as a total. A financier needs to know how much is civil works, how much equipment and how much certification, because each carries a different risk profile.
- OPEX comes by phase, not as an annual average. A plant starting at 40% of capacity does not have the cost structure of one running at 100%.
- The financing structure states what external capital covers and what internal cash flow covers, and when that mix changes.
- Projections come in several scenarios, aligned with what buyers in the sector actually expect rather than with what suits the project.
| Piece | Business plan | Investment-grade case |
|---|---|---|
| CAPEX | A single total | Broken down by category: civil works, equipment, certification |
| OPEX | Annual average | By phase, against the capacity actually running in each |
| Financing | The amount requested | What external capital covers, what cash flow covers, and when that shifts |
| Projections | One scenario, the favourable one | Several scenarios, each with its break condition |
| Compliance | Mentioned as a requirement | Sized: it lands in the CAPEX and in the headcount plan |
| Schedule | Target dates | A sequence tied to certifications and to available cash |
What an investor is really evaluating is not the projected return: it is whether whoever is presenting the project understands what it will cost to run.
It is also why a well-built business case earns its keep even when the funding does not arrive. The exercise forces a number and a date onto decisions that were intentions until then, and that material stays inside the company: it serves to negotiate with a bank, a partner or a buyer, and it serves to kill the project in time if the numbers do not work.
Killing it in time is, in fact, the least celebrated outcome and the one that saves the most money. An agro-industrial project that does not close gets discovered on paper or gets discovered with the works half built, and the difference between those two ways of finding out is several orders of magnitude.
What was delivered?
A seven-piece package covering the thesis, the operation, the money and compliance. Each one answers a question a financier asks before committing.
- Executive summary with the investment thesis and the phased construction roadmap.
- Full product and capacity architecture across three processing plants and two sub-plants, with outputs ranging from gluten-free flours and dehydrated fruits to concentrates and starch pellets.
- CAPEX breakdown by category and OPEX by phase, with the financing structure: external funding only in Phase 1, subsequent phases funded by reinvested margins.
- Multi-scenario revenue and cost forecasts aligned with wholesale buyer expectations.
- HACCP-aligned operational flowcharts and standard operating procedures.
- A complete headcount plan ensuring regulatory compliance and production-aligned staffing.
- Stakeholder map: government bodies, certifiers, financial backers and potential multinational buyers.
That package applies the same criterion we use in business consulting, carried over to a capital decision: make explicit what is going to be done first, price it second.
Why is compliance designed before construction?
Because a compliance requirement shapes the civil works, and discovering it later forces a rebuild. Designing the plant and certifying it afterwards is the most expensive route to the same place.
The framework is not a matter of opinion: the FDA describes HACCP as a systematic approach to the identification, evaluation and control of food safety hazards, based on seven principles — conduct a hazard analysis, determine the critical control points, establish critical limits, establish monitoring procedures, establish corrective actions, establish verification procedures, and establish record-keeping and documentation procedures.
The last two are the ones most often underestimated at project stage. Verification and documentation are not paperwork for later: they define what gets measured, where, and with what instrument, and that translates into equipment, floor space and headcount. Which is to say, into CAPEX and OPEX.
That is why the HACCP-aligned flowcharts went into the business case rather than into a later phase. A plan that promises certification without having sized what certification demands is not an optimistic plan: it is an incomplete one.
The same logic applies to the standard operating procedures. Writing them during the project stage looks premature until you notice that they determine how many people each shift needs, and that headcount is one of the largest recurring lines in the OPEX a financier will read.
How long does building one take?
This case took two months, and the timeline was not set by the volume of work: it was set by the availability of decisions only the investor could make.
A business case stalls at the same four points almost every time, and none of them is analytical:
- The definition of Phase 1 scope. While it stays open, CAPEX cannot close and everything else hangs off it.
- Equipment quotes, which depend on outside suppliers and on lead times the project does not control.
- Confirming requirements with the certifier, because a different reading changes the plant design.
- Wholesale buyers' price expectations, the input without which the projections are an arithmetic exercise.
When those four run in parallel from week one, two months is enough. When they run in series, the same work takes six, and for most of that time the company is waiting rather than analysing.
What does the free trade zone add?
A special regime built for operations that export, in a country whose economy depends on exporting. The fit is not incidental: it defines the market the project sells into.
The context sizes it. Costa Rica exported US$40 billion in goods and services in 2025, equal to 38.8% of its GDP, according to World Bank data. An agro-industrial complex in a free trade zone is not betting on a niche: it plugs into the main current of the country's economic activity.
For the business case that has a practical consequence. The stakeholder map — government bodies, certifiers, financiers and multinational buyers — is not a courtesy appendix: it is the list of counterparties Phase 1 depends on to start on the promised date.
It also shapes how the case is written. A document aimed at a financier and a document aimed at a certifier are not the same document, and a project inside a free trade zone needs both to hold up at once.
How do you sequence a three-year project without overpromising?
By funding each phase with what the previous one produces, and committing external capital only where there is no prior cash flow to replace it. That rule orders the sequence on its own.
The criterion followed here is repeatable in any phased project:
- Phase 1 is sized by what can be sold from year one, not by the installed capacity you would like to have.
- External capital is raised once and for that phase: raising for all three forces you to defend three-year projections at the level of detail of the first.
- Each subsequent phase is funded by reinvested margins, which makes progress a consequence of performance rather than a promise.
- Certification for each plant is scheduled before its construction, because the certifier's timeline is not negotiable.
- Headcount is tied to each phase's real production, not to the target roster of year three.
- Every projection scenario carries its break condition in writing: what would have to happen for that phase not to start.
That sequencing discipline is what separates a plan that gets executed from one that gets filed. We develop it in how to build a growth plan that actually gets executed.
What can your company take from this case?
That raising capital is not telling the project well: it is proving you understand its cost, its compliance and its sequence. If you cannot explain what gets built in Phase 1 and with whose money, there isn't a business case yet.
At ZENITAR the full case was built in two months, with CAPEX broken down by category and OPEX by phase, because the result is measured in the decision the client was able to make and not in the length of the document.
If the project has not reached that stage yet, two useful reads: the case of a transport rental operator that fixed its controls and that of a retailer that grew 35% by documenting its operation. Both show the groundwork that makes any projection credible.
