School District Budgeting and Position Control Software: Build or Buy

What the off the shelf products actually do well

Your finance system already has a screen labelled position control, and it is better than the people complaining about it usually admit. Tyler Technologies Munis and Skyward Business Suite are strong systems of record. They hold the general ledger, encumber salaries, run payroll and keep the transactional record straight through an audit. Frontline ERP goes further on the join districts most often get wrong, tying a hiring requisition to a position, because human resources (HR) and finance sit inside one product. Allovue is a genuinely good layer for pushing budgets down to principals and showing each school what its funding source composition looks like. Forecast5 handles multi year forecasting and peer comparison capably at fund and object level.

Most districts should buy. If you employ under about 500 people, run largely on the general fund with a handful of grants, and negotiate with one or two bargaining units, the position control module you already pay for plus a well maintained workbook is proportionate to the problem. A custom platform at that size becomes a maintenance obligation that outlives the budget director who commissioned it. We tell districts this regularly and it costs us work.

The honest floor sits lower still. A charter network with 90 staff on a single salary schedule does not need planning software. It needs the advancement rules written down, a named second reader on every projection, and a standing rule that no requisition leaves the office without a funded position number attached to it.

Where they stop: the split funded position

The object generic products model badly is a person paid from four sources. A bilingual instructional coach might sit thirty percent general fund, thirty percent Title I, twenty five percent Title III and fifteen percent a state grant. Three numbers then have to agree: the split on the position record, the semiannual certification or personnel activity report you keep under the Uniform Guidance at 2 CFR Part 200, and what payroll actually distributed. They drift apart within weeks of the school year starting, because the split is entered once and the reality moves.

Here is the failure that funds these projects. A reading interventionist is hired in April into a position vacant since a grant year that has already closed. The vacancy still carries its old seventy thirty split. Human resources fills it because the requisition exists, payroll charges what the position record says, and in the third week of October your distribution report shows several hundred thousand dollars against the general fund that the adopted budget placed in a federal grant. Nobody was wrong at any single step.

The second gap is projection. Your salary schedule is a grid of steps and columns with your own longevity increments, your own stipend table and your own rules for column movement on credits earned. A finance system computes the current year correctly, because that is a payroll calculation. It does not walk four thousand employees across that grid for three out years and hand you an employee level result you can drill into. That is why the workbook exists, and why it leaves the building when its author retires.

The arithmetic: per employee licensing versus a build

Planning and position control modules in this category are priced per employee per year, or as an uplift on your existing enterprise resource planning contract. Whatever number lands in your quote, do three things with it before you compare anything. Multiply by headcount. Multiply again by five, because that is the horizon a build has to be judged over. Then add the cost nobody puts in the comparison, which is analyst time: the days spent rebuilding the projection workbook every February, the days spent reconciling distribution against the adopted budget, and the week that disappears when the board asks what a settlement costs.

At 900 employees the subscription wins comfortably. Five years of licensing plus a workbook that is ugly and nearly free costs less than any build, and the risk is lower. At 3,500 employees with three bargaining units, the same per employee rate has become a six figure annual line and the analyst time behind it is a second salary you are already paying. The crossover for districts we have priced sits between roughly 2,000 and 3,000 employees. It moves down quickly once grant funded staff pass about a fifth of headcount, because split reconciliation is labour that scales with complexity rather than with headcount.

Run that number honestly before you read the rest of this page. If you are below the line, go and renegotiate your renewal instead.

What a custom build actually costs

A first release covering authoritative position records, requisition gating, effective dated split funding constrained by grant award periods, and salary schedule projection across your own grid runs $90,000 to $180,000 and ships in 16 to 22 weeks in Digital Heroes delivery experience. A full platform adding enrollment driven staffing allocation, settlement scenario branching and monthly reconciliation of adopted budget to actual payroll distribution runs $250,000 to $600,000 phased across 9 to 15 months.

Two lines sit outside those bands and both are routinely missing from quotes. Data migration runs 10 to 25 percent of build cost, and in this category it lands at the top of that range whenever position history has to be reconstructed rather than copied, because a projection computed from a messy history is worse than no projection at all. Year two and every year after runs 15 to 20 percent of build cost annually, covering salary schedule changes after each settlement, state chart of accounts revisions, and the interface work that follows any upgrade to your finance system.

Cost climbs with the number of bargaining units, since each carries its own schedule structure and advancement rules. It climbs when an on premise Tyler or Skyward instance means a negotiated database interface rather than an application programming interface. It falls when you accept that the finance system stays authoritative for actuals and the build owns planning only, which is the scope we recommend in nearly every case.

The four situations where building wins

• Regulatory fit. Federal time and effort expectations under 2 CFR Part 200 require the charged split and the certification on file to agree, and your state mandates its own account code structure for reporting that will not accept your internal codes. A build enforces both as constraints instead of reporting on them afterwards.
• Scale economics. A county office of education, a regional service agency or a charter management organisation running budgets for several entities with different bargaining units and different charts of accounts is a multi tenant requirement, and per district licensing across a dozen tenants is where the arithmetic above stops being close.
• A workflow that is your competitive advantage. Pricing a three percent settlement with a step adjustment across three years, by fund and by bargaining unit, during the session rather than a week later, changes how you negotiate. No product models your advancement rules closely enough to do that.
• Integration sprawl across three or more systems. Position data has to reconcile across your student information system for enrollment projection, an applicant tracking and human resources system, the finance ledger, a grants management system and your state reporting submission. Once five systems disagree about one full time equivalent, the reconciliation is the product.

One of those alone is rarely enough. Two or more, and the build is usually cheaper than the year you are already spending on workarounds.

How to decide in a week

Run this test instead of another vendor demonstration. On Monday pull 25 positions at random from your most recent monthly distribution report. For each one, place the adopted budget split, the current position record split and the actual payroll distribution side by side. On Tuesday count how many of the 25 disagree, and for each disagreement write down which department created it and in which month. On Wednesday ask your budget analyst to time, honestly, how long a three year projection takes from a standing start. On Thursday ask your grants coordinator to produce certification evidence for the five most heavily split positions.

By Friday you will know whether you have a tooling preference or a control problem. If fewer than three of the 25 disagree, renew and stop reading about this. If a third disagree and each traces to a different department, no product will fix it, because the errors originate upstream of finance.

Then buy the specification before you buy the software. Digital Heroes runs a paid discovery phase that ends in a signed product requirements document covering the position data model, the split approval workflow, acceptance criteria and a fixed price, and you keep that document whoever builds from it. We are wrong for districts that want code started next week without settling advancement rules first, and wrong for anyone who needs people in the building every day, because we have no local office anywhere and will not pretend otherwise. We do have more than fifty specialists, over 2,000 delivered projects, in house products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. You meet the named engineers before signing, and you can check us 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.