Hey Indie Hackers 👋
I launched Lexray 3 days ago - AI that scans contracts in 60 seconds and flags risky clauses.
THE BACKSTORY
I've signed hundreds of contracts over 15 years as a freelancer, contractor, and startup founder (Microsoft → Auth0 → Fusebit).
Every single time: "What am I missing?"
I'd read all the pages, Google confusing terms, ask founder friends "does this seem normal?" And still lose sleep wondering if I'd agreed to something that would haunt me.
Lawyers are expensive. Most contracts don't justify $500 for legal review. But signing blindly is how you get burned.
WHAT I BUILT
Lexray scans contract PDFs and tells you—in plain English—what's risky:
Takes 60 seconds. Free during beta.
Target: Freelancers and SMBs who sign vendor agreements, client contracts, partnership deals, etc.
TRACTION SO FAR (3 DAYS)
WHAT I NEED FROM YOU
Try it: https://lexray.io
Happy to answer any questions about the tech, the business, or the journey.
Tech stack:
Background:
20 years building dev tools at Microsoft , HP, Auth0, and Fusebit. This is my first solo bootstrapped product after leaving big tech and VC-backed startups.
Current focus:
Collecting feedback, refining analysis quality, figuring out monetization (probably transactional pricing).
This scratches a real itch — I've signed plenty of contracts with that same "what am I missing?" anxiety. The 60-second turnaround and plain-English output are exactly what makes this usable for quick decisions.
On distribution:
Freelancer communities that might be worth exploring:
The "contract horror stories" angle is smart for content — those posts tend to go viral in freelancer communities because everyone has one.
A few questions:
How are you handling edge cases where the AI flags something ambiguous? Is there a confidence score or "get a lawyer for this" threshold?
For monetization — have you considered per-contract pricing with volume discounts? Transactional feels right for this use case. Subscriptions might work for agencies/SMBs who review contracts regularly.
Are you seeing any patterns in what clauses trip people up most? That data could shape which risks to highlight first.
Good luck with the launch!
Thank you for the thoughtful comments and distribution ideas!
Regarding the "contract horror stories", I just published a blog on the five most common issues I have seen in the contracts I worked with so far: https://lexray.io/blog/5-contract-clauses-that-cost-freelancers-thousands
The current model does not assess ambiguity; this is a very good point. I have seen contracts that were a patchwork of some prior art or a poor copy & paste job, that were sometimes internally inconsistent. I will queue it up for next version. Right now the tool only gives a risk score on individual clauses, with the understanding that a "high" risk is a clue to consider working with a lawyer.
I am getting overwhelming feedback that transactional pricing is the way to go. I am currently considering a fixed per-contract price with some number of "first" contracts free (per lifetime) to plant a hook. I don't want to overcomplicate it with volume discounts until I see demand from companies that justifies it. I have not seen a freelancer who would be signing contracts at a significant rate.
Again, thank you!