Teacher Evaluation and Professional Growth Software: Build vs Buy
Buy. If you evaluate under roughly 1,200 certificated staff on one rubric and one bargaining agreement, Frontline Professional Growth or Standard for Success will serve you and a build will not repay.
On this page
Buy. If you evaluate under roughly 1,200 certificated staff on one rubric and one bargaining agreement, Frontline Professional Growth or Standard for Success will serve you and a build will not repay. The line moves when you carry three or more bargaining units, need contractual observation windows enforced in school days, or have already settled a grievance on process rather than on substance.
What Frontline, Standard for Success and PowerSchool Perform do well
You already have a rubric that works. What you probably do not have is a defensible record of when each observation happened. That is the real gap, and most districts should close it by buying rather than building.
Frontline Professional Growth is the most widely deployed option and it earns that on forms, routing and professional development tracking. If you already run Frontline for absence management or applicant tracking, the evaluation module arrives with staff records in it, which removes a nightly file nobody wants to own. Standard for Success is genuinely faster in the field: a principal captures low inference notes on a phone at the back of a room and tags them to indicator 3b of the Danielson Framework for Teaching before the lesson ends. Whetstone Education is the strongest of the group on coaching cadence, which is the part that changes instruction rather than the part that documents it. PowerSchool Perform sits beside the student information system, so rostering, assignment and staff changes arrive without an integration project.
None of these are weak products. A district that buys one and uses it properly runs a better process than a district that builds one and half adopts it. They handle rubric versioning, evidence storage, teacher acknowledgement, summative form generation and the reporting a superintendent asks for, and they are configurable enough to hold the Marzano Focused Teacher Evaluation Model or a locally written framework.
If you evaluate one bargaining unit, on one rubric, under a contract that has been stable for three cycles, stop here and buy. Spend the difference on instructional coaching. We say that to districts regularly and it costs us work.
Where they stop: the contractual observation window
The stopping point is the same in every district we have worked with, and it is not the rubric. It is the timeline.
Your collective bargaining agreement, not the framework, is the specification. It sets how many announced and unannounced observations a tenured teacher receives and how many a probationary teacher receives. It says whether a walkthrough under a stated number of minutes counts toward the required total. It says how many school days, not calendar days, may pass between a visit and the written feedback. It sets pre conference notice, who may observe, and whether a second evaluator is triggered when a rating drops a band.
Packaged products record what you did. They do not compute in school days against your district calendar, so a snow day inside a five day feedback window is invisible to them. They do not tell a middle school principal on the third of March that he has eleven school days left and two unannounced visits outstanding on a teacher carrying a non renewal recommendation. They record the visit he finally logs on the nineteenth of April for a walkthrough he says happened in November, and that record is what the association representative will ask to see.
The second stopping point is the composite. Student growth enters through a state produced measure for tested subjects and through locally written student learning objectives for everyone else, which is most of your staff. Weights, minimum data thresholds, rounding rules and cut scores sit in the contract or in state rule. When a settlement lands in July and has to be live in September, a vendor configuration cycle is not a schedule you control.
The arithmetic: cost per certificated staff member versus a build
Do this with your own renewal figure rather than ours. Products in this category are priced per certificated staff member per year, often bundled into a suite so the line is not visible until you ask for it broken out.
Divide the annual figure by headcount to get a rate per staff member. Now take the build side. A first release covering observation capture, evidence tagging and a contract aware timeline engine runs $70,000 to $140,000 in our delivery experience. Amortise the midpoint across five years, add year two support at the rate in the next section, and you carry roughly $28,000 to $34,000 a year for a system you own.
At a quoted rate of $10 per certificated staff member, the build breaks even somewhere near 2,800 to 3,400 staff. At $20 the crossover halves to roughly 1,400 to 1,700. At $40, which is where per seat pricing lands once professional development tracking and state reporting are added as modules, it falls near 700.
Two adjustments matter more than the rate. Add the staff time the product does not remove: the two to three weeks of human resources (HR) and principal time that vanish every spring reconstructing a paper trail. In a district of 2,000 that is frequently larger than the licence. Then subtract nothing for risk. One settled grievance on process is never a line in a software budget, and it is the reason most build decisions here actually get funded.
What a custom build actually costs
Bands first, then the lines nobody quotes.
A first release covering process templates by bargaining unit and tenure status, offline capable mobile capture with device timestamps, an evidence library with amendment history, and caseload dashboards showing days remaining rather than work completed, runs $70,000 to $140,000 and ships in 12 to 18 weeks. Time it to land before your first observation window.
A full platform adding the summative composite versioned by year and unit, student learning objective workflow, improvement plan generation with checkpoints and second evaluator assignment, a professional development hours ledger tied to licence renewal cycles, and the state reporting export runs $180,000 to $450,000 across 8 to 14 months.
Data migration is the line that surprises people. Budget 10 to 25 percent of build cost. You are moving staff records, historical ratings, rubric versions and improvement plans, and the historical ratings are the part that will not tie out, because they were computed in a spreadsheet that has been edited since. Move the current and prior school year fully, archive the rest as searchable documents, verify a sample by hand.
Year two runs 15 to 20 percent of build cost annually for support and enhancement, and that figure is not optional here. Your contract gets renegotiated, your state changes the growth weight, your student information system upgrades. A system nobody maintains becomes a spreadsheet again inside two cycles.
The four situations where building wins
Four conditions move a district across the line. One alone is rarely enough. Two together usually are.
- Regulatory and contractual fit. Your state mandates a composite your vendor cannot configure without a change request, or your agreement expresses observation counts, notice and feedback windows in school days with per unit variation. Evaluation records are employee personnel records rather than student education records, so access is governed by your state personnel file statute and the confidentiality terms in the contract, not by the Family Educational Rights and Privacy Act. Any product built around a student data model has misread the problem.
- Scale economics. Above roughly 1,500 certificated staff, spring reconstruction stops being an inconvenience and becomes a staffing decision. That is also where the arithmetic above turns in favour of ownership at most quoted rates.
- A workflow that is your advantage. For a charter network or a regional service centre, the evaluation and coaching model is part of what you offer member districts and the teachers you recruit. Multi tenancy with genuinely different rubrics, timelines and composite rules per school is exactly where packaged district products assume one district with one configuration.
- Integration sprawl across three or more systems. Count honestly: the student information system for rosters, the human resources system for tenure status, the professional development catalogue, the licence renewal register, and the state reporting file. That is five, and most districts keep at least two synchronised by hand.
How to decide in a week
Run this test before you talk to anyone. Pull twenty summative packets from last spring at random, including three teachers who were on an improvement plan. For each one produce four things: the date of every required observation, the date written feedback was delivered, the elapsed school days between them against your district calendar, and the evidence attached to each rating band. Give it an afternoon.
Count how many of the twenty you can defend without opening an email thread or asking a principal what he remembers. If it is eighteen, your process works and a build is an expensive way to feel safer. If it is under twelve, no rubric change fixes it, because the failure is in dates, notice and evidence rather than in judgement.
Then ask your vendor two questions in writing: how the system computes a feedback window in school days against a calendar you upload, and what happens to a submitted observation when the evaluator wants to change a word after the teacher has acknowledged it. The right answer to the second involves an amendment record with the original preserved and the author named. If either answer is a change request, you know what you are buying.
If the test points to building, the next step is a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the data model, process templates per bargaining unit, permissions and acceptance criteria. You own that specification and can take it to any other firm on your shortlist. We are the wrong firm if you want a hosted product with a support desk and no engineering ownership on your side, or if nobody in the district yet has authority to say what the contract means. We are an India LLP with US LLC and UK LTD entities so the intellectual property assigns under your own law, more than fifty specialists and over 2,000 projects delivered, with a named team you meet before signing and a record you can check on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SHRM's 2025 benchmarking data puts the average cost-per-hire at $5,475 for nonexecutive roles and $35,879 for executive roles - executive hires are on average nearly 7x more expensive than nonexecutive hires. Source: SHRM (Society for Human Resource Management) (2025) →
- An earlier SHRM benchmarking report (reflecting fiscal year 2015, published 2016) established a widely cited baseline average cost-per-hire of $4,129, illustrating how recruiting costs have climbed over time (SHRM's separate 2025 Benchmarking Report shows $5,475 for nonexecutive roles). Note: the $5,475 figure is not on this linked page; it comes from SHRM's 2025 report. Source: SHRM (Society for Human Resource Management) (2016) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
How long does it take to build a teacher observation system before the first window?
Twelve to eighteen weeks for a first release covering capture, evidence and the timeline engine. The schedule risk is rarely engineering. It is getting one authoritative reading of the bargaining agreement, because human resources, the association and building principals often describe the same clause three different ways. Districts that put those three parties in a room during week one finish noticeably faster than districts that resolve each disagreement by email.
Who owns the evaluation data and the code if an agency builds it?
You should own the repository, the cloud accounts and the unrestricted right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit. This matters more than usual here because the records are employee personnel files that may be produced in arbitration years later, and a record you cannot reach without a vendor's cooperation is not a record you control.
What happens if our bargaining agreement changes in the middle of the school year?
The system needs process templates that are versioned and effective dated, so observations completed under the old rules keep the old rules while new cycles pick up the new ones. Settlements often land after the year has started and sometimes apply retroactively. Ask any prospective vendor this directly. A product that stores a single current configuration cannot answer it honestly, and configuration cycles rarely match your September deadline.
Can we keep Frontline for professional development and build only the timeline engine?
Yes, and for many districts that is the sensible first move. A timeline engine anchors on the observation date, computes notice and feedback windows in school days against your district calendar, and escalates to the principal before the window closes rather than after. It touches neither your rubric nor your professional development catalogue. Expect a much smaller scope than a full platform and a correspondingly shorter delivery.
What is the difference between a walkthrough and a formal observation in software terms?
In most contracts a walkthrough is shorter, may not require notice, and only counts toward the required total if it exceeds a stated duration. A formal observation carries pre conference notice, a minimum length and a post conference. In software they are separate event types with different required fields, different clocks and different evidence rules. Products that model one observation type with a duration field push the difference back onto principals.
Should a charter network with several contracts buy or build?
Building usually wins, and it wins on multi tenancy rather than on features. Packaged district products assume one district with one configuration, so genuinely different rubrics, observation counts and composite rules per school become workarounds. Budget for tenant level configuration and reporting that rolls up across the network, and expect the network office to become the owner of a shared process rather than a collector of spreadsheets from each school.
Do teacher evaluation records fall under FERPA?
Evaluation records are employee personnel records, not student education records, so the Family Educational Rights and Privacy Act is the wrong frame for the access model. What governs is your state public records and personnel file statute plus the confidentiality terms in the bargaining agreement. Practically a principal sees their caseload, human resources sees the district, and draft access is contract dependent. Student data appearing inside a growth measure does carry its own obligations.
Can the system compute licence renewal hours from the same record?
Yes, and connecting them is where teachers notice the difference. The build links the growth or improvement goal to the learning activity completed, the hours it carried, and the educator renewal cycle, so a teacher sees one page rather than assembling a folder in June. Human resources gets a verification queue instead of a stack of sign in sheets. This is normally second phase work rather than first release.
What happens if we build and the state changes the student growth weight?
Nothing breaks if the composite formula is versioned by school year and bargaining unit and the inputs are stored rather than only the output. You add a new formula version with an effective date, and prior years continue to recompute to their original numbers. That property is also what lets you answer an appeal on a three year old rating with a printable derivation rather than a reconstruction.
How do we migrate ten years of ratings without inheriting errors?
Do not migrate ten years. Move the current and prior school year completely, with rubric versions and evidence, and archive everything older as searchable documents linked to the staff record. Historical ratings computed in spreadsheets that have since been edited will not reconcile, and forcing them to is the most common reason these projects overrun. Verify a hand picked sample of the migrated years rather than trusting a row count.
How long does it take to build a custom HR system?
A working first version takes 12 to 16 weeks in Digital Heroes projects: employee records and onboarding first, then time off and reporting. A full platform with applicant tracking, performance reviews, and payroll integration is a 6 to 9 month effort. Anyone quoting a complete HR suite in 4 weeks is describing a template, not custom software.
Can we keep using BambooHR while the custom system is being built?
Yes, and you should; the standard approach is to run both in parallel and cut over one module at a time, using BambooHR's API to keep employee data in sync. Your HR team keeps working normally while each new module is tested against real records. The final cutover then retires a system you have already replaced in daily use, not one you are gambling on.
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.
At what point does a company outgrow BambooHR?
The breaking point Digital Heroes sees most often is 100 to 250 employees, when approval chains, multi-state rules, or shift scheduling stop fitting BambooHR's fixed workflows and HR starts managing exceptions in spreadsheets. If your team exports to Excel every week to do something the platform cannot, you have already outgrown it. Per-employee pricing compounds the problem, since the bill grows with every hire while the feature gaps stay the same.
How do I vet a developer or agency for an HR software project?
Ask two questions: show me a project where you handled sensitive employee data, and walk me through how you would stop a manager from seeing salaries outside their team. Teams that have built HR systems answer the second one immediately with role-based access design; teams that have not will improvise. Also ask which payroll APIs they have integrated, because ADP, Gusto, and Paychex each behave differently in practice.
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.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Who can build a custom HR software system?
Digital Heroes builds custom HR 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 HR 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 .
