The pattern I almost missed
Last year I shipped two products from two completely different worlds.
FillTheTimesheet — a time tracking and billing tool for freelancers, agencies, and remote teams.
PromptShip — a shared prompt library for marketing, sales, HR, and support teams using ChatGPT, Claude, and Gemini.
On paper, they share nothing. Different audiences. Different pricing. Different categories. One sits next to invoicing apps, the other next to Notion.
But about six months into each, the same sentence started showing up in both products' inboxes — and it taught me the founder lesson I should have learned the first time.
The wrong question I kept building around
When I started FillTheTimesheet, I assumed freelancers wanted better time tracking.
So I built better timers. Smarter project categorization. Cleaner invoicing exports. All of it was real work, and all of it was missing the point.
The first long-tenured customer told me, in different words, what I now hear from almost every user:
"I don't want to track time better. I want to stop thinking about time tracking."
That sounds like the same thing. It isn't.
"Better tracking" is a feature problem. "Stop thinking about it" is a workflow problem. The first one is solved by polish. The second one is solved by removing decisions.
I rebuilt the onboarding around that. Automatic project allocation from calendar events. Smart billing presets. Defaults that mostly just work. Retention curve flattened in the good way.
And then I did the same thing again
A year later, I started PromptShip thinking teams wanted a better place to write prompts.
So I built a nicer editor. Tags. Categories. Search.
And then the first cohort of users told me, in different words:
"I don't want a better prompt editor. I want to stop losing prompts."
Same shape. Different domain.
The thing teams were buying wasn't a writing tool — it was a "this thing won't disappear into a Slack DM" tool. One-click copy into ChatGPT, Claude, or Gemini. Usage analytics so a team lead can see which prompts actually earn their keep. Version history so nobody's afraid of touching the good ones.
The shipped product looks like a library. What it actually is, for the user, is a guarantee that institutional knowledge doesn't evaporate every time someone switches projects.
The lesson — boring, obvious, and easy to forget
Founders build the feature. Users buy the relief.
For FillTheTimesheet, the feature was tracking; the relief was not thinking about tracking.
For PromptShip, the feature was a library; the relief was not losing prompts.
In both cases, the first six months of roadmap was features. The next six months — the months that actually moved retention — were spent removing friction the user didn't want to think about.
If I could send one note back to past-me at the start of both projects, it would be this: before you ask "what feature is missing?", ask "what decision is the user tired of making?" That's the one worth building around.
Key takeaways
- The product you ship is a feature. The thing customers actually buy is the absence of a recurring annoyance.
- Listen for the sentence "I don't want X, I just want to stop Y." The "stop Y" is the real product.
- Polish wins demos. Removed decisions win retention.
- The fix is usually un-glamorous, less demo-friendly, and harder to put on a landing page — and it's the thing that turns one-month users into one-year users.
Building in public at FillTheTimesheet and PromptShip.
Top comments (0)