How to Hire a Street Lighting Management Software Company
Ask every candidate how they would reconcile your utility's unmetered billing file against your asset register when the identifiers do not match. If the answer is a lookup table, they have not seen a real one.
On this page
Ask every candidate how they would reconcile your utility's unmetered billing file against your asset register when the identifiers do not match. If the answer is a lookup table, they have not seen a real one. Expect $50,000 to $110,000 over 10 to 14 weeks for register, billing reconciliation and outage-to-work-order, and $140,000 to $300,000 for the full platform.
An unmetered street lighting bill is not a measurement. It is a count of fixtures by wattage class, multiplied by assumed annual burn hours from the tariff sheet, multiplied by a rate. The count comes from a file the utility maintains, and your city has almost certainly never audited it against the poles that exist. You are hiring someone to build a system whose main job is proving a bill wrong, and most of the firms bidding will show you a map instead.
That is what makes this category difficult. The products in the space are control management systems sold beside hardware. Telensa built its platform around its own telecells. Itron Streetlight.Vision handles multiple node vendors, which matters in a city that bought controllers in three waves. Signify Interact City is strong inside its own ecosystem, and Ubicquia and Tvilight are hardware-led. Every one of them sees what it is attached to, and your estate includes thousands of luminaires with no node at all. The TALQ interoperability standard exists because the industry knows this, and standardising a control interface still does not give you a register, a bill check or a work order.
What a street lighting development company actually does
The register comes first, and the part that separates a real firm from a hopeful one is that a good register is honest about uncertainty. Each record is a pole with a location, ownership and structure type, carrying one or more luminaires with fixture type, wattage, control type, install date and a source-of-truth flag. That last field matters more than it sounds. A record confirmed by a field survey eighteen months ago is a different thing from a record inherited from a conversion contractor's closeout spreadsheet, and a system that cannot tell them apart produces a clean-looking database that is as wrong as the spreadsheet it replaced.
Then billing reconciliation, which is the feature that pays for the project. Ingest the utility's unmetered file each cycle, match it to the register on identifier and location, and produce three lists: billed but not in your register, in your register but not billed, and billed at a wattage that disagrees. Compute the expected charge yourself from the tariff schedule and its printed burn hours, and show the variance with location evidence attached. That report is the artefact that gets bills corrected.
Then the outage loop across three channels. Resident reports through 311 or SeeClickFix, controller alarms from whichever vendor portals you have, and crew observations on patrol. All three create or update one issue against one pole, deduplicated so four residents reporting the same dark corner produce one work order and four notification subscriptions. The crew gets a pole identifier, coordinates, fixture type, expected part and last work history, rather than a ticket saying the light near Elm and Fifth is out, which describes four poles.
What it really costs in 2026
Digital Heroes delivery bands from our own work, not an industry average.
| Scope | Cost | Timeline |
|---|---|---|
| First release: pole and luminaire register, field survey app, utility billing file reconciliation, citizen report to work order | $50,000 to $110,000 | 10 to 14 weeks |
| Full platform: multi-vendor controller adapters, energy and burn hour modelling, savings verification, capital programme tracking, public outage map | $140,000 to $300,000 | 6 to 10 months |
| Each additional controller vendor adapter | $12,000 to $30,000 | 2 to 4 weeks |
| Support and tariff-change maintenance | 15% to 20% of build per year | Retainer |
The first missing line item is not software at all. Somebody has to walk or drive the estate and confirm what is actually on each pole. If your register is going to be trustworthy, budget the survey, do it with the app you just built, and treat it as part of the project rather than a surprise in month four. Cities that skip it get a database with the same errors and better fonts.
The second is the savings guarantee. If your LED conversion was financed through an energy savings performance contract, verification for lighting retrofits is normally a stipulated calculation rather than metered consumption, because these circuits are unmetered by definition. The guarantee is therefore only as good as the fixture count and wattage assignment, which is the same register you cannot currently trust. When a council member reads the ESPC schedule and asks in a public meeting whether the guaranteed savings are real, you need a traceable answer. Quotes rarely price that reporting path.
Signals of a strong partner
- They ask for your last utility billing file and your GIS layer. A firm that wants to see how far apart they are before quoting has done this before.
- They describe matching as spatial plus fuzzy plus a human review queue. Identifiers will not line up. Anyone promising a clean join has not opened a real file.
- They ask about poles carrying two luminaires on different circuits. Your estate has them, and a one-to-one model will corrupt your counts permanently.
- They propose skipping controller integration in release one. Register plus reconciliation plus work orders delivers the money and works with zero connected nodes.
- They name what they have integrated. Itron, Telensa or Signify on the controller side, Cityworks, Accela or SeeClickFix on the city side. Named projects, not claimed capability.
- They raise accessibility before you do, because a public-facing outage map at a public agency brings conformance obligations and a different security posture.
- Ownership settled in writing before kickoff. Your lighting register is a public asset record that will outlive several vendors. At Digital Heroes the client owns the repository from the first commit.
Red flags
- The pitch leads with dimming and energy analytics. Those are node features. If the register is wrong, the analytics are decorative.
- No mention of the field survey. Either they do not know it is needed or they know and are letting you discover it later.
- A single vendor controller assumption. Most estates are mixed after a decade, and you will operate two vendors at once during a transition.
- Work orders treated as an export. A crew needs a pole identifier and a part, in the system they already use. A CSV to the depot is not integration.
- Reluctance to be measured on the first variance report. That report is the payback. A confident firm will happily tie a milestone to it.
Questions to ask on the first call
- Our utility file uses their identifiers and our GIS uses ours. How do you match them, and what happens to the residue?
- How do you model a pole with two luminaires on separate circuits, and how does that flow into a wattage count?
- What does your system do with a fixture that appears in the billing file and does not exist in the field?
- How do you compute the expected charge from our tariff schedule, and where do the burn hours come from?
- How would you substantiate our ESPC savings figure for a council meeting?
- Four residents report the same dark pole in one evening. What does the crew receive?
- Which controller platforms have you integrated, on which project, and what broke?
- How does a knockdown replacement or a capital conversion appear against the same asset record?
- What would you deliver in the first twelve weeks if we have never surveyed the estate?
A simple way to decide
Buy a paid discovery phase rather than picking a proposal. Give your two strongest candidates the same inputs, your latest utility billing file and your current GIS lighting layer, and require the same output: a written specification covering the register model with confidence flags, the matching approach, the reconciliation report design, the work order flow, the survey plan and acceptance criteria. You own that document. It makes the next quotes comparable for the first time, and it is useful even if you decide not to build.
Digital Heroes is the wrong choice if the utility owns your poles and maintains them under a full service tariff. Ask for their inventory file annually and audit a sample on foot. Under roughly 1,500 lights, a maintained GIS layer plus your existing work order tool is proportionate. Above that, on an unmetered tariff you cannot verify, we work PRD-first, with 2,000+ projects behind us and a company verifiable through D-U-N-S, Clutch and Trustpilot.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Global retail loses an estimated $1.73 trillion annually to inventory distortion (out-of-stocks and overstocks), equal to about 6.5% of global retail sales, despite $172 billion spent on improvements in the past year. Source: IHL Group (2025) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
Frequently asked questions
How much does custom street lighting management software cost?
A first release covering the pole and luminaire register, a field survey app, utility billing file reconciliation and citizen report to work order runs $50,000 to $110,000 over 10 to 14 weeks. The full platform adding multi-vendor controller adapters, energy and savings modelling, capital programme tracking and a public outage map runs $140,000 to $300,000 across six to ten months. Each extra controller vendor is a separate adapter.
Do we need controller integration in the first release?
Usually not, and skipping it is the cheapest way to keep the first phase small. The register, the billing reconciliation and the work order flow deliver the financial return and work with zero connected nodes on the estate. Add adapters later, normalised behind one internal model so your work order flow does not care whose node reported the fault. You will change vendors eventually.
Why does the field survey cost extra?
Because it is labour, not software. Somebody has to confirm what is physically on each pole, since your current data is a merge of a GIS layer, a utility file and a conversion contractor's closeout spreadsheet, all of which disagree. Build the survey app first, then survey with it, and record a source-of-truth flag per record so the system knows which entries were confirmed and which were inherited.
Can this substantiate an ESPC savings guarantee?
It can, and that is often the reason a council approves the budget. Verification for lighting retrofits is typically a stipulated calculation rather than metered consumption, because the circuits are unmetered. The calculation depends entirely on fixture count and wattage assignment, so a register with confirmed records and dated sources is what makes the guaranteed figure defensible in a public meeting rather than a number from a contractor's spreadsheet.
When should a city not build this?
When the utility owns the poles and lights and maintains them under a full service tariff, and you have no conversion programme running. Ask for their inventory file annually and audit a sample on foot instead. Also stay off a build under roughly 1,500 lights with manageable complaint volume, where a maintained GIS layer and your existing work order system are proportionate to the problem.
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.
What does upkeep on a custom inventory system cost per year?
Budget 15 to 20 percent of the build cost per year, so a $50,000 system runs roughly $8,000 to $10,000 annually across Digital Heroes maintenance contracts. That covers hosting, security patches, integration updates when Shopify or Amazon change their APIs, and small improvements. Skipping it is how a channel sync quietly breaks in month nine and corrupts your counts.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How much does custom inventory management software cost for a small business?
A single-location system with receiving, stock movements, and barcode scanning typically runs $15,000 to $40,000, based on Digital Heroes delivery experience across 2,000+ projects. Multi-warehouse, multi-channel builds land between $40,000 and $120,000, and manufacturing or forecasting features push past that. The biggest cost driver is logic rather than screens: lot tracking, unit conversions, and channel sync each add real engineering time.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
How many SKUs are too many for managing inventory in Excel or Google Sheets?
Excel and Google Sheets typically start failing past roughly 1,000 SKUs, more than one sales channel, or more than two or three people editing stock levels. The failure mode is not the row count but stale, conflicting edits that cause oversells and phantom stock. If someone on your team spends hours each week reconciling the sheet against the shelf, you have already outgrown it.
Who owns the code when an agency builds my inventory system?
You should, in full, with intellectual property assignment written into the contract before any payment is made. Insist on the code transferring to a repository you control no later than final payment, plus hosting and domain accounts in your own name. If an agency offers to license you their platform instead of assigning the code, you are buying another Cin7 with fewer features.
What should a post-launch support agreement for inventory software cover?
Written response times for stock-critical failures measured in hours, monitoring that alerts on sync failures and count drift before your customers notice, and a monthly window for small fixes and integration updates. It should also confirm that you hold the code, hosting access, and documentation, so switching vendors stays possible. Across Digital Heroes support engagements, a broken channel sync during peak week is the single most expensive gap.
How do I vet a software agency for an inventory project specifically?
Ask three technical questions before discussing price: how they stop two simultaneous orders claiming the same last unit, whether stock is stored as an append-only movement ledger or a single overwritable quantity field, and how they test channel sync under load before launch. A team that answers fluently has built inventory systems before; one that steers the conversation to screens and design has not. Then ask for a reference from a client whose system has survived at least one peak season.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Who can build a custom inventory management software system?
Digital Heroes builds custom inventory management 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 inventory management 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
Published · Last updated .