Jim White, PhD — Founder & CEO, PHT Investment Group
June 2026
Every time I sit down with a Salinas Valley operator to talk about GIAC, the same concern comes up within the first few minutes. It doesn’t matter whether I’m talking to a grower-shipper, a logistics provider, or a brand program manager. The question is always some version of the same thing: “If this is a shared facility, who else is in there? And what do they get to see?”
It’s a fair question. In fresh produce, your customer relationships are your business. Your pricing is proprietary. Your volume commitments, your product specs, your buyer programs, your carrier arrangements — these are not things you share with a competitor who might be operating two dock doors away. The confidentiality concern is not paranoia. It is a reasonable and legitimate commercial instinct.
So let me address it directly. Shared infrastructure does not have to mean shared customers. Here is how GIAC is designed to protect tenant relationships, pricing, and data — while still delivering the efficiency of a shared backbone.
First, the distinction that matters.
There is a difference between a shared facility and a neutral facility. A shared facility implies that tenants commingle — that your product, your data, and your customer relationships are exposed to other occupants. A neutral facility means the infrastructure is shared, but the operations are separated.
GIAC is designed as the latter. The refrigeration system, the utilities, the dock infrastructure, the yard, and the control-tower backbone are shared in the sense that multiple tenants benefit from them. The capital cost of building and maintaining that infrastructure is spread across the platform rather than borne by any single operator. That is the efficiency argument for a shared backbone — and it is a real one.
But the operations — the cooler rooms, the dock positions, the inventory records, the customer specifications, the QA workflows, the pricing, the carrier relationships — those are tenant-specific. Separated by design. Not visible to other tenants. That is what neutral means in practice.
What “shared backbone” actually means.
Let me be specific about what is shared at GIAC and what is not, because the line matters.
Shared backbone
- Refrigeration infrastructure and utilities
- Truck yard and circulation
- Facility maintenance and security
- Control-tower platform layer
- USDA and QA support areas
Private to each tenant
- Dedicated cooler rooms and dock positions
- Customer names, pricing, and volumes
- Inventory records and lot-level data
- QA specifications and product workflows
- Carrier relationships and departure windows
The refrigeration plant doesn’t know whose romaine it is cooling. The dock doors don’t know whose carrier is backing into them. But the WMS does — and that data belongs to the tenant whose product it is. It is not accessible to other tenants. It is not aggregated in ways that expose individual commercial activity. It is not available to GIAC’s operating entity for any purpose other than executing the service that tenant has contracted for.
This is not a promise made in a pitch deck. It is a design requirement that has to be built into the operating agreements, the WMS architecture, the information firewall structure, and the governance framework from day one.
How the operating model enforces separation.
At GIAC, tenants choose from three operating structures, each designed to give them the level of operational control they need while still benefiting from the shared infrastructure.
Option A — Dedicated tenancy
Long-term occupancy of dedicated cooler rooms, reserved dock positions, and private staging zones. The tenant controls day-to-day operations or co-manages with GIAC. Their space is theirs. No other tenant has access to it, can see into it, or can direct anything that happens inside it.
Option B — Turnkey 3PL service
GIAC’s operating entity, CCC-2, handles labor, compliance, and warehouse management on behalf of the tenant under defined SLAs. The tenant’s customer specs, pricing, inventory, and documentation are held in tenant-specific partitions of the WMS. CCC-2 operates to those specs. No other tenant sees them.
Hybrid model
A committed baseline of dedicated capacity combined with flexible 3PL services for overflow, seasonal peaks, or additional commodities. Common for operators whose volume varies by season or crop. The confidentiality protections apply equally to both components.
In all three structures, the principle is the same: GIAC knows what it needs to know to execute the service. It does not have access to commercial information that is not relevant to execution — and it does not share what it does know with anyone who isn’t party to that tenant’s program.
The consolidation question.
One of the things a first-mile platform can do that a single-operator facility cannot is consolidate outbound loads — combining product from multiple suppliers into a single full truck heading to the same destination. This is genuinely valuable. It reduces partial loads, empty miles, and the cost of building DC-ready shipments across a fragmented supplier base.
“Consolidation at GIAC only happens by explicit permission. A tenant’s product is never combined with another tenant’s product without a permissioned workflow that both parties have agreed to in advance.”
The same buyer who is consolidating loads from multiple GIAC tenants is already buying from those tenants separately. They know the relationship exists. The consolidation is not the confidential part. What is confidential is pricing, volume, specifications, and the commercial details of each tenant’s individual program — and none of that is visible to another tenant in a consolidation workflow.
The person managing the outbound load at GIAC sees: this pallet, this lot number, this temperature zone, this destination. They do not see: what this tenant charges per pallet, what volume commitment this buyer made, or what that program looks like commercially. Those are firewall-separated at the WMS level.
The LP governance question.
There is another dimension of the neutrality question that comes up in investor conversations, and it is worth addressing directly. Some prospective LPs in PHT Growth Fund are active in adjacent or competing segments of the fresh produce supply chain. They are growers, shippers, logistics providers, or brand program operators. Their participation as fund investors should not — and will not — give them access to non-public commercial information about other tenants, customers, or operators at GIAC.
LP participation does not provide rights to set prices, choose customers, allocate capacity, or access tenant-specific operating data. PHT plans to implement independent governance, information firewalls, objective access protocols, and PropCo/OpCo separation to preserve competition among growers, shippers, marketers, and service providers who use the platform — while still gaining the pro-competitive advantages of upgraded shared infrastructure.
This is not an afterthought. It is a design requirement. The governance structure has to be built to support the neutrality promise — or that promise is not credible.
Why neutrality is actually a competitive advantage.
The operators who are most hesitant about shared infrastructure are often the ones who have the most to gain from it — because they are running high-volume, high-service-standard programs that currently depend on first-mile infrastructure that cannot keep up.
A neutral platform that is demonstrably confidential removes the main objection to using it. And once that objection is removed, the value proposition becomes clear: origin-adjacent capacity without building your own facility, pre-cooling that targets a four-hour harvest-to-cool window, consolidation that reduces your partial-load problem, lot-level documentation that satisfies your retail buyer’s audit requirements, and a control-tower layer that gives you visibility into your own program without exposing it to anyone else’s.
That is a meaningfully better first-mile outcome than most Salinas Valley operators are getting today from aging, fragmented, undercapitalized facilities that weren’t designed for the service levels they are now being asked to meet.
Shared infrastructure is how you get the economics to work. Neutral operations are how you get the operators to trust it. GIAC is designed to deliver both.
Learn more about the PHT Growth Fund
PHT Growth Fund LP is a dedicated private investment vehicle focused on modernizing first-mile cold chain infrastructure, starting in the Salinas Valley. Fund materials are available to accredited investors upon request.
This article is for informational purposes only and does not constitute an offer to sell or a solicitation of an offer to buy any security. PHT Growth Fund LP is available only to eligible accredited investors. Past performance is not necessarily indicative of future results. Investing involves risk, including the possible loss of principal. Project descriptions, phasing, and specifications referenced herein are preliminary and subject to final design, engineering, permitting, financing, and project approvals.