SaaS business platform for EdTech: pivot from K–12 to medical education

Insight already had serious learning technology. The missing layer was the business platform: modular SaaS, a coherent ecosystem story across authoring, delivery, and analytics, and a GTM path into medicine—not a skinned K–12 product pretending to be clinical training.

insight learning technology · b2b · strategic expansion

Click to enlarge

My role

I was the technical product manager and design lead on this track at Insight Learning Technology, Inc.—translating leadership direction and domain input into concrete product bets, interaction models, and shipped UX. The through-line was not “more features”; it was making SaaS-scale business operations legible for a company whose strength was learning science and productized instruction, not billing-and-CRM theater.

Concrete responsibilities included:

• Auditing the legacy experience and naming the friction that capped growth—not just cosmetic issues, but structural gaps in how institutions and individuals could buy, deploy, and operate products.
• Developing personas, edge-case rules, and scenario coverage so mixed audiences (existing vs prospective) did not collapse into one fictional “average educator.”
• Working with scholars to keep pedagogical goals explicit in product decisions—so commerce and admin mechanics did not steamroll instructional intent.
• Partnering with data scientists, business analysts, and domain experts so visions stayed inside real business requirements, not hand-wavy roadmap slides.
• Pairing with engineering on implementation fidelity—design QA, usability fixes, and the unglamorous alignment work that keeps shipped UI trustworthy.
• Introducing new brand identities and microsites where go-to-market needed a public face that matched the repositioning.

employer: insight learning technology, inc. · role window (résumé line): sep 2013 – dec 2022

Program context

Insight Dashboard Ecosystem was the umbrella concept: software meant to handle the full enterprise loop for learning businesses—deploying full-featured learning products, selling subscriptions to individuals and institutions, and operating the supporting rails (identity, access, reporting) those customers audit before they renew.

The company’s learning technology was already deep. What it lacked was capable infrastructure for conducting SaaS business at scale: the modular components, integration story, and operator-grade admin that let sales and success teams speak credibly to hospitals, medical programs, and international institutions—not only district IT.

The strategic bet—reflected in how we talked about the product and how we sliced engineering—was modular SaaS plus an ecosystem narrative tying authoring, delivery, and analytics into one coherent stack. That framing mattered as much as any single screen: buyers needed to see how pieces connect, not a bag of unrelated tools rebranded for medicine.

How we framed the pivot

We opened with business analysts producing competitive analysis and a new business plan as we prepared to enter the medicine space—so product work rode on an explicit commercial thesis, not only on design instinct.

Management vision and survey work converged on educators as the core target audience. In parallel, we maintained a parallel persona set to surface need differences between existing clients and prospective ones— a deliberate guardrail so scenario coverage did not default to “what we already hear from incumbents.”

The public-facing story and the internal roadmap had to stay aligned: a B2B platform for institutions, with subscription mechanics that also worked for individuals where the model allowed— without pretending consumer simplicity could substitute for enterprise procurement reality.

Platform constraints

A multi-purpose platform with varied target users surfaces boring, decisive complexity: permission and entitlement logic that is everywhere and invisible when wrong. The product had pervasive, intertwined behind-the-scenes checks—what we described at the time as a logic gate balancing user goals with business goals so access to product tiers, classes, and analytics stayed coherent under real account structures.

That layer is easy to underspecify. We treated it as a first-class design problem: if operators cannot predict who sees what, neither can compliance, finance, nor faculty support—and the medical vertical only raises the stakes.

Delivery rhythm and validation

We built incrementally across multiple phases. The recurring loop was intentional: brainstorming, expansive clickable wireframes, then a prioritization pass sharp enough to survive engineering capacity—not a backlog swamp.

We pressure-tested prototypes with pilot contributors and revised based on internal design QAs, user interviews, and usability audits. Once a direction survived that friction, we invested in polish and presentation quality rather than restarting from blank Figma files every quarter.

Through a close partnership with the UCLA Human Perception Lab, we ran structured feedback with medical students and professionals from UCLA and other institutions—so the pivot was not only a sales narrative validated in conference rooms.

Surfaces in the ecosystem

The following is not an exhaustive backlog; it is the surface-area list we used to communicate scope to stakeholders—admin, instruction, and revenue-adjacent capabilities grouped so buyers could map product to their operating model.

• User & class management — rostering, roles, and instructional groupings that had to stay sane at institution scale.
• Individual & group analytics — reporting paths for both cohort and learner-level views without duplicating two disconnected products.
• Guided vs unguided modes — instructional modes that had to remain explicit in UX so faculty could reason about classroom vs self-paced use.
• Timed assessments — high-stakes timing semantics (medical education does not forgive sloppy clock behavior).
• Subscriptions & payments — the commercial spine the prior K–12-era stack had not fully carried.
• Data import-export — operational reality for IT and instructional design teams swapping content and rosters.
• Dynamic help center — self-service support that scales when sales cannot answer every ticket.
• Responsive UI — baseline expectation for administrators and learners on heterogeneous devices.

What shipped and traction

The program’s intent was operational: let Insight deploy full-featured learning products rapidly, sell subscriptions to individuals and institutions, and supply educators with systematic education management plus customized learning experiences for individuals and groups—now in verticals where procurement and pedagogy both tightened requirements.

• Market expansion: entry into new markets—notably medicine—without abandoning the core learning technology story.
• Named partnerships: relationships with Primal Pictures and TDS Health as examples of credible clinical-content and distribution adjacencies cited at the time.
• International institutions: acquisition of institutional customers in regions called out explicitly in program retrospectives—UK, Australia, and New Zealand.
• Research footprint: ability to collect scientific data supporting peer-reviewed publications, with the Community College Mathematics Project given as a concrete example of that pipeline.

I am not attaching revenue or completion metrics here: this write-up stays aligned to what we documented in narrative form—capabilities, partnerships, and geography—rather than retrofitting quantified outcomes the source material did not carry.

Closing

EdTech pivots fail when teams confuse a vertical rebrand for a product strategy. The defensible version is modular SaaS with honest permissions, a through-line from authoring to analytics, and validation with the actual humans who will fail students if the software lies. That was the bar we held—clinical adjacency as a commercial thesis, not wallpaper on K–12 assumptions.