The timeline below tracks the moments that defined how we work: field seasons, dossiers that went through council review, and the phases where our role shifted from surveying to structuring. It is not a list of credentials, but a record of the problems that shaped our method.
2019
We started walking sites with local planning teams, mapping substations, access roads, and fiber trunk distances by hand. Those early notebooks became the checklist we still use to discard unviable lots before any topographic work begins.
2021
A cooperative asked us to size a redundant ring without overbuilding. We built the model from current subscribers, five-year projections, and peak traffic per segment. The phased schedule that came out of it let them defer two civil works stretches until adoption caught up.
2022
After a returned submission, we rebuilt the dossier format into four blocks: context and demand, network design, permits and easements, and phased schedule. The note of assumptions at the end became standard, so committees could see exactly what remained unconfirmed.
2023
We began sitting with municipal IT staff to translate rack, power, and cooling needs into equipment specifications they could defend internally. Vendor-neutral by design, these specs kept the conversation on load profiles and redundancy rather than brand preferences.
2024
The first ring we accompanied end to end went live with the original phase plan largely intact. The deviations we logged during construction fed back into the risk sections of later dossiers, closing the loop between field reality and planning documents.
InfraFund Co is a small group of engineers and planners. We are not a construction firm and we do not sell equipment. Our job is to walk the terrain, model what the network can carry, and hand your team documents that hold up in front of a council or a cooperative board.
We visit candidate plots and existing substations, log coordinates, tenure status, and access routes. The output is a comparison matrix, not a single recommendation, so your committee can weigh alternatives on the same footing.
Starting from current subscribers and a five-year projection, we size active strands, identify segments that can wait, and flag where empty ducts are worth laying now. Peak traffic per segment drives the numbers, not vendor brochures.
Trenching, easements, and municipal permits tend to stall projects longer than the electronics. We map the sequence of approvals and prepare the drawings that match what was actually surveyed in the field.
Councils and boards read in a predictable order: justification, technical viability, then budget by year. We structure the file in those blocks, with annexes and an explicit note on what still needs confirmation.
Full civil works up front rarely matches how adoption actually happens. We break the rollout into phases with verifiable milestones, so each stage can be reviewed before the next commitment is made.
Equipment specifications are written around your operating conditions and maintenance capacity. We have no reseller agreements, which keeps the comparison honest when your team evaluates proposals.
InfraFund Co did not start as a firm with an office and a logo. It started as a recurring problem: municipalities and cooperatives were being handed network designs that ignored the ground beneath them. Substations undersized, access roads too narrow for a service truck, fiber routes crossing land nobody had secured. The early work was field surveys and capacity models, done alongside planning teams who needed numbers they could defend in front of a council.
We stopped accepting desktop studies as a starting point. Every site visit produces coordinates, photos, notes on power availability and a rough sketch of how equipment would actually reach the location. That habit shaped the firm: the survey comes before the model, not after.
As projects grew, so did pressure to recommend specific equipment. We kept the opposite stance. Specifications describe capacity, redundancy and environmental tolerances, not brands. This lets a cooperative run its own procurement and compare offers on equal terms, which is often the difference between a project that moves and one that stalls in committee.
A recurring failure in municipal projects was documentation. Plans that did not match the field, budgets without phasing, missing servitude records. We rebuilt the technical dossier around four blocks: demand context, network design, permits and easements, and a phased schedule. Councils still ask hard questions, but now they get answers instead of deferrals.
The most visible shift came when we stayed past the approval stage. Commissioning the first ring exposes assumptions that no model catches: splice losses, duct obstructions, coordination between civil crews and fiber teams. Those lessons now feed back into every new assessment, and they are the reason our phased schedules leave room for field corrections rather than treating them as failures.