I'm Tomasz, former Microsoft/Auth0 engineer and founder. I built Lexray to solve a problem I've had for years: understanding contract risk without hiring a lawyer for every agreement.
WHAT IT DOES
Upload a contract PDF (NDA, MSA, client agreement, vendor contract) → AI scans for risk patterns → Returns plain-English explanations in 60 seconds.
Flags:
- IP clauses that claim more than deliverables (e.g., "work created during the term" vs "for this project")
- Auto-renewals with short notice (90-day notice buried on page 12)
- Net-60/Net-90 payment terms hidden in fine print
- Unlimited indemnification (uncapped liability)
- Overly broad non-competes
WHY I BUILT IT
I've signed hundreds of contracts as a freelancer, contractor, and startup founder. Every single time: "What am I missing?"
Most contracts are fine. But the risky ones cost thousands. I've missed auto-renewal deadlines, signed overly broad IP clauses, and lost sleep over clauses I didn't fully understand.
Lawyers are $500/hour. Most freelance contracts don't justify that cost. But signing blindly is how you lose money.
TECHNICAL APPROACH
- Next.js + TypeScript + Tailwind
- AWS cloud: AppRunner, SQS, Lambda, DynamoDB
- Google Auth via Auth0
- Anthropic Claude API for contract analysis (tested vs OpenAI, Claude performed better on legal nuance)
- Privacy-first architecture: Files encrypted in transit, deleted right after analysis (<60 seconds)
- Zero data retention, no model training on uploads, no third-party sharing
TRACTION (LAUNCHED 5 DAYS AGO)
- 40+ users analyzed contracts
- Real testimonials:
- "Lexray is pretty cool! And, I am a lawyer!" (Chief Legal Officer, 200-person startup)
- "Lexray spotted a ton of issues in a contract we had that standard AI tools missed." (Jeffrey Doehler, Partner at Lead Cookie)
- "This scratches a real itch — the 60-second turnaround and plain-English output are exactly what makes this usable." (Indie Hackers user)
- "This is a product that solves a pain that is acute and widespread." (Venture Builder & Investor)
- Free during beta
WHAT I'D LOVE FEEDBACK ON
1. *Timing problem:* People like the idea but don't have a contract to review RIGHT NOW. How do I stay top-of-mind for when they actually need it?
2. *Trust barrier:* How do I convince strangers to upload confidential documents? Even with encryption/deletion guarantees, it's a big ask.
3. *Analysis accuracy:* If you try it, how good is the analysis? False positives/negatives? Anything it missed that a human would catch?
4. *Positioning:* Is "triage before lawyer" the right framing? Or should this be positioned differently?
Happy to answer questions about the tech stack, privacy model, business approach, or share specific examples of what it catches.
---
EDIT (SINCE PEOPLE WILL ASK)
*Privacy/security technical details:*
- Upload: HTTPS to AWS load balancer, VPN later
- Processing: In-memory only, never written to disk
- Deletion: Immediate after analysis (<60 seconds)
- Logs (CloudWatch): Metadata only (timestamp, file size), no contract content
- Training: Never used for model training (explicit in Claude API terms)
- Audit: Happy to show the deletion code if anyone wants to verify
I'm a solo founder with zero interest in your confidential data. The entire business model is helping you understand contracts, not harvesting them.
*Liability question (since it'll come up):*
This is a screening tool, not legal advice. Explicit disclaimer on site. Like TurboTax isn't liable if you file taxes wrong, I'm not liable for missed risks. This supplements legal review, doesn't replace it.
*Why not open source:*
Considered it. Prompts are my competitive advantage right now, and I worry about forks that might not respect privacy (storing user contracts). Might open-source parts later (e.g., contract parsing utilities).
janczukt•1w ago
I'm Tomasz, former Microsoft/Auth0 engineer and founder. I built Lexray to solve a problem I've had for years: understanding contract risk without hiring a lawyer for every agreement.
WHAT IT DOES
Upload a contract PDF (NDA, MSA, client agreement, vendor contract) → AI scans for risk patterns → Returns plain-English explanations in 60 seconds.
Flags: - IP clauses that claim more than deliverables (e.g., "work created during the term" vs "for this project") - Auto-renewals with short notice (90-day notice buried on page 12) - Net-60/Net-90 payment terms hidden in fine print - Unlimited indemnification (uncapped liability) - Overly broad non-competes
WHY I BUILT IT
I've signed hundreds of contracts as a freelancer, contractor, and startup founder. Every single time: "What am I missing?"
Most contracts are fine. But the risky ones cost thousands. I've missed auto-renewal deadlines, signed overly broad IP clauses, and lost sleep over clauses I didn't fully understand.
Lawyers are $500/hour. Most freelance contracts don't justify that cost. But signing blindly is how you lose money.
TECHNICAL APPROACH
- Next.js + TypeScript + Tailwind - AWS cloud: AppRunner, SQS, Lambda, DynamoDB - Google Auth via Auth0 - Anthropic Claude API for contract analysis (tested vs OpenAI, Claude performed better on legal nuance) - Privacy-first architecture: Files encrypted in transit, deleted right after analysis (<60 seconds) - Zero data retention, no model training on uploads, no third-party sharing
TRACTION (LAUNCHED 5 DAYS AGO)
- 40+ users analyzed contracts - Real testimonials: - "Lexray is pretty cool! And, I am a lawyer!" (Chief Legal Officer, 200-person startup) - "Lexray spotted a ton of issues in a contract we had that standard AI tools missed." (Jeffrey Doehler, Partner at Lead Cookie) - "This scratches a real itch — the 60-second turnaround and plain-English output are exactly what makes this usable." (Indie Hackers user) - "This is a product that solves a pain that is acute and widespread." (Venture Builder & Investor) - Free during beta
WHAT I'D LOVE FEEDBACK ON
1. *Timing problem:* People like the idea but don't have a contract to review RIGHT NOW. How do I stay top-of-mind for when they actually need it?
2. *Trust barrier:* How do I convince strangers to upload confidential documents? Even with encryption/deletion guarantees, it's a big ask.
3. *Analysis accuracy:* If you try it, how good is the analysis? False positives/negatives? Anything it missed that a human would catch?
4. *Positioning:* Is "triage before lawyer" the right framing? Or should this be positioned differently?
Try it: https://lexray.io
Happy to answer questions about the tech stack, privacy model, business approach, or share specific examples of what it catches.
---
EDIT (SINCE PEOPLE WILL ASK)
*Privacy/security technical details:* - Upload: HTTPS to AWS load balancer, VPN later - Processing: In-memory only, never written to disk - Deletion: Immediate after analysis (<60 seconds) - Logs (CloudWatch): Metadata only (timestamp, file size), no contract content - Training: Never used for model training (explicit in Claude API terms) - Audit: Happy to show the deletion code if anyone wants to verify
I'm a solo founder with zero interest in your confidential data. The entire business model is helping you understand contracts, not harvesting them.
*Liability question (since it'll come up):* This is a screening tool, not legal advice. Explicit disclaimer on site. Like TurboTax isn't liable if you file taxes wrong, I'm not liable for missed risks. This supplements legal review, doesn't replace it.
*Why not open source:* Considered it. Prompts are my competitive advantage right now, and I worry about forks that might not respect privacy (storing user contracts). Might open-source parts later (e.g., contract parsing utilities).