How Much Does a State Longitudinal Data System Cost in 2026?
A state longitudinal data system runs $200,000 to $2M, with the first production component, normally submission intake plus the statewide identity spine, at the bottom of that range and a full platform spanning accountability rule processing, interagency linkage, public reporting and researcher access at the top.
On this page
A state longitudinal data system runs $200,000 to $2M, with the first production component, normally submission intake plus the statewide identity spine, at the bottom of that range and a full platform spanning accountability rule processing, interagency linkage, public reporting and researcher access at the top. The single decision that moves the number most is whether you can mandate a submission standard: an agency that can require districts to submit through Ed-Fi runs a materially cheaper project than one obliged to accept whatever each local system produces, because the adapter count, the validation surface and the support burden all scale with the number of shapes arriving at your door.
The bands a state longitudinal data system build falls into
Two price points matter, and they are components rather than tiers. The first production component runs $200,000 to $450,000 and takes 5 to 9 months in our delivery experience. It should almost always be district submission intake with a validation workspace the district data coordinator actually works in, plus the statewide identity resolution spine. Nothing downstream is defensible until those two exist.
A full platform spanning prekindergarten through postsecondary and workforce, commonly called P20W, runs $700,000 to $2M phased over 18 to 36 months, usually against federal grant funding. That adds accountability rule processing with reproducible publication, interagency linkage, governance metadata driving access control, public reporting with defensible suppression, and a researcher request and access workflow.
Below both sits the answer for smaller organisations. A single district, or a small state buying a warehouse rather than building a system of record, should adopt Ed-Fi and a commercial product. These bands assume you publish accountability results that districts dispute and legislators cite.
What drives a state longitudinal data system build up
Five things account for most of the variance, and only one of them is data volume.
- Source system diversity. Each distinct student information system in your state is its own adapter with its own version quirks. Six vendors across three hundred districts is six adapters and dozens of version behaviours, and you cannot fix any of them at the source.
- Partner agency count. Every interagency data sharing agreement is a legal negotiation measured in quarters rather than weeks, and the engineering waits on it. Two partners is not twice one, because the second negotiation runs concurrently with the first agency's amendments.
- Historical identity resolution. Twenty years of legacy identifiers have to be resolved rather than imported, with human review of the ambiguous band. This is the least visible and most consequential work in the project.
- Public dashboards. They look cheap and are not, because accessibility conformance and complementary suppression are both real engineering rather than presentation choices.
- Rule volatility. A state whose accountability rules were amended twice in the last three legislative sessions needs versioned, reviewable rule definitions, which costs more upfront and far less over a decade.
What keeps the number down
Sequence the identity spine and the intake loop first and refuse to build dashboards until they exist. Agencies that invert that order build a handsome front end over numbers they cannot defend, and then rebuild the back end anyway.
Adopt Ed-Fi for the model and transport and the Common Education Data Standards element definitions for your dictionary rather than inventing either. Interoperability with district systems and alignment with federal reporting is worth more than a bespoke schema, and it removes an entire category of translation work.
Mandate the submission standard if your authority permits it. This is the single largest lever available to you and it is a policy decision rather than a procurement one.
Buy the identity resolution component if a credible product fits your matching policy, and spend the saving on the accountability rule engine, which nobody can sell you because it encodes your statute.
Load the last three collection years for operational use and backfill the archive in parallel. Reproducibility matters for what you have published, not for every record you have ever held.
A worked example that adds up
A state agency serving roughly three hundred and forty districts across six distinct student information systems, with one workforce agency partner and one public postsecondary partner. Component one, 8 months:
- Discovery capturing statute, board rule and accountability definitions with counsel and analysts: $46,000
- Identity resolution with tunable versioned thresholds, a human review queue and reversible merges: $142,000
- Submission intake with staging, validation and explicit district certification: $128,000
- District facing validation workspace with issue assignment and prior collection comparison: $64,000
Component one subtotal: 46 plus 142 plus 128 plus 64 equals $380,000.
The remaining platform, across the following twenty two months:
- Accountability rule engine with versioned, analyst readable rule definitions: $290,000
- Interagency linkage to wage and postsecondary records in the pattern your statute permits: $210,000
- Public reporting with versioned complementary suppression and accessibility conformance: $195,000
- Reproducible publication with manifests and on demand recompute: $170,000
- Governance metadata with access control derived from the agreements themselves: $150,000
- Researcher request, approval and secured access workflow: $120,000
Subtotal: 290 plus 210 plus 195 plus 170 plus 150 plus 120 equals $1,135,000. Historical identity resolution across legacy identifiers with human review: $185,000. Total: 380 plus 1,135 plus 185 equals $1,700,000, sitting in the upper half of the full platform band for a mid sized state.
How the spend phases
Discovery is legal and definitional work before it is technical. Six to eight weeks with counsel, accountability staff and your federal reporting lead, writing down what cohort membership actually means and which agency may hold which field, absorbs roughly an eighth of component one and it prevents a design that is lawful nowhere.
Component one then ships in 5 to 9 months and runs a complete collection cycle before anything else starts. That cycle is the gate, and it must include a district that submits badly, because your validation loop is designed for that district rather than for the one with a data team.
Interagency negotiations start at the same time as component one even though the linkage builds much later, because agreements take quarters. Engineering waiting on legal is the most common schedule failure in this category and it is entirely avoidable.
Public dashboards come last of the visible pieces, after reproducible publication and suppression exist. Publishing a number you cannot recompute is the outcome the whole system is designed to prevent.
The ongoing costs nobody quotes
Support to districts is a permanent operating cost and it is a people cost. Somebody answers the coordinator in a small district whose file will not validate, every collection window, every year. Fund the post rather than assuming the workspace removes the need.
Compute for recomputation is spiky rather than steady. Reproducing a published result on demand and re running a rule across years of data are both heavy operations, and infrastructure sized for the average will disappoint you the week a superintendent disputes a graduation rate.
Maintenance runs at roughly a sixth of the build cost each year in our delivery experience, so around $283,000 on the example above. That is a small standing team rather than a support contract, and it is consumed by statutory change: legislatures amend cohort rules, federal plans are revised, a new partner agency joins, and a district replaces its student information system.
Accessibility retesting recurs with every public reporting change, and it is easier to fund as a line than to discover as an obligation.
Comparing a build against your current renewal
Most agencies are comparing a build against a services contract rather than a licence, so price both sides honestly. Take the current annual contract value, then add every change order from the last three years, since in this category the change orders are where a legislature meeting turns into an invoice.
Then price the risk you are actually carrying. If the knowledge lives with a vendor team, the next accountability amendment is a procurement rather than a sprint, and the cost of that delay is measured in a reporting deadline rather than in dollars. If you cannot reproduce a published number, the exposure is a withdrawn result, which is not a budget item at all but is the event that changes who runs your office.
Now compare against the build amortised over five years plus its standing team. The example above is roughly $340,000 a year of capital plus $283,000 of maintenance, which for a mid sized state agency is a modest programme line and a considerably better position than an annual re procurement of the same knowledge.
When buying beats building
Buy the components that are genuinely generic. Identity resolution is the strongest candidate and eScholar has earned its position there, with several states running on it. If its matching model fits your policy and you can still tune thresholds and reverse merges, buy it and spend the saving where your statute lives.
Adopt rather than build the data standard. Ed-Fi gives you a model district systems already support, and the Common Education Data Standards give you element definitions aligned with federal reporting. Writing your own dictionary is a decade of translation work you chose voluntarily.
Contract the delivery if you must, with care. Public Consulting Group and firms like it deliver real outcomes, and the risk is not competence, it is that the knowledge leaves when the contract ends. If you go this route, make source code delivery, documentation and knowledge transfer contractual deliverables with acceptance criteria rather than intentions.
If you are a single district, or a small state buying a warehouse rather than building a system of record, buy a commercial product on top of Ed-Fi and stop. Nothing in these bands applies to you and the effort would be indefensible.
Build the parts that encode your law: accountability rules, reproducible publication, suppression, the district feedback loop and the governance metadata that controls access. Those change when your legislature meets, and you cannot afford a change order every time it does.
If you would rather someone argued with your brief than agreed with it, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Flexera's 2025 State of the Cloud Report (survey of 750+ technical and executive leaders) found that 84% of respondents believe managing cloud spend is the top cloud challenge for organizations today, with cloud budgets already exceeding limits by 17%. Source: Flexera (2025) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
What is the total cost of building a state longitudinal data system?
$200,000 to $450,000 over 5 to 9 months for the first production component, which should be submission intake with a district facing validation workspace plus the statewide identity resolution spine. A full platform adding accountability rule processing, interagency linkage, public reporting and researcher access runs $700,000 to $2M across 18 to 36 months, usually against federal grant funding.
A mid sized state serving around three hundred and forty districts across six student information systems lands near $1.7M all in, of which $185,000 is historical identity resolution across legacy identifiers.
What does it cost to run each year after launch?
Budget continuing engineering at roughly a sixth of the build cost, around $283,000 on a $1.7M platform. That is a small standing team rather than a support contract, and it is consumed by statutory change: amended cohort rules, revised federal plans, a new partner agency, and districts replacing their student information systems.
Two other lines are permanent. District support during every collection window is a staffed post, not a self service assumption, and accessibility retesting recurs with each public reporting change. Compute is spiky rather than steady, because recomputation and multi year rule re runs are heavy operations.
How long does an SLDS programme actually take?
The first production component takes 5 to 9 months and the full platform is realistically an 18 to 36 month programme. Engineering is rarely the constraint.
The two things that set the schedule are interagency data sharing agreements, negotiated in quarters rather than weeks, and historical identity resolution across legacy identifiers, which is the least visible and most consequential work in the project. Start the legal negotiations at the same time as component one even though the linkage builds much later.
Should we buy eScholar instead of building identity resolution?
It is the strongest buy candidate in the category and several states run on it successfully. If its matching model fits your policy, and you can still tune thresholds, review the ambiguous band and reverse a merge years later with full history, buying it and spending the saving on your accountability rule engine is a defensible allocation.
The constraint to test before signing is visibility. Matching thresholds, tie breaking and merge authority are policy decisions your agency owns, and a model you cannot inspect makes them harder to change when your board asks why two records were combined.
How much does the accountability rule engine cost?
Around $290,000 in the worked example, making it the largest single component and the one nobody can sell you, because it encodes your statute rather than a general practice. That covers rules expressed as versioned, analyst readable definitions with effective dates rather than logic buried in stored procedures.
Reproducible publication is priced separately at around $170,000 and the two belong together. A rule engine without publication manifests can compute a number correctly today and cannot prove what it computed three years ago, which is exactly the challenge you will receive.
What does linking to wage records add, and is it legal?
Around $210,000 in the example, and the legal design comes first with the engineering following it. Depending on your statute and the agreement with your workforce agency, the pattern may be a token based match executed inside the workforce agency environment returning aggregates only, or a linked research file in a separately secured environment with a defined retention clock.
The Family Educational Rights and Privacy Act exceptions for audit and evaluation are usually part of the analysis, but state law frequently constrains more than federal law does. Involve counsel before design, not after, because building the join first is how agencies end up with a system they are not permitted to run.
Does adopting Ed-Fi reduce what we have to spend?
Materially, and mandating it reduces the cost more than adopting it. Each distinct student information system arriving in its own shape is its own adapter, its own validation surface and its own support burden, so the ability to require a single submission standard is the single largest lever in the budget and it is a policy decision rather than a procurement one.
Adopting Ed-Fi and the Common Education Data Standards also removes the translation work of a bespoke schema. It does not fix data quality, though, since the district feedback loop is a user experience problem no standard addresses.
Why do public dashboards cost so much?
Because two of their requirements are engineering rather than presentation. Complementary suppression has to understand that hiding one cell without hiding a second lets a reader subtract to recover it, and it has to apply consistently across dozens of report types, which means a versioned service at publication rather than a manual step per report.
State accessibility requirements apply to public reporting and retrofitting conformance is expensive, so budget it upfront and budget the retesting that follows every change. In the example above, public reporting carries $195,000 for those reasons.
When should an agency not build?
If you are a single district, or a small state buying a warehouse rather than building a system of record, adopt Ed-Fi and buy a commercial product. Nothing in these bands applies and the effort would be indefensible.
Also buy or contract the genuinely generic components regardless of your size, particularly identity resolution. Reserve your build budget for the parts that encode your law, meaning accountability rules, reproducible publication, suppression, the district feedback loop and the governance metadata that drives access, because those change whenever your legislature meets.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
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.
We already pay for Microsoft 365. When does building custom actually beat Power BI?
Keep Power BI for internal reporting; at $14 per user per month for Pro it is hard to beat for employee-facing analytics. Custom wins in three cases: you are showing dashboards to customers, since embedded Power BI is priced on capacity and gets expensive fast, you need a fully white-labeled experience inside your own product, or your team keeps fighting the tool to support a specific workflow. Most companies we build for keep Power BI internally even after launching a custom customer-facing dashboard.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
What are the most common mistakes companies make on dashboard projects?
The four we see most: designing charts before modeling the data, cramming 30 metrics onto one screen so nothing stands out, letting every team define revenue slightly differently, and skipping data quality checks so the dashboard confidently displays wrong numbers. The wrong-numbers failure is the fatal one, because a dashboard loses trust once and never fully earns it back. Spend the first weeks on metric definitions and data quality, not on colors.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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 Camille.
Office Manager · New York · New-york · 7 posts on the site
Published · Last updated .
