Cash flow, fund balances, tax rates, debt, capital, and board reporting, projected five years out and accurate to Indiana law.
Upload the reports your ERP already produces. FundView validates the numbers, drafts the board narrative, and assembles the packet, all before your next board meeting.
The Command Center tracks each month like a checklist: reports uploaded, numbers validated, narrative approved, packet sent. You always know exactly where the month stands and when the board meets next.


Every fund is projected five years out, monthly where you manage and annually where you plan. Freeze a plan of record, then watch filed actuals track against it as the year unfolds.
Every screen below is the live application. This is what your business office signs into.
Not a general chatbot. The assistant answers from three things no outside AI can reach: your district's own numbers, a verified library of Indiana law, and your own documents.
"What happens to fund balance if the referendum fails?"
Answered straight from your live five-year projection, and every figure is checked against your data before it reaches the screen.
"When is the AFR due, and can we still appeal the levy?"
Answered from rules verified against DLGF, SBOA, IDOE, and IEERB publications, with the citation and verification date attached.
"What does board policy say about fund balance targets?"
Answered with the exact passage quoted word for word, with the page number, from documents your office approved.
Ask about compliance and the assistant returns verified deadline cards: the date, the agency, the rule behind it, and a link to file. If a rule is not in the verified library, it says so instead of guessing.


Board policies, bond memos, master plans, and board packets become part of the assistant's memory. Every upload is screened first, and anything sensitive is held for a human decision before the assistant can quote a word of it.
The assistant cites its sources, says when it does not know, and never invents a statute. That discipline is the product.
ERPs process transactions. Analytics tools chart history. The forward-looking work still lives in spreadsheets, and it depends on whoever built them. That is the gap FundView closes.
| ERP Systems | Analytics Platforms | FundView | |
|---|---|---|---|
| Primary function | Transaction processing | Historical reporting | Forward-looking planning |
| Cash flow projections | No | Limited | 5-year, object-code level |
| Referendum planning | No | No | Full module, statutory timeline |
| Capital, debt, and fleet plans | No | No | Built in, statute-grounded |
| Compliance calendar | No | No | Indiana deadlines, verified |
| AI analysis | No | No | Built in, validated answers |
| Board reporting | Export to Excel | Dashboards | Presentation-ready views |
| Indiana-specific | Yes | Varies | Built for Indiana statute |

Steve Troyer spent 22 years in Indiana public education, including five as superintendent of a 2,500-student district: a $32M operating budget, $77M in capital projects, and roughly 450 employees. He has presented fund balances to a school board, planned around circuit breaker losses, and made the case for an operating referendum with real money on the line.
FundView is not a tech company's guess at school finance. It is the tool a former district leader built for the people doing the work he used to do, refined every month with the business offices using it.
Thirty minutes on your district's financial operations: what you use today, what is working, what is not. We walk the live platform and answer every question.
We configure FundView with your district's actual structure: funds, object codes, enrollment, tax rates. You judge it on your own numbers, not a demo district's.
If FundView solves the problem, we talk pricing and timeline. If it does not, you spent thirty minutes and know what is possible. No pressure either way.
Questions first? Write to steve@thewillowrungroup.com or call (574) 238-8179.
No. FundView sits alongside your ERP. It imports the reports systems like Boyce and Komputrol already produce, then adds the forward-looking layer: projections, planning modules, board reporting, and AI analysis.
FundView is built only for Indiana school finance. Fund structure, SBOA object codes, tax rate mechanics, circuit breakers, and referendum rules follow current Indiana statute, including the SEA 1 changes. Every rule in the compliance library carries its citation and the date it was verified against the agency source.
Each district runs in its own isolated deployment with its own database. Nothing is shared between districts. Data is encrypted in transit and at rest, and sign-in runs through your district's own Google accounts.
Every figure the assistant produces is checked against your district's actual data before it appears; anything that fails the check is removed. Legal claims must trace to the verified rule library or they do not ship. When the assistant does not know, it says so.
Analytics tools report on where money went. FundView projects where money is going and manages the plans built on those projections. Districts run both, or replace the forecasting spreadsheets entirely.
Initial setup, including data import and district configuration, typically takes one to two weeks. A working walkthrough with your own data can be ready in days.
FundView is a per-district annual subscription. Exact pricing depends on modules and district size, and we put it on the table at the walkthrough, before any commitment.
Thirty minutes, no obligation. If it does not fit, you will know quickly.