Built It. Now What?

During the wind-down, I asked my son to help list some of the company's equipment on Carousell. I had enough on my plate — creditors, lawyers, suppliers — and I thought: here's an opportunity. Let him use AI to research what he's selling. Figure out what the items are worth. Write a decent listing. See what the tool can actually do.

He took photos. Uploaded them. Listed a FortiGate enterprise firewall for sixty dollars.

I only found out when a buyer messaged to confirm if it was still available.

Sixty dollars is sixty dollars when you're a poly student with no idea what a FortiGate is. And to his credit, he had used AI — just not the platform I'd built. He used ChatGPT, asked what the item was worth without any context, and got sixty dollars back. Which is, technically, a price.

But that moment crystallised something I'd been circling around for weeks. It wasn't that he hadn't tried. It was that my platform hadn't even crossed his mind.

A problem I hadn't named yet

The platform had been live for a few weeks. Cloudflare tunnels working. Tailscale connected. Mobile apps installed. API keys configured per person. The friction of access was close to zero — you could open a phone anywhere in the world and be connected to the home server in seconds.

My wife was using it approximately never. My son was using it approximately never. I was using it constantly, which tells you something.

I'd been telling myself this was a deployment problem. The right walkthrough. Show them once and the habit would form. Solve access and adoption follows.

I don't think that anymore.

The friction of caring is something else entirely. My wife has managed documents, passwords, and family admin for decades without a self-hosted archive. The system she has works well enough. My son has a mental model of his own obligations that doesn't need a task manager. Nobody reaches for a new tool when the old approach is adequate — and adequate is a very high bar to clear when you're asking someone to change a habit they've never questioned.

I'd built for capability. I hadn't built for motivation.

The gift they didn't ask for

There's a kind of father who is so absorbed in providing that he forgets to notice what anyone actually wants. He works long hours building something for the family. The family appreciates it, in the polite way you appreciate effort. But the thing itself — the thing he was so sure they'd love — sits in the corner untouched.

I know that feeling from both sides.

I kept finding small reasons to add features. The photo library — I told myself it was about preservation. But it was also an attempt to build something my wife would open on her own, because everyone has photos and everyone wants to find them. The document archive — I told myself it was for the estate scenario, the emergency. But it was also a reason to start a conversation. Can you help me file this? Something that might become a habit.

Every feature was another attempt to close the same gap. To find the thing that gives someone a reason to open the platform on a Tuesday evening when they weren't planning to.

Where does something actually get opened?

Not because you built it well. Not because access is frictionless. Not because you left a walkthrough guide somewhere that they will definitely read.

People open things in the places they already are. Where the message is already waiting. Where opening it is the path of least resistance, not the obstacle itself.

Where does something get opened without being asked?

That question is where Post 7 starts.

Next: The obvious place I should have started — and why it took me this long to get there.