Built by someone who lived the problem

My name is Corey Canfield. I've spent over 15 years working in K-12 schools — and for most of that time, I tracked devices in spreadsheets just like everyone else.

I've been the person getting called when a Chromebook goes missing the week before state testing. I've been the one building the refresh plan in Excel at 11 p.m. because the board presentation is in the morning. I've tracked loaner carts on sticky notes. I've inherited a "device inventory" that was a shared Google Sheet with four people's edits fighting each other.

None of that is a failure of effort. It's a failure of tools.

The software built for K-12 IT is either too expensive, too complicated, or not really built for education at all — it's enterprise software with a school discount painted on top.

I looked at what was available and it fell into two categories: platforms designed for corporate IT that cost more than a school's entire hardware budget, stuffed with features no district would ever touch — or nothing, which is how the spreadsheets keep winning. I kept waiting for something built specifically for the way school IT actually works. When it didn't show up, I built it.

What I was trying to solve

School technology directors don't have large teams or large budgets, but they carry a lot of responsibility. Every device they manage may hold student data. Every ticket they field could be a teacher unable to teach. Every refresh cycle they miss creates a budget problem three years later that surprises everyone except them.

They need tools that work the way school IT works — where a broken screen becomes a ticket, becomes a loaner checkout, becomes a line in next year's refresh forecast. Where the AUE clock on a Chromebook actually matters. Where "user" might be a third-grader who just dropped something in a puddle. Where the board wants a clear answer to "what do we need to spend and why?" and you need real data to back it up.

No system handled all of that in one place at a price that made sense for public school budgets. So Edventory does.

What I believe

• Simplicity isn't a feature — it's the whole point. A tool only helps if people actually use it. I've watched expensive platforms get abandoned within a year because they were too hard to train on and too slow to get anything done in. Edventory has to be fast to learn and fast to use, or it's useless.
• Privacy is a constraint on everything. School technology touches student data. That's not a compliance checkbox — it means no ads, no trackers, no data resale, FERPA-conscious design in every corner of the product. Student data is never used to train AI models. It stays yours.
• Priced for public money. School districts don't buy software the way businesses do. They have fiscal years, board approvals, purchase orders, and budget ceilings. Every plan should fit how schools actually spend money — and a Free tier should be genuinely free, not a bait-and-switch trial.
• Every plan gets every feature. I will never lock audit logs, two-factor authentication, or your own export behind an "enterprise tier." The tool should give you everything it has; the plan just scales with your fleet.
• Honest numbers, always. When the AI forecasts your refresh budget, it tells you what assumptions it's making and flags gaps in your data. A number that sounds right but isn't is worse than no number at all — especially when a board is voting on it.

Where things stand

Edventory is a real, working tool in active use — not a landing page with a waitlist. I'm onboarding districts in early-access cohorts and shaping the roadmap directly with the technology directors and technicians using it every day. It's moving fast because I know exactly what problem it needs to solve.

If you're a technology director tired of the same broken options, I'd genuinely love to talk about how your district runs and whether Edventory fits.