The Tools I Keep Are the Ones I Helped Build

TL;DRTwo or three workflows in an AI tool is still a trial. The tools that stick keep offering the next useful thing and let you shape what they learn.

Over the last couple of months I’ve tried and dropped about ten different agent platforms. Trying one has never been cheaper. But it’s taught me something about what makes these products stick, and I think a lot of founders building them are measuring the wrong thing. They count how often customers show up. What matters is how many things a customer would have to rebuild to leave.

Here’s how a new tool usually goes for me. I sign up, get through onboarding, and set up two or three things to see whether it’s useful. That’s deliberate. Setting up a couple of workflows is cheap, and it tells me enough to decide whether the product has something. The problem, from the founder’s side, is that the same cheapness cuts both ways. If it was quick to set up, it’s quick to replace. Two or three things in a product is still a trial, even if I’m logging in every day. Those daily logins can look like traction and still be easy to walk away from.

The tools still on my desktop are the ones where I have more than three things built in. Claude is the clearest example. At this point I have scheduled jobs and a whole set of workflows that depend on it, and leaving would mean rebuilding all of them somewhere else. That’s what actually keeps me: walking away would take real effort.

The obvious objection is that an agent could rebuild all of that somewhere else. It probably could rebuild the setup. What doesn’t move easily is the trust built from months of small corrections. And a copy of the setup can’t keep up with a product that’s adding the next useful thing every week.

How a product gets from three things to eight

The other thing I’ve noticed is how the sticky products get there. They don’t wait for me to go looking for the next use. They bring it to me.

Town, a newer agent tool I’ve been using, does this really well. It notices what I already have and offers to pull it in. Then it suggests a tweak, then something else it could take on for me. Within a few days I’d gone from the couple of things I set up to test it to something like eight, and I didn’t set out to do that. Each step was small and obviously useful, so I said yes. It’s always offering me the next thing, so I never quite feel done with what I’ve already turned on.

Town also keeps a wiki of what it’s learned about me that I can read and edit. That turned out to matter more than I expected. I trust it because I can see what it thinks it knows, and every correction I make is a little more of me invested in it.

Most products I try work the other way. They’re pull: the value is in there, but I have to go find it. That’s fine for a power user with time to explore. Most users don’t have that time, and they won’t do the exploring for you. The products that have gotten deep into my workflow work more like push: they keep putting the next useful thing in front of me.

What separates push from nagging is that every suggestion Town made was small, built on something I’d already set up, and grounded in what it had learned about me. A next step that could have gone to any customer is a pitch. One that only makes sense for me is help.

When I talk with founders building agent tools, this is usually where I end up. Don’t measure whether customers are using you. Measure how many things depend on you, and work on making that number go up. Every time a customer logs in, show them how the thing they set up is going and offer to start the next one. Have that next step ready before they finish the current one, and make it easy to say yes.

Where this applies

This is about tools where setup is cheap and the value builds as more of someone’s work runs through the product, which describes most of the agent and workflow software I see right now. The counts here are my own experience as someone who tries a lot of these tools, not a measured benchmark. Your customers might be slower to try things and slower to leave.

But if you’re building something people can set up in an afternoon, assume they can also replace it in an afternoon. What I’ve seen work is getting deep enough into their week that leaving costs more than staying. Figure out what the fourth, fifth and sixth things are for your best customers, and go build them.

Sources