Colocation Billing Software: Build or Buy at Your Cabinet Count
The threshold is roughly 200 cabinets on a single site with flat or simply committed power: below it, buy Ubersmith or EasyDCIM and let one person track the cross connects, because a build solves a problem you do not yet have.
On this page
The threshold is roughly 200 cabinets on a single site with flat or simply committed power: below it, buy Ubersmith or EasyDCIM and let one person track the cross connects, because a build solves a problem you do not yet have. Above roughly 300 cabinets, with metered power on tiered overage and a cross connect count nobody can reconcile against the invoice run, the unbilled revenue alone usually funds the build in its first year.
When is off the shelf genuinely the right call here?
Ubersmith is a real billing platform and handles recurring hosting and colocation services well. EasyDCIM suits smaller operators and covers the basics without ceremony. On the physical side, FNT Command and Sunbird dcTrack hold cabinet, circuit and connection records properly, and they are the right kind of tool for that job. None of these is a bad product, and replacing what they already do is a poor use of capital.
Buy, and commission nothing, if this describes you. You are under roughly 200 cabinets on a single site. Your power is billed flat or on a simple committed model with one convention across the book. Your cross connect count is small enough that one person can reliably say how many are live. And you operate one entity in one currency, so the accounting question is a posting rather than a design conversation.
At that size the invoice run is an afternoon rather than a week, and the leakage that funds a build has not accumulated yet. There is no prize for engineering your way out of a problem you do not have, and we tell operators that even when it costs us the work.
There is a second case where buying is right for a different reason. If nobody can say with confidence which breaker feeds which cabinet, do not commission a rating engine. A rating engine built on a mapping nobody trusts produces invoices nobody trusts, and the fix is physical work in the building rather than software. Sort the record first, keep billing as it is, then revisit.
When does a custom build actually pay off?
When two or more of these are true, and not before.
- Your contract constructs have outgrown any product catalogue. Committed kilowatts with tiered overage defined differently per customer, per customer cross connect pricing, remote hands allowances and escalators that need to fire automatically all end up as custom fields and maintenance scripts. If one person is quietly keeping that layer alive, you have already outgrown the product.
- You cannot say how many cross connects are billed against how many are live. This is usually the largest single item, and it happens because the connect is created by a technician closing a work order with no revenue step in the flow.
- Remote hands hours are delivered and never invoiced. The ticket holds everything needed to bill, and the ticket system has no concept of a rate card or an allowance balance.
- You operate multiple sites or entities needing consolidated invoicing. That brings currency policy, conversion dates and a boundary question about who holds a service on the changeover.
- A customer dispute cannot be answered because nobody can show the meter data behind the charge. Traceability is the feature spreadsheets structurally cannot provide.
The clearest signal is the one nobody says out loud. Your finance manager is the only person who understands the invoice run, and the month she is on leave is the month invoices go out late.
How do they compare on the things that matter in this industry?
Five comparisons, and none of them are about screen design.
Where the measurement rule lives. Contracts commit power at the cabinet or suite. Meters measure at the branch circuit. On a dual corded cabinet the A feed and the B feed carry roughly the same load, so summing them counts the draw close to twice. Whether you bill the sum, the higher side or a combined derived figure is a contractual decision that differs per customer, and your book almost certainly contains more than one convention signed by different people in different years. It has to be data attached to the contract, not a global setting.
Which number the tier applies to. Monthly peak kilowatts, average kilowatts, a ninety fifth percentile sample, or metered kilowatt hours passing through your utility cost. Operators use all of these. A system supporting one forces the rest into manual adjustments, and manual adjustments are where the errors live.
Whether the connect order is the billing trigger. Data centre infrastructure management products, abbreviated DCIM, record the physical connection correctly and are not billing systems. If a human has to carry that information across, at scale somebody eventually does not.
Reproducibility. Cabinets get recabled. An invoice from fourteen months ago has to still be reproducible, which means versioned circuit to cabinet mapping designed in from the start rather than bolted on later.
Contract terms as structure. Escalators, ramp schedules, free months and minimum commitments living in a signed document mean the escalator that should have lifted the rate on the anniversary quietly did not, and the gap compounds for the rest of the term.
What does total cost of ownership look like at your scale?
Three bands, and one preliminary purchase that makes every quote comparable.
A first release covering structured contracts, metered power rating against your real circuit mapping and cross connect billing driven from the work order runs $60,000 to $140,000 over 12 to 16 weeks in Digital Heroes delivery experience. A carrier hotel operator across two sites with roughly 600 cabinets, four contract constructs, two branch circuit monitoring vendors and about 900 live cross connects delivered at $140,000 over fifteen weeks, including $14,000 of contract discovery and $13,000 for a parallel run across one complete billing cycle.
The second tier, at roughly $160,000 to $280,000, adds remote hands capture from your ticket system, bandwidth billing on percentile sampling and revenue recognition schedules. The third, at $280,000 to $400,000, adds a customer portal with usage visibility, multi currency and multi entity operation and a real posting model into NetSuite or Sage Intacct with your dimension structure. That accounting piece is a design conversation with your controller rather than a connector, and teams consistently underestimate it.
Then the running cost. Plan 15 to 22 percent of build cost a year, roughly $21,000 to $31,000 on the worked example. It covers new contract constructs your sales team signs within the first year, ingestion fixes after monitoring firmware updates scheduled by facilities without reference to billing, tax and regulatory changes on power resale, accounting drift when the chart of accounts changes, and hosting at $5,000 to $20,000 driven by meter reading volume and invoice history retention rather than user count.
One preliminary purchase pays for itself. Commission the contract read as a small paid piece of work before you ask anyone for a build quote. It converts the largest unknown into a known number and makes every quote you receive afterwards comparable.
What does the hybrid look like, and when is it the honest answer?
Keep the platforms, build the rating engine. This is the shape most operators should be considering and it is frequently missed because the conversation starts as a replacement conversation.
Your DCIM stays the record of physical truth for cabinets, circuits and connections, and the billing layer consumes that rather than duplicating it. Your accounting system stays the ledger, receiving posted invoices and revenue schedules with your dimensions applied, and nobody rebuilds general ledger functionality you already own. What you build is the middle: the structured contract model, the rating engine and the invoice with a defensible trail from every line back to the meter reading behind it.
There is a narrower version worth naming. Start with power and cross connects only, because those two carry most of the leakage. Remote hands and bandwidth follow in a second phase with their own budget and their own business case. That keeps the first commitment inside the first release band while addressing the money that is actually moving.
The hybrid stops being honest in one situation. The customer and contract record should live in the billing system, because it is the only place your commercial terms are fully represented. If you try to keep contracts in one system and rating in another, you have two versions of what a customer agreed to, and reconciling those is worse than the spreadsheet you started with.
Which should you choose, by operator size and stage?
Direct answers.
- Under 200 cabinets, one site, flat or simply committed power. Buy Ubersmith or EasyDCIM. Commission nothing.
- Any size with unreliable circuit to cabinet mapping. Fix the physical record first. No software decision is worth making until that is known.
- 300 to 600 cabinets, metered power, cross connects nobody has reconciled. Build the first release covering contracts, power rating and cross connects, keep the DCIM and the accounting system, and insist the parallel run is inside fixed scope rather than an option.
- Multi site operator with remote hands allowances and bandwidth commitments. Build the first release, then phase remote hands and bandwidth once the rating engine is proven against known invoices.
- Multi entity, multi currency, customers asking to see their own power draw. Build through to the third tier, but get internal billing correct before the portal, because a portal showing numbers your finance team does not yet trust creates support load rather than removing it.
One discipline regardless of stage. Before you decide anything, pull one month of your invoice workbook and one month of your cross connect work orders and reconcile them against each other. Then do the same for remote hands hours logged against remote hands hours billed. Whatever gap that exercise exposes is your business case, it usually takes an afternoon to find, and it recurs every month until somebody fixes the pipeline between operations and finance.
If you would rather scope this before committing budget, 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. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
- Organizations that scaled intelligent automation report an average cost reduction of 32% (up from 24% in 2020), and respondents expect an average 31% cost reduction over the next three years. Source: Deloitte (2022) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
Frequently asked questions
What does it cost to switch off Ubersmith or a spreadsheet based invoice run?
Usually less than expected on data and more than expected on discovery. Migrating open contracts, current meter mappings and any active disputes is necessary. Historical invoices can stay readable in the old system for the retention period your agreements require, which avoids weeks of migration for data nobody queries.
Agree that boundary in writing with your controller before scoping, because assumptions differ. The expensive part of switching is not the export, it is somebody reading every active contract and cataloguing the constructs.
What happens if our billing vendor changes pricing or its module packaging?
Check whether your fees scale with cabinets, customers or invoice volume, because a volume linked model means every good year permanently raises your software cost on a product that has not changed.
The exposure that matters more is the maintenance scripts and custom fields keeping your contract constructs alive inside the product. Those are unpriced and undocumented, and they are held by one person. That dependency, not the renewal, is what limits your options at the next negotiation.
How long does a colocation billing build take?
Twelve to sixteen weeks for the first release covering contracts, power rating and cross connects, then six to twelve months for the full platform. Add one complete billing cycle for the parallel run, which we treat as part of the project rather than an optional extra.
The pacing item is usually contract discovery rather than engineering. Operators who already maintain a clean contract summary move noticeably faster, and accounting posting design is often the second longest thread.
Can EasyDCIM or a DCIM product handle billing instead?
FNT Command and Sunbird dcTrack hold connection records properly and are the right tools for the physical estate, but they are not billing systems, so the connection lives in one product and the invoice is produced in another with a human between them.
EasyDCIM does bill and suits smaller operators. Judge it on one question: can it express committed kilowatts with tiered overage defined per customer, and can it start a recurring charge on the date a technician marks a connect patched.
How should we bill the A and B feeds on a dual corded cabinet?
Under normal operation the two feeds carry roughly the same load, so summing them counts the draw close to twice. Operators bill the higher side, a combined derived figure, or the sum with an agreed factor, and all three are defensible.
The important thing is that the rule is stored per contract rather than set globally. Your book almost certainly contains more than one convention, signed by different sales leads in different years, and a global setting quietly undercharges some customers and generates disputes with others.
Is a parallel run worth paying for?
Yes, and it is the line most likely to be cut under time pressure and most likely to pay for itself. It means producing one full billing cycle in both systems and reconciling every difference before you switch.
It typically costs around ten percent of the build. In the worked example it was $13,000 and it surfaced eleven cross connects that had been installed and never billed. The first cycle produced by a new system is also the one your customers scrutinise hardest.
What does adding a customer portal cost?
It pushes the project into the $280,000 to $400,000 range when combined with multi entity work. It is not just screens: it brings authentication, entitlement rules so a customer sees only their own cabinets, and a support surface you now have to staff.
Most operators are better served getting internal billing correct first. A portal showing usage that disagrees with the invoice creates more calls than it prevents, and the credibility cost of that is hard to recover.
What is the single biggest hidden cost in this category?
Contract constructs discovered late. A sales team closing deals for a decade has usually written more billing variations than anyone remembers, and each one is a rating path with its own proration and overage behaviour.
Ask your sales director how many exist, then have somebody read the contracts, because the two answers are rarely the same. Reserve ten to fifteen percent contingency specifically against this, because it is where the category overruns.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
Who owns the code when an agency builds my accounting software?
You should, outright, and the contract must say so with an explicit IP assignment clause rather than a usage license. Insist that the code lives in a repository you control from day one, so nothing, including the ledger schema and migration scripts, can be held back at the final invoice. Third-party libraries and any framework the agency reuses stay under their own licenses, and a clean contract lists exactly which those are.
How much do developers charge per hour for accounting software work?
In the competing quotes clients share with Digital Heroes, established US and UK agencies charge $90 to $200 an hour for accounting and fintech work, senior freelancers $60 to $150, and offshore teams $25 to $60. We price accounting builds as fixed-scope milestones instead, because hourly billing on ledger work rewards slow debugging. Compare total quoted cost against your workflow list rather than comparing rates against rates.
Can I extend QuickBooks with custom features instead of replacing it?
Yes, and it is often the right first step. QuickBooks Online has a public API, so an agency can build a custom layer for quoting, inventory, or field service that pushes clean transactions into QuickBooks, which stays your ledger of record. Roughly half of the accounting engagements Digital Heroes scopes start this way because it costs a fraction of a full build and leaves your accountant's workflow untouched.
How long until custom accounting software pays for itself?
Typical payback in Digital Heroes accounting projects is 18 to 36 months, driven by recovered labor hours and fewer billing errors rather than saved subscriptions. A business spending 30 hours a week on manual reconciliation and rebilling can justify a $75,000 build inside two years at ordinary bookkeeper rates. If your projected payback stretches past five years, extend your current tools instead.
What should I prepare before contacting an agency about accounting software?
Bring three things: the 5 to 10 workflows that hurt most today, sample data such as your chart of accounts and a redacted month of transactions, and a list of every system the software must connect to, including banks and payroll. You do not need a formal spec; a good agency writes that with you during discovery. In our experience buyers who arrive with concrete workflow pain get accurate quotes, and buyers who arrive with a feature wishlist get padded ones.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting 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 accounting 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 Layla.
Senior Account Manager · Wellness · Sydney · 1 post on the site
Published · Last updated .
