Educator Preparation Program Management Software: Build or Buy at Your Candidate Volume
The number that decides this is candidates placed per year.
On this page
The number that decides this is candidates placed per year. Under roughly 150 a year in one or two licensure areas within a single state, buy Watermark Tk20 or Anthology Chalk and Wire and put the money into placement staff, because at that scale a good coordinator outperforms software. Over roughly 400 a year, or across more than one state, placement stops being a scheduling task and becomes a constrained assignment problem, and a first release runs $65,000 to $140,000 over 12 to 18 weeks. Most colleges of education sit between those numbers, which is why the hybrid, keeping the assessment platform and building only the field office layer, is the answer we give most often.
When is off the shelf genuinely the right call here?
Watermark Tk20, Watermark LiveText and Anthology Chalk and Wire are the established products in this category, and they are genuinely strong at what they were built for: rubric based assessment collection, portfolio management, and reporting aligned to standards frameworks. If your central problem is aggregating key assessment data against the standards of the Council for the Accreditation of Educator Preparation (CAEP), that is the job these products do, and rebuilding it is poor value.
Buy if you place fewer than about 150 candidates a year in one or two licensure areas within a single state, with a stable set of partner districts. At that scale, placement is a scheduling task that a coordinator holds in their head and manages in a spreadsheet without drama, and the accreditation reporting is the harder half. Buy the product that does the harder half.
Buy also if your next self study is inside twelve months. A build during an accreditation cycle compresses everything and puts your evidence assembly on a schedule that engineering controls, which is a bad trade whatever the software promises. Get through the cycle on what you have, then decide.
And buy if your instruments are still moving. If faculty are actively revising rubrics and checkpoint structures, a packaged assessment platform absorbs that churn at no marginal cost, while a build absorbs it as change orders. Freeze your instruments first, then talk to a developer.
What these products are honestly thin on is the operational half, and you should not read this section as a criticism of them for it. Placement as a capacity constrained matching problem, cooperating teacher relationship and stipend history, clearance expiry gating, and formal disposition workflow with appeal paths are not what they were designed to carry, which is exactly why nearly every field office in the country runs a parallel spreadsheet next to a perfectly good assessment platform.
When does a custom build actually pay off?
It pays when placement has become an optimisation problem. Placing a candidate requires a district currently accepting placements, a school within a travel distance you are willing to pay mileage against, a cooperating teacher who holds the right certification and has capacity this term, a supervisor with room in that geographic cluster, and a grade and subject match for the licensure area. Underneath all of it sits clearance: background checks, fingerprinting, mandated reporter training and required testing, every one of which expires. Above roughly 400 candidates a year, no person holds those constraints simultaneously and the failures start arriving at partner schools on day one.
In Digital Heroes delivery experience the first release covering placement with clearance gating, checkpoint assessment capture at item level, and standards aligned evidence aggregation runs $65,000 to $140,000 in 12 to 18 weeks. The full platform adding disposition workflow, cooperating teacher management with stipends, state licensure recommendation and federal Title II preparation runs $180,000 to $420,000 phased over 7 to 13 months.
Build when two or more of these are true. You place more than roughly 400 candidates a year. You operate across more than one state, so clearance, testing and recommendation rules differ per candidate. You run many licensure areas with materially different checkpoint structures. Your last accreditation cycle required weeks of manual evidence assembly that nobody could reproduce. Or you have had a disposition decision challenged and found the record thin, which is the signal that turns a nice to have into a governance requirement.
How do they compare on the things that matter in this industry?
On assessment collection and standards reporting, buy wins. Item level rubric capture, portfolios and standards mapping are mature in the packaged products and expensive to rebuild well.
On placement, build wins outright, and the reason is structural rather than a feature gap. Packaged products treat a placement as a record stored after a human decides it. The decision itself, with district and school capacity caps, cooperating teacher eligibility and current load, supervisor travel clusters and licensure area matching all holding at once, is what a build models. That is why the spreadsheet survives the purchase.
On clearance, build wins because gating is the point. A field that says the background check is current is not the same thing as a system that blocks placement confirmation and start when anything has lapsed, alerts at horizons you choose, and knows that a clearance obtained in a junior year routinely expires before a final clinical placement eighteen months later.
On dispositions, build wins on the parts that matter legally. These are the most sensitive records a college of education keeps, and what they need is role scoped visibility, access auditing, append only storage with amendments rather than edits, documented notification, an improvement plan with checkpoints and a defined appeal path. A comments field on a form is cheaper and will not survive the one situation in which it is ever examined closely.
On state licensure portals, neither side wins. Portals such as New York's TEACH system or the Illinois Educator Licensure Information System rarely offer usable bulk interfaces, so the realistic design is a prepared file and supervised submission. Anyone promising full automation without having seen your state's system is guessing.
What does total cost of ownership look like at your scale?
Take a college placing roughly 600 candidates a year across nine licensure areas in one state, keeping its existing assessment platform as the evidence warehouse. Placement as a constrained assignment problem is $34,000. Clearance tracking with per requirement expiry and hard blocks is $16,000. Cooperating teacher and supervisor records carrying certification, training, capacity, stipend history and candidate feedback are $18,000. Item level checkpoint capture from mobile devices, tolerant of poor connectivity inside school buildings, is $22,000. Evidence aggregation mapped to accreditation standards and reproducible on demand is $20,000. Student information system integration is $12,000. That totals $122,000 and ships in about sixteen weeks.
Phase two, adding disposition workflow, rater calibration and agreement analysis, licensure recommendation packets and Title II preparation, adds roughly $100,000 to $160,000 and brings the programme to around $250,000 across the year. The disposition module alone is $25,000 to $45,000, and the cost sits underneath the screens rather than in them.
Running costs are 15 to 25 per cent of build value a year, so $18,000 to $31,000 on that release. Two lines sit outside it. State requirement maintenance is ongoing for every state you operate in. And if you keep the assessment platform, that renewal continues, which is a deliberate trade and belongs in both columns of the comparison.
Operating in a second state is the largest single multiplier in this category, commonly 30 to 50 per cent on a first release, because clearance rules, testing, performance assessment expectations and recommendation processes all become per state configuration bound to each candidate's intended licensure state.
What does the hybrid look like, and when is it the honest answer?
Keep the platform, build the field office layer. For most colleges of education this is not a fallback, it is the correct architecture, and it is what holds a first release near the bottom of the band rather than the top.
Concretely: Watermark Tk20 or Chalk and Wire stays as the evidence warehouse holding instruments, rubrics, portfolios and your historical cycles. You build placement, clearance gating, cooperating teacher and supervisor management, and an aggregation layer that can regenerate accreditation figures on demand from the underlying records. The two connect through candidate identity from your student information system, so a placement in one system and an observation score in the other belong to the same person without anyone retyping.
Replacing the assessment platform instead means rebuilding instruments, rubrics, portfolios and three cycles of historical evidence. That roughly doubles the first release and adds a migration your accreditation cycle will not thank you for. We have not yet met a college where that trade was worth it.
Sequence it so placement reaches coordinators first, before assessment capture. They will tell you within one cycle whether the constraint model matches reality, and their corrections are cheap in week eight and expensive in month five. Then run one full placement cycle alongside the existing spreadsheet before retiring it, and start that parallel period between cycles rather than during one.
Which should you choose, by operator size and stage?
A programme under 150 candidates a year, one or two licensure areas, one state: buy Tk20 or Chalk and Wire, hire a placement coordinator with the difference, and revisit in three years. Nothing here argues otherwise.
A programme at 150 to 400 candidates with a spreadsheet that is starting to fail: build the placement and clearance layer only, at the bottom of the $65,000 to $140,000 band, and keep everything else. This is the smallest useful project in the category and it targets exactly where staff time is burning.
A college at 400 to 800 candidates across many licensure areas in one state: the $122,000 shape above, with phase two timed to land before your next self study rather than during it.
A multi state college, a large system or a consortium where per campus rules and central reporting must coexist: expect the full $180,000 to $420,000 programme over 7 to 13 months, and treat the second state as a configuration layer scoped from day one rather than an increment added in month nine. Adding it late is the single most reliable way to overrun this build.
If you want that decision made properly rather than quickly, 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.
- McKinsey emphasizes that most L&D functions still fail to tie training to business outcomes, recommending organizations track 2-3 business-relevant indicators (such as time-to-proficiency, redeployment into priority roles, or frontline productivity) rather than participation metrics to demonstrate training effectiveness. Source: McKinsey & Company (2025) →
- 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) →
- 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) →
- 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 switch off Watermark Tk20 later if we want to?
The licence is the easy part. The expensive part is three or more cycles of historical evidence: instruments, rubrics, item level scores and portfolios that accreditation expects you to be able to produce. Moving that is a normalisation exercise with faculty judgement in it, not a data export.
The practical protection is to write the export right into your contract now, in a documented structured format at item level rather than as totals. Totals are worthless for the comparisons accreditation actually asks about.
What happens if our assessment platform changes its pricing at renewal?
If you kept it as the evidence warehouse under a hybrid, your exposure is the licence alone, and your placement, clearance and partnership data live in systems you control. That makes a switch a project rather than a crisis.
If everything runs inside the product, a pricing change is effectively unpriceable, because moving is a migration your next self study cannot absorb. That asymmetry is a fair reason to hold your operational records yourself even when the product is good.
How long before the field office is actually working in a custom system?
Three to four weeks of discovery with coordinators rather than faculty, then 12 to 18 weeks to a working release, then one full placement cycle running in parallel with the spreadsheet before it is retired.
Import partner districts, cooperating teachers and historical placements first. That relationship history is the asset your coordinators currently carry in their heads, and getting it into structured form is worth more in release one than any feature.
Can we just build placement and leave everything else alone?
Yes, and for many colleges that is the right first project. It is where staff time is burning, it is the half of the category packaged products leave thin, and it produces partnership data nobody currently has: how many candidates each district took over five years, which schools produce strong outcomes, which cooperating teachers your candidates consistently rate highly.
Scope it with clearance gating included from the start. Placement without clearance gating is a directory, and you already have one of those in a spreadsheet.
Will a build submit licensure recommendations to the state for us?
Not fully, and you should not pay for a promise that it will. State portals such as New York's TEACH system or the Illinois Educator Licensure Information System rarely expose usable bulk interfaces, and automation built against them is fragile.
Scope the version that works: assemble the eligibility packet, verify completion, testing and clearances, flag what is missing per candidate in April rather than July, produce a prepared file for supervised submission, and retain the recommendation record for verification requests years later.
How much does operating in a second state add to a build?
Commonly 30 to 50 per cent on a first release, and it is the largest single multiplier in this category. Clearance requirements, required testing, performance assessment expectations and recommendation processes all differ, so each becomes per state configuration bound to a candidate's intended licensure state rather than a programme wide setting.
Reporting multiplies as well, since each state publishes its own expectations alongside federal Title II obligations, drawn from the same records in different shapes.
Is a disposition module worth building on its own?
Only if you have had a decision challenged, in which case it moves from useful to necessary. Budget $25,000 to $45,000 and understand that the cost sits under the screens: role scoped visibility so a concern filed by one instructor is not broadcast to all faculty, access auditing, append only storage with amendments rather than edits, notification records, improvement plans with checkpoints and a defined appeal path.
Built as a form with a comments field it costs a fraction and fails in the only situation where it will ever be read closely.
Who owns the code and the records if an agency builds this?
You should own the repository, the data and the cloud accounts, written down before kickoff. At Digital Heroes the institution owns the repository and the data from the first commit.
Retention matters more here than in most categories. Licensure recommendations get queried years later, sometimes by another state, so agree how long records are kept and in what form they remain producible after any vendor relationship ends.
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.
Can a custom LMS handle 10,000 or more learners?
Yes, if scale is a design input rather than a hosting upgrade: enrollment and progress modeled as event-style records, video offloaded to a streaming CDN, and reports served from aggregates instead of live table scans. Most LMS scaling failures trace back to a schema tested at demo size, not to undersized servers. The question to put to an agency: what happens Monday at 9 a.m. when 3,000 people open the same compliance course before a deadline.
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.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What tech stack should a custom LMS be built on?
A boring, hireable one: React or Next.js on the front end, Node.js or Python on the back end, PostgreSQL for data, and a managed video service like Mux or Cloudflare Stream instead of self-hosted video. The stack matters far less than the enrollment data model and the SCORM/xAPI runtime, which is where LMS builds actually succeed or fail. The red flag is an exotic stack chosen for the agency's own interest that nobody in your market can maintain.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
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 Kabir.
Director of Mobile Engineering · Delhi · 2 posts on the site
Published · Last updated .
