Dark Fiber IRU Management Software: Keep Icertis and VETRO, and Build Only the Encumbrance Layer Between Them
Live agreement count decides this, and the number is roughly thirty. Below that, with one or two counterparties on a route you know well, a well maintained folder and a calendar entry is honestly enough and we would say so.
On this page
Live agreement count decides this, and the number is roughly thirty. Below that, with one or two counterparties on a route you know well, a well maintained folder and a calendar entry is honestly enough and we would say so. Above it, once you cannot answer which strands on a given route are encumbered without opening portable document format (PDF) files, the exposure is real. Even then the right move is almost never a replacement. Keep the contract platform, keep the fiber geographic information system (GIS), and build only the encumbrance record that joins a clause to a strand.
When is off the shelf genuinely the right call here?
Buy the document layer and buy the plant layer. Agiloft and Icertis handle contract lifecycle, clause libraries, approvals, renewals and obligation dates at a general level, and there is no reason to rebuild any of that. VETRO FiberMap and 3-GIS model fibre plant seriously, down to strands, splices and segments, and rebuilding a fibre GIS would be an expensive mistake with no upside.
Buy, and stop here, if this describes you:
- You hold a handful of indefeasible right of use (IRU) agreements on a single route with one counterparty.
- Nobody disputes which strands are assigned, because the exhibits are recent and the plant has not been relocated since.
- Your commercial team is small enough that one person genuinely knows every agreement touching every route you sell on.
- Your problem is that contracts are unsigned or unfiled, which a contract lifecycle product solves properly.
- Your fibre records stop at cable level, in which case the inventory work comes first and it belongs in a fibre GIS rather than in custom code.
That last row is worth stating plainly because it changes the sequence rather than the answer. An encumbrance has nowhere precise to attach if your inventory does not record strands. A developer who does not raise that before quoting has not thought the project through, and you should treat it as a signal about the rest of their estimate.
There is also a legitimate reason to defer even when the case exists. If your ownership is stable, no lender or infrastructure fund is asking portfolio questions, and your route miles are not growing, this is a real risk carried cheaply. Deferring is a decision rather than an oversight, provided somebody has actually made it.
When does a custom build actually pay off?
The limit of both product categories is the same and it is structural. A contract platform manages documents. A fibre GIS manages glass. The risk in an IRU portfolio lives precisely where a clause has to be enforceable against a strand, and nothing sold today sits in that join, because the join is made of your plant records and your agreements.
An IRU is closer to a property interest than a service contract. A counterparty prepaid capital for exclusive use of specific fibres along a specific route for twenty or thirty years, pays a recurring operations and maintenance charge for the term, and holds rights over what happens when the route moves or gets cut. The money arrived long ago. The obligation is still running, and the person who negotiated it has almost certainly left.
Build when two or more of these are true:
- Your commercial team quotes availability on a route without any system check against existing encumbrances.
- You hold agreements older than the people managing them, described in exhibits as written segment lists rather than as records in any system.
- Maintenance charge escalators are applied by whoever remembers, or you cannot confirm they have been applied at all.
- Relocation or restoration cost sharing is computed by reading every contract touching a segment.
- A financing, a sale or an acquisition is on the horizon, where encumbrance clarity affects valuation directly.
How do they compare on the things that matter in this industry?
Encumbrance identity through plant change. Ask a contract platform what happens to a clause referring to strands 25 through 36 when that span is relocated for a highway widening and the cable is replaced with a different fibre count. It has no answer, because the clause is text. A build makes the encumbrance a versioned record referencing your inventory's own strand and segment identifiers, so a relocation carries a recorded reassignment rather than a silent detachment.
Pre quote availability. A GIS will return total fibre count and lit usage on a segment. It will not return encumbered strands and their expiry dates, because that is contract data. A system check before quoting is the entire point of the project and it is the feature that stops the double sold strand.
Charge as formula rather than amount. The recurring maintenance charge is usually per fibre mile or route mile, adjusted annually by an index or a fixed percentage, sometimes capped. Over a twenty five year term that compounds. Holding rate basis, unit count, escalation method, index source, effective month, cap and floor as structured fields makes the annual adjustment automatic and reproducible. A general ledger records what was invoiced, not what was owed, which is why leakage here is invisible on both sides.
Cost sharing at the segment. Relocation and restoration are geographic events. Attaching each agreement's cost sharing formula to the affected segment through the encumbrance record turns a relocation into a participant list with each party's share as an output. Doing it the usual way invites challenge, because your counterparties are also reading from PDFs.
Data portability. Whatever you choose, ask how the complete record leaves the system, including the strand assignment basis rather than just contract totals. In an asset class where agreements outlive several rounds of ownership, that answer matters more than any feature comparison.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, a first release covering structured agreement records, strand and segment level encumbrance linked to your inventory, the maintenance charge engine with escalators and pre quote availability checking runs $60,000 to $130,000 and ships in 12 to 16 weeks. Within that, a contract model joined to strands with maintenance invoicing lands at $60,000 to $95,000 in 12 to 14 weeks, and the conflict check that refuses a new grant on already encumbered strands sits in the $95,000 to $130,000 tier. A full platform adding relocation and restoration cost sharing, assignment and change of control tracking, counterparty portals and diligence pack generation runs $160,000 to $380,000 over 6 to 11 months.
Component by component: relocation and restoration cost sharing $25,000 to $65,000, counterparty portal $20,000 to $48,000, route and segment model depth including laterals and shared conduit $12,000 to $35,000, and $3,000 to $9,000 per distinct escalator formula, since fixed percentage, index linked, stepped, capped and reset on review are five different calculations that each have to replay historically.
The line nobody puts in a quote is contract abstraction at $400 to $1,400 per agreement. Two hundred agreements is $80,000 to $280,000 of effort. It can be shared with your own team, which lowers cash cost and stretches the calendar, but it cannot be skipped, because a contract model populated by guesswork is worse than the folder it replaced. If your inventory is not at strand level, add 15 to 40 percent, and scope that work separately as a fibre record project.
Annually: hosting $250 to $1,100 a month with retention measured in decades, ongoing abstraction of $400 to $1,400 per new agreement, inventory reconciliation $8,000 to $22,000, escalator and index maintenance $3,000 to $8,000, diligence support $5,000 to $15,000, and maintenance at 15 to 20 percent of software cost.
What does the hybrid look like, and when is it the honest answer?
For nearly every operator this is the answer. Keep Icertis or Agiloft for the document, the clause library and the approval trail. Keep VETRO FiberMap or 3-GIS for the plant. Build the encumbrance layer between them and nothing else in phase one.
In practice that is three pieces:
- The encumbrance record itself. A versioned object referencing segment and strand identifiers from your inventory, carrying term, counterparty, charge basis and rights, surviving plant changes through recorded reassignment.
- Pre quote availability and conflict check. Before any grant is recorded, the segment returns total fibre count, lit usage, encumbered strands and expiry, and a new grant touching encumbered strands is refused rather than reported later.
- The maintenance charge engine. The formula rather than the amount, producing both the invoice and a notice document with the arithmetic shown, and validating incoming invoices where you sit on the paying side, which most operators do on some routes.
Sequence abstraction the same way. Take the twenty agreements covering most of your route miles first, plus anything active, disputed or renewing. The distribution here is steep, so most of the risk is covered quickly and the dormant agreements can wait a year without harm. Portals, diligence packs and assignment tracking belong in a later phase, once a counterparty reading your data will not immediately find an ambiguity to argue about.
Which should you choose, by operator size and stage?
Find your row.
- Under ten agreements, one route, one counterparty. A folder and a calendar entry. Spend the money on plant.
- Ten to thirty agreements, stable ownership, no acquisitions in progress. Keep the contract platform. Abstract the terms into a structured spreadsheet yourself and set escalator reminders. Revisit when the count or the ownership changes.
- Thirty to a hundred agreements on one network you built. Build the encumbrance layer and the charge engine, roughly $60,000 to $95,000 plus abstraction. Availability checking before quote is what you are buying.
- Acquired networks, mixed conventions, several hundred agreements. Build the complete first release including conflict prevention at $95,000 to $130,000, and treat abstraction as a parallel workstream running alongside the build rather than before it, so engineers model against real clauses as they surface.
- Relocations happening quarterly across a few thousand route miles. Add cost sharing at $25,000 to $65,000 in phase two. This is where the money actually moves and it is consistently underestimated because relocations feel exceptional when they are not.
- A sale, a financing or an infrastructure fund on the register. Build, and put diligence pack generation in scope at roughly $18,000. It turns a month of senior time into a report run, and the same view serves wholesale quoting every day.
One condition applies to every build row. Before committing to anything, pick a single route where you are confident there is spare capacity, have someone read every agreement touching it, and confirm. Whatever that exercise turns up, and how long it takes, is your business case in your own numbers.
If you want that decision made properly rather than quickly, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- Deloitte's research found that digitally advanced small businesses experienced revenue growth nearly 4x as high as the prior year, were about 3x as likely to have exported, were nearly 3x as likely to have created new jobs, and were more than 3x as likely to have seen more sales inquiries in the last year. Source: Deloitte (research summarized by Google) (2017) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- In an October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
Frequently asked questions
Can we use Icertis or Agiloft instead of building anything?
If your problem is purely contractual and nobody disputes which strands are assigned, yes. Both products manage clauses, renewals, approvals and obligation dates well, and you should keep whichever you already run.
What neither does is enforce an obligation against a physical fibre record, because a clause is text and a strand is an object in a different system. Most operators who try the contract tool alone come back when they cannot answer an encumbrance question about a specific segment inside a quoting conversation.
What does it cost to switch contract platforms or fibre systems later?
The direct migration cost is modest. The real expense is that your encumbrance records reference one inventory system's strand and segment identifiers, so changing the fibre system means remapping every encumbrance rather than exporting a table.
Build the identifier mapping as its own layer and ask, before signing anything, how the complete record leaves each system including the strand assignment basis rather than just contract totals. In an asset class where agreements outlive several rounds of ownership, portability is worth more than any feature.
What if our contract platform changes its pricing at renewal?
Work out what the fee looks like at double your current agreement count and user count before renewal rather than during it, because seat based and record based pricing rise as the portfolio grows.
The structural protection is that the encumbrance layer is yours. Once the strand level record, the charge engine and the availability check sit in a system you own, the contract platform is providing document management you can price and compare against alternatives, rather than holding the part of the portfolio that carries the asset value.
Why is contract abstraction such a large part of the cost?
Because somebody has to open an agreement signed in 2011 and record the strand assignment, the escalator formula, the relocation clause, the assignment restriction and the restoration standard in a form software can enforce. That is $400 to $1,400 per agreement, so two hundred agreements is $80,000 to $280,000.
It can be shared with your own team, and it should be sequenced so active, disputed and renewing agreements go first. It cannot be skipped, because a contract model built on guesswork is worse than the folder of files it replaced.
How long does an IRU management build take?
Twelve to fourteen weeks for the contract to strand model with maintenance invoicing, and 14 to 16 weeks for a complete first release adding obligation tracking and conflict prevention, based on Digital Heroes delivery experience. A full platform phases across 6 to 11 months.
The schedule is driven by abstraction rather than engineering, and abstraction should run in parallel with the build rather than before it, so engineers are modelling against real clauses as they surface rather than against an assumed structure.
Do we need strand level fibre records before we start?
Effectively yes. If your inventory records only cable level detail, an encumbrance has nowhere precise to attach and the system cannot answer the question you are asking it. Expect 15 to 40 percent added if that work is in scope.
That work belongs to the fibre record rather than the contract system, so do it in VETRO FiberMap or 3-GIS and scope it separately. A developer who does not raise this before quoting has not thought the project through.
How do we stop selling strands that are already committed?
Make encumbrance a system record referencing your inventory's own strand and segment identifiers, then require an availability check before any quote and a conflict check before any new grant is recorded. The check returns total fibre count, lit usage, encumbered strands and expiry for the segment.
That conflict check sits in the $95,000 to $130,000 tier of a first release and it is the single feature this category exists to deliver. Everything else in the project is built around it.
What does relocation cost sharing add, and can it wait?
Between $25,000 and $65,000, and it can wait for phase two but usually not longer. It apportions a relocation cost across every grantee on a segment using formulas that differ per agreement, then invoices and tracks recovery.
Operators underestimate it because relocations feel exceptional. Across a few thousand route miles they are not exceptional, and the amounts are large enough that counterparties will argue about them from their own portable document format files unless you can show the arithmetic.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Arjun.
Chief Technology Officer · Delhi · 1 post on the site
Published · Last updated .
