Skip to content
§
§ · hiring guide

How to Hire a Toll Back Office Software Development Company

Judge candidates on one thing first: whether they draw the transaction lifecycle as separate events on a ledger or as a table with a status column. The second answer means you are funding their tolling education. Brief two or three identically.

Custom Software Development software overview illustration for Tolling Back Office Software.
The short answer

Judge candidates on one thing first: whether they draw the transaction lifecycle as separate events on a ledger or as a table with a status column. The second answer means you are funding their tolling education. Brief two or three identically. Expect $150,000 to $320,000 for a first release in 16 to 22 weeks, and far more once violations and settlement arrive.

Every other system your agency buys is judged by the people who use it. A toll back office is judged by a bond trustee and an external auditor, neither of whom will ever log in. That changes what you are hiring for. You are not buying a nicer console for customer service. You are buying the numbers that feed a covenant test, and the evidence packet that decides whether a civil penalty survives a hearing.

This is a difficult category to buy because the incumbent vendors are genuinely competent. Conduent, TransCore, Kapsch TrafficCom and Emovis run back offices at scale and know tolling far better than most software firms ever will. The problem is contract shape rather than capability: your instance was configured against a specification written before the facility opened, and every change since has moved through a change order process with a lead time your board does not care about. So when you go looking for a development partner, you are not looking for someone who claims to beat those vendors at operations. You are looking for someone who can build the parts where your statute, your rate schedule and your leakage questions do not fit inside somebody else's product.

What a toll back office development company actually does

The customer portal is the part everyone imagines and the smallest part of the work.

The core is a transaction ledger where each posting carries its own resolution history: the read, the confidence score, the reviewer decision, the registered owner lookup request and response, the invoice, every notice, the settlement posting. No in place edits, everything replayable. That single design choice is what turns leakage from a mystery into a filterable work queue, and it is usually what pays for the project.

Around it sit four pieces of real engineering. Rate schedules as versioned, effective dated data by facility, lane, vehicle class and time of day, so a board approved peak period change is an afternoon rather than a change order. An image review workbench where confidence thresholds are yours to tune per camera and per lane, because review is priced per image and nobody else has an incentive to reduce the volume flowing into it. Registered owner lookup with your state motor vehicle interface for in state plates and NLETS handling for the rest, including retry logic and stale address detection. And a violations engine where the notice sequence, the clocks between steps and the required content of each notice are configuration your counsel can review, not scheduled jobs buried in code.

What it really costs in 2026

These are the delivery bands Digital Heroes works to across 2,000+ projects. Transaction volume matters less than the number of interoperability partners and state motor vehicle interfaces in scope.

ScopeCostTimeline
First release: transaction ingest, plate to account matching, image review workbench, pay by plate invoicing$150,000 to $320,00016 to 22 weeks
Adds violations engine with statutory escalation, registered owner lookup across states, hearing evidence packets$330,000 to $550,0008 to 14 months
Full back office with interoperability settlement, customer portal and covenant grade revenue reporting$550,000 to $900,00012 to 24 months
Operate and maintain15 to 20 percent of build cost a yearOngoing

Two costs are absent from every proposal. The first is access approvals. Out of state registered owner lookups run through NLETS, and authorisation comes from your state's control agency under a use agreement on a calendar nobody on the project controls. Your state motor vehicle interface has its own approval path. Start both in week one, because they will set your date for the violations phase regardless of how fast anyone codes.

The second is your exit from the incumbent. Read your current back office contract for a transition services clause before you brief anyone. If data extraction and transition assistance are not priced deliverables in that agreement, you will negotiate them from a weak position at exactly the moment you need the data, and the quote will reflect that. Agencies routinely discover this in month six of a build.

Signals of a strong partner

  • They draw the lifecycle as events on a ledger. Read, resolution attempt, owner lookup, invoice, notice chain and settlement posting as separate, replayable facts.
  • They ask what your bond covenants define as revenue. Reporting has to be built to the definitions your trustee and auditor already use, not to a dashboard convention.
  • They treat image review volume as an engineering target. Per camera thresholds, duplicate read retirement, and a measurable link between threshold changes and dispute rate.
  • Statutory clocks are data, not jobs. Ask what happens when the legislature shortens a window by ten days, and listen for whether counsel reviews the change as configuration.
  • They separate the three integration problems. A roadside lane controller, a state motor vehicle interface and an interoperability file exchange are not variations of the same task.
  • Settlement is matched line by line. Daily variance exceptions rather than a monthly summary and a rejects file.
  • They tell you when a hosted platform is the right answer. One facility, modest volume, stable rates and no reciprocity obligations, and building is the wrong use of public money.

Red flags

  • A transactions table with a status column. That is an ecommerce checkout, and tolling will break it inside a quarter.
  • Enthusiasm about building a new plate reader. Machine reading is a commodity. The value is in the routing layer around it.
  • No questions about your notice sequence. Escalation content and timing are state law, and a firm that has not asked has not built a violations programme.
  • Interoperability described as a file import. Settlement moves in both directions daily and small variances hide for months.
  • Any hesitation on code ownership. You are having this conversation because of a dependency you cannot exit, and repeating it would be remarkable.

Questions to ask on the first call

  1. Draw the transaction lifecycle for a plate read that fails optical recognition, goes to review, and resolves to a leased vehicle.
  2. How do we change a peak period rate approved by the board nine weeks from now?
  3. Who owns the confidence threshold per camera, and how quickly can we see the effect on review cost and disputes?
  4. What have you integrated on the roadside, and which lane controller protocols have you actually spoken?
  5. How do you handle NLETS responses and detect a stale registered address?
  6. What happens to the notice sequence when the legislature changes the window, and who reviews that change?
  7. How does a representative produce a hearing evidence packet, and how many clicks is it?
  8. How do you match interoperability settlement files line by line and raise a variance the same day?
  9. How does revenue reporting map to the definitions in our bond covenants and our annual audit?

A simple way to decide

Buy a paid discovery phase, and do it before your procurement for the build. Four to eight weeks with your strongest one or two candidates, each producing the same deliverable: a written specification your agency owns. It should carry the transaction ledger design, the rate schedule model, the review threshold approach, the notice sequence as configuration with counsel's sign off, the interoperability settlement design, the reporting definitions agreed with your finance team, an access approvals timeline for NLETS and your motor vehicle interface, and a fixed quote against milestones. That document also makes a far better basis for a competitive procurement than a wish list written internally.

Digital Heroes is the wrong choice for many authorities. One facility under roughly fifteen million transactions a year with a stable rate schedule and no reciprocity obligations should keep the hosted platform and spend the money on gantry maintenance and camera alignment. An agency with no permanent technical staff should not own a revenue system. If you want engineers by the month rather than delivery against a specification, hire contractors. Where the fit is real, Digital Heroes writes the product requirements document before any code exists, fields a team of 50-plus across 2,000+ delivered projects, and contracts through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law. The record is checkable 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.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
  2. 76% of developers are using or planning to use AI tools in their development process in 2024 (up from 70% in 2023), with current active use rising to 62% from 44%; 81% agree increasing productivity is the biggest benefit of AI tools. Source: Stack Overflow (2024) →
  3. Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
  4. Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
FAQ

Frequently asked questions

How long does it take to stand up a custom toll back office?

A first release covering transaction ingest, plate to account matching, image review and pay by plate invoicing typically ships in 16 to 22 weeks. Violations escalation and multi-state registered owner lookups add another two to four months. The schedule risk is rarely engineering. It is getting written confirmation of the current notice sequence and rate schedule from legal and finance, and securing lookup access approvals.

Who owns the code and the transaction data if a firm builds this for us?

Your agency should own the repository, the cloud infrastructure accounts, the database and an unrestricted right to hire a different firm to continue the work, written into the contract before kickoff. This matters more in tolling than almost anywhere, because the usual reason an authority looks at custom software is an existing dependency it cannot exit. Treat hedging on this point as disqualifying, whatever the price.

Why do counted vehicles end up unbilled?

Because billing a plate read is a chain and every link drops volume. The optical read may be low confidence, the review queue may age past a statutory notice window, the owner lookup may fail on a lease, a rental or a recent transfer, and the invoice may reach a stale address. Each loss looks small alone but they multiply, which is why leakage is rarely traceable to one cause without a full resolution history per transaction.

Should we replace our hosted back office vendor at all?

Not automatically. Established vendors run real back offices at scale, and for a single facility with modest volume, a stable rate schedule and no reciprocity obligations, hosting is cheaper than staffing your own. The case for building appears when every fee change becomes a change order, when you cannot investigate leakage without raising a ticket, or when your statutory violation sequence does not fit the product you were sold.

Can we build part of it and keep the vendor for the rest?

Often yes, and it is usually the lower risk path. A common split leaves transaction capture and account management with the incumbent while a custom layer takes image review routing, leakage analytics and hearing evidence assembly. The constraint is what data your contract entitles you to receive, in what format and how often, so read that clause before designing anything around it.

How does interoperability settlement work between agencies?

Agencies exchange away and home transactions daily in agreed file formats, with reject and correction cycles running behind the main flow. Because settlement moves in both directions, a small daily variance can persist unnoticed for months and then be found by an auditor. The technical requirement is line level matching with a same day exception when a variance appears, rather than a monthly summary and a rejects file nobody reads.

What should a hearing evidence packet contain?

At minimum the plate image, the machine read with its confidence, the human reviewer decision, the registered owner lookup result with its timestamp, the full notice history with delivery evidence, and the rate schedule in force at the moment of the trip. The practical test is whether a representative can produce all of it in one action. If it takes twenty minutes across three screens, staff quietly start waiving rather than defending.

How much does it cost to operate a custom back office each year?

Plan on 15 to 20 percent of the build cost annually for hosting, security work, interface upkeep and continued development. Separately, image review labour remains your largest variable cost, but owning the thresholds means you can actually reduce it. Lookup fees, postage on statutory notices and payment processing scale with transaction volume and should be modelled at your real numbers rather than quoted as unit prices.

What is the difference between a toll back office and a customer service system?

The back office is the revenue system: it ingests roadside transactions, resolves them to accounts or owners, invoices, escalates and settles with other agencies. The customer service system is the console and portal on top of it. Buyers often scope the second and assume the first, which is how projects arrive at month eight with a beautiful account screen and no defensible answer about leakage.

Can custom software really make rate changes faster?

Yes, if rate schedules are versioned effective dated data your own staff can edit rather than a configuration only the vendor touches. A board approved peak period change then takes an afternoon. On its own that agility rarely justifies a build. It matters because it usually arrives alongside unexplained leakage, a fixed image review cost and a violation sequence that no longer matches statute, and the combination is the case.

Should we build an MVP first or go straight to the full system?

MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.

What are the biggest mistakes first-time software buyers make?

Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.

What does a $50,000 custom software budget actually buy?

One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.

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.

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.

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.

Will custom software work with the tools we already use, like QuickBooks and Stripe?

Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.

How do I vet a software development agency before signing a contract?

Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.

What should I have ready before I contact a development agency?

Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.

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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply