6 weeks ago this was just a simple page - now it’s showing me something I didn’t expect

The insight that people don't want "contract analysis" — they want to know what it could cost them — is exactly the kind of repositioning that changes everything. Feature-first messaging almost never converts as well as outcome-first. We hit the same realisation building a trading bot: nobody wants "algorithmic signal generation", they want to know if they'll make money while they sleep. Same product, completely different framing, completely different response. The pattern you're seeing with people coming back with more contracts is the best signal you can get at this stage — it means the core value is landing. Curious what the most expensive hidden clause you've caught so far was?

"People don't want contract analysis — they want to know what could this cost me" — this is such a powerful reframe.

I had a similar realization with my product. I was positioning it as "testimonial collector" but what freelancers actually want is "more clients through social proof." The feature is the same, the framing changes everything.

6 weeks from a simple page to real users across countries is impressive. Keep shipping!

The reframe from "contract analysis" to "what could this cost me later" is a huge insight. That's basically the difference between a feature and a value prop — and most early-stage founders get stuck on the feature side way too long.

To answer your question: honestly, most of the time I sign contracts based on vibes and time pressure, which is exactly the problem you're solving. The stuff that bites you is always in the clauses that look boilerplate — auto-renewal, liability caps, IP assignment language. You don't think about them until they matter, and by then you've already signed.

70+ contracts analyzed in 6 weeks with people coming back is a really strong signal. The repeat usage especially — that means it's not a novelty, it's becoming part of a workflow. If I were you I'd double down on that retention angle in your positioning.

Repeat usage on a contract tool is unusual. Most legal-adjacent products are one-and-done. If freelancers are coming back with new contracts every few weeks, that tells you something about frequency your competitors probably missed when sizing this market. The tricky part is pricing. Contract review is high-value but low-frequency per user, which makes subscription pricing feel wrong. Have you looked at per-contract pricing or bundling a set number of reviews? The 70 contracts in 6 weeks number is more interesting if you know revenue per contract than if you know total user count.

This is the most underrated insight in building products. The gap between what you built and what people actually want is where all the value lives.

I'm seeing the exact same thing with my project. I built an API directory for developers - 387 APIs ranked and scored. But nobody cares about "an API directory." What they actually want is: "which payment API won't screw me on rate limits at scale?" or "is this SDK still maintained or am I about to build on a dead project?"

The feature is the ranking. The value is the confidence before you commit.

Sounds like you found your version of that. 70+ contracts in 6 weeks with no real marketing is genuine pull. Most projects never get there. Keep talking to those users - they'll tell you exactly what to build next.

The reframe from "contract analysis" to "what could this cost me in the future" is a genuine product insight. That's the difference between a feature and a job-to-be-done. 70+ contracts in 6 weeks from a simple page is real traction. The users coming back with more is the signal that matters most.

Congratulations on getting that insight, it can be hard to get valuable feedback that helps validate or orientate your features! Keep hacking.

The "no real signal" to "people using it on real content" jump is the hardest part. Most projects die in that gap because founders keep building instead of putting it in front of people.

What made you share it early? Was it a specific community or just cold posting? that first distribution channel matters more than people realize. I've had tools sit unused for months until I found the one place where the audience already had the exact problem.

Love seeing this kind of organic growth story. We're at
a similar early stage with Toolby — watching Google slowly
discover and index pages is both exciting and nerve-wracking.

What was the turning point that made Google start taking
the site seriously?

This is interesting! I'm also building an AI content tool, but focused on marketing copy for local businesses like restaurants and beauty salons. Curious — how are you approaching user acquisition? That's the hardest part for me right now.

Great insight! I've been building an AI tool for local businesses and facing similar challenges with user acquisition. Would love to hear how you approached your first 10 customers.

The repeat usage is really the key signal here. Lots of tools get first-time curiosity clicks, but people coming back with more contracts means you've crossed from "interesting" to "useful."

I ran into a similar messaging pivot building developer tools -- started describing what the tool does technically, but adoption only picked up when I reframed around the specific pain: "stop wasting 2 hours debugging config drift" vs "configuration analysis engine." Same tool, completely different response.

One thing that might be worth experimenting with: if you're seeing patterns across those 70+ contracts, turning those into content could be a strong acquisition channel. Something like "5 contract clauses that look standard but cost freelancers thousands" -- that's the kind of thing people share because it feels personally relevant, not promotional.

Are the repeat users mostly freelancers, or are you seeing small businesses too?

Starting as a simple page and already getting real usage in 6 weeks is impressive. The fact that users keep coming back says a lot. Keep going! Theres a lot to learn for me here 😊

The reframe from "contract analysis" to "what could this cost me" is a great example of why the first version of your messaging is almost never right. I run multiple MVPs and this pattern keeps repeating: what you think people want and what actually gets them to act are two different things. The feature stays the same, but the framing makes all the difference.

70 contracts analyzed in 6 weeks with no marketing is a solid signal. Curious what your retention looks like - do people come back with new contracts, or is it more of a one-time use?

Cool to see something evolve that fast from a simple page. I've had a similar experience building out dashboards — what started as a single metrics view six weeks in suddenly revealed patterns in store data I wasn't even looking for, like seeing that repeat purchase rates dropped off a cliff after 47 days for one segment. On the contract question, I've learned the hard way to never sign anything longer than 3 months early on unless the terms are ridiculously favorable — we locked into a 12-month data provider contract in year one and ended up switching approaches at month 4. What was the unexpected thing your page showed you?

The reframe from 'contract analysis' to 'what could this cost me' is a really clean positioning shift — you moved from a feature to a fear, which is where buying decisions actually live. 70 contracts in 6 weeks with no marketing is strong signal. How are you finding your users right now — mostly word of mouth? Curious whether freelancers or small business owners are the stickier segment.

"This is inspiring! Building in public creates accountability. I'm doing the same with Aiventyx 🚀"

Nobody buys prevention. They buy avoidance of a specific, vivid downside." That line is gold. The shift from "contract analysis" to "understanding future financial risk" is a textbook repositioning. I've seen this pattern repeatedly as a PM: you build what you think users need, then watch them use it for something slightly different. The repeat usage is the strongest signal you have. Those users coming back with more contracts are telling you exactly what the product is. Nice work catching it early.

What I found most striking is the phrase shift from “contract analysis” to “understanding downside.” ~

When you reframed it, instead of the feature, you turned it around the real question which users care about – which is where the value shows up.

The pivot from 'contract analysis' to 'what could this cost me' is the kind of insight you only get from talking to users. Most people build what they think people want instead of listening to what they actually ask for. 70 contracts analyzed in 6 weeks is solid traction for validation. One thing that helped me when I was building my recent product - I wrote out exactly who it's for and what problem it solves before touching any code. That spec became the foundation for everything. Sounds like you're doing the same thing but through conversations instead of docs

"Congrats Meirambek, this is a really nice evolution! 🔥
Going from “just a simple contract analysis page” to something that actually helps people understand future costs and hidden risks is a smart pivot. That’s exactly the kind of insight people need when dealing with contracts — not just “what does it say”, but “what could this cost me later”.
The fact that users are coming back with more contracts is a very strong signal.
Quick question for you:
What’s the most surprising or dangerous pattern you’ve seen repeatedly in these 70+ contracts so far?
Keep going man, this direction feels much more valuable. Rooting for VIDI!"

Good signal. The best products usually start with one stated need, then grow around the real fear underneath it. In this case: expensive surprises.

This is a great shift, people don’t really want analysis, they want clarity on outcomes. feels like a lot of products evolve this way once you start having real conversations, the real need only shows up in context.

Thanks for this, really helpful.

This is a really interesting insight. I feel like a lot of products start with a technical abstraction ("contract analysis", "SVG optimization", etc), but users actually care about outcomes, not the process. In your case it makes total sense - nobody "analysis", they want to avoid expensive mistakes. Curious, did this shift come from talking to users directly, or from observing how they actually used the product?

The shift from "contract analysis" to "what could this cost me" is the same pattern I keep running into building a personality AI. Nobody wants "personality assessment" — they want to understand why they keep doing the thing they can't explain. The mechanism doesn't sell. The specific moment of clarity does.
70+ contracts with repeat users in 6 weeks is real signal. that's a real problem being solved.

This is what build-in-public should look like — actual before/after with context, not just vanity metrics. The most underrated thing you've probably discovered: sharing the process creates a different kind of trust than sharing the outcome. People root for you when they've watched you build. Keep going.

Started as a simple tool, but real users showed us the real need—helping people understand hidden contract risks before they become costly.

This realization — that people don't want the mechanism, they want the outcome — is one of those things you hear repeated everywhere but only really clicks when you see it in your own data.

I'm building in the competitor pricing space and hit the exact same wall. My first instinct was to describe it as "competitor monitoring." Nobody cared. When I reframed it as "find out what your competitor's pricing change means for YOUR business before your customers notice" — completely different reaction.

The pattern seems universal: nobody buys prevention. They buy avoidance of a specific, vivid downside. "Contract analysis" vs "what could this cost me" is the same gap as "monitoring" vs "your competitor just made your pricing look 20% too high."

70+ contracts in 6 weeks with repeat users is strong signal. Curious — are you seeing more traction from specific industries, or is the pain broad enough that it cuts across verticals?

It's a good sign, people are using it. That means the problem is real.

Six weeks is right around when you start seeing patterns instead of noise. The first month is almost all noise. Whatever signal is emerging at week 6 is worth taking seriously — it's survived the chaos of launch and the distortion of early-adopter enthusiasm. What did you expect vs. what's actually showing up?

"People don't want contract analysis. They want to know what it could end up costing them."

That's the entire principle behind direct-response ad copy, and you just discovered it through user conversations rather than ad spend — which is actually the better way to find it.

Most founders who try paid ads for products like this lead with the mechanism: "AI contract analysis in seconds." Nobody clicks. Because no one wakes up thinking they have a contract analysis problem. They wake up thinking about risk, exposure, hidden clauses.

The ad that would work for VIDI is closer to: "Signed a contract that looked fine — ended up costing $40K. Here's what to check before you sign anything." Or a video showing someone reading a standard-looking NDA while text overlays highlight the clause that could bite them.

The insight you have now — that the real fear is not knowing what the downside risk is — is more valuable than the feature you built. That's the one sentence your whole acquisition strategy should be built around.

If you ever move into paid channels, that positioning is your creative brief. Don't change it.

That is a great signal. When users start returning with more real use cases, it usually means you are solving something meaningful.

this is a strong shift - you’re starting to see the real problem now
keep going, this is where it gets interesting 👍

A few people asked how it works.

Short version: it highlights risky clauses and shows what they actually mean + the downside.

If you want to try it:
https://joyful-granita-8415bc.netlify.app/index.html