A STORY IN PROGRESS · EDISON TOWNSHIP PUBLIC SCHOOLS

Edison didn't buy a product. They built one with us.

Three Edison administrators didn't sit through vendor demos. They sat at the table where the product was shaped. Pilot launches September 2026. This is their journey and the path they would tell you to walk.

UI Dashboard
ACT ONE · WHERE WE STARTED

A teacher needed to know one thing about one student. It took five systems to find the answer.

Before this work began, Edison Township was running on a familiar problem. Information about students lived in different places. Teachers logged into one system for attendance, another for assessments, another for interventions, another for communication with families. The systems didn't talk to each other.

Attendance System
×
Assessment Platform
×
Intervention Tools
×
Family Communication
×
Student Records
FIVE SYSTEMS. FIVE LOGINS. FIVE PLACES TO LOOK. NO SINGLE VIEW OF THE CHILD.

"Information about students lived in different places. We knew it. Everyone knew it. We just didn't have a way to start solving it."

Elementary Leadership Team
Edison Township
ACT TWO · HOW WE BUILT IT TOGETHER

They didn't adopt a platform. They co-designed one.

The Edison administrators didn't sit on the receiving end of vendor demos. They sat at the table where the product was being shaped. They mapped the gaps in their own workflows. They challenged assumptions. They pushed for what teachers actually needed and let go of what looked good in a slide deck.

Vision Workshops
Vision Workshops
Stakeholder Sessions
Stakeholder Sessions
Gap Mapping
Gap Mapping
Co-Design Sprints
Co-Design Sprints
District Security Review
District Security Review
#Phase 1

Vision Workshops

Defining what one connected view should mean

  • Define what a "single view of the student" should include
  • Align district leadership around shared goals and outcomes
  • Identify the most critical educator workflows to improve
  • Prioritize the data and insights teachers need every day
  • Establish success metrics for the pilot and future rollout
Vision Workshops
#Phase 2

Stakeholder Sessions

Gathering input from across the district

  • Engage teachers, administrators, and support staff
  • Understand unique pain points in different departments
  • Ensure diverse representation in product feedback
  • Map out daily communication channels and barriers
  • Consolidate findings into actionable product requirements
Stakeholder Sessions
#Phase 3

Gap Mapping

Identifying systemic workflow disconnects

  • Audit existing software tools and data silos
  • Document manual workarounds used by educators
  • Pinpoint where critical student data gets lost
  • Evaluate the limitations of current reporting systems
  • Outline the necessary data integrations for success
Gap Mapping
#Phase 4

Co-Design Sprints

Collaborating on the ideal solution

  • Facilitate rapid prototyping with end-users
  • Test early interface concepts and dashboard layouts
  • Iterate on features based on direct teacher feedback
  • Refine the user experience for maximum efficiency
  • Finalize the core functionalities for the MVP
Co-Design Sprints
#Phase 5

District Security Review

Ensuring compliance and data protection

  • Conduct comprehensive technical security audits
  • Verify compliance with FERPA and local privacy laws
  • Establish robust user authentication protocols
  • Review data encryption standards and storage policies
  • Approve the platform for district-wide deployment
District Security Review
EDISON'S PILOT LAUNCHES SEPTEMBER 2026.

Elementary School Leadership

"What we pushed for that made it into the product..."

Middle School Leadership

"What we had to let go of..."

Assistant Principal Perspective

"What surprised us most about our own schools..."

A PAUSE IN THE STORY

Before we go further what does this look like for you?

Edison's story is specific to Edison. But the math behind it isn't. Every district running on disconnected systems is paying for that fragmentation somewhere — in dollars, in educator time, or in decisions made with incomplete data. Take a minute. See what your district's numbers look like.


Now back to the story. ↓
Laptop Dashboard
ACT THREE · PILOT GOES LIVE

September 2026. Edison's first connected school year.

When school starts in September, teachers will log in once. The information they need about every student will be in one place. Attendance, assessments, interventions, family communications — connected. Not because a vendor sold it. Because the district built it for itself.

Before

  • 5 system logins per day
  • Information scattered across platforms
  • Manual data pulls for reporting
  • Teachers chasing data instead of teaching

Year One - September 2026

  • One login. One view.
  • Every student visible to every authorized educator
  • Time recovered to classrooms
  • Decisions made on real data, not anecdotes
ACT FOUR · WHAT BECOMES POSSIBLE

Once your data lives in one place, you can finally ask better questions.

Edison's pilot starts with something simple: connection. But connection is the foundation everything else sits on. When the data is in one place, AI stops being a buzzword and starts being a tool. Patterns become visible. Risks become predictable. Teachers get insights surfaced for them in the morning instead of hunting for information across systems.

Bullet

Which interventions are actually working — and for which students?

Bullet

Which students are showing early signs of disengagement — before grades drop?

Bullet

Which interventions are actually working — and for which students?

ACT FIVE · WHERE YOU START

If you're sitting where Edison was, here is what they would tell you.

Edison's pilot starts with something simple: connection. But connection is the foundation everything else sits on. When the data is in one place, AI stops being a buzzword and starts being a tool. Patterns become visible. Risks become predictable. Teachers get insights surfaced for them in the morning instead of hunting for information across systems.

01

Understand what you already have.

Most districts don't have a tools problem. They have a visibility problem about their own stack.

02

Talk to your team before talking to a vendor.

The problem definition matters more than the solution.

03

Build with a partner. Not buy from one.

Process matters as much as product.

04

Start small. Scope tight.

You don't have to replace everything on day one. You shouldn't.

05

Define success in outcomes, not features.

What do you want to be true for your students at the end of year one? Start there.

Take your first step. No commitment.
No pitch.

We run a free, 90-minute SmartEducation workshop for NJ district leadership teams. We walk your stack with you. We map your friction points. We help you see what's already overlapping and where the real opportunities are. You leave with a one-page picture of your district's technology landscape and a recommended first move — whether or not it involves us.

No cost

No cost we cover the discovery

No vendor pitch

No vendor pitch if there's nothing to build, we'll tell you

Your team

Your team, our facilitation 90 minutes, on-site or virtual