HVB pilots are the bridge between systems thinking and real infrastructure. We package pilots with partner lanes, stakeholder legitimacy, and grant-ready artifacts so developers and municipalities can move.
Pilot packages include opposing flows—systems diagrams, partner lanes, grant-ready narratives, and community-proof.
A pilot is a defined site + defined stakeholders + a fundable “next step.” HVB’s job is to standardize the packaging.
Capture the minimum viable truth: site, feedstocks, constraints, and desired outcomes.
Build artifacts: one-pager, partner lanes, stakeholder map, and a credible funding pathway.
Submit to a grant program and/or hand off to a delivery team with clarity and momentum.
These are starting points. Actual designs depend on feedstocks, siting constraints, EJ realities, and partner capacity.
A municipality anchors collection and routing; partners align preprocessing + digestion + end products.
Wastewater treatment becomes a circular node (energy + soil products), reducing disposal costs and emissions.
Pair lake/river management with circular processing so removal becomes a resource flow (when feasible).
Each system includes a community narrative, operational learnings, and a grant-ready artifacts bundle to speed decision-making.
'Gateway' transfer concept with waste, compost, and resource-recovery neighbors.
Large feedstock clusters paired with WWTPs for community-scale gas-to-grid pilots.
Transfer and recycling campus adjacent to riverine logistics, ready for anaerobic upgrades.
Regional partnership with compost, landfill, and waterside landscape insights.
These inputs are the difference between a feasible plan and a slow-motion failure.
A pilot needs a real location with a stakeholder who can open doors (municipality, operator, landowner).
Volume, seasonality, and contamination profiles—plus who can commit (in writing, eventually).
Energy + hauling cost + soil outcomes + environmental restoration—prioritized and defensible.
EJ and siting concerns aren’t “later problems.” Address them early or pay later.
A credible developer/operator path is part of the package (even if it’s preliminary).
Grant eligibility and timelines + a plan for letters of support and local commitments.
Two foundation publications + a pilot grant case study. Use these as reusable modules when drafting a pilot proposal.
Regional resource potential and system context for organics-to-value solutions.
Ten siting concepts + coverage strategy for the Hudson Valley.
A coalition-built pilot attempt: valuable as a template, even though it wasn't awarded.
Common questions from municipalities, advocates, and developers.
Submit anyway if you have a real location and a stakeholder who can engage. The intake helps us identify what’s missing and what lane(s) are needed.
No. We improve the odds by producing a coherent package with partner lanes, credible constraints, and strong documentation—then aligning to grant cycles.
Typically municipalities, developers, and operators. HVB helps assemble the conditions for building: legitimacy, partners, feasibility framing, and fundable packaging.
A pilot is how the movement becomes infrastructure. If you have a candidate location (even rough), start here: