Build vs Buy: Language School Software for Continuous Intake Schools
Most language schools should buy. Below roughly 400 active students on one site with fixed term starts, Teachworks or Classe365 is enough and a build is a distraction.
On this page
Most language schools should buy. Below roughly 400 active students on one site with fixed term starts, Teachworks or Classe365 is enough and a build is a distraction. Build when placement rules, cohort construction and seat level payments have moved into spreadsheets your Director of Studies maintains by hand, which usually happens past two sites and continuous intake.
Where a packaged school platform is still the right purchase
Start with the case against spending money with anyone. If you run one site, fixed term starts and somewhere under 400 active students, Teachworks or Classe365 will hold your student records, your invoices and your registers perfectly well. Your Director of Studies can build twelve sections on a printed sheet in a morning, and the grid is small enough that she can see all of it at once and spot the collision before it happens. At that size a custom platform buys you a slightly better version of a problem you do not have, and the same money spent on two more teachers or a proper local marketing push moves revenue further and faster.
Buying is also the correct answer when the real problem is behaviour rather than features. If teachers do not mark registers until Friday, if the front desk takes deposits without recording which cohort they belong to, if nobody calls the students who went quiet after week three, a new system will record the same mess more expensively. Fix the operating routine on the tool you already pay for. The schools that get the most out of a build are the ones that had tight process on a limited system, not the ones hoping that software will impose a discipline management has not.
There is a third buy case worth naming, because it saves people from expensive rework. If your academic model is about to change, if you are moving from ten week cycles to rolling four week modules, or adding an online division with its own pricing and its own teachers, do not encode the old model in custom software while the argument is still live. Wait until the model settles. A structure you are halfway through abandoning ends up baked into the data model rather than into a screen you can redraw, and that is the most costly kind of change to reverse.
The point where building becomes the cheaper option
The trigger is not student count. It is whether your operating logic still lives inside the software you pay for. The moment placement decisions are recorded in a workbook with a colour fill only one person can read, the moment next cycle's grid gets assembled on paper and typed back in afterwards, the moment a seat a corporate client paid for cannot be traced to the student sitting in it, your school platform has quietly become a filing cabinet. Every additional student past that point makes the manual layer heavier rather than lighter, which is the opposite of what software is supposed to do for you.
Four conditions push schools over the line in practice. Continuous or rolling intake, so there is never a quiet week when everything resets and you can catch up. Two or more sites with teachers shared between them, which turns availability into a travel time and contracted hours problem rather than a calendar entry. Corporate contracts where the payer is not the student and the client expects attendance evidence before renewing. And any reporting duty tied to student visa status or accreditation, where attendance is not a percentage on a dashboard but a rule you must be able to defend to an authority with power over your students.
This is the kind of build Digital Heroes takes on, and we start with a written product requirements document before anyone writes code, because the argument worth having at a language school is about what counts as a placement decision and who is allowed to override one, not about button colours. We operate as an India LLP, a US LLC and a UK LTD, so a school in Manchester or Chicago contracts and takes IP assignment in its own jurisdiction. We work in public with 2.5 million subscribers on our YouTube channel, hold Fiverr Vetted Pro status, and have delivered more than 2,000 projects with a team of over 50 people.
What each route costs over three years
Packaged platforms in this category are usually priced per active student or per seat, with an implementation fee and a support tier stacked on top. The number worth modelling is not the monthly invoice. It is the invoice plus the salary cost of whoever maintains the shadow spreadsheets, plus the hours your Director of Studies loses to grid building every cycle, plus the re-enrolments that leak whenever a student gets telephoned and asked to move class. A school running 1,200 students at a four figure cycle price does not need many lost re-enrolments in a year before that invisible line is larger than the licence fee that shows up in the accounts.
On the build side, our delivery bands for this category run $60,000 to $130,000 for a first release shipping in 12 to 16 weeks. That covers placement records with a rule engine and a reasoned manual override, cohort building with a solver and a review screen for your Director of Studies, seat based enrolment with payment plans, teacher assignment with an hours ledger, and an attendance app that works when the basement classroom has no signal. A full platform adding a student portal, corporate contract management, multi site scheduling with travel constraints and compliance reporting runs $150,000 to $400,000 phased across 6 to 12 months.
Then budget the part that gets left out of both quotes: what it costs to keep running. Hosting for a system this operationally central is modest, but change is not. Academic models move, payment rules move, and an authority can revise a reporting definition with a few months of notice. Treat ongoing development as a standing annual line rather than an occasional surprise, and pick a partner who will still take a small change request in year three without pricing it as a new project.
The costs neither quote will show you
The first is your own history. Five years of records where level was a free text field, and somebody typed a hybrid answer several hundred times because the student was genuinely between two levels, is not a data export. It is a cleanup project, and in our builds migration in this category routinely lands at 15 to 25 percent of a first release. Ask for a data audit in week one, before anybody commits to a cutover date, because that audit is where the real timeline lives rather than in the proposal.
The second is access to the data you already own. Before assuming you can read your current platform nightly, confirm in writing whether API access sits behind a higher plan tier, what the rate limits are, and whether uploaded documents come out with the records. That answer changes the shape of any integration and sometimes changes the decision.
The third catches schools with continuous intake, and it is the item most operators do not see coming. There is no quiet week to cut over in. A school with September and January starts can switch during a gap. A school with a new cohort starting every fortnight has to run both systems in parallel through at least one full cycle, which means double entry for eight to twelve weeks and a named person accountable for reconciling them daily. Staff that period explicitly. It is the phase where badly planned projects lose the trust of the front desk, and once the counter stops believing the new system, adoption is finished no matter how good the software is.
The fourth is vendor pricing behaviour, and it deserves an email before you next renew. Ask whether per student pricing counts peak headcount in a month or a monthly average, because a six week summer intensive can set the rate you pay for the rest of the year. Ask what happens to the price when you open a second location and whether an online division counts as one. Ask what format your data leaves in on termination. Schools tend to discover these terms during a migration, which is precisely the moment they have no bargaining power left.
The test that settles it
Do not decide this from a feature comparison. Reconstruct one recent cycle and count four things honestly. Hours your Director of Studies spent building and rebuilding the grid, evenings included. Seats that were transferred, frozen or refunded, and how long each one took to reconcile against a payment. Students you telephoned and asked to move section because the one they wanted was full or below minimum. And re-enrolments you did not get, split by whether that student was one of the people you had to phone.
Then price it. Take the loaded hourly cost of the staff involved, multiply the grid and reconciliation hours by the number of cycles you run in a year, and add the revenue from the re-enrolments that leaked. If that annual figure sits below the cost of a first release, stay where you are and tighten the routine instead. If it sits above, the build has already been paid for and you are only choosing whether to keep paying in salary and lost renewals. Run the count at the site with the worst records rather than your best one, because that site is the one the software has to survive.
What to do next
Pull the fifty hardest cases from last cycle: the transfers, the frozen seats, the corporate students who left mid term, the placements a teacher overrode in week two. Write down how each was resolved and who decided. That list is your specification, and it will teach you more in an afternoon than a month of vendor demonstrations. Take it to whichever route you choose and make the vendor or the developer walk you through every case in front of you.
Then vet the shortlist properly. Ask a developer to whiteboard the relationship between student, placement record, cohort, seat, session and payment before anything is signed, and keep interviewing if a seat is modelled as a join table rather than an object with a lifecycle of its own. Get code ownership in writing: repositories, infrastructure accounts and data yours from the first commit. And confirm the company is real before money moves, through D-U-N-S registration and public Clutch and Trustpilot profiles rather than a case study page they wrote about themselves.
If you want a second opinion before signing anything, 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. 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.
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
- The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (2025) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
Frequently asked questions
How much does custom language school software cost?
A first release covering placement records, cohort building with a solver, seat based enrolment and teacher assignment runs $60,000 to $130,000 and ships in 12 to 16 weeks in Digital Heroes delivery experience. A full platform with a student portal, corporate contracts, multi site scheduling and compliance reporting runs $150,000 to $400,000 across 6 to 12 months. Multiple sites with shared teachers push you toward the upper half of both bands.
How long does a build take before our Director of Studies feels the difference?
Twelve to sixteen weeks to a usable first release, but the felt difference arrives at the first cycle build after go live, which may be another six to ten weeks depending on where you land in the calendar. Plan the schedule backwards from a cycle boundary rather than forwards from a kickoff date, because arriving mid cycle means running both systems through a full intake period.
Can we migrate student history out of Classe365 or Teachworks cleanly?
Usually yes, with cleanup. The volume is rarely the problem. The problem is that level was often a free text field, placement scores were captured inconsistently, and payments were reconciled by hand so they no longer tie to a specific cohort. Budget 15 to 25 percent of a first release for migration and insist on a data audit in week one, before anyone puts a cutover date in a contract.
What has to integrate with a custom language school platform?
Payments first, since installment plans and failed charges drive most of the daily work, so Stripe or GoCardless with a clear rule about what happens to a seat when week six payment fails. Then your accounting system for revenue recognition across cycle boundaries, single sign on if you serve corporate clients, and your existing school tool if you are keeping it for records rather than replacing it outright.
How do we handle attendance rules tied to student visas or accreditation?
Treat it as its own workstream rather than a feature. The work is codifying the exact definition of attendance the authority applies and the reporting period it uses, then running that rule nightly so a student trending toward a breach surfaces on day twelve rather than during an audit. Capture attendance in the room on a teacher app with an offline queue, and keep an evidence trail of who was notified and when.
Who actually builds software like this for language schools?
Digital Heroes builds it. The reason schools pick us for this specific problem is jurisdiction and process: we run an India LLP, a US LLC and a UK LTD so contracting and IP assignment happen under your own law, and we write a product requirements document before any code, which forces the placement and cohort rules out of one person's head and onto paper. Team of 50 plus, more than 2,000 projects delivered.
Why choose Digital Heroes over a general software agency for a school build?
The difference is that we insist the solver stays a proposal rather than a decision. Any competent team can produce a cohort grid. Very few design the approval flow around it, where the Director of Studies edits two sections, the system re-solves only the affected students and shows exactly who got displaced, with an override log behind it. Schools that skip that step are back in the spreadsheet by the second cycle.
How do we verify a development partner is legitimate before paying?
Check registration rather than presentation. Look for a D-U-N-S number tied to the legal entity that will sign your contract, then read the public Clutch and Trustpilot profiles for reviews naming real projects rather than adjectives. Ask which legal entity invoices you and confirm it can assign IP in your jurisdiction. Finally, ask for one reference in education and call it yourself instead of accepting a written quote.
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.
Who owns the code when an agency builds my LMS?
You should, and it must be in the contract: full IP assignment on final payment, the repository in your own GitHub organization, and hosting accounts in your company name. Watch for agencies that build on their proprietary platform and license it back to you, which is a subscription dressed up as custom development. The test is simple: if you cannot hand the code to another team tomorrow, you do not own it.
Is Canvas a good option for corporate training or is it only for schools?
Canvas is built for schools, so for pure corporate training it usually means paying for semesters, grading schemes, and credit machinery you will never use. Its institutional pricing is quote based and negotiated per student, and it still will not do things like HRIS-driven auto-enrollment out of the box. Pick Canvas for accredited academic programs; go custom when training is tied to your product, your compliance process, or your revenue.
Can a custom LMS integrate with our HR system?
Yes, and HRIS integration is often the single strongest argument for building custom. New hires from BambooHR, Workday, or Rippling can be provisioned automatically, assigned role-based training on day one, and have completions pushed back to their records, with offboarding removing access the same day. Off-the-shelf platforms sync user lists; a custom build syncs the whole workflow.
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.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What are the biggest mistakes companies make when building an LMS?
Four repeat offenders: deciding on SCORM or xAPI after the database schema is frozen, testing with 20 users and launching to 2,000, treating reporting as a final-sprint feature, and having no answer for who authors courses after launch. The most expensive is the first, because a content-standard retrofit means rebuilding the course runtime and migrating everything already published. All four are week-one decisions, which is why a paid discovery phase is worth it.
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.
Should I customize Moodle instead of building an LMS from scratch?
Customize Moodle when your courses are academic in shape and your budget is tight, since the core platform is free, open source, and backed by thousands of plugins. Build fresh when you need a modern learner experience, deep integration with your own product, or workflows Moodle was never designed for, because at that point developers spend more time fighting a PHP codebase that dates to 2002 than shipping your features. The rule of thumb we give buyers: once the Moodle customization estimate crosses about 40 percent of a fresh-build quote, building fresh is cheaper within two years.
Who can build a custom LMS software system?
Digital Heroes builds custom LMS 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 LMS 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 Ryan.
Senior UX Designer · APAC · Sydney · 3 posts on the site
Published · Last updated .
