I had one of those founder moments today.

Not the loud kind. Not the kind you post about because something big externally happened.

The quiet kind. The kind where something internally just… clicks.

I spend my days in micro sessions with myself.

Not because I have to, but because I genuinely don’t get bored of what I’m building.

I’ll sit with one part of the product, go deep on it, then step away.

Come back later with a different perspective. Refine it. Challenge it. Simplify it.

It’s a rhythm I didn’t plan but now I realize it’s part of how I build.

And today, something shifted.

I was thinking about WISDM, specifically Core, the actual workflow engine. The part that everything else depends on. The part that, if done right, makes everything else make sense.

And I caught myself thinking about all the programs I want WISDM to eventually support. Interim housing. Permanent supportive housing. Rapid rehousing. ODR. TAY. Group homes.

All of it.

But then I paused.

Because this phase isn’t about everything.

It’s about getting the foundation right.

Interim housing.

Permanent supportive housing.

Movement and retention.

That’s it.

And in that moment, I realized something that honestly stopped me for a second.

I understand this more than I think I do.

Because up until now, I’ve been approaching this through the lens I know best as a clinician. Someone who studies behavior, patterns, responses, environments.

But I had to take that hat off.

And when I did, it became clear:

Behavior is logic.

In the SaaS world, what we call “logic” is really just behavior translated into a system.

If a program is Interim Housing, then the behavior is movement so the system should track movement.

If a program is Permanent Supportive Housing, then the behavior is retention, so the system should track retention.

It’s not about adding features.

It’s not about building more.

It’s about understanding what is actually happening in real life and making the system reflect that.

That clarity changed how I’m thinking about everything.

It also grounded me.

Because I’m not building something I don’t understand.

I’m building something I’ve lived.

And I’m not here to just hand this off to developers and hope it comes together.

I’m here in it. Every day. In small, intentional moments. Thinking, refining, questioning, aligning.

Staying close enough to the work that it continues to inspire me.

Because that’s where the real product is built not just in code, but in clarity.

Today was one of those days where everything felt aligned.

Where the noise dropped and the direction became simple again.

And in that simplicity, I realized something important:

I am exactly where I need to be.

Ciao, Reese

But we don’t talk about housing tech.

And that’s a problem.

Every week, I create training materials for my team—PowerPoints, scenarios, GIRP note examples.

They’re practical. They’re necessary.

But recently, I had a realization:

We might be beyond this.

Not because training isn’t important—but because what we’re training on shouldn’t live outside the system anymore.

It should be built into it.

Living in Two Worlds

On one side, Clinician, Operations Leadership, supporting teams, reviewing documentation, ensuring compliance.

On the other side, I’m building a CRM for housing programs.

And I started noticing something:

What I teach and create micro trainings for my teams on Monday…
I’m trying to build into a system by Tuesday.

So I asked myself

Why are we still training people to manually do what systems should already support?

The Gap No One Is Talking About

Housing isn’t just apartments or rentals.

It’s a full ecosystem:

• Case management

• Compliance

• Documentation

• Housing navigation

• Client stability

And yet, the tools we use don’t reflect that reality.

So teams rely on training…
To fill a gap that technology should close.

From Training to Embedded Workflow

Take GIRP notes.

We train staff on:

• How to structure them

• How to stay compliant

• How to write them correctly

But what if the system guided that process?

Not replacing the work
But supporting it.

Not automation
But a co-pilot.

Building While Doing

Right now, I’m doing both.

Creating trainings…
And building the system that should eventually make those trainings unnecessary.

That’s where housing tech is headed.

And if it’s not fully there yet, I plan to be part of the momentum that gets us there.

Where This Is Going

We don’t need more tools.

We need smarter systems
Systems that understand workflow, compliance, and the realities of this work.

Because if we’re still training people on the same things every week…

That’s not a training issue.
That’s a systems issue.

What I’m Building

This is exactly why I created WISDM a housing technology platform built from inside the work.

Focused on:

• Workflow-driven systems

• Embedded compliance

• Smarter documentation

• Real operational clarity

If you want to follow along or learn more:
getwisdm.org

I started in housing.

Every day, I work inside interim housing programs where the goal is clear: stabilize individuals and support them in moving toward permanent housing. On paper, the system looks structured. There are workflows, case notes, service requirements, compliance standards, and multiple teams working toward the same outcome.

But in practice, the system is fragmented.

Clients move through different stages referral, intake, active case management, and eventually permanent housing but the systems supporting that journey don’t move with them. Information gets lost. Responsibilities shift. Teams operate in silos. And what should be a coordinated process often becomes reactive.

This is what people don’t see.

There is an entire operational layer behind housing programs that determines whether someone successfully moves forward or falls through the cracks. It’s not just about services it’s about how those services are tracked, coordinated, and executed across time and across teams.

That’s where the real gap is.

Most existing systems in this space were not designed for daily operations. They are built for compliance, reporting, and data collection. They tell you what happened, but they don’t help you manage what’s happening.

And housing doesn’t work in snapshots. It works in motion.

From interim housing to permanent housing, there is a continuum of care that requires coordination, visibility, and accountability at every stage. But right now, that continuum is not supported by a system that actually reflects how the work is done on the ground.

That’s why I’m building WISDM.

WISDM is designed as an operational intelligence platform for housing programs — a system that supports the full housing journey from entry to permanent housing. It’s built from the perspective of someone working inside the system, not outside of it.

It focuses on what teams actually need:
clear workflows, real-time visibility, document readiness, service tracking, and the ability to move clients forward intentionally not reactively.

This isn’t about replacing existing systems. It’s about filling the gap between them.

Because the success of housing programs doesn’t just depend on funding or policy. It depends on execution.

And execution depends on systems that actually work.

I’m building WISDM to support that reality and I’ll be sharing more as I continue building.

— Dr. Reese Levy
Founder & CEO, WISDM