These are composite accounts drawn from anonymized engagements. Names, locations and figures are changed, but the sequence of work and the sticking points are the ones we keep running into: a rural fiber extension that stalled on land access, a cooperative node upgrade that needed civil works permits before any equipment could be ordered.
"We had three candidate sites and no way to compare them. The capacity model and the field notes gave the council something concrete to argue about instead of guessing. The phased ring meant we could start where demand already existed."
"The civil works permits were the part we kept postponing. Having the equipment specifications and the permit package in one place let our board approve the first phase without reopening the whole discussion."
"What helped most was the assumptions note. Every number had a source or a flag saying it still needed confirmation. That honesty is why the committee trusted the rest of the document."
Engagement types covered in our case files
Feedback from municipal IT leads, cooperative engineers, and planning staff who took a project from field survey to an approved first ring. Names and locations are withheld; the substance is not.
We had four candidate plots for an edge node and no way to compare them. The site matrix came back with power capacity, access roads, and distance to the trunk line side by side. The council stopped arguing about the land and started asking about the substation, which was the real constraint all along.
Our board wanted a redundant ring immediately. The capacity model showed we could serve the first three districts on a single path and leave empty ducts for the rest. Splitting it into phases kept the civil works budget within what we could actually operate.
The first dossier we submitted got sent back twice for missing servitude documents. The second version had the permits, the survey notes, and the phased budget in one place. Committee review took a single session.
What helped most was the assumptions note. Every figure in the model had a source or a flag saying it still needed field confirmation. Nobody had to guess which numbers were solid and which were placeholders.
We expected a vendor pitch and got a survey schedule instead. Equipment specs listed two compatible options per node with the trade-offs written out, so our procurement team could run its own comparison.
The phased schedule named the milestones that would trigger the next tranche of work. When adoption in the first segment ran slower than projected, we paused phase two without renegotiating the whole plan.