Tolling Back Office Software: Custom Build vs Off the Shelf Platforms
Run one facility under roughly 15 million transactions a year with a stable rate schedule and no reciprocity obligations, and you should stay on a hosted platform.
On this page
Run one facility under roughly 15 million transactions a year with a stable rate schedule and no reciprocity obligations, and you should stay on a hosted platform. A vendor back office is cheaper than the staff you would need to run your own, and your leakage is probably a camera alignment problem. Building becomes defensible when every rate or statute change turns into a change order you cannot schedule.
What Conduent, TransCore, Kapsch and Emovis actually do well
It is 2:15 in the morning and the image review queue holds 38,000 unreviewed plate captures. Some are motorcycles photographed at an angle. Some are trailers obscuring the towing vehicle. A contracted review team in another time zone is clearing them at a rate that will not catch the oldest ones before the statutory notice window closes, at which point those transactions stop being revenue and become write-offs. Nobody on the authority side can see the queue depth, because the queue lives inside the vendor platform and surfaces once a month in a report.
That is a real operating problem, and it is not evidence that the vendors are bad at tolling. Conduent, TransCore, Kapsch TrafficCom and Emovis run real back offices at real scale, and they know this domain far better than any generalist software firm. They operate customer service centres with staff you would otherwise hire. They run image review operations. They handle interoperability file exchange, payment processing, notice printing and mailing, and the accounting that sits behind all of it. For a mid-sized authority, buying that as a service is not a compromise. It is the correct use of public money, and most authorities reading this should renew.
Be specific about what you are buying, though, because the value is operational rather than technological. You are buying people and a running system, not a product you control.
Where they stop: the contract shape, not the engineering
The structural problem is procurement, not code. These systems are specified years before a facility opens, delivered as a configured instance of a product designed for many agencies, and changed afterwards through a change order process. When your board approves a new peak period rate starting in nine weeks, or your legislature amends the notice sequence on unpaid tolls, the question is never whether the vendor can do it. It is what the change costs and whether nine weeks fits inside their release train. Authorities live with workarounds because the alternative is a procurement.
Underneath that sit three specific gaps. The first is that matching a transaction to an owner is a chain and every link leaks. A transponder read is easy and it is most of your traffic, which is exactly why the unhappy paths get underbuilt. Everything else has to be read by optical character recognition and then by a human when confidence is low, resolved to a registered owner through a state motor vehicle lookup for in-state plates and a request across the NLETS network for the rest, and both of those fail on leases, rentals, recent transfers and surrendered plates. Each link drops a percentage, and the drops compound. When an authority cannot explain the gap between gantry counts and posted revenue, it is almost never one leak. It is four small ones multiplying.
The second is that image review is a cost centre priced by the image. That gives the vendor no reason to reduce the volume flowing into review and gives you no lever to pull. Confidence thresholds sit where the vendor set them. Nobody is tuning them against your camera angles, your lighting at that gantry, or the fact that one lane has produced twice the review rate since a resurfacing job changed the vehicle approach.
The third is interoperability. The federal interoperability requirement in MAP-21 pushed the industry toward customers carrying one transponder through other agencies, which means you send transactions away daily and receive theirs, in agreed formats such as the E-ZPass Group interagency communications definition, with reject and correction cycles running behind them. Platform back offices handle this, but they typically hand you a summary and a rejects file rather than an investigable ledger. The failure mode is not dramatic. It is a small daily variance nobody has time to chase, repeated for eleven months, then discovered by an auditor.
The arithmetic: per-transaction and per-image fees versus a build
This category has an unusually clean per-transaction comparison, so run it properly. Take your hosted back office fee per transaction, multiply by annual transactions, and add image review priced per image reviewed. Then separate those two lines, because they behave differently. Transaction processing scales with traffic, which you do not control. Image review scales with how many images fail automated reading, which is an engineering variable somebody else owns.
Now price the third line, which never appears on an invoice. Add the transactions that aged past a statutory window because a queue was not visible. Add the penalties made unenforceable by an evidence packet nobody could reproduce at a hearing. Add the interoperability variances found by an auditor rather than by your team. On a facility financed with revenue bonds, those are not operating annoyances. They feed covenant tests a trustee checks.
In our delivery experience the crossover sits at roughly 15 million transactions a year, and it moves earlier with two conditions rather than volume: multiple interoperability partners, and a rate or fee schedule that changes more than once a year. A single facility with static rates can sit well above that volume and still be better served by a hosted platform. An authority changing rates twice a year with four reciprocity partners can be below it and still be paying more in change orders than a build would cost.
Cost to build a custom back office, plus migration and annual upkeep
These are Digital Heroes delivery bands. A focused first release covering transaction ingest from your roadside system, plate to account matching, the image review workbench and pay by plate invoicing runs $150,000 to $320,000 and ships in 16 to 22 weeks. That is a system your team uses daily, not a pilot. A full back office adding interoperability settlement, the violations engine with statutory escalation, a customer portal and covenant-grade revenue reporting runs $450,000 to $900,000 phased over 12 to 24 months.
Data migration is 10 to 25 percent on top and belongs at the upper end here. You are moving open accounts with stored value balances, transponder assignments, in-flight violations at different escalation stages, and a history you may need to produce at a hearing years later. Every one of those has a clock attached, and a migration that resets a clock creates an unenforceable penalty.
Budget 15 to 20 percent of build cost every year from year two. In tolling that money goes on the outside world: an interoperability format revision, a state motor vehicle interface change, a payment compliance update, and statutory amendments that must be reviewed by counsel and encoded as data.
What drives cost up here: the count of interoperability partners, since every agency pair has its own quirks in practice; the number of states you look plates up in, because each motor vehicle integration is its own effort; the payment stack, since kiosks, walk-up centres and stored value accounts each carry their own compliance scope; and the roadside interface, because older lane controllers speak protocols that need real integration work rather than an interface call. What keeps it down is starting with one facility, the current rate schedule and the existing violation sequence, and leaving the customer portal for phase two.
How to decide in a week, and what to take to your board
Run this before the next contract cycle. On Monday, ask for the current image review queue depth and the age of the oldest unreviewed capture, and time how long the answer takes to arrive. On Tuesday, take one day of gantry counts and try to reconcile them to posted revenue, naming the drop at each link in the chain. On Wednesday, pick one closed violation and assemble the hearing evidence packet by hand: the image, the read, the reviewer decision, the lookup result and the notice history. Time it. On Thursday, pull the last twelve months of interoperability settlement variances and check who found each one. On Friday, list every change order raised in the last two years for a rate or statute change, with cost and elapsed time.
Friday is usually the decision, and it is a number your board understands without translation. Monday and Wednesday tell you whether you have visibility or only reports.
Then fund a discovery phase before you fund a build. At Digital Heroes that means a signed product requirements document before any code exists, covering the transaction ledger and its replay guarantees, the resolution chain as first-class events, rate schedules as versioned effective-dated data your staff can change, the notice sequence as counsel-reviewable configuration, and acceptance criteria written as audit questions. Ask any firm to whiteboard the transaction lifecycle first: a team that draws a transactions table with a status column has built a checkout and is about to learn tolling on public money. You meet the named team, from more than fifty specialists, before anything is signed. We contract through India LLP, US LLC and UK LTD entities so the intellectual property assignment sits under law your own counsel reads, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. You keep the specification either way. We are the wrong firm for an authority with no permanent technical staff, because owning a revenue system means owning its operations.
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.
- 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) →
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
- EMARKETER reports that over 54% of mobile commerce transactions now happen within shopping apps rather than mobile browsers, underscoring the app channel's growing dominance of m-commerce. Source: EMARKETER (2025) →
Frequently asked questions
How long does it take to build toll violation processing software?
The violations engine is normally part of the second phase rather than the first. A focused first release covering transaction ingest, plate to account matching, image review and pay by plate invoicing ships in 16 to 22 weeks. Adding statutory escalation, interoperability settlement, a customer portal and covenant-grade reporting runs 12 to 24 months. Counsel review of the notice sequence is usually the pacing item, not development.
Why do toll transactions go unbilled even when the gantry counted the vehicle?
Because owner resolution is a chain and every link drops a share. The plate has to be read, reviewed when confidence is low, resolved to a registered owner through a state lookup or an out-of-state request, and then invoiced to an address that may be stale. Leases, rentals, recent transfers and surrendered plates each break a link. The drops compound, which is why the gap is rarely traceable to one cause.
How does interoperability settlement actually work between agencies?
You send away transactions to other agencies daily and receive theirs, in agreed file formats such as the E-ZPass Group interagency communications definition, with reject and correction cycles behind them. A customer may see a transaction from a facility hundreds of miles away arrive days after the trip. The risk is small daily variances nobody chases, so insist on line-by-line matching with a same-day exception rather than a monthly summary.
Can we own our rate schedule without a change order?
Only if rates are modelled as versioned, effective-dated data by facility, lane, vehicle class and time of day, changeable by your own staff. That is a design decision made at the start, not a feature added later. If a board approves a schedule that starts in nine weeks and your system needs a release, you do not control your own pricing policy regardless of who wrote the software.
What should be in the evidence packet for a violation hearing?
The image, the automated read with its confidence score, the human reviewer's decision and identity, the registered owner lookup request and response, the invoice, and the complete notice history with dates. The customer and the hearing officer should see the same packet. If assembling that takes a representative twenty minutes across three screens, your dispute cost exceeds the toll by orders of magnitude and staff will quietly start waiving instead.
Do we own the code if an agency builds our back office?
Get it in writing before kickoff. You should own the repository, the cloud accounts and an unrestricted right to hire a different firm. At Digital Heroes the client owns the code from the first commit. This matters more here than in most sectors, because the reason an authority is having this conversation at all is usually a dependency it cannot exit, and repeating that with a new supplier solves nothing.
How do we reduce image review cost without raising disputes?
Own the confidence thresholds per lane and per camera, then move them deliberately and measure both review cost and dispute rate the same week. Retire images automatically where a second camera on the same vehicle already produced a high confidence read. Plate reading itself is a mature commodity, so the value is not a better reader. It is the routing layer deciding which reads reach a human and in what order.
What is the difference between a roadside system and a back office?
The roadside system detects vehicles, reads transponders and captures images at the gantry. The back office turns those events into money: owner resolution, account posting, invoicing, violation escalation, interoperability settlement, customer service and revenue reporting. They are usually different vendors under different contracts, and the interface between them is where a build most often has to do real integration work rather than call a published interface.
Is it worth building custom software just to change rates faster?
On its own, rarely. Rate agility becomes a build case when it appears alongside other conditions: image review cost you cannot influence, leakage questions you cannot answer without a vendor ticket, interoperability variances found by auditors, or violation hearings lost on evidence production. Two or more of those together, plus a genuine change order history, is the argument. One of them is a contract negotiation, not a project.
How do we vet a developer for a toll back office?
Ask them to whiteboard the transaction lifecycle before anything else. A team that has done this draws the read, the resolution attempt, the owner lookup, the invoice, the notice chain and the settlement posting as separate events on one ledger. Then ask what happens when your legislature shortens a notice window by ten days, and listen for whether counsel can review that change as data rather than code.
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.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
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.
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.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
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 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.
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.
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 Kabir.
QA Lead · Mobile · Delhi · 1 post on the site
Published · Last updated .
