DispatchDispatch
EdTech Intelligence — Every Tuesday, 7 AM
Every Tuesday at 7 AM, one EdTech story — the funding round that reshapes a category, the policy shift that kills a business model, the quiet API update that unlocks a new market. Written for people who need signal before the noise settles.
I spent six years writing reports nobody read.
At a major LMS company, my job title was "Market Intelligence Analyst." What that actually meant: I read every EdTech trade publication, every funding announcement, every policy brief that crossed the wire. I synthesized them into quarterly reports. Forty-page PDFs with executive summaries and footnotes and color-coded matrices.
Three years in, I asked our VP of Product if she'd read the Q2 report. She looked at me with the specific kindness reserved for people you're about to disappoint. "I skimmed the summary," she said. "Was there something I should have caught?"
There was. There always was. The story that would have changed the decision already made. The acquisition that reframed the category everyone was still building toward. The thing that mattered, buried in paragraph fourteen of a document nobody had time to open.
Forty-three people. No editor. No safety net.
I quit in March. Sent the first issue to forty-three people — former colleagues, a few founders I'd met at ASU+GSV, two VCs who'd given me their cards and probably forgotten. One email. One story. 600 words. I spent more time on the subject line than on the lede.
The story: a Series B round for an adaptive assessment startup that, on the surface, looked like another unremarkable edtech raise. But the lead investor had quietly exited their position in the incumbent three weeks prior. Nobody had connected the dots. I had the time to. I had the obsession to.
Eleven of the forty-three replied. Not to say thanks — to say they'd forwarded it to someone who needed to see it.
"I forwarded it to my entire investment committee with one line: read this before Thursday's call. It reframed everything we thought we knew about the formative assessment market."
— Priya Nambiar, Associate, Owl Ventures2,847 readers ahead of you
Reserve your seat. The first issue drops the Tuesday after the waitlist closes.
No spam. One email per week, every Tuesday at 7 AM. Unsubscribe anytime.
On a Tuesday morning, a superintendent replied.
By issue twelve, the list had grown to four hundred. I still wrote every word myself. I still spent every Monday in the same chair, reading everything so you don't have to, deciding what the one story was — not the most-covered story, not the most dramatic story, but the one with actual downstream consequence for the people building and buying and funding learning technology.
Issue twelve was about a regulatory comment period that most of the industry had ignored. A proposed FERPA amendment that, if passed, would materially change how edtech companies could handle student data from Title I schools. I read the 94-page draft. I found the clause that mattered. I explained what it would do to every major LMS vendor's data resale model.
At 6:47 AM on a Tuesday, Dr. Marcus Webb, Superintendent of a mid-sized district in Ohio, replied with four words: "Changed our procurement decision."
"We were two weeks from signing a three-year contract. Dispatch landed that morning and we pulled the deal. Saved us from a vendor who was quietly exiting the K-12 market. Nobody else was writing about that."
— Dr. Marcus Webb, Superintendent, Licking Valley Local SD, OhioThe EdTech industry produces more noise than any sector its size.
There are seventeen EdTech newsletters. Four EdTech trade publications. Three dedicated podcasts. Two analyst firms charging $12,000/year for access. And still — every week — the story that actually moves the market gets missed by everyone chasing the press release.
Dispatch exists because signal is not the same as volume. One story per week. The one that matters. That's the whole product.
"I write investment memos for a living. Dispatch is the only newsletter I've ever cited in a memo. Not because it's the only one I read — because it's the only one that tells me something I couldn't have found myself in an afternoon."
— James Okafor, Senior Associate, Reach CapitalRead Issue #001 right here.
Subject: The LMS that stopped being an LMS — and why the market hasn't noticed yet
The LMS That Stopped Being an LMS
Why Instructure's API strategy is the most important EdTech story nobody's calling a story
Last Monday, Instructure pushed a documentation update to their Canvas API that most people in EdTech would scroll past without blinking. It was buried in a changelog. Four paragraphs. No press release. No LinkedIn post from the CEO.
The update introduced granular read/write permissions for third-party integrations at the assignment-level — not the course level, not the enrollment level, but the individual assignment level. For anyone who has spent time thinking about where the real data gravity in K-12 actually sits, this is significant. For everyone else, it looks like a routine developer maintenance item.
Here is what it actually is: Instructure quietly opening a door that, twelve months ago, they would have kept closed. A door that, if enough developers walk through it, fundamentally changes the LMS's position from platform to infrastructure.
Why This Matters for Founders
If you're building anything that touches assignment data in a Canvas school — adaptive practice tools, writing assistance products, formative assessment platforms — this update just changed your integration story. You no longer have to convince a district IT director to grant you blanket course-level access. You can scope permissions to exactly what you need, which removes the single biggest objection in most procurement conversations.
Two founders I spoke with this week said they'd been waiting for exactly this kind of granular API access for over a year. Both are now revisiting product roadmaps they'd deprioritized because the integration overhead wasn't worth it at scale.
Why This Matters for District CTOs
Vendor security reviews just got easier to scope. When a vendor can request only the permissions they actually need — not the permissions the API previously forced them to request — your data governance conversation changes. Ask every new vendor to show you their Canvas permission scope. If they're still requesting course-level access when assignment-level would do, that's a red flag worth flagging.
Why This Matters for VCs
The integration moat that protected large LMS-native vendors is narrowing. Not gone — but narrowing. Any company that built its competitive advantage on "we're the only ones who can do X inside Canvas" should be re-underwritten against this update. Any company that was blocked from building X inside Canvas should be on your call list by Thursday.
That's the one story that mattered this week. See you next Tuesday at 7 AM.
— Dispatch
Don't read the noise.
Read the one thing that matters.
Read by
Priya K.
Founder, LearnFlow
James O.
Associate, Reach Capital
Tomás M.
CTO, Austin ISD
Sarah W.
VP Product, Coursera
Dev R.
Founder, Pathways AI
2,847 readers ahead of you
No spam. One email per week, every Tuesday at 7 AM. Unsubscribe anytime.
Frequency
Every Tuesday, 7 AM
Format
One story, ~600 words
Cost
Free during launch