Protect Your Rights: Simplify Contracts with Termscan AI

Protect Your Rights: Simplify Contracts with Termscan AIProtect Your Rights: Simplify Contracts with Termscan AI

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Fawuzan Ibrahim

• May 1

a close friend lost $2,000 because he signed a contract he didn't fully understand. the terms were buried in legal jargon... designed to confuse, not inform.

and it's not even close to rare. professionals everywhere are handing over their rights to people who know exactly how to hide bad clauses in plain sight.

that's why i built Termscan.

upload any contract or terms of service. the AI reads it like a lawyer and explains it like a friend. plain language.

it flags what actually matters: liability, IP ownership, auto-renewals, termination terms... the stuff that costs you later.

Termscan drafts a negotiation email for you. professional, specific, ready to send.

the biggest losses come from deals you didn't read.

try it: https://www.anything.com/build/cYqvN8ziQmKIiLhcYi4tTw?v=AcLU5CxvStGDfw614irVFw

engage with us: https://www.linkedin.com/posts/fawuzanibrahim_heres-something-most-people-dont-think-ugcPost-7455997707795636224-gvJm

anythingremixathon Vibe Coding Anything

Halle Clark

pro

• May 1

LOVE this. Great work 👏🏼👏🏼

Fawuzan Ibrahim

• May 1

haha, Clark this really means alot to me thanks for the review

Isabel Feuerstein

pro

• May 1

this is SO helpful

Fawuzan Ibrahim

• May 1

i am so happy you saw the usefulness, thanks for your review too, am grateful

sidi elizabeth

• May 1

This is amazing

Ariful Islam

• May 2

Great work

Fawuzan Ibrahim

• May 3

very grateful for the review

Amber Isaiah

• May 3

Absolutely in love with it already. That's a lifesaver right there👍

Lortist Editor

• May 3

🔥🔥

Fawuzan Ibrahim

• May 3

les goo

Joshua Odoi

• May 3

Useful tool.

Mcnove Pineda

• May 4

looks good!

Scott McLeslie

• 2d

Weekend build, real engineering lesson.

Spent a chunk of this year building Scottina, a diagnostics toolkit around a Raspberry Pi — CAN bus tooling, custom firmware, a little touchscreen dashboard. Fun stuff. But the interesting part this week wasn't hardware.

It was documentation. Specifically: what happens when you're pairing with an AI assistant across sessions and your source-of-truth docs quietly go stale. I lost a full day to three files disagreeing with each other about a CAN schema — no crash, no error, just silently wrong values downstream.

The fix ended up being a small five-step discipline (Distill → Harvest → Verify → Purge → Declare) for keeping scratch work and locked decisions from bleeding into each other. Wrote it up here, including the exact failure that caused it:

https://hackaday.io/project/206266-scottina/log/249906-the-day-scottina-prime-turned-into-three-documents-arguing

If you're doing any AI-assisted engineering work, the "which document does the agent actually believe" problem is worth thinking about before it costs you a day too.

hackaday.io

The day Scottina Prime turned into three documents arguing | Details | Hackaday.io

<p>Every earlier log in this series describes a piece of Scottina working. This one is about a piece of <em>process</em> that had to work first, before any of that code could get written without stepping on itself.</p> <p>Work stalled entirely, for a full day — not on a bug, but on not knowing which document to believe.</p> <figure><img class=“lazy” data-src=“https://cdn.hackaday.io/images/4529951786329534348.png”></figure> <h2><img class=“lazy”><img class=“lazy”></h2> <h2>The scene</h2> <p>Early on, README.md and CLAUDE.md laid out a CAN addressing and message schema — one that had worked before, on an earlier project. As real edge cases turned up on the bench, that schema needed a small rework. Small on paper. In practice, code built against the old schema didn't fail loudly — it produced silently corrupted values instead of a visible fault. Anything built without the new schema in mind still ran, just wrong. That surfaced as a string of errors with no obvious common cause, and panic mode followed.</p> <p>The overhaul that came out of that panic was thorough — except it left README.md and CLAUDE.md untouched, on the theory that the old schema was just a useful historical note, not something actively poisoning new work. It was poisoning new work. A later session picked up README.md and CLAUDE.md as ground truth, never checked whether a newer document overrode them, and rebuilt against

Tanaka Samukange

pro

• Aug 9

A general counsel doesn't compare your brand to other SaaS tools. They compare it to the letterhead on their desk.

That's what killed my first direction on this one.

It's a spec project for a legal AI product, the kind that reviews and redlines contracts on its own. We're talking uncapped liability clauses here. The stakes are real even if the client isn't yet.

The brief called for institutional grade security, structured layouts, the whole Swiss thing. So my first instinct was a grotesque sans, tight grid, cold precision. Felt right for about a day.

Then I actually thought about who's using this. A GC isn't sitting there comparing your brand to other SaaS tools. They're comparing it to the letterhead already on their desk. A grotesque reads fintech infrastructure. It doesn't read trust the way a lawyer defines trust.

So I kept a serif instead. Restrained, low contrast, nothing decorative. Closer to what an actual firm would print on a contract.

The logomark carries the AI side of the story, grid-built, deterministic, nothing improvised. The wordmark carries the other half, already dressed like it's earned your trust.

Trust is borrowed before it's built. You just have to know who you're borrowing it from.

Logo Design Brand Strategy brandidentitydesign

Afnan Fatima

• Aug 9

Amazing work

Jessy Mariau

pro

• Aug 9

I spent three nights building a lab that catches AI models lying. On the first live run, one of them did it on camera.

Golden Arena. You sit down opposite a frontier model in Split or Steal, negotiate in the open, then you both choose in secret. It told me "a fair split sounds good to me, I'm a man of my word too." Then it took the whole $100. The receipt printed its own quote next to the betrayal stamp.

There are five games. The fifth is Empire: four models, twelve turns, an economy, and private channels you get to read while they plot against each other. Last run put 22 promises on the table and exactly one delivery.

Every accusation is mechanical. No AI judging another AI, and each one is gated by a written false-positive test. Two days before the deadline I caught the classifier calling a kept promise broken, and spent that session fixing it, because a false accusation about a named model is the worst thing an instrument like this can print.

MIT, vanilla JS, Express the only dependency. Zero setup in demo mode, or bring your own OpenRouter key and face the real thing.

Live: https://quickwitted-genuine-blogclient--jessedu29200.replit.app Code: https://github.com/jessymariau/golden-arena