Transit Agency Operations Software: Custom Build or Buy Trapeze and Optibus
Buy. Under roughly 50 peak vehicles on fixed route, with a simple bargaining unit and no paratransit obligation of scale, Optibus or a Trapeze module will serve you and a build would consume capital that belongs in service hours.
On this page
Buy. Under roughly 50 peak vehicles on fixed route, with a simple bargaining unit and no paratransit obligation of scale, Optibus or a Trapeze module will serve you and a build would consume capital that belongs in service hours. Building wins once your labour agreement carries rules no product expresses and dispatch is carrying them by hand at four in the morning.
What Optibus, Trapeze, Init and Clever Devices actually do well
It is 4:20 in the morning. Three operators have called out. Your dispatcher is holding a printed runcut, a clipboard listing the extraboard in seniority order, and a mental model of who has worked into overtime this week and who is protected by a guarantee. Nothing on that desk is software, and the products are not to blame for it.
Optibus is genuinely good at generating an efficient runcut, and the optimisation behind it represents work you should not attempt to reproduce. GIRO HASTUS has been doing the same job at scale for decades. Init and Clever Devices know vehicle systems, automatic vehicle location and passenger counting, and they know what those look like on a real bus rather than on a test bench. Trapeze Group covers a wide operational footprint including paratransit, and Via has moved microtransit and demand response scheduling forward considerably.
All of them will beat a spreadsheet. If you operate under about 50 peak vehicles on fixed route only, with one straightforward bargaining unit and no complementary paratransit obligation of any size, buy the scheduling product, add a modest dispatch tool, and put the remaining money into service. We say that to agencies regularly and it costs us work.
Where they stop: the labour agreement is where transit operations lives
Agencies buy scheduling software and are then surprised it does not run operations. The scheduled cost of service is set at the runcut. The actual cost is set at four in the morning by whoever fills the open work, and that decision is governed by a document negotiated locally that changes every contract cycle.
Pick rules. Spread time penalties. The guarantee. Report and travel allowances. Who may be held over and for how long. The order in which the extraboard is offered work, and what happens when nobody accepts. None of that is in any product, because it is your agreement and not their market. So the software produces a plan and a human turns the plan into reality using rules the software does not know, which makes that human your single point of failure. When they retire, the agency loses the only working copy of how dispatch actually works.
The pick is the second place products stop, and it is the most consequential week of your operating year. Operators select work in seniority order and every selection constrains the next. Mis-state a run's spread or platform time, or offer a run that violates the agreement, and you have a grievance, a rerun of the pick and an operator relations problem that lasts a year. Most agencies run it on paper in a room, reconciling a runcut from the scheduling product against a seniority list from human resources (HR) and a leave calendar from somewhere else.
The third gap is the one that reaches Washington. Formula funding depends on data reported to the National Transit Database, and the definitions are specific. Revenue hours are not pull out to pull in. Deadhead does not count as revenue service. A dropped trip changes delivered service and should change the number. In most agencies these figures are reconstructed after the fact from a scheduled runcut, an odometer report, a farebox summary and a passenger counter feed nobody fully trusts. That reconstruction is legitimate work and it is also the point at which you stop being able to defend your own numbers in a review.
Custom versus off the shelf: the arithmetic per coverage decision
Seat licences are the wrong currency here, so price this in premium hours instead. In Digital Heroes delivery experience a focused first release runs $90,000 to $180,000 across 12 to 18 weeks. Midpoint $135,000, plus migration and four years of support, puts five years near $251,000, so roughly $50,000 a year, or about $200 per working weekday.
Now count your open runs. If your dispatch office fills twelve pieces of open work on an average weekday, and one in six is currently filled at a premium that a correctly ordered eligible list would have avoided, at an average avoidable premium of $110 an occurrence, that is $220 a day. The build pays for itself on that alone.
So the crossover sits near twelve open runs a day, which in most agencies means somewhere between 120 and 180 peak vehicles. Below that, the daily leak is real but smaller than the build, and a product plus a good dispatcher is the correct answer. Above it, the leak compounds every operating day and nobody is measuring it, because ask any agency what a covered absence costs against a straight assignment and the honest answer is that it shows up at payroll a fortnight later.
One adjustment to make before you use that number. If you run two bargaining units, double the rule work and move the crossover out. If you run fixed route and demand response as two separate operations with separate operator pools, move it in, because the shared availability model is where the larger saving sits.
What a custom build actually costs, from kickoff to steady state
A focused first release covering runcut import from your existing scheduling tool, daily dispatch with extraboard and absence coverage, and clean capture of the service actually delivered runs $90,000 to $180,000 in 12 to 18 weeks. That is a system the dispatch office uses at four in the morning on day one. A full platform adding the pick engine, real time adherence from vehicle location data, an operator self service portal, payroll export and federal reporting runs $250,000 to $600,000 phased over 9 to 18 months.
Data migration runs 10 to 25 percent of the build. The runcut is easy. The expensive parts are the seniority list with its ties and adjustments, leave balances that currently live in three places, and operator qualifications and licence and medical certificate expiry dates, which usually exist as paper in a supervisor's file cabinet and have to be keyed and verified before the pick engine can validate anything.
Year two and each year after runs 15 to 20 percent of build cost annually, and in transit that is not optional. Every contract cycle produces a new rule version. A system nobody funds after go live stops matching the agreement within two rounds, and a dispatcher who finds one rule wrong stops trusting the whole eligible list.
The line that arrives around month seven is payroll. Agencies commonly run older payroll systems that need file based interfaces with careful reconciliation, and this is the integration that decides whether operators trust the system at all. Get it wrong once and you will spend a year rebuilding confidence you could have kept.
The four situations where building wins
Regulatory fit. National Transit Database definitions have to be applied to a clean event log rather than reconstructed, so a reviewer asking how a number was produced gets lineage. Complementary paratransit under 49 CFR Part 37 carries its own service criteria. Your Public Transportation Agency Safety Plan under 49 CFR Part 673 needs operational data you can produce on request. And labour protective arrangements under 49 U.S.C. 5333(b) mean employment terms are a federal grant condition, not just a local negotiation.
Scale economics. Past roughly twelve open runs a day the avoidable premium alone covers the build, and it recurs every operating day.
A workflow that is your actual capability. The coordination logic between the agreement, the extraboard and the day is the agency. It should not live in one dispatcher's head, and no vendor will encode a document they did not negotiate.
Integration sprawl across three or more systems. A scheduling product, vehicle location and passenger counter hardware, a farebox, a payroll system, human resources for seniority and leave, and General Transit Feed Specification output for riders and third parties. One operator record and one vehicle record underneath all of it is the build.
How to decide in a week, then commission a written specification
Reconstruct one week of coverage. Take last week's dispatch log and, for each piece of open work, write down who filled it, what it cost against a straight assignment, and who else was eligible and available at the time in correct order. Then mark every occurrence where a cheaper eligible option existed.
Two things come out of that exercise and both are useful whatever you decide. The first is a real number for the daily premium, which most agencies have never seen and which is the only credible input to this decision. The second is the list of rules your dispatcher applied that exist nowhere except in the agreement and their memory. Write those down. That list is the specification.
If the week produced almost no avoidable premium and the rule list is short, keep your product and spend the money on service. If the rule list runs to two pages and nobody else in the building could have filled the work correctly, you already know the answer.
Then buy a specification rather than a build. At Digital Heroes that means a signed product requirements document covering the operator record, the work rules as versioned configuration with effective dates, the offer sequence and acceptance criteria, produced before any code exists. You keep it either way, so take it to three other firms and get quotes priced against the same document, which is the only way procurement ever compares like with like.
We are the wrong firm for you if you want your runcutting optimiser rebuilt. Optibus and HASTUS do that better than we would and we will say so on the first call. We are also wrong if the agency has no permanent technology staff and no plan to acquire any, because an operations system needs an owner inside the building. What we bring is more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and India LLP, United States LLC and United Kingdom LTD entities so intellectual property assigns under your own law. Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing are all verifiable before a procurement conversation starts.
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.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- 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) →
Frequently asked questions
What is the difference between scheduling software and operations software?
Scheduling software builds the runcut before the pick: blocks, runs, spread and platform time, optimised against your service plan. Operations software runs the day the runcut meets reality, meaning absence coverage, extraboard offers in the correct order, held over work, dropped trips and the record of what was actually delivered. Agencies buy the first and assume it covers the second, which is why dispatch still runs on a clipboard.
How much does it cost to load a seniority list and leave balances?
Budget 10 to 25 percent of the build figure for migration overall, and expect the seniority list to take longer than the runcut. Ties, adjustments, prior service credit and leave balances usually live in three places that disagree, and every disagreement has to be resolved with human resources before the pick engine can validate a selection. Resolve them early. A pick run on a disputed list is a grievance waiting to happen.
Who owns the code and the data if the developer relationship ends?
You should, and for a public agency this belongs in the contract rather than in a conversation. Repository in the agency's own organisation, cloud infrastructure in accounts the agency owns and pays for, and full assignment of intellectual property. At Digital Heroes the client owns the code from the first commit. Your board should expect to see that answered in writing, because stewardship of public systems is a procurement question.
Can we keep our current runcutting tool and build only dispatch?
Yes, and it is the phase we recommend first in almost every case. Import the runcut from Optibus, HASTUS or whatever you already run, and build daily dispatch with the extraboard, absence coverage and clean capture of what was delivered. Most of the recoverable premium sits in that phase. The pick engine, the operator portal and federal reporting can follow once dispatch has run for a season.
How long before the dispatch office feels a difference?
Twelve to eighteen weeks for a first release, and the test is whether the clipboard disappears rather than whether training happened. Check at week two of live running. If a dispatcher is still keeping a parallel list, some rule in the eligible ordering does not match how the agreement actually works, and that is worth fixing immediately, because a dispatcher who distrusts one rule will stop trusting the ordering entirely.
What happens if the labour agreement changes mid build?
It will, and the design has to expect it. Work rules should be versioned configuration with effective dates, loaded and validated before they take effect rather than patched into code afterwards. The useful capability is being able to run the new rules against last month's actual assignments to see what changes before the contract starts. Ask any developer how they would do that, because the answer reveals whether they have done this.
Can one system cover fixed route and paratransit together?
It can, and the shared operator and vehicle availability model is where real money sits, because the one lever that saves across modes is unavailable when no system sees both. It is not a small build. Scheduling logic differs sharply, since fixed route is scheduled work against a runcut and complementary paratransit is trip based and scheduled dynamically. One operator record underneath, mode specific scheduling above.
Should we build if our federal reporting is already accepted?
Acceptance is not the same as defensibility. The question to ask is whether you could show a reviewer how a revenue hour figure was produced, from actual pull out, actual pull in and trips actually operated, rather than from a scheduled runcut adjusted by somebody who understands the definitions. If the honest answer is no, that exposure exists whether or not anyone has raised it, and it grows with your funding.
What happens if an automatic passenger counter feed is unreliable?
You capture what you can defend and mark the rest. Vehicle location, passenger counters and fareboxes are three different problems with different failure modes, most of them involving cellular dead zones and buses parked in a yard rather than anything that shows up in a lab. Ask any developer for the specific hardware and protocol they have integrated, and ask what broke. Counted data with known gaps beats confident data nobody trusts.
Is it worth building if we contract out our operations?
Sometimes, and the case is different. If a contractor runs service on your behalf, your exposure is verification rather than dispatch: did the trips operate, what was delivered, and does the invoice match. A lighter build focused on delivered service capture and contract compliance often pays quickly, and it avoids the labour rule engine entirely, which is the expensive half. Scope it as an oversight system, not an operations system.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
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 owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 .
