For EdTech companies
Advice from the district side of the table, and extra hands when your roadmap is bigger than your team.
Your software is not failing in the build. It is failing in the district — bought with money that has now dried up, rolled out to staff who have since turned over, and quietly unused by March. Software nobody opens does not get renewed.
Extra hands are easy to hire. Hands that have sat on the district's side of the table are not. We have been the district-side people deciding whether your category of software got adopted — and we have built and shipped it too.
The bit nobody else can offer you
- Michael: 35+ years in software delivery, first as a developer, then director and above, at large enterprises and startups. Certified Scrum Trainer® since 2006; co-author of The Enterprise Unified Process (2005); Implementing Scrum published weekly since 2006 — the half many agile coaches have.
- Michael: a decade inside a school district's leadership team, advising Blueprint Education, an Arizona charter district, since 2014 — the half almost no agile coach has.
- Kenton: six systems architected and run in a real district. Designed against real SIS and LMS data (rostering from SIS exports, student identity matching, LTI 1.3 launches), with the hard parts written up in The Standardless Standards of EdTech. They are on this site as evidence, and available to license (below). We know what a registrar will actually open on a Tuesday.
Advise: four ways in
Every engagement has started as a conversation rather than a package, and nothing here is priced off a shelf.
Coaching your product and engineering teams
The delivery work you would expect from a Certified Scrum Trainer — with someone who can also tell you why the last district rollout stalled.
Ask about it below — choose “Education — Consulting”.
Discovery and product advisory
Before you build it: will a district adopt this, who has to say yes, and what will quietly kill it in month three. We have been the people who decided.
Ask about it below — choose “Education — Consulting”.
Training and workshops for your staff
Sessions for product, engineering and customer-facing teams — including what school and district buyers actually care about, which is rarely your feature list.
Ask about it below — choose “Education — Training”.
A fractional seat with your leadership
The district's Impact Team arrangement, on the vendor side: in the room when the decisions get made, ongoing rather than a report.
Ask about it below — choose “Education — Mentoring”.
We get our hands dirty with you
We don't build for districts directly. We build with the companies that serve them.
You work directly with the founders: Kenton leads engineering, Michael leads product and delivery.
Engineering capacity
Kenton Vizdos, our Chief Architect, works alongside your engineers: SIS and LMS integrations, data pipelines, the roadmap item that keeps slipping. How he approaches integrations →
Ask about it below — choose “EdTech: Extra capacity”.
Product and delivery
Michael embedded as product owner, Scrum Master or delivery lead until your team can carry it.
Ask about it below — choose “EdTech: Extra capacity”.
District implementation
We work with your customers so what you sold is rolled out and in use before renewal.
Ask about it below — choose “EdTech: Extra capacity”.
Licensing
Six systems we built and ran in a district, licensed into your product instead of built from scratch.
Ask about it below — choose “EdTech: Licensing”.
How we contract
- Direct services agreement. You contract with Edvizion, and we scope the work with you before it starts.
- Subcontractor under your contract. We work inside your existing agreement with a district, under your statement of work.
- Teaming partner on a bid or RFP. We join your response as a named partner before it is submitted. Ask about it below — choose “EdTech: Teaming on a bid”.
Where we overlap, we say so. Michael advises a district's leadership team. If your work touches it, both sides hear it from us first.
Need one page to forward to your team? Download the EdTech one-pager (PDF, 1 page).