Behind the Scenes

How a Family of Four Ships Like a Team of Ten

Benjamen Pyle·
#homeschool software#engineering#ai#family#building

I actually resisted AI early on, and I need to be honest about that before I say anything else. I’ve spent thirty years learning to build software with my own two hands, and part of me didn’t want a machine in the middle of that. Some of my hesitation was practical and some of it was pride. Probably more pride than I’d like to admit.

Then I started using it, and the ground shifted.

The job was never the typing

The keyboard was always just how I talked to the computer. The real job, the one I’ve been doing for three decades, was figuring out what problem needs solving and how to solve it well. The language and the framework and whatever syntax happened to be in fashion that year. Those were the medium. They were never the point.

That’s the reframe that changed how we build Homeschool Ace. I still make every decision about what this platform is and how it should work. But I’m not alone at the keyboard anymore doing all the mechanical parts by hand. Elizabeth and I can now do the work that used to take a real team, because the tedious middle of software, the boilerplate and the wiring and the tests, has a helper.

And shipping was never just the code. Our two boys are the other half of this. They use the app every day as students. They break it in ways I’d never think to try, and they tell us the truth about it long before any other family sees it. Four of us doing the work of ten isn’t a stretch when two of the four are the toughest testers we have.

What that actually looks like

People imagine AI writing an app while I watch. That’s not it.

What it looks like is closer to having a very fast, very tireless junior engineer who never gets bored. I decide a feature should exist. I’ve argued it around the kitchen table, watched our own boys struggle with something, and figured out what would help. Then I sit down and describe the shape of it, and the machine handles the parts that used to eat my nights. I review every line. I throw out plenty of it. The judgment is still mine, because the judgment is the job.

The result is that we move fast without cutting the corners that matter. A small change that would have taken me a full evening five years ago now takes an hour, and I spend the rest of that evening on the part that’s actually hard. Is this the right thing to build at all.

The line I won’t cross

Now the part I need parents to hear clearly, because “AI” is a word that makes people nervous, and it should.

AI helps me build the software. It does not touch your family’s records.

Your child’s grades, their transcript, their progress, the notes you keep. None of that gets fed to a model to train it or to answer someone else’s question. The tools I use to write code work on the code, in my environment, on my time. They are nowhere near your data. That separation isn’t an accident or a nice-to-have. It’s a wall, and I built it on purpose, because I’ve watched our whole industry get careless with exactly this kind of trust.

So when I say AI helps us build, I mean it helps me and Elizabeth do more of the work of making the tool. What happens to your records is a different question with a much simpler answer. They’re yours. They stay yours. Nothing about how we build changes that.

Why a small team is a feature

There’s a temptation to apologize for being small, and I’ve decided not to.

A big company has a hundred people who each own a sliver of the product and nobody who holds the whole thing in their head. We’re the opposite. Elizabeth and I know every corner of this platform because we built every corner of it. Our boys know it too, because they live in it every school day as students. When something feels wrong, someone in this house feels it as a user before we ever see it as a bug.

The tools let us punch above our weight. Being a family lets us aim at the right target in the first place. Those two things together are the whole reason a platform this small can go toe to toe with software backed by teams a hundred times our size.

That’s either the most efficient way to build homeschool software or a slightly crazy one, and I’ve decided it’s both.

What it means for you

You get software that moves quickly, built by people who use it themselves and answer for every part of it. You get the speed of modern tools without your family becoming the price of them.

We’re going to keep building this the way we build everything. Carefully, quickly, and with our own kids as the first people who have to live with what we ship.

← Back to Blog