One thing I didn’t expect after people started using my product

For anyone who asked, here’s the tool:
https://joyful-granita-8415bc.netlify.app/

Would appreciate any feedback - still early and improving it.

This is interesting — especially the shift from “one-time use” to something people return to in decision moments.

Feels like that’s where a lot of products actually win or lose:
not in discovery, but in that exact moment where someone has to decide.

I’ve been seeing a similar pattern — tools that reduce the need to think in that moment tend to get reused.

Curious — do you think it’s the repetition itself, or the fact that it shows up exactly when the decision happens?

This framing maps exactly to what I'm seeing building Autoreport — a tool that sends Stripe founders a PDF report every Monday morning.
The external trigger (Monday, 8am, inbox) was a deliberate design choice precisely because of this. I didn't want users to have to remember to open a dashboard — the product shows up in their workflow whether they think about it or not.
What I didn't anticipate: the trigger also changes how people read the report. Because it arrives at a fixed moment, they treat it more like a briefing than a dashboard — skimming the narrative first, then drilling into numbers if something looks off. That's a completely different reading behavior than I designed for, and it's now shaping how I think about what the AI narrative should actually say.
Your point about the gap between first and second use is interesting. For a weekly-trigger product the gap is forced (7 days), which makes early churn signals harder to read — someone who unsubscribes after two reports gave the product a real shot, which is different from a tool they just forgot to come back to.

For me it was the support load. My first paying customer ($6.28 PayPal sale) didn't message me, but the second one wrote 3 emails in the first hour — half asking for product help, half being friendly, and I realized I had no support channel set up.

Now I treat the first 100 customers as a feedback gold mine, not a support burden. Every email I get teaches me what's missing or unclear on the sales page, and the changes I make from those emails convert way better than anything I've A/B tested.

What was yours?

How is this different from uploading the contract to Claude or ChatGPT?

Interesting approach. Have you run into stability issues over long-running agent sessions? I’ve been experimenting with runtime monitoring and drift detection, and reliability over time seems to be a major challenge.

I see the same kind of behavior with Alora Home Health Software. People assume they’ll use it for one task, like setting something up or fixing a claim, but then it turns into the place they go every time something similar comes up.

In home health especially, it happens with billing and compliance stuff. Once someone figures out how to handle one Medicare issue in Alora, they keep coming back to it for every similar scenario instead of trying something new.

The distinction between a "one-off check" and a "moment of decision" tool is one of the clearest early PMF signals I've seen discussed on here. Products that get pulled back by external triggers — a new contract lands, a quarterly review comes up — have structurally different retention from products where users have to remember to come back. The trigger lives in the customer's workflow, not your onboarding funnel.

One thing worth tracking closely: the time gap between first and second use. Short gaps (days) suggest you have power users who deal with contracts frequently — they're likely worth more per seat and worth targeting explicitly in your ICP. Longer gaps (weeks or months) mean the product is still essential but the positioning story shifts from "daily tool" to "trusted advisor for high-stakes moments." Both are strong, but they lead to different pricing and marketing strategies.

To answer your question — yes, we built something expecting weekly active usage and found that users actually cluster around a monthly audit cycle instead. Completely changed how we thought about engagement metrics and what "healthy" retention looks like for our product.

Had a very different experience. Built a calibration quiz, launched through an HN post and got 1,900 completions in a day. The thing I didn’t expect was that users engaged with the quiz (sharing scores, debating methodology in comments) but almost nobody cared about the actual product behind it (decision journal, pre-mortem analysis).

It was unexpected to build something as a marketing hook that ended up being more compelling than the platform I spent months building as the core product.

Reaching out to early users and getting some great feedback. I am curious to know how long before you started to see a definite repeat user trend? Was that something you noticed from data, or something users let you know?

This is a cool idea - my past sales role saw some sketchy contracts and would've loved to have this before then.. lol. Best of luck!

Experience the latest features we’ve implemented—now available for free for a limited time. You can access and install the update directly via the Chrome Web Store:

https://chromewebstore.google.com/detail/marginix-–-amazon-profit/gmgajlccniogemeeocgcnagpfngomloe

Try it out today and let us know what you think. I'm available if you need any assistance or have questions during your trial.

This is a valuable analysis. High retention and repeat usage are often much stronger indicators of product-market fit than initial acquisition metrics.

We experienced a similar divergence from our assumptions during the recent beta launch of KortexMail. While the tool was primarily developed for outbound email drafting, we quickly observed users adopting it to summarize lengthy internal threads instead. It is always instructive when actual user behavior clarifies the product's most significant value.

Repeat usage is the metric most early founders underweight. New signups feel exciting but returning users are actually telling you "this fits my life" — which is the hardest thing to manufacture.

The "moment of decision" framing you landed on is powerful for distribution too. The tools that win on Twitter/X are the ones that show up exactly at the moment someone needs them. If your product is that tool for contracts, leaning into that in your content is valuable — "here's a scenario where this saved me $X" type posts perform really well because they create the mental anchor in the reader's mind.

On the audience-building side, the pattern I've noticed is that founders with products like yours benefit most from showing the use case in action rather than talking about features. Building in public around real decisions (not just wins) tends to compound. Tools like AlphaTweet (alphatweet.pro) help with keeping that kind of content consistent without it becoming a second job — worth a look if distribution is a bottleneck.

This is interesting — I’ve been noticing similar things while building my own product.

What surprised you the most after launch?

There's a massive difference between "useful once" and "this is now what I reach for every time." Sounds like IntroCave crossed into the second category faster than you expected.

Repeat usage early on is genuinely rare. Most early tools get tried once, forgotten, then uninstalled. The fact that people are coming back with the next contract means it actually fits into how they work, not just how they thought they might work.

Did you have any pricing intuition from this? Subscription feels way more justified when you see that pattern.

Repeat usage is the most underrated validation metric early on. First-time users tell you your acquisition is working. Users who come back tell you your product is working.

The 'moment of decision' framing you've identified is key — contract review is a high-stakes moment, and people don't risk high-stakes moments on tools they don't trust. The fact that they trusted it once and came back means you passed the test.

I've noticed the same pattern with voice-based tools: people try them when curious but only integrate them when the habit forms around a specific trigger. For you it's the contract signing moment. That's a very strong hook to build around.

Repeat usage on contract review is a strong signal. It means people trust the tool with real decisions, not just experiments. That also means the data flowing through it matters more than a typical productivity app. Contract content, user behavior, potentially PII. Worth a surface check before it scales. https://scan.mosai.com.br runs 78 checks in 60 seconds if you want a baseline.

I relate to this a lot.

One thing I’ve started noticing is that users don’t just “use” your product—they reshape what it actually is.

You think you’re building X, but once people start interacting with it, they reveal what they actually care about (and it’s usually not what you expected).

I’ve been thinking about this a lot while working on a small project—how hard it is to get useful, thoughtful responses instead of surface-level engagement.

Curious—did this change how you think about what your product is really for now?

Yes — saw the same thing with Delineato (delineato.app), our minimalist diagramming/mind-mapping tool. We built it thinking people would fire it up to make a quick diagram, export it, and move on. What actually happened: a segment of users came back every Monday morning to map out their week, or used it as a running 'thinking canvas' they kept adding to. That repeat, ritual usage wasn't something we anticipated at all.

The signal you're describing — repeat usage at the moment of decision — is much more valuable than we gave it credit for early on. We were tracking new signups but missed the cohort that was quietly becoming weekly active users.

What changed for us: once we noticed the pattern, we added features that served the 'recurring use' case rather than just making the one-time creation flow easier. The product shifted from 'output tool' to 'thinking environment'. Still figuring out how to monetize that distinction, but the usage pattern is real.

That repeat usage pattern is honestly one of the best signals you can get as an early-stage builder. It means the product is solving a real recurring pain point, not just a curiosity. A lot of founders obsess over new signups, but returning users are where the real value is — it means you've built something that fits into a workflow.

I've been noticing something similar with a side project I built — a free chess puzzle trainer. I expected people to solve a few puzzles and bounce, but the streak and rating system keeps them coming back daily. Totally unplanned, but that retention loop became the core of the product.

Your insight about it being a "moment of decision" tool is key. That's a strong position to be in for pricing too — if people reach for your tool every time a new contract comes in, the value clearly compounds. Have you thought about tracking which types of contracts bring people back most? That could help you double down on the highest-value use case.

That repeat behavior is a stronger signal than raw signup numbers. It usually means the product is becoming part of a real workflow, not just satisfying curiosity once. The framing around decision moments also feels important, because users may be buying confidence as much as analysis. If you keep seeing this pattern, it might be worth instrumenting what triggers the second and third use, since that will probably tell you more about retention than top-of-funnel metrics.

That’s actually a really strong signal.

It means your product isn’t just useful — it’s becoming a default step in a workflow.

Those are usually much more defensible than tools people just “try”.

Really interesting, that shift from “one-off tool” to something people return to at decision moments is a strong signal.

It almost sounds like the value isn’t just in the analysis itself, but in the confidence it gives users when they’re about to act.

In cases like this, I’ve seen it help to lean into that behavior more explicitly positioning it less as a tool you try, and more as something you rely on whenever a new contract comes up.

Have you explored making that repeat use more visible or intentional in the experience?

This is the best part of building — users always surprise you. What was the most unexpected feedback you got?

The "moment" product category is underrated. If your tool is tied to a recurring life event — signing a contract, starting a new week, hiring someone — retention mirrors how often that event happens. You don't need to engineer habit loops. The moment brings people back. Good early signal to catch.

That’s a strong signal — I’ve seen the same when a tool solves a “moment” problem, people just come back naturally.
Repeat use > signups any day.

This is such a valuable insight. Retention often reveals the real use case — users show you how they actually value your product, not how you imagined they would. It sounds like you accidentally built a workflow tool, not a one-time utility. Are you now thinking about features that support that repeat behavior more deliberately?

The repeat usage signal is one of the most underrated early indicators. First-time usage tells you the pitch worked. Repeat usage tells you the product actually fits into how someone works.

I've seen this pattern before — people assume they're building something people will "try," but the users who stick around have quietly made it part of their workflow. They don't announce it. They just keep coming back.

The "moment of decision" framing is a useful way to think about it. Products that sit at decision points — where someone needs to act and wants a second opinion or a structure to work within — tend to get used more than products that sit in the "nice to have" category.

Curious whether you've thought about how to deliberately trigger that return — or whether you're waiting to see more of the pattern before designing around it.

The repeat usage part means the product is becoming part of how people make decisions, not just something they test once out of curiosity. That behavior is a very strong foundation of curiosity.

This is such a valuable insight about building in public. The gap between what you assume users will do and what they actually do is where the real product lessons live. I've been building a lightweight memo app and had a similar surprise - I designed it as a quick capture tool, thinking people would use it once in a while. Turns out, the users who stuck around were using it multiple times daily as part of their core workflow, not just for occasional notes.

That repeat usage pattern you're describing is honestly one of the strongest signals you can get. It means the product is solving a recurring pain, not just a curiosity. It's also a great foundation for thinking about pricing - if people come back with every new contract, the value compounds over time.

Did you notice any patterns in how users discover this repeat use case? Like, do they come back on their own, or does something prompt them to return?

Great insight
Repeat usage isn’t just interest it signals real value and trust. Looks like the product became part of the decision-making process, not just a one-time tool.

The gap between what you think users will do and what they actually do is where every real product insight lives. Curious what surprised you most — was it how they used it or who was using it?

that’s a strong signal - when people come back on their own, you know it’s real

keep going, you’re building the right thing 👍