How Much Does Toll Back Office Software Cost in 2026?
A custom toll back office runs $150,000 to $900,000, and the two things that move the number most are how many interoperability partners you settle with and how many state motor vehicle departments you look plates up in.
On this page
A custom toll back office runs $150,000 to $900,000, and the two things that move the number most are how many interoperability partners you settle with and how many state motor vehicle departments you look plates up in. Each partner pair has its own file quirks in practice, and each motor vehicle interface is a separate integration with its own access agreement. One facility, one state and no reciprocity obligations sits near the bottom of the range. Six settlement partners and lookups in nine states sits near the top before you add a customer portal. A first release covering ingest, matching, image review and pay by plate invoicing is $150,000 to $320,000 over 16 to 22 weeks in our delivery experience.
The bands a toll back office build falls into
The first release band is $150,000 to $320,000 over 16 to 22 weeks. That covers transaction ingest from your roadside system, a ledger where every posting carries its full resolution history, plate to account matching with confidence based routing, the image review workbench with per camera thresholds, registered owner lookup, and pay by plate invoicing. It is a system your team uses daily rather than a pilot.
The full back office band is $450,000 to $900,000 phased over 12 to 24 months. That adds interoperability file exchange in both directions with line level settlement matching, the violations engine with statutory notice sequences and clocks held as configuration, a customer account portal and representative console sharing one view, and revenue reporting built to the definitions in your bond covenants.
There is a narrower option that some authorities take first, and it is worth knowing about. The transaction ledger and image review workbench alone, running alongside your existing platform in read and analyse mode rather than replacing it, runs $70,000 to $120,000 over eight to twelve weeks. It does not process a single toll. It does let you answer, without a vendor ticket, where transactions are being lost and what your review volume actually costs.
What drives a toll back office build up
Interoperability partner count is the first driver and it does not scale linearly. Every hub and every agency pair has its own quirks once files start moving daily in both directions, and the reject and correction cycles behind the main flow are where the effort accumulates. Two partners is a format. Six is an operations capability with its own exception queue.
State motor vehicle interfaces are the second. In state lookups and out of state requests through the National Law Enforcement Telecommunications System are different problems, and each state you add carries its own access agreement, its own response behaviour and its own failure modes on leases, rentals and recent transfers.
The roadside interface is the third and it is where generalist estimates go wrong. Older lane controllers speak protocols that require a real integration rather than an application programming interface call, and the only way to price it honestly is to see the interface specification first.
The payment stack is the fourth. Card present kiosks, walk up centres and stored value accounts each carry their own compliance scope, and that scope is engineering work rather than a policy document.
Statutory complexity is the fifth. A notice sequence with four steps, differing content requirements and a registration hold at the end costs more than a two step sequence ending in collections referral.
What keeps the number down
Start with one facility, the current rate schedule and the existing violation sequence exactly as it stands. Every authority is tempted to redesign the notice sequence during the build. Do that afterwards, once the mechanism exists and counsel can review a rule change as data.
Leave the customer portal to phase two. The representative console and the account model deliver most of the operational value, and a portal built before the transaction ledger is stable will need rebuilding.
Do not build a plate reader. Machine reading of plates is a mature commodity and the useful work is the routing layer around it: which reads go to a human, in what order, with what context, and what happens when the same plate is read differently by two agencies.
Sequence interoperability after the ledger. Settlement matching against a ledger that already records every posting with its lifecycle is straightforward. Settlement matching against a partially built ledger is a rewrite waiting to happen.
Finally, get written confirmation of the current notice sequence and rate schedule from legal and finance before kickoff. In our delivery experience that document, not the engineering, is the most common cause of schedule slip in this category.
A worked example that adds up
A single facility authority with roughly twenty million annual transactions, one roadside system, in state plate lookups plus out of state requests, no interoperability partners in phase one, and an existing violation sequence being carried over unchanged.
- Roadside transaction ingest, including the lane controller interface and reconciliation against gantry counts: $58,000
- Transaction ledger with full resolution history, no in place edits and a complete audit trail: $46,000
- Plate to account matching with confidence scoring and routing rules: $40,000
- Image review workbench with per camera and per lane thresholds, reviewer productivity and quality sampling, and automatic retirement of duplicate reads: $52,000
- Registered owner lookup covering in state motor vehicle integration and out of state requests, with retry logic and stale address detection: $38,000
- Pay by plate invoicing and payment acceptance: $34,000
- Rate schedules as versioned effective dated data editable by your own staff: $16,000
- Discovery, testing and a parallel run against the existing platform: $28,000
Total $312,000 over 21 weeks. Adding the violations engine with statutory escalation and a hearing evidence packet typically adds $90,000 to $160,000. Each additional state motor vehicle interface adds $12,000 to $25,000, and each interoperability partner adds $25,000 to $45,000 once the first exchange is built.
How the spend phases
Weeks one to four are discovery and they are unusually document heavy here. You need the roadside interface specification, the current rate schedule signed off by finance, the notice sequence confirmed by counsel, and a real month of transaction data with its gaps intact. Roughly ten percent of the budget goes here and it is the ten percent that prevents the rest from being a guess.
Weeks three to ten build ingest and the ledger. Nothing user facing appears in this window, which makes it the phase most likely to be compressed and the phase least able to survive compression.
Weeks eight to sixteen deliver matching, image review and owner lookup. Image review is the largest single line and it is also the one that starts paying immediately, because per camera thresholds you control let you move review volume in the first month.
Weeks fourteen to twenty two cover invoicing, rate schedules and a parallel run where both systems process the same transactions and the results are compared daily. Do not skip the parallel run on a revenue system with covenant reporting attached to it.
The ongoing costs nobody quotes
Image review labour is the largest running cost in any back office and it does not disappear when you build. What changes is that the volume becomes an engineering target rather than a fixed line, because you own the confidence thresholds per lane and per camera. Model it as cost per transaction and track it weekly, since a resurfacing job that changes vehicle approach angles can move it without warning.
Plate lookup fees are charged per request in most states, and out of state requests carry their own cost. Those scale with unmatched volume, which is another reason the matching chain deserves attention.
Hosting and infrastructure for a system of this shape typically runs $1,500 to $5,000 a month, with the transaction ledger being the growing component. A twenty million transaction facility accumulates a large audit trail and you cannot prune it, because the resolution history is the evidence in a hearing.
Notice delivery is a real per item cost, and physical mail is unavoidable for statutory notices in most states.
Support and enhancement typically runs 15 to 20 percent of the build cost annually. In this category the enhancement half concentrates on rate changes, statutory updates and new interoperability partners, all of which are recurring rather than exceptional.
Comparing a build against your current renewal
This is the comparison most authorities do badly, because the hosted platform fee looks like the whole cost and it is not.
Start with the fee itself, then add every change order raised in the last three years. Rate changes, fee schedule updates, statutory notice changes and report requests all show up there, and the pattern of that spend tells you more than the base fee does. Then add the lead time on each of those changes. A board approved peak period rate that could not start for nine weeks has a revenue cost, and your finance team can compute it because they know the rate differential and the traffic.
Then add image review. Ask what you paid per image reviewed last year and whether that unit cost has ever gone down. If it has not, you are carrying a variable cost with no lever attached to it.
Then add the leakage you cannot explain. Take last year's gantry counts against posted revenue, and be honest about how much of the gap you could actually account for. You do not need an industry benchmark for this. Your own unexplained variance is the number, and if the answer to why is a vendor ticket rather than a query, that dependency is the real subject of the business case.
When buying beats building
Do not build if you run a single facility under roughly fifteen million transactions a year with a stable rate schedule and no reciprocity obligations. A hosted back office from Conduent, TransCore, Kapsch TrafficCom or Emovis is cheaper than the staff you would need to run your own, and your leakage is more likely a camera alignment problem than a software problem. Do not build if your agency has no permanent technical staff, because owning a revenue system means owning its operations, its on call rota and its audit.
Those vendors run real back offices at scale and know tolling better than any generalist software firm. The case for building is not that they are poor operators. It is that a system procured against a specification written before your facility opened, delivered as a configured instance of a multi agency product and changed through a change order process, will always lag your board and your legislature.
Build when two or more of these are true. Your rate or fee schedule changes more than once a year and every change is a change order. Your image review cost per transaction has never fallen. You cannot answer a leakage question without asking your vendor. Your violation programme has lost hearings on evidence production. Or your interoperability variances are found by auditors rather than by your own team.
When you are ready to turn this into a specification, 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. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- 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) →
- The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (2025) →
Frequently asked questions
What is the total cost of a custom toll back office system?
A first release with transaction ingest, plate to account matching, image review and pay by plate invoicing runs $150,000 to $320,000 over 16 to 22 weeks in our delivery experience. A full back office adding interoperability settlement, the violations engine, a customer portal and covenant grade revenue reporting runs $450,000 to $900,000 phased over 12 to 24 months.
The number of interoperability partners and the number of state motor vehicle interfaces drive most of the variance in any quote.
What does a toll back office cost to run each year?
Image review labour remains the largest running cost, but building changes it from a fixed unit price to an engineering target, because you own the confidence thresholds per lane and per camera. Track it as cost per transaction weekly, since a resurfacing job can move review volume without warning.
Plate lookup fees are per request, notice delivery has a real per item cost, hosting runs roughly $1,500 to $5,000 a month, and support and enhancement runs 15 to 20 percent of the build annually.
How long does it take to build toll violation processing software?
A first release covering ingest, matching, image review and invoicing typically ships in 16 to 22 weeks. Adding the violations engine with statutory escalation, multi state registered owner lookups and a hearing evidence packet usually adds another two to four months depending on how many motor vehicle interfaces are in scope.
The schedule risk is rarely engineering. It is obtaining written confirmation of the current notice sequence and rate schedule from legal and finance.
Is building cheaper than a Conduent or TransCore hosted back office?
Below roughly fifteen million transactions a year on a single facility, no, and we would tell you to stay hosted. Above that, the honest comparison is not fee against build cost. It is the fee plus three years of change orders, plus the revenue cost of lead time on rate changes, plus an image review unit price that has never fallen, plus the leakage you cannot currently explain without a vendor ticket.
Those vendors are capable operators. The problem being solved is contract shape rather than capability.
How much does interoperability settlement add to the build?
Roughly $25,000 to $45,000 per partner once the first exchange is built, with the first one costing more because the two directional posting model and the line level matching come with it. Files move both ways daily with reject and correction cycles behind them, so each partner brings its own exception queue rather than only a format.
Sequence this after the transaction ledger. Settlement matching against a partially built ledger is a rewrite waiting to happen.
What does each additional state motor vehicle interface cost?
Between $12,000 and $25,000, covering the access agreement work, the request and response handling, retry logic and stale address detection. In state integration and out of state requests through the National Law Enforcement Telecommunications System behave differently and both need handling.
Lookups also carry a per request fee that scales with unmatched volume, which is a further reason to invest in the matching chain rather than the lookup volume.
Can we build just the ledger and image review to diagnose leakage first?
Yes, and for an authority that cannot currently explain a gap between gantry counts and posted revenue it is often the right first step. A read and analyse layer running alongside your existing platform, holding the transaction ledger and the image review analytics, runs $70,000 to $120,000 over eight to twelve weeks.
It processes no tolls. It does tell you where transactions are lost and what your review volume genuinely costs, which is usually enough to decide whether the full build is justified.
Is it worth building custom software just to change toll rates faster?
On its own, probably not. Rate schedules as versioned effective dated data that your own staff can edit was $16,000 in the worked example above, and that alone does not justify a programme.
It matters because rate agility rarely arrives alone. It usually sits beside unexplained leakage, a fixed image review unit cost and a statutory sequence that does not fit the product, and it is that combination rather than any single symptom that carries the business case.
Do we own the code if an agency builds our back office?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more in tolling than almost anywhere else, because the reason most authorities look at custom software in the first place is a vendor dependency they cannot exit. Treat any hedging on ownership as disqualifying.
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.
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 happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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.
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.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
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 Ishaan.
Shopify Plus Tech Lead · Delhi · 2 posts on the site
Published · Last updated .
