Bridgewell Studio School software, built to connect
Software studio where special education is first

The special needs classroom isn't an afterthought here. It's where we start.

Bridgewell Studio makes focused tools for K-12 schools and Young Adult Programs, with particular depth in special needs classrooms — a corner of edtech that's long been overlooked.

The day we build for

How a student's day travels — and where it gets lost

A single student in a special needs classroom is surrounded by a whole team. Follow how information moves between them today.

Why we exist

Built inside this world, not designed around it from the outside.

Special needs classrooms carry more coordination than almost any other part of a school. A single student's day might involve a classroom teacher, an aide, a speech therapist, an OT, a PT — each with their own observations that a family needs to know about, on a day when their child can't always tell them.

Most of that coordination still runs on paper folders, printable forms, and hallway conversations. Not because schools don't want better tools, but because the edtech vendors serving K-12 built for the general classroom first, and treated accessibility as a checkbox added after the fact.

Software for the schools most vendors build around, not for.

Bridgewell Studio exists to close that gap directly — building focused, single-purpose tools shaped by real time spent in these schools, not assumptions about what they might need.

What we're building

Small, focused tools. One studio. The same schools.

ArriveWell

Coordinates student pickup and drop-off — connecting the parking lot manager, the classroom teacher, and the para escorting each student between classroom and car, so every arrival and dismissal is a smooth, communicated handoff.

Threadwell

A daily home-school communication log for nonverbal and complex-needs students — weaving entries from teachers, aides, and related-service providers into one coherent record a family can rely on.

ConveneWell

IEP meeting scheduling, built for the real thing: matching availability across a whole team, tracking compliance deadlines, and keeping families — and interpreters — in the loop.

How we build

Three things that don't change, product to product.

Built with schools, not just for them

Every product starts from a real problem observed in a real classroom, refined with the people who'll use it daily — not shipped as a finished assumption.

Accessibility is the starting point

Complex-needs classrooms shape the first version of everything we build, not a feature request that arrives after launch.

Small, focused tools over platforms

We'd rather do one thing well and let it earn its place in a school's day than bury it inside a platform nobody asked for.

Bring us the gap

Have a problem worth building for?

The best tools we make start as a frustration someone inside a school tells us about — a paper form that shouldn't exist, a daily coordination headache, a gap nobody else seems to see. If your school lives with a problem like that, we want to hear about it. If it's a fit, we may build it — often with the school that surfaced it as our first pilot partner.

Tell us about it