English Learner Program Compliance Software: Buy Ellevation, or Build the Identification Chain Yourself?
Identified student count and the shape of your exit rule decide this. Under roughly 2,000 identified English learners with a single assessment threshold and no federal agreement in place, buy Ellevation Education and spend the difference on bilingual staff.
On this page
Identified student count and the shape of your exit rule decide this. Under roughly 2,000 identified English learners with a single assessment threshold and no federal agreement in place, buy Ellevation Education and spend the difference on bilingual staff. Above roughly 8,000 across many campuses, with multi criteria committee reclassification or an imposed compliance calendar, build. Most districts reading this sit between those numbers, and for them the honest answer is neither: keep the platform and build only the identification front end and the post exit monitoring record.
When is off the shelf genuinely the right call here?
Buy Ellevation Education if you have under roughly 2,000 identified English learners, your state's exit criteria are a single assessment threshold, and you are not under an agreement with the Office for Civil Rights or any heightened state monitoring. At that size Ellevation does the job well. The teacher facing profiles and service plans are genuinely useful to the people delivering instruction, and a build would be an expensive route to the same screen. The money is better spent on bilingual staff and interpreter capacity, which is closer to what the Castaneda test actually measures you on.
Buy and stop, too, when the failure you are trying to fix sits upstream of any platform. Ellevation consumes what your student information system gives it. If a home language survey never made it off a clerk's desk at a campus front office in August, no program management layer catches that, because the student never arrived as an English learner in the first place. Fixing the registration workflow, even on paper with a named owner and a weekly count, costs almost nothing and removes more risk than a software decision does.
Keep PowerSchool, Infinite Campus or Skyward as the system of record for enrolment, demographics and scheduling whatever else you decide. Nobody needs another student information system, and every district that has tried to build one has doubled its budget proving it.
The honest test is whether your English learner office can produce, for a student a reviewer picks rather than one you pick, the survey, the screener inside the state window, the placement decision, the parent notice in a language the family reads, and the post exit monitoring record. While that takes an afternoon rather than a fortnight, your tooling is adequate and you should leave it alone.
When does a custom build actually pay off?
Two or more of these usually settle it. You have more than roughly 8,000 English learners across many campuses. Your state's exit criteria are multi criteria with a committee decision rather than a single cut score. You are operating under an agreement with the Office for Civil Rights, a consent decree or a state corrective action plan. Your reclassification math lives in a workbook that one person maintains. Or your last monitoring visit produced a finding on post exit monitoring, which it probably did, because that is the finding almost everyone gets.
In Digital Heroes delivery experience, a focused first release covering the identification chain, meaning a digital home language survey at registration, a screening task queue with due dates computed from your state's window, placement, parent notification generation and the evidence log, runs $60,000 to $120,000 and ships in 10 to 16 weeks. A full platform adding versioned reclassification decisioning, post exit monitoring, staffing qualification evidence and Title III reporting extracts runs $150,000 to $320,000 phased over 6 to 10 months.
The argument that carries a school board is not efficiency. A monitoring finding does not cost money directly. It costs a corrective action plan, a compliance calendar set by somebody else, and years of additional reporting. The second finding is far more expensive than the first, because the first put the district on a list. Fund a build when the exposure is that shape, not when the office is simply busy, because busy is a staffing problem and software does not fix staffing problems.
How do they compare on the things that matter in this industry?
The teacher facing features are a solved problem and Ellevation solves them well. Compare on the parts that decide a monitoring visit.
- Where identification starts. A program management platform begins at the student information system record. A build can begin at the registration desk, turning a qualifying survey answer into a dated screening task with a named owner at that campus and an escalation schedule behind it.
- Rule versioning. Ask whether a reclassification decision stores which version of the exit rule it was evaluated under, and which evidence satisfied each criterion. States revise criteria in budget bills, and a decision made in year one has to remain defensible in year three.
- Post exit prompts. A reclassified student leaves every list the English learner office looks at while the monitoring obligation runs for two to four years. Ask what generates the checkpoint task, who it goes to, and what closes the record with an outcome.
- Notice evidence. Not translation, evidence. Which notice, which version, which language, which date, sent by which method, to which address, for this named student.
- Staffing coverage. Joining certification records with effective dates to course sections and student service assignments, so you can answer who is receiving service from an uncertified teacher, campus by campus.
- Data portability. Ask in writing what an export contains and in what structure, because a compliance history you cannot extract is a history you do not really control.
None of these are feature gaps in the marketing sense. They are the difference between a platform that reports your program and a system that runs it.
What does total cost of ownership look like at your scale?
Take the district from our cost work: 14,000 identified English learners across 62 campuses, nine home languages requiring generated notices, PowerSchool as the student information system, two assessment feeds, multi criteria committee reclassification and an open state corrective action plan. The components total $290,000, and with a 10 percent contingency the committed number is $319,000 across roughly nine months.
The recurring side is where districts get caught. Support and maintenance runs 15 to 20 percent of build, so roughly $48,000 to $64,000 a year. State rule changes run $10,000 to $25,000 a year, because exit criteria get revised and screening windows move, and a versioned rule engine makes that a data change rather than a rewrite, but somebody still has to encode and test it. Assessment file format changes run $6,000 to $15,000 a year, and they arrive with less notice than you would like. Hosting under the Family Educational Rights and Privacy Act plus your state student privacy statute runs $9,000 to $22,000. A student information system major version costs $6,000 to $18,000, because enrolment and course data models move and compliance logic breaks quietly rather than loudly.
Then campus staff training at $8,000 to $20,000 a year, which is the line districts cut first and regret at the next visit, because front office staff rotate constantly and the survey only works if the person handing it over understands why it matters.
That is about $487,000 across three years on the worked example. Put it beside your per student subscription across 14,000 identified students, which you can read off your own contract rather than accept from either side, and beside the cost of a second finding.
What does the hybrid look like, and when is it the honest answer?
Keep Ellevation for what it is good at, meaning English learner profiles, service plans and the strategies teachers actually open, and build only the two pieces it structurally cannot hold. For more districts than either pure option, that is the right answer.
The first piece is the front of the chain. A digital home language survey at the point of registration runs $22,000 to $40,000, and a screening task queue with state window timers and escalation runs $18,000 to $32,000. Together they are the only thing that lets a director answer how many students are currently unscreened without sending emails to 60 campuses and waiting three days.
The second piece is the back of the chain. Post exit monitoring runs $25,000 to $45,000 on its own, and it is worth building first if you have already had the finding, because it is the only part of the process with no natural prompt. Reclassification creates a record with an end date, checkpoints generate tasks to named staff each grading period, grade and assessment evidence flows in automatically, and the window closes with a documented outcome.
Roughly $65,000 to $115,000 buys both, against $319,000 for the full platform, and your subscription continues untouched. Sequencing matters more than scope here. Launch the survey and screening queue before a registration season rather than during one, because an August launch competes with 400 enrolments a week and the training does not stick. Reclassification can follow a term later, since its calendar is annual rather than daily.
Which should you choose, by operator size and stage?
Under roughly 2,000 identified English learners, single threshold exit rule, no agreement in place: buy Ellevation and put the difference into bilingual staff. A district that builds at that size will have spent a teacher's salary to arrive at the same screen.
Between 2,000 and 8,000: take the hybrid. Keep the platform, build the identification front end and the post exit monitoring record. This is the population where the manual work is real but a full platform does not repay itself inside a superintendent's tenure.
Above roughly 8,000 across many campuses, with multi criteria committee reclassification: build. At that point the reclassification workbook is a single point of failure, the notice evidence problem is genuine, and a configured product gets worked around rather than used.
Under a federal agreement or a state corrective action plan at any size: build the evidence layer regardless of student count. The evidence standard is higher, the reporting cadence is set by somebody else, and a product designed for the ordinary case will not produce what an imposed calendar asks for.
Post merger, or running charter partners on a second student information system: build, and start by reconciling the enrolment, campus and course models before anything else. That reconciliation is unglamorous and slow, and it determines whether either district's history survives the integration. Whichever route you take, plan the historical migration for students already inside an open monitoring window as real funded work, because those files still have to be produced.
If you want a second opinion before signing anything, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- 76% of developers are using or planning to use AI tools in their development process in 2024 (up from 70% in 2023), with current active use rising to 62% from 44%; 81% agree increasing productivity is the biggest benefit of AI tools. Source: Stack Overflow (2024) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
What does it cost to move off Ellevation later?
The subscription exit is straightforward. The real cost is that your reclassification decisions, the evidence behind them and any notice history sit inside a platform whose export shape you have not tested. Ask before renewal what an export contains, specifically whether it includes the decision record and the evidence per criterion rather than only current student status.
Budget migration of students already inside an open post exit monitoring window at $10,000 to $30,000 either way, because that window still has to produce its file for a reviewer regardless of which system you are running.
What happens if our platform vendor changes per student pricing?
Commercially you can absorb a rise, and per student pricing at least scales with something you can forecast. The structural exposure is different: your compliance evidence lives somewhere you do not control, and a repricing arrives at the same time every year as your renewal, which is not when you have room to move.
That is the argument for the hybrid. Keep renting the teacher facing program management, which is genuinely useful and cheap to replace, and own the identification chain and the monitoring record. A repricing then becomes a procurement conversation rather than a compliance risk.
How long before a custom build is usable?
Ten to sixteen weeks for the identification release covering the digital home language survey, the screening task queue, placement, notification generation and the evidence log, in our delivery experience. Six to ten months for the full platform including reclassification and post exit monitoring.
The schedule risk is decision latency rather than engineering. Districts that arrive with their state rules already written down, and a named owner in the English learner office who can decide, move three to four weeks faster than districts working it out during the build.
Is Ellevation enough if our state uses one cut score?
For a district with a single threshold exit rule, modest enrolment and no agreement in place, yes, and building would be poor economics. The rules maintenance you would otherwise fund yourself is real work and worth renting.
Its boundary is structural rather than a feature gap. It consumes what the student information system gives it, so an identification failure at a registration desk is faithfully reproduced rather than caught, and it is a program management layer rather than a rules engine when your state moves to a multi criteria committee decision.
Why is post exit monitoring worth building before anything else?
Because it is the only step in the chain with no natural prompt. The student is out of the program, so they leave every list the English learner office looks at, while the obligation continues for the state window of commonly two to four years. Nothing in a student information system generates the reminder.
At $25,000 to $45,000 it is a small build with the highest finding rate attached to it. If your last monitoring visit produced one finding, this is almost certainly where it landed.
How many home languages can we afford to generate notices in?
Each language variant adds $3,000 to $6,000 during the build and $4,000 to $9,000 if added later, because a late addition needs the whole existing notice set translated and approved rather than only the new templates. The engineering is modest. The content governance is not.
The approach that works is generating your top languages and having the system flag where no approved translation exists, so the office arranges interpreter support in advance rather than discovering the gap during a review with twelve families affected.
Do we have to replace PowerSchool to do this?
No, and you should not. Leave it as the record for enrolment, demographics and scheduling and build the compliance layer beside it, reading what it needs. Integration runs $16,000 to $32,000 depending on platform, and PowerSchool, Infinite Campus and Skyward are three genuinely different problems rather than one with settings.
Attempting to replace the student information system is the single most reliable way to double the cost of this project, and it does not improve any compliance outcome a reviewer will ask about.
When should a district not build this at all?
Under roughly 2,000 identified students, with single threshold exit criteria, no federal agreement or corrective action plan, and nobody who can own the system after go live. That last condition matters more than the others, because a compliance system without an owner decays into the workbook it replaced within two years.
In that situation buy the platform, fix the registration desk process on paper, and put the difference into bilingual staff. The build case starts at committee reclassification, heightened monitoring, or a workbook only one person understands.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
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 questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
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.
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.
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 Mahira.
Lead UI/UX Designer · Lucknow · 1 post on the site
Published · Last updated .
