State Tax Administration Software: Build vs Buy for a Department of Revenue
Buy the core. If you administer more than three tax types, an integrated package from Fast Enterprises or Revenue Solutions is the right system of record, and a custom rewrite is not a cheaper route to the same place.
On this page
Buy the core. If you administer more than three tax types, an integrated package from Fast Enterprises or Revenue Solutions is the right system of record, and a custom rewrite is not a cheaper route to the same place. Build the surround instead: the taxpayer portal, a versioned rules service, and audit selection you can open and inspect. That split fits almost every state.
What the off-the-shelf products actually do well
Start with the position that costs us work. If you run registration, returns, billing, collections and audit across income, sales, withholding and excise, you are going to buy an integrated tax system, and you should.
Fast Enterprises GenTax is the reference product for a reason. It holds every tax type in one account structure, it arrives with the filing and payment plumbing already built, and Fast Enterprises puts its own people inside the agency for the length of the implementation rather than emailing from a distance. Revenue Solutions Inc pairs Revenue Premier with a discovery and data warehouse practice that several states run alongside a different core. Tyler Technologies covers the local and property side that your department touches but does not own. Pegasystems and Salesforce show up when an agency wants case management without disturbing the ledger underneath.
What you are buying is twenty years of other states' edge cases. Somebody has already asked the package what happens when a taxpayer files an amended return for a period that is under audit and also carries an instalment agreement. It has an answer, and that answer has usually survived a hearing somewhere.
The plumbing matters more than the demonstration screens. A package already speaks Modernized e-File for the Fed and State return exchange, already produces the electronic W-2 file in the Social Security Administration EFW2 layout, already files information returns under IRS Publication 1220, and already reads the TXP addenda convention that arrives inside an ACH CCD credit when a taxpayer pays through their bank. Every one of those is a specification with a change history, and none of them is interesting work. Buying them is the correct decision.
Where they stop: the law is versioned and the package is not
Here is the workflow that packages model badly, and it is the one that defines your department.
A revenue agency operates in several years at once. Your call centre is answering on a period filed three years ago. Your audit division is assessing five years back. Appeals is defending a position taken under a statute amended twice since. Processing is accepting current period returns under rules effective in January. Each of those conversations needs the law as it stood for that period, with the derivation visible in front of an administrative law judge.
Packages store rate tables, bracket definitions, nexus thresholds, credit eligibility, apportionment formulas and penalty and interest rules as configuration, and configuration is updated in place. That is fine until your legislature amends something retroactively, which happens most sessions. A retroactive amendment means recomputing periods already assessed and already collected, issuing refunds or supplemental assessments, and surviving review afterwards. When a system cannot replay old law, staff rebuild the calculation in a spreadsheet from a printed copy of the repealed rule, and the department's position in an appeal now rests on that spreadsheet.
The second gap is the taxpayer, not the tax. One business holds a monthly withholding account, a monthly sales account with a prepayment, an annual corporate account with quarterly estimates, and a fuel account on its own schedule. Legacy cores are organised by tax type because the divisions were organised that way in 1988, so the single view of everything one entity owes, has overpaid, is protesting and is paying down does not exist as an object. Third, audit selection scores arrive as a number with no explanation, which is a governance problem the first time a representative asks why their client was picked.
The arithmetic: per named user versus a build
An integrated core is priced as a programme, not per seat, so the per-seat arithmetic that settles most custom versus off the shelf questions belongs to the surround rather than the core. That is where you are actually choosing.
Take the per named user figure from your own quote for a case management platform, a portal product or an analytics tier. Suppose it is $150 a user a month. One hundred and twenty staff in collections, protests and audit selection is $216,000 a year, $648,000 over three, before the professional services line that always accompanies a configuration change. A custom component covering the same ground lands at $220,000 built once, plus roughly $35,000 a year to keep it current. Over three years that is $290,000 against $648,000.
The crossover sits near 60 named users held for three years at $150 a month, and near 120 users if your quote is closer to $75. If the vendor prices the portal by transaction instead, the equivalent line is roughly 350,000 filings and payments a year at 20 cents each before a build is cheaper on cash alone.
Two adjustments before you trust that number. Seat counts in a revenue agency grow during filing season and never fully shrink, so price your peak headcount rather than your average. And a licence that scales with returns processed scales with the thing your commissioner is trying to increase, which is worth noticing at contract signature rather than at renewal.
What a custom build actually costs
A targeted component runs $150,000 to $350,000 and ships in 16 to 24 weeks. That buys one of these properly: a taxpayer portal with its own read models, a versioned rules service that computes under the law as at any effective date, an inspectable audit selection pipeline, or an agency to agency data exchange.
A multi component programme, meaning a portal, the rules service, selection analytics and one tax type modernised ahead of the rest, runs $500,000 to $1.5M phased over 12 to 24 months.
Two lines nobody puts in the paper. Data migration runs 10 to 25 percent of the build figure on its own, and in tax administration it sits at the top of that band, because a converted balance is not a number, it is a number plus the assessments, credits, payments and interest computations that produced it, and each one has to reproduce. Year two is 15 to 20 percent of the original build annually, covering legislative changes, IRS Publication 1075 safeguard review evidence, and the January work that arrives whether or not you budgeted for it.
Publication 1075 deserves its own note because agencies treat it as a network checklist handed over after design. It is not. Segregation and access logging obligations shape the data model, the reporting layer, how developers reproduce a defect without production data, and whether your warehouse is buildable at all. Retrofitting that costs more than building it in.
The four situations where building wins
Regulatory fit that no package models. Your statute is yours. If your state runs an unusual apportionment formula, a credit with eligibility rules that change annually, or a retroactive amendment pattern the package treats as an exception, the rules service is the thing to build. Every other state's edge cases do not include yours.
Scale economics. Once the surround touches more than roughly 60 named users on a per-seat product, or you are paying per filing on volumes above a few hundred thousand, the arithmetic above has already turned.
A workflow that is your advantage. In a revenue agency that is audit selection. A selection pipeline the department owns, with features defined in readable code, the model version recorded against each case, an explanation of the top contributing factors, and a random holdout sample to measure against, is the most defensible analytics spend you can make. A vendor model you cannot open cannot be defended to a representative or to your own leadership when yield falls.
Integration sprawl across three or more systems. If a single collections action touches your core, the Treasury Offset Program, your labour department's unemployment system, the courts and a bank file, the joins are yours to own. Packages integrate outward one connector at a time and charge for each.
How to decide in a week
Run this test, and run it with staff rather than with a vendor in the room.
Pull the last twenty protest files. For each, time how long it takes to reproduce the original assessment under the law as it stood for that period, showing the rule, its effective date, and the arithmetic. Record where the answer came from: the system, a spreadsheet, or a person. Then pull the last ten selection decisions and ask your audit division to explain, in writing, why each case was chosen.
- If most assessments reproduce from the system in minutes, buy and configure. Your problem is training, not software.
- If more than a third need a spreadsheet, build the versioned rules service first.
- If nobody can explain a selection, build the selection pipeline before anything else.
- If the portal is the only thing legislators mention, build that and leave the core alone.
Then buy a paid discovery phase, not a proposal. At Digital Heroes that means two to three weeks producing a signed product requirements document covering the data model, the permission model, the Publication 1075 handling and the acceptance criteria, before anyone writes code. You keep that document whether or not you hire us, and you can put it out to tender.
Who we are wrong for: if your decision is to replace the integrated core across every tax type, we are not the firm and Fast Enterprises is. We are a team of more than fifty specialists with over 2,000 projects delivered, listed on Clutch, Trustpilot and Fiverr Vetted Pro with a D-U-N-S number, and we build the surround, the exchanges and the components. Our own products, ShopScore, HeroCheckout and Section Vault, are commerce tools rather than public sector ones, and we will say so. We hold India LLP, US LLC and UK LTD entities, so intellectual property assigns under your own jurisdiction rather than ours, which matters when a state procurement office reviews the contract. You meet the named engineers before you sign.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
- 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) →
Frequently asked questions
How much does custom state tax administration software cost?
A targeted component such as a taxpayer portal, a versioned rules service or an audit selection pipeline runs $150,000 to $350,000 and ships in 16 to 24 weeks. A multi component programme spanning several of those, plus one tax type modernised ahead of the rest, runs $500,000 to $1.5M phased over 12 to 24 months. Data migration adds 10 to 25 percent on top of whichever figure applies to you.
How long does a replacement of an integrated tax system take?
Longer than any vendor will say in a first meeting. A full replacement across every tax type at a state department of revenue is measured in years and is normally staged tax type by tax type, with a filing season between each stage because nobody cuts over in March. A single component built alongside the existing core is a different question and lands in 16 to 24 weeks.
Who owns the code and the data if we commission a custom build?
You should, from the first commit, and it belongs in the contract rather than in an assurance. That means the repository, the cloud accounts, the deployment pipeline and the unrestricted right to hire a different firm to continue the work. For a public agency this matters twice over, because your records are subject to retention schedules and public records law, and a system you cannot reach without a vendor's cooperation is not a system you administer.
What happens if the legislature changes a rule retroactively?
This is the test question to put to any vendor. A retroactive amendment means recomputing periods already assessed and often already collected, then issuing refunds or supplemental assessments that survive review. A system that stores rules as configuration updated in place cannot do it, so staff rebuild the calculation by hand. Ask to see the same taxpayer's liability computed under two effective dates on one screen.
Can we build only the taxpayer portal and leave the core alone?
Yes, and for most departments it is the right first move. A portal built as a separate application with its own read models can show a taxpayer the derivation of a notice, meaning the return as filed, the adjustment, the rule applied with its effective date and the interest itemised. It absorbs filing season peaks without touching the system of record, and it ships in months rather than years.
Should we build our own audit selection model instead of buying one?
Build it if you have to defend it, and you do. Vendor scoring models are often genuinely useful, but a score with no explanation becomes a problem the first time a taxpayer representative asks why their client was chosen, or your own leadership asks why yield fell. Owning the pipeline lets you record the model version against each case and hold out a random control sample to measure against.
What is the difference between GenTax and a custom build?
GenTax from Fast Enterprises is an integrated tax system covering registration, returns, billing, collections and audit across every tax type, priced and delivered as a multi year programme. A custom build is normally a component beside it: a portal, a rules service, an analytics pipeline or an agency exchange. Treating custom work as a cheaper substitute for the core is the most expensive misreading in this category.
Does IRS Publication 1075 rule out cloud hosting for a custom system?
No, but it shapes the design from the first sprint rather than the last. Publication 1075 governs how federal tax information is handled, where it may live, who may reach it, how access is logged and what evidence you produce at a safeguard review. Tag data by classification at field level, make access logging a property of the data layer, and generate synthetic data so developers never touch production.
How do we compare quotes when every firm has priced something different?
Insist on a written specification before any fixed price, because otherwise you are comparing four different scopes wearing one name. Ask each firm to price the same numbered requirements, to state the data migration line separately, and to name the year two support percentage. If a quote has no migration line at all, it is not cheaper, it is incomplete, and that gap is 10 to 25 percent of the build.
Are there alternatives to a full system replacement we should look at first?
Usually yes. Most departments get more from a portal with its own read models, a rules service that can replay old law, and an explicit account state machine covering protests, payment plans and offsets, than from a replacement programme that consumes the next four years. Those three components address the complaints legislators and taxpayer representatives actually raise, and they leave the core in place.
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.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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.
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.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
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.
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.
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 James.
Senior Copywriter · New-york · 14 posts on the site
Published · Last updated .
