Four years ago, we built the platform Psych Hub needed.
It worked. It grew. It supported real customers. It carried us a long way.
But over time, something became obvious.
The system we built was not designed for the future we were trying to create.
The codebase was hard to reason about.
The database needed to be rethought from the ground up.
The user experience had years of friction layered into it.
Our backlog was full of things we knew mattered, but could never quite justify prioritizing.
And we are not a massive team.
At some point, incremental improvement started to feel like the real risk.
So we made a decision that felt, at the time, about an 8 out of 10 on the insanity scale.
We stopped building on top of the old system.
Not fully. We still supported the platform. We still handled major issues. We still had customers relying on us.
But we stopped pretending the old foundation could stretch forever.
We decided to rewrite the game mid-play.
I told people: give us two weeks. If this is a bad idea, we will know quickly and go back.
We never went back.
Getting on the Tallest Lift
When I was in middle school, I decided to learn to snowboard.
Instead of starting on the bunny slope, my friends and I got on the tallest lift at the mountain.
We all fell getting off.
It took hours to get down that first run. Falling. Sliding. Getting up. Falling again.
By day three, we were flying.
That is what this rebuild felt like.
We did not ease into it.
We did not slowly refactor around the edges.
We did not spend months creating a perfect plan before touching the product.
We got on the biggest lift and committed to figuring it out on the way down.
What We Actually Rebuilt
In a matter of weeks, we migrated the platform we had spent years building into a completely new system.
Not a cosmetic update.
Not a fresh coat of paint.
Not a rewrite for the sake of rewriting.
A dramatically better user experience.
A normalized database from the ground up.
A new backend.
A new frontend.
A new back office.
Multiple products and proof-of-concepts consolidated under one house.
A year’s worth of customer feedback and backlog items addressed in one motion.
The new platform brings together training, content, administration, enterprise workflows, and new AI-enabled capabilities in a way the old system never could.
Things we thought we would never get to are now live.
That is still a little surreal to say.
But the bigger story is not only what we shipped.
It is how we shipped it.
The New Development Model
This rebuild was made possible by an agent-native development pipeline we designed from scratch.
Memory files live inside the repo and evolve with the product.
Skills generate tickets and research requirements.
Orchestration logic decides whether work needs a single agent or a larger sub-agent flow.
Multiple models review implementation plans and code before we do.
Code review happens before humans ever see the pull request.
Agents write tests, update tests, and revise their own work.
Infrastructure is managed as code.
Humans are still deeply involved.
We supervise.
We refine.
We challenge.
We make judgment calls.
We decide what good looks like.
But we are not operating the same way anymore.
We are not typing every line of code by hand.
We are not spending weeks waiting for perfectly groomed tickets.
We are not treating prototypes as disposable theater.
The prototype is the spec.
The review is the process.
The loop is the operating model.
Our retros now are not conversations about story points.
They are conversations about workflow pain, agent performance, context quality, review quality, and where human judgment needs to be inserted earlier.
We did not just rebuild the platform.
We rebuilt how we build.
Why It Had to Happen
The uncomfortable truth was simple:
With a small team and big ambition, the status quo was not going to get us there.
Waiting would have been slower than rebuilding.
The old architecture could not support the speed we needed. It could not support the quality bar we wanted. And it definitely could not support agents operating effectively inside it.
If we wanted to build something much bigger than our team size suggested was possible, the foundation had to change.
So we changed it.
The Part I’m Most Proud Of
I have been a primary contributor on this rebuild.
Not because I am the only one capable.
Because this new model makes it possible.
I can move like a team.
Research competitors.
Spin up prototypes.
Port them into real repos.
Migrate data.
Refine UX interactions.
Test flows.
Review implementation.
Push the system until the product feels like a leap forward instead of another marginal improvement.
Features that used to take weeks now take hours.
Not because we are cutting corners.
Because the machine removes friction.
That is the part that is hard to fully explain until you experience it.
A lot of product leaders talk about using AI to prototype. That is useful.
But this is different.
We are not just making clickable demos faster.
We are building and shipping a real enterprise platform with agents as first-class contributors.
That is a different chapter.
What This Proves
The platform is live.
The migration is complete.
The user experience is dramatically better. Features that sat in the backlog for months or years are now part of one cohesive system.
And the team now has a new operating model for what comes next.
That matters.
Because the lesson here is not “AI can help you code faster.”
That is too small.
The lesson is that small teams can be much more powerful than they used to be if they are willing to rethink the entire system around how work gets done.
Not just the tools.
Not just the prompts.
Not just the prototypes.
The operating model.
Small teams can be mighty when they build the machine around them.
Four years ago, we built what we could with the tools and model we had.
Today, we are building differently.
And now that we have seen what is possible, there is no going back.
When we got off that tallest lift in middle school, we fell. Everyone does the first time.
But you do not remember the falls.
You remember realizing you could ride.
This rebuild felt impossible not long ago.
Now it feels like the only way forward.
Leave a Reply