Operations Plan 2026–2035

This revised long-form operations plan is intended to do what the earlier short 5+5 operating summary did not do: explain in detail how the tighter five-country Acrete company would actually run over the 2026–2035 period. It keeps the stronger operating language from the larger source plans, factory discipline, staffing architecture, quality control, delivery logistics, training, project support, and governance cadence, but it re-centers the early years on one TCI proof node funded under the 5+5 structure. In other words, this is not a new operating philosophy. It is the same operating philosophy expressed through a more manageable first phase and a clearer sequencing logic.

The operating challenge is broader than starting a plant. Acrete has to build a company that can batch reliably, produce panels credibly, support on-site poured projects, manage island logistics, translate technical claims into field behavior, and eventually support its own aligned development pipeline. That means the operations plan must cover factory operations and project-facing execution. It must describe how the company will work at the node level, at the project level, and at the portfolio level as more countries and more demand lanes come online.

The key operating principle remains proof before premium. In practical terms, that means: do not oversell a product before the batch routine, QC checks, field-support habit, and documentation pack are good enough to support the claim. This principle shapes staffing, training, release gates, and even commercial behavior. It is also why the tighter footprint is valuable operationally. Fewer near-term nodes mean more management attention per node, cleaner learning transfer, and a better chance of turning the first factory and first projects into repeatable templates rather than one-off hero efforts.

Exhibit ES-1. Illustrative coordination of node rollout and project activity.

Exhibit ES-2. Illustrative staffing ramp for the tighter footprint.

The tighter five-country Acrete company should be operated as a platform with one common operating spine and several different demand lanes. The common spine includes batching discipline, mix governance, QC routines, dispatch, proof-pack generation, basic plant maintenance, and commercial coordination. The demand lanes include direct market sales, panels and engineered outputs, technical services, and increasingly project-linked demand from aligned developments. The point of the operations plan is to define how those shared and differentiated elements fit together without producing chaos.

The phase logic matters because each phase adds a different kind of operating burden. Phase 1 is mostly about control: start the TCI node correctly, prove the basic routines, and avoid false speed. Phase 2 is about transferability: show that the TCI template can survive movement into Bahamas. Phase 3 and beyond are about portfolio management: coordinating multiple nodes, deeper product lines, more project complexity, and more management infrastructure. If operations treat all phases as if they are just bigger versions of Phase 1, the company will underbuild the systems needed for later complexity. If operations treat Phase 1 as if it were already a mature regional network, the company will overbuild cost and bureaucracy. The plan must therefore show continuity and evolution.

Phase 1 should be described operationally as a controlled proof window, not merely as a launch. The TCI node has to establish four things simultaneously: reliable plant operation, disciplined product release, strong site / project support, and usable management reporting. Those four are the operating equivalent of the investment thesis. If the plant makes product but cannot support the field, the proof fails. If it supports the field but the documentation is weak, the replication story fails. TCI therefore has to be run like a reference site from day one.

Bahamas replication then has a different mandate. It is not just another plant opening. It is the operating audit of the whole system. The management team should treat the Bahamas node as the place where every important playbook gets tested: recruiting, startup training, batching controls, dispatch norms, materials reserves, proof-pack generation, and project support. If those routines travel well, Acrete has a real platform. If they do not, the company should slow further geography until the transferability issue is fixed.

From an operating standpoint, this means the Bahamas launch should inherit more than equipment specification. It should inherit shift structure, quality logs, nonconformance response rules, customer-communication cadence, and first-90-day decision rights. The second node is where operating discipline becomes visible as an asset rather than as a preference.

Factory operations should be built around a practical principle: every product family must fit a repeatable planning routine. The plant cannot become a place where every project improvises a different operating rhythm. Ready-mix and site pours require tight dispatch control, queue visibility, truck and crew readiness, and close communication with site teams. Panels require mold planning, cure-cycle planning, storage discipline, and installation sequencing. Bagged and repair materials require a different packaging and inventory rhythm. Technical services require time from the lab and field team. The operations plan should therefore define the plant not as one undifferentiated throughput engine, but as a multi-lane industrial site with a common quality core.

That multi-lane view is especially important because Acrete intends to serve everything from affordable housing to hospitality and later industrial and commercial projects. Some work will be driven by large pours and civil schedules. Some will be driven by repeatable panel runs. Some will be driven by smaller repair and specialty demand. The plant's scheduling system must therefore prioritize sequence clarity. It should decide what gets produced when, how much slack is needed for project uncertainty, and which lanes are allowed to interrupt others. Without that discipline, the company will experience plant-level confusion that looks to the customer like reliability failure.

Exhibit 3-1. Illustrative operating focus by product and service lane.

Quality control inside Acrete should be treated as the commercial heart of the company. It is not enough for the plant to believe that a product is good. The company needs a documented path from specification to mix translation, from batch to test, from test to release, and from release to reference pack. That is what allows Acrete to speak credibly about durability, performance, and reliability. It is also what allows the company to support premium pricing and later project-led growth without losing control of claims.

The operating implication is that release gates must be explicit. A product should not ship or pour simply because the schedule is tight. The company needs stop-ship authority, defined nonconformance response routines, field escalation logic, and documented close-out procedures. Those routines sound procedural, but they are strategically important because they protect the brand and lower the risk of building the company on weak proof. In a tighter footprint, the advantage is that management can watch those routines closely and strengthen them before the network gets larger.

Exhibit 4-1. Quality and proof-pack release cycle.

Island operations create a brutal lesson quickly: good product design cannot overcome poor logistics discipline. Acrete therefore needs a procurement and supply-chain model built around resilience rather than bare-minimum inventory. The company should think in terms of critical inputs, backup suppliers, spare-parts readiness, and shipping-calendar management, not just spot purchasing. This is particularly important for additives, specialized components, replacement parts, packaging inputs, and any items that can turn a plant stoppage into a reputational event.

The same principle applies to project delivery. Panels, pours, and site support all depend on getting the right material to the right place with the right timing. If Acrete is going to support its own and aligned projects more heavily over time, supply chain becomes a strategic capability, not a clerical one. The plan should therefore treat procurement, warehouse control, inventory days, and transport scheduling as core operating disciplines with board visibility when exceptions become material.

Acrete's staffing model should be built around depth in the functions that protect reliability: production, QC, dispatch, estimating, technical services, and site support. It should not try to look artificially lean by starving the technical and operating middle layer. This is especially true in a platform that expects to support factories and projects. The wrong organization for Acrete is one that staffs enough operators to batch concrete but not enough technical, commercial, and supervisory talent to sustain proof-backed growth.

The training model should likewise be treated as part of the operating system. New operators, dispatch staff, QC technicians, site supervisors, and estimating or technical-sales staff should all be trained against the same reference playbook. In the early years, that playbook can be relatively light. By the time the company is replicating into Bahamas and preparing for the larger markets, the playbook should become a real academy-style system with onboarding modules, field refreshers, product family training, and management routines that travel.

Exhibit 6-1. Illustrative staffing ramp for the tighter footprint.

Operations should not separate commercial workflow from production workflow. Quotes influence scheduling. Estimating choices affect site performance. Technical services shape margin quality. Proof packs influence customer conversion. The company therefore needs a simple but integrated flow from lead to estimate to production plan to delivery record to close-out file. In the proof-node phase, this may be partly manual. But the logic should be defined early because a later multi-node company will break if those steps remain disconnected.

Reporting discipline should follow the same principle. The weekly operating review should cover dispatch performance, batch exceptions, quality issues, on-time delivery, project support, and inventory pressures. The monthly review should connect those metrics to revenue, gross margin, project mix, and proof-pack production. The quarterly board pack should aggregate them into platform-level insight. When Acrete eventually supports more of its own projects, this reporting stack becomes even more important because plant and project exceptions will affect each other directly.

As the revised strategic materials suggest, Acrete's future value creation depends increasingly on project participation. The operating plan therefore needs a real project-delivery section. The company has to learn how to support its own and aligned projects without destabilizing its industrial base. That requires clear rules around who owns the client relationship, who owns the project schedule, how the plant protects base-load demand while serving project peaks, and how reference-project documentation is produced without slowing operations to a halt.

The company should think about project delivery in layers. At the lightest layer, it supplies materials and technical support. At the middle layer, it supplies panels, selected installation oversight, or field support. At the heaviest layer, it becomes an active developer or delivery partner with a larger share of schedule and economic responsibility. Each layer requires different operating commitments and different governance sign-off. The operations plan should therefore formalize the layers rather than letting every project define its own rules.

Exhibit 8-1. Illustrative evolution of Acrete project focus.

The optional LGS modular strategy belongs in the operations plan because it affects how Acrete should design interfaces, not because it must be launched immediately. If the company expects to support modular or light-gauge steel systems later, it should define early how panels, foundations, slabs, and site packages would integrate. That prevents future sister operations from becoming disconnected businesses with weak operational overlap.

The right operating stance is to define LGS as a gated compatibility track. Management should identify the concrete components that are most likely to interface with modular systems, the installation and design standards that would be required, and the procurement or factory implications of that interface. But no launch should occur until the core Acrete network is stable enough that management attention can absorb it. In this way, the plan acknowledges optionality without letting optionality run the company.

The milestone system in this plan should be treated as the operating equivalent of investment underwriting. Every major operating expansion should be gated: Bahamas replication, later market entry, second-node launches in the larger markets, deeper DevCo commitments, and any sister-operation move. Gates should combine plant performance, project execution quality, proof-pack maturity, staff readiness, and capital resilience. The purpose is not to slow the company for its own sake. The purpose is to keep the pace of expansion aligned with what the operating system can actually support.

Contingency planning should be equally explicit. Island operations face shipping disruption, weather risk, project delays, staff turnover, and supply interruptions. The plan should therefore define what management does when any of those occur: what reserves are protected, how dispatch priorities are reset, who decides on project deferrals, how customer communications are handled, and when the board is asked to intervene. The existence of those contingency rules makes the broader platform more reliable because it reduces the chance that each disruption becomes a fresh debate.

The correct operating ambition for Acrete is not to look busy across many markets. It is to become highly reliable in a manageable footprint and then widen that footprint without losing quality or control. That is the deeper meaning of the 5+5 revision. The first node should prove that the company can batch, dispatch, support the field, and document its work credibly. The second node should prove that the template travels. Later nodes should prove that the company can manage a network and support a project platform at the same time.

If that operating arc is executed well, Acrete becomes much more than a concrete manufacturer. It becomes a regional industrial and project-delivery system capable of serving external customers, supporting its own communities and resort or residential product, widening into bagged and repair materials, and selectively adding compatible sister operations such as LGS modular. None of that is possible without disciplined factory operations, project coordination, supply resilience, staffing depth, and governance gates. That is why this operations plan is intentionally long-form: the opportunity is bigger than a plant startup, and the operating answer has to be correspondingly complete.