Election Management Software: Where to Build and Where to Buy
One boundary decides most of this before budget does. Anything that marks, casts, counts or tabulates a ballot is a certified voting system and must be bought, never built.
On this page
One boundary decides most of this before budget does. Anything that marks, casts, counts or tabulates a ballot is a certified voting system and must be bought, never built. Everything around it is fair game, and the number that decides whether to build there is split precincts rather than registered voters: below roughly 50,000 registered voters with cleanly nested districts, buy the statewide system plus a commercial pollbook and a tracking service. Above that, with dozens of splits and a mail ballot programme that outgrew its spreadsheets, a first release at $80,000 to $160,000 over 16 to 22 weeks starts to pay. Most counties should buy the core and build a narrow band around it.
When is off the shelf genuinely the right call here?
Some of it is not a choice. Voting systems fall under the federal Voluntary Voting System Guidelines administered by the Election Assistance Commission and under your own state certification regime on top of that. Electronic pollbooks are separately regulated in many states. No jurisdiction should commission custom tabulation from a software firm, and any developer who offers it is telling you they have never worked in this field. Buy those, and confirm your state rules before scoping anything that touches voter check in.
Beyond the certified boundary, buy your pollbook and keep it. KNOWiNK Poll Pad and Tenex deployments are certified for check in where certification applies, and VR Systems components serve parts of this market well for the same reason. Integrating with them is cheaper, faster and legally simpler than any alternative.
Buy your ballot tracking service too. Transit visibility built on postal barcode scans is handled properly by existing services, and there is no version of building that which improves a voter's experience.
And buy, meaning stay as you are, if you run a handful of precincts with a modest mail programme. Your statewide voter registration system plus a pollbook plus tracking will carry you, a build cannot be justified from that budget, and the maintenance obligation would land on an office that is not staffed to carry it. The right investment at that size is writing your processes down so they survive a staff change, which costs nothing but calendar time.
The reason this section is longer than it is in most categories is that the buy side here is genuinely large. The custom scope in elections is a band, not a platform.
When does a custom build actually pay off?
It pays where your specific district geometry meets your specific state code, which is the one combination no vendor has ever had to solve. A ballot style is the exact set of overlapping districts at an address: congressional, state senate, state house, county commission, city council, school board, fire, water, library, a special assessment area with its own measure. The statewide system assigns districts from a street file maintained by people, and it contains the errors people make. Odd house numbers on the wrong side of a line. A new development coded to the old precinct. An apartment complex straddling a boundary.
Nothing in a purchased stack systematically proves that every registered address resolves to exactly one valid style, or shows you the difference after an annexation. A build holds districts as geographic layers, resolves each address against them, and reconciles that against the statewide result. Run it in July and you fix street file errors when it is boring. Run it never and you fix them on the phone with a voter fourteen days out.
It pays a second time inside your office on mail ballots. Tracking services see transit. They do not see the signature challenge queue, cure notices with deadlines computed from statute, second and third contact attempts, or the daily reconciliation between ballots issued and returned by precinct that your county administrator and the local paper both want by lunchtime.
In Digital Heroes delivery experience the first release covering ballot style reconciliation, the mail ballot state machine with signature review and cure, and poll worker assignment runs $80,000 to $160,000 over 16 to 22 weeks. The full platform adding custody records, ballot and supply logistics, canvass and audit support and public status pages runs $200,000 to $500,000 phased over 9 to 15 months.
How do they compare on the things that matter in this industry?
On certified functions, there is no comparison to make. Buy, and treat any proposal that blurs the line as disqualifying rather than ambitious.
On ballot style correctness, a build wins because the work is reconciliation rather than storage. Purchased tools hold the style a voter is assigned. They do not independently derive it from boundaries and tell you where the two disagree, because they are not holding your district layers and were never asked to.
On mail ballot deadlines, a build wins because the deadlines come from your state code rather than from a product default. Cure windows, notice requirements and reviewer rules differ by state, and legislatures amend them. A rule engine that tracks your statute is a maintainable thing. A product setting that approximates it is a risk somebody in your office is quietly managing by hand.
On poll workers, a build wins for a reason people underestimate until they try to buy it. Party balance is a constraint on the composition of a location team, not on an individual shift, and that is precisely what generic schedulers cannot express. Add bilingual coverage, equipment certification, a chief who has served before and a limit on first timers, and you are solving assignment rather than filling a rota.
On chain of custody, a build wins on the property that matters in a contested race: an append only log cannot be edited afterwards and can prove it. Paper fails through illegible seal numbers and missing signatures. A spreadsheet fails differently, because it can be changed and cannot demonstrate that it was not.
On calendar risk, buying wins. A purchased product does not need your December to April window, and that constraint is real.
What does total cost of ownership look like at your scale?
Take a county with roughly 210,000 registered voters, 140 precincts containing about 90 splits, a mail ballot programme that grew faster than its tools, and around 900 poll workers per election. Discovery, district layer inventory and statutory deadline mapping is $11,000. District boundary layers with an address resolution engine are $26,000. The ballot style reconciliation report against the statewide file is $18,000. The mail ballot state machine with signature review queue and two reviewer rule is $30,000. Cure notice generation with statutory deadlines and multi channel contact logging is $16,000. The poll worker model with party balance, language and certification constraints is $28,000. The statewide exchange with defensive validation, quarantine and reconciliation is $14,000. Total $143,000, near the top of the first release band.
Running costs are 15 to 20 percent of build a year as a support retainer, higher than an ordinary system because election period support is not a business hours arrangement. Add $8,000 to $20,000 for hosting and record retention, $10,000 to $25,000 for annual independent security testing, $10,000 to $30,000 for statutory change as legislatures amend deadlines and notice rules, and $5,000 to $15,000 for statewide interface breakage, which is always urgent because formats change without consultation. Redistricting re-runs the whole address resolution and produces a new style set, so plan it as a funded event rather than a support ticket.
There is usually no single renewal to compare against, and that absence is itself informative. Build the comparison from the four weeks before an election instead: hours spent on ballot style questions from voters, on rebuilding poll worker assignments after cancellations, on cure notice production, on reconciling custody paperwork after election night, plus overtime and temporary staff. Then price the thing nobody quantifies, which is that your office runs on one long serving director's memory and none of it is written where a successor could use it.
What does the hybrid look like, and when is it the honest answer?
In elections the hybrid is not one option among several. It is the only responsible architecture, and every recommendation in this guide assumes it.
Concretely: the certified voting system stays exactly as it is. The commercial pollbook stays, integrated rather than replaced. The ballot tracking service stays, because postal scan visibility is a solved problem. The statewide voter registration system stays, and you exchange with it through scheduled files with defensive validation, a quarantine for records that fail and a reconciliation report, because you do not control it and a clean live interface is not what you are going to get. Any developer who assumes one has not worked here.
What you build is the band in between: address resolution and ballot style reconciliation, the mail ballot workflow inside your office, poll worker assignment, custody records, logistics and public status pages. That band is where your staff time actually goes and it touches no certified boundary anywhere.
There is a smaller hybrid worth naming for counties that cannot fund a first release. Build ballot style reconciliation alone, at roughly $18,000 to $45,000 including the boundary layers. It is the cheapest item in the category, it can run months before an election, and it removes the failure that generates the most voter contact. Everything else can wait for a later budget cycle.
Which should you choose, by operator size and stage?
Under about 50,000 registered voters with nested districts and a modest mail programme: buy everything, document your processes, and revisit after redistricting. A build at that size adds an obligation your office cannot staff.
Fifty thousand to 150,000 voters where ballot style errors recur annually: build the reconciliation piece alone first. It is the smallest useful project here, and it can be delivered inside a single off cycle window.
One hundred and fifty thousand voters upward with heavy mail volume and several hundred poll workers: the $143,000 shape above, sequenced into the December to April window and first used live on a small special or municipal contest rather than a general election.
Large jurisdictions running vote centres, multiple ballot languages and a canvass under public scrutiny: expect the full $200,000 to $500,000 programme over 9 to 15 months, with vote centre provisioning at $12,000 to $28,000 and each additional language at $12,000 to $30,000 because ballots, notices, worker materials and public pages all multiply together.
And any jurisdiction whose critical process knowledge sits with one director approaching retirement should move regardless of size. Writing the process into software while the person who knows it is still there costs a fraction of reconstructing it after they have gone, and it is the signal we see most often and the one counties consistently underrate.
If you would rather scope this before committing budget, 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 keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
- PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
Frequently asked questions
What does it cost to change election vendors once we are running?
For certified components, the switching cost is dominated by state certification and staff retraining rather than by software, and the timing has to sit in an off cycle window regardless of price. Treat it as a multi cycle project.
For the custom band, the point of owning it is that there is no switching cost of that kind. You hold the repository, the infrastructure accounts and the right to hire another firm, so a change of developer is a handover rather than a procurement.
What happens if our pollbook or tracking vendor raises prices?
You absorb it on the certified side, because certification is the barrier and alternatives are limited. That is worth accepting honestly rather than pretending a build removes it.
What the custom band does is stop the vendor relationship expanding. Once ballot style reconciliation, mail ballot workflow and poll worker assignment sit in software you own, a price rise is bounded to check in and transit visibility rather than reaching across your whole operation.
How long does a build take, and when can it actually go live?
Sixteen to twenty two weeks of build for a first release, but the deployment date is set by your calendar rather than by the project. Nothing lands in the eight weeks before an election under any circumstance, so in a jurisdiction with a fall general election the usable windows run roughly December to April.
Plan first live use on a small special or municipal contest. It exercises the mail ballot workflow end to end without a high turnout audience watching.
Should we keep KNOWiNK Poll Pad rather than building check in?
Yes. Voter check in is regulated in many states and the pollbook products in that market are certified for it, so integrating is cheaper, faster and legally simpler than any alternative you could commission.
Build the part those products cannot see, which is the reconciliation between what the pollbook recorded and what your ballot style resolution says should have happened. That is where discrepancies surface early enough to fix.
Can we build only ballot style reconciliation?
Yes, and for many counties it is the right first project. Expect $18,000 to $45,000 for district boundary layers, address resolution and a reconciliation report against the statewide file.
It is the cheapest item in the category and the one that cuts voter contact volume most, because it lets you fix street file errors in July when they are boring rather than fourteen days out when they are urgent and public.
Why can a smaller county cost more to build for than a larger one?
Because the budget follows district geometry rather than registered voters. A county of 200,000 voters with cleanly nested districts is a smaller build than one of 80,000 with school, fire, water and library districts crossing each other and a charter city with its own boundaries.
Count your split precincts before anyone quotes. That number, not your voter roll, is what determines how much resolution and reconciliation work sits underneath every ballot style you print.
What does redistricting do to a system we have built?
It re-runs the entire address resolution and produces a new ballot style set, so budget it as a funded event on a known cycle rather than as a support ticket.
The compensation is that a build makes redistricting survivable. Boundary layers are replaced, every address is resolved again, and the output is a diff showing exactly which voters changed style. Doing that by hand against a street file is the version that produces errors nobody catches until an election.
Who owns the code and the custody records if an agency builds this?
The jurisdiction should own the repository, the infrastructure accounts and the right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more here than almost anywhere else. Election records carry retention obligations, custody logs may become evidence, and public trust does not survive a vendor dependency argument in a contested year.
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.
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.
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.
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.
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.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
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 Eleanor.
VP Client Services · UK & EU · London · 1 post on the site
Published · Last updated .
