Operations Plan 2026–2035

The operations plan for 65+5 has one central job: keep a larger opening move governable. The company is no longer commissioning only a single proof factory. It is commissioning a two-node operating system, standing up a Nassau-centered development capability, deploying land and project capital, and doing all of that inside a leveraged capital structure. That changes the operating burden even though the platform thesis itself remains familiar.

The right operating philosophy is still reliability before premium. The factories must ship on time, deliver repeatable quality, and earn the right to higher-value mixes and engineered outputs. Technical services and proof packs must convert performance into bankable adoption. Development participation must remain selective and stage-gated. Treasury must stay tied to operations rather than managed as a separate afterthought. If any of those systems drift, the larger Phase 1 becomes harder to defend.

Operating markers at a glance

Operations must support three distinct but linked revenue families. The first is recurring factory output: ready-mix, premium pours, panels, and selected engineered concrete products. The second is technical service and proof-pack work, which reduces adoption friction and helps the company defend premium realization. The third is controlled project activity through Nassau DevCo and associated land / project positions. The operating system should be designed so that the first family supports the second and the second supports the third, rather than letting project activity destabilize the factory base.

Operating revenue families and operating implications

The two-node system should be run as one operating spine with local accountability, not as two disconnected plants. TCI remains the reference node for recipe discipline, QA templates, and the initial proof pack. Bahamas is the first replication test: same operating philosophy, same quality thresholds, same traceability logic, but executed in a second island market with its own logistics and demand profile.

Exhibit OP-1. Factory output ramp and utilization

Factory operating disciplines by function

Nassau DevCo should be treated as a governed execution layer, not as a parallel company free to outrun the factories. The purpose of the development layer is to create controlled pull-through for Acrete materials, shape proof assets, and capture more value where the company's concrete system gives it a real advantage. That requires disciplined site selection, conservative project underwriting, and explicit stage gates for land, design, permitting, procurement, and construction start.

Project and land gate framework

The organization should be built around clear functional accountability: plant management, QC and laboratory, maintenance, dispatch and logistics, technical services, treasury / finance, Nassau DevCo execution, and a small corporate development / diligence layer where needed. The wrong operating pattern would be a thin management team trying to compensate with heroic effort. The right pattern is a deliberately staffed system with clean reporting lines and defined escalation rights.

Core staffing pillars for the larger Phase 1

Supply chain and quality control priorities

Treasury cannot sit downstream of operations in 65+5. Cash, inventory, and project timing are operating issues because they interact directly with leverage. Management therefore needs a live weekly and monthly cadence that ties production, receivables, debt service, reserve balances, project milestones, and procurement commitments into one operating review.

Exhibit OP-2. Liquidity and deleveraging profile

Minimum reporting cadence

The 2026-2035 operating roadmap is sequential. 2026-2028 is about commissioning two factories, stabilizing logistics, standing up DevCo processes, and proving that the larger operating perimeter can be controlled. 2028-2030 is about repetition: repeatable QA, better panel throughput, cleaner receivables discipline, and credible project-delivery rhythm. 2030-2032 is about applying that maturity to larger markets without losing operational discipline. 2032-2035 is about selective capacity additions, deeper own-project pull-through, and only then broader optionality such as LGS or modular sister operations where the demand signal is strong enough.

Quality is not a support function in Acrete. It is the mechanism by which advanced concrete becomes commercially usable. The operating plan should therefore treat QC, laboratory routines, proof packs, technical services, and warranty boundaries as one integrated workstream. The laboratory does not only test material; it creates the evidence set that sales, engineering, lenders, and owners need in order to accept the product.

Proof-system operating stack

The larger Phase 1 needs more than spreadsheets and weekly calls. It needs a simple but disciplined digital operating layer: dispatch visibility, production logs, receivables and inventory dashboards, project-milestone tracking, and QC document storage. The company also needs a way to keep future sister operations coordinated without letting them overtake the base business. LGS or modular should therefore be planned as a linked but gated operating track rather than as a parallel growth experiment.

Minimum systems architecture

The 65+5 operating plan is stronger when it is read as a discipline document rather than a growth document. The company already has enough ambition. What it needs is clean operating order: reliable factories, documented proof, measured development activity, reserve protection, and a reporting cadence that does not let complexity hide inside momentum. When those things are present, the larger opening move becomes a platform advantage rather than a platform risk.