I got tired of signing contracts I didn't understand. So I built Pactar.

“I’m a lawyer and share the exact same pain point – client signing things that they didn’t fully understand – so your story really resonated. Unlike you, I came in with zero tech background, so I’m genuinely impressed you managed to ship all of this solo.

I’ve been working on something similar called EqualDocs, and your post actually pushed me to think harder about what makes it different from what you’re building. In my case, I’ve gone a bit more ‘all‑in‑one’: EqualDocs covers create → review → negotiate → sign in one place, with clause libraries, bulk review and e‑signature, so it’s aiming to be more of a lightweight in‑house legal stack for small teams rather than a single‑use reader.

The way I think about it now is: Pactar helps individuals understand one contract at a time; EqualDocs helps small teams run their recurring legal workflows with more clarity and speed.

If you’re curious, I also wrote up my story as a non‑technical founder launching an AI legal tool on Product Hunt today – happy to share the link!”

The counterparty experiencing the product and wanting it themselves is genuinely your best growth loop and I think you've underrated it in this post. Every contract has two sides — if the other person goes "wait what is this tool" that's word of mouth that costs you nothing. On the segment question — freelance developers and designers feel this pain acutely and move fast when they find something that works. Lawyers who work with small business clients is the higher ACV path but slower to close. I'd go developers first, lawyers second. Product looks genuinely useful.

The gap between "understand the contract" and "sign the contract" is where all the bad deals happen. Good spot to build.

I don’t mind contracts being long — I mind not knowing what actually matters.

Most of the time everything is presented with the same weight, even though only a few parts have real consequences.

The real value is in cutting through that, not just summarizing.

The counterparty insight is the one worth doubling down on.

Most tools optimize for the person who pays. You're describing something different — a product where the person who doesn't pay might be your best distribution channel.

That changes what "free tier" means. It's not just a conversion funnel for the uploader. It's a first impression for every counterparty who clicks that link, reads a contract in plain language for the first time, and thinks: why don't I have this?

The question I'd be asking: what does that counterparty experience feel like right now? Is it obviously Pactar, or does it just feel like a clean document?

This is very relatable. I have signed contracts before without fully understanding them, just to avoid the back and forth.

The part about multiple versions in email is so real — that alone creates a lot of confusion.

I like that you focused on clarity instead of just signing. Even a simple summary of each section can help people feel more confident before agreeing.

Kudos to you for building this. This is a really spot-on idea. Understanding legalese feels like one of those areas that people pre-AI still think it's a human only skill while post-AI folks realize it's ready made for an AI to interpret faster and with a higher degree of quality. The way contracts are structured opaquely with references to sub-sections is perfectly designed to be challenging for a human in ways that are incredibly simple for Claude or equivalent to figure out. I'm nervous for Lawyers in the same way I'm nervous about Software Engineers at the moment.

great work brother honestly , will check out your tool

The sharpest part of this is the insight that e-sign tools only solve the last step, while the real mess is negotiation, version sprawl, and not understanding what you’re signing. If Pactar makes clause-by-clause collaboration simpler than email, that’s the wedge. Curious what early users value more: the plain-language summaries or the shared negotiation workflow?

this actually hit harder than i expected
the “which version are we on” thing is way too real

i’ve been stuck in that exact loop of pdf, email, edit, resend, and somehow it just gets more confusing every time
and yeah you end up signing something you don’t fully understand just to move things forward

having everything in one place with plain language summaries makes a lot of sense, especially for people who are not from a legal background

i’m curious how it handles messy real world contracts though, like poorly formatted docs or clauses that are all over the place

either way this feels like something that should have existed already. solid build

Hey,

Good job!

As per positioning you're going to take a step or two back to enable you to view from various perspectives as far as PMF is concerned.

It may or might not be your first view that'll open the floodgate for you but just the right positioning - and bang!!

Stay sharp!

The "word of mouth" angle you mentioned is the most powerful distribution channel hiding in plain sight. When the counterparty receives a Pactar link and has a better experience than the usual PDF-email-chaos loop, they become your next customer organically.

This is actually a pattern I think about a lot in the AI tools space — the best products don't just solve a problem for the buyer, they create a better experience for everyone in the workflow. That's what makes the viral coefficient real instead of theoretical.

One thought on the lawyer angle: small business lawyers who handle 20-50 contracts/month for clients would be incredible distribution partners. They'd essentially be onboarding their entire client base onto Pactar. Worth exploring a referral or white-label model there.

The gap you identified is real. Everything between "here's a PDF" and "sign here" is basically held together with email threads and good faith. I've been on both sides of that as a freelancer and it's always messy.

Using Claude for the plain-language summaries is a smart call. Curious how you handle edge cases where the AI misinterprets a clause. Do you have any kind of confidence scoring or disclaimer flow? That feels like the trickiest part of putting AI anywhere near legal text.

Also, the no-account-required approach for the other party is going to be huge for adoption. Every friction point you remove from that invite flow matters. Good luck with the launch!

Love the pay-as-you-go...$9 is a fair price for DFY contracts, and someone doing 6+ contracts a month can afford $49.

How is the user experience for the counterparty? The viral loop makes sense, but only if the learning curve is minimized on the receiving end.

So i went through the site, couple of things Excellent SEO foundation (97/100), clean and functional codebase, great loading performance (sub 1.6 secconds). But you do have a couple of potential security flags. The site lacks a Content-Security-Policy header, which prevents protection against cross-site scripting (XSS) attacks by controlling which resources the browser can load. (just go to whatever AI you used and instruct it "Add a Content-Security-Policy header to restrict resource loading. Start with: 'default-src 'self'' and expand as needed for your specific resources.". Also, the site lacks a Permissions-Policy header, which controls access to browser features like camera, microphone, and geolocation. so same thhing, just instruct it to Add a Permissions-Policy header to explicitly control which browser features can be accessed by your application. :) cheers!

On your first segment question, I think I'd go freelance developers and designers before agency owners. They may be more likely early adopters of a tool like this, perhaps less likely to have an existing workflow they're attached to, and more likely to tell other people about it when it works. Lots of likely's haha. I hope it made sense though. Agency owners (speaking as a consultant here) tend to already have processes, even if they are chaotic ones, but processes nonetheless. Freelancers (ahem ahem this guy) are usually still improvising every time. The counterparty flywheel you mentioned is the most interesting thing in this post. If the other party's experience is good enough, that's essentially free distribution on every deal you close. I'd put more engineering time into that experience than almost anything else right now. But super great to see something like it. Good luck with it! PS The pay-per-contract pricing is the right call for this audience.

On your first segment question, I think I'd go freelance developers and designers before agency owners. They may be more likely early adopters of a tool like this, perhaps less likely to have an existing workflow they're attached to, and more likely to tell other people about it when it works. Lots of likely's haha. I hope it made sense though. Agency owners (speaking as a consultant here) tend to already have processes, even if they are chaotic ones, but processes nonetheless. Freelancers (ahem ahem this guy) are usually still improvising every time. The counterparty flywheel you mentioned is the most interesting thing in this post. If the other party's experience is good enough, that's essentially free distribution on every deal you close. I'd put more engineering time into that experience than almost anything else right now. But super great to see something like it. Good luck with it! PS The pay-per-contract pricing is the right call for this audience.

This is so real honestly.

We deal with contracts on Upwork and direct clients both. And the PDF back and forth thing is something I have lived many times. Client suggests change, you update, send new PDF, they send another version, now nobody knows which one is final.

The part that hit me most is signing something you half understand. As agency owner dealing with international clients, contract language is sometimes very confusing and you just hope the other side is being fair.

Builder solving problem they personally lived is always best starting point. What tech stack you used to build this? Curious if it handles multi party contracts where more than 2 people need to sign 😄

This comment was deleted 5 months ago