Teachfloor — Web learning & edtech product delivered by Coralsoft

The situation

What was in place before we started.

The client needed a focused product for educators running cohorts. The first release needed course scheduling, peer activities, and progress insights, while managing content growth and learner drop-off. Coralsoft designed and delivered the 12-week MVP from discovery through release.

The client needed a focused product for educators running cohorts. The first release needed course scheduling, peer activities, and progress insights, while managing content growth and learner drop-off.

Coralsoft owned product shaping, engineering, QA, and release across a 12-week engagement.

Constraint

Turn the core customer journey into a dependable first release without overbuilding the product.

Estimated Timeline: 3 months
Estimated Team: 3 people
Estimated Budget: $9k – $15k
Platforms: 1

Estimated stack

Next.jsReactTypeScriptSupabase

Delivery story

Teachfloor: a focused product delivered from discovery to release

01

Challenge

The client needed a focused product for educators running cohorts. The first release needed course scheduling, peer activities, and progress insights, while managing content growth and learner drop-off.

02

How we built it

We mapped the core journey and data model first, then delivered course scheduling as a working vertical slice. The next iteration added peer activities and progress insights, with authentication, validation, loading and failure states designed into each flow. A web-first TypeScript build using Next.js, React, TypeScript, Supabase kept the interface and service contracts consistent; the final weeks focused on QA, accessibility, and release preparation.

03

Delivery

The delivered 12-week MVP let educators running cohorts complete the core journey without relying on disconnected tools. It provided a small, maintainable foundation for testing demand and prioritising the next release.

Coralsoft turned the product brief into a maintainable 12-week MVP.

Challenges

Each constraint, and what we did about it.

Constraint

Turn the core customer journey into a dependable first release without overbuilding the product.

What we did

We mapped the core journey and data model first, then delivered course scheduling as a working vertical slice. The next iteration added peer activities and progress insights, with authentication, validation, loading and failure states designed into each flow. A web-first TypeScript build using Next.js, React, TypeScript, Supabase kept the interface and service contracts consistent; the final weeks focused on QA, accessibility, and release preparation.

Showcase