Pactar
Pactar is where contracts are negotiated.
Two weeks ago I posted here about Pactar — a contract negotiation and signing tool I built because I kept signing PDFs I half-understood.
The response was better than I expected. 25 comments, real conversations, people sharing their own contract horror stories. A few of you tried the product and gave me honest feedback. Thank you for that.
Here's what happened since.
What the comments taught me
One thread kept coming up, worded different ways by different people:
The counterparty experience is your distribution channel.
I knew this intellectually when I wrote the post. The comments made it concrete. Every contract has two sides. When the other party clicks a Pactar link and sees a contract broken into plain-language sections instead of a wall of PDF legalese — that moment is the product marketing itself.
Brady put it best: "Is it obviously Pactar, or does it just feel like a clean document?"
That question stuck with me. The answer right now is: it's somewhere in between. That's not good enough. The counterparty experience needs to be so clearly better than what they're used to that they immediately want it for themselves. I'm treating this as the most important UX problem in the product right now.
The segment question I couldn't answer two weeks ago
In the original post I asked: who's the right first customer? Freelancers? Agencies? Small business owners?
I've spent the last two weeks thinking about this. My answer has shifted.
Freelancers feel the pain. But they're slow to pay for tools, especially tools they use a few times a month. The math is hard.
Small agencies and SMBs — 5 to 20 person operations without a legal department — feel the same pain and have a very different relationship with business tools. They're used to paying for software. They close more deals. They have more at stake per contract. And they're sending contracts to clients, not just receiving them — which means they control the counterparty experience.
That's who I'm building for now. The product doesn't change. The positioning, the examples, the copy — those are changing.
One competitor worth noting
Yesterday, Legora announced $100M ARR in 18 months — the fastest any enterprise software company has ever hit that milestone. They're backed by Bessemer, serving law firms like White & Case and Linklaters, and just closed a $550M Series D.
This is not my market. Legora sells to legal departments at Blackstone and Barclays. I'm building for the agency owner who doesn't have a lawyer at all.
But it validates something important: the legal AI category is real, it's moving fast, and buyers are willing to pay serious money for products that reduce the friction in legal workflows. The enterprise end of the market is getting crowded. The SMB end is still wide open.
What I shipped
A few things have changed in the product since the post:
The parsing is more reliable. A few early users hit edge cases with unusual PDF formatting. I've made the Claude parsing prompt more resilient to messy real-world documents — better section detection, better handling of contracts that don't follow standard structure.
The counterparty onboarding is cleaner. When someone receives a Pactar review link for the first time, the experience now does a better job of explaining what they're looking at and what they can do. Still room to improve but meaningfully better than two weeks ago.
A contract wizard is in progress. Right now you have to upload or paste an existing contract. A lot of people — especially agencies — want to create a contract from scratch. I'm building a plain-English wizard that walks you through a few questions and generates a complete Service Agreement, SOW, or NDA using AI. No legal templates to hunt for. No blank page to stare at.
What I'm still figuring out
The counterparty flywheel is theoretically the best growth mechanism in the product. But I'm still learning how to make it reliable. Someone receiving a Pactar link for the first time needs to have a great enough experience that they sign up — not just review the document and move on.
If you've been on the receiving end of a Pactar review link, I'd love to know what that experience was like. Did you understand immediately what you were looking at? Did it feel useful or confusing? Did you sign up afterward?
And if you're running a small agency or a small business and deal with contracts regularly — I'd genuinely love to get on a call. Not to pitch you. To understand how contracts actually work in your operation right now.
Pactar is free for your first contract. If you haven't tried it yet: pactar.app
Every freelance deal follows the same pattern.
A PDF lands in your inbox. You open it, skim through pages of dense legal language, and tell yourself you'll read it properly later. You don't. You go back and forth over email for days — someone suggests a change, you make it, export a new PDF, attach it, send it. They do the same. Now there are four versions of the contract and nobody's sure which one is current.
Eventually you sign something you half-understand. You file it somewhere — a folder, an email thread, a downloaded file that lives on a laptop you'll replace in two years. Six months later something comes up and you're searching through your inbox trying to remember what you actually agreed to.
I'm a builder, not a lawyer. And I kept thinking: this process is broken in a way nobody has properly fixed. Not for people like me.
The tools that exist weren't built for us
There are two categories of contract tools.
The first is enterprise CLM software — Ironclad, ContractPodAi, DocuSign CLM. Powerful, deeply integrated, and priced and designed for legal teams at mid-size companies. Not for a solo founder closing a freelance deal.
The second is DocuSign for e-signing and... nothing for everything before the signing. The negotiation, the back and forth, the "wait which version are we on" — that all still happens in email. DocuSign picks up at the very end, after all the chaos.
Nothing in the middle existed for founders, freelancers, and small teams who need to close deals properly but don't have a legal department.
What I built
Pactar is a contract negotiation and signing tool for people like me.
You upload a contract — PDF, Word doc, or paste the text. Pactar parses it into sections automatically. Then for each section, AI generates a plain-language summary of what you're actually agreeing to, and flags anything unusual, one-sided, or missing. Not legal advice — just clarity.
You invite the other party with a single link. No account required on their end. Both of you see the same document, comment on specific clauses, propose edits, and track changes in context — not buried in an inbox. When a section is settled, both parties mark it as agreed. When everything is agreed, you sign inside Pactar. Legally binding. Done.
No more "which version is final". No more "I'll read the legal stuff later". No more searching through email threads six months later.
The stack
For anyone interested in the technical side:
Next.js (App Router) — full stack in one repo
Supabase — auth, database, file storage, row-level security
Liveblocks — real-time collaboration and presence
Anthropic Claude API — contract parsing, plain-language summaries, flag detection
Docuseal — e-signature integration
Vercel — deployment
The hardest part technically was the parsing step — taking an uploaded PDF or Word doc, extracting the raw text, and getting Claude to reliably segment it into named sections with accurate metadata. It took more prompt iteration than I expected, but the results are solid now.
The most satisfying part was the AI summary feature. Watching a dense legal clause get translated into "this means you can't work with their competitors for 12 months after the contract ends" — that's the moment the product clicks.
Pricing
Free — 1 contract, full features. No credit card required.
Pay-as-you-go — $9 per contract. Pay when you need it, no subscription.
Unlimited — $49/month. For people closing deals regularly.
I deliberately kept the free tier real — one full contract, not a crippled demo. I want people to actually experience the product before deciding whether to pay.
Where I am
The product is live and working. I've been using it for my own contracts at Laterous, my consultancy, and it's already changed how I approach deals. The chaos is gone.
Now I'm looking for the first people outside of me to use it — founders, freelancers, agency owners, anyone who's felt this pain. If that's you, I'd genuinely love to hear what you think.
The first contract is free. No credit card. Just upload something and see what it does.
What I'm figuring out
A few things I'm still working through that I'd love input on:
The right first segment. I built this for myself — a founder/consultant running a small operation. But I can see it being equally useful for freelance designers, developers, agencies. I'm trying to understand where the pain is sharpest and who'll become a paying customer fastest.
The lawyer angle. There's an interesting persona I haven't fully explored — lawyers who work with small business clients. If Pactar becomes the place where lawyer, client, and counterparty all collaborate on a contract, that's a different and potentially more powerful distribution model. Still thinking through it.
Word of mouth. For a tool like this, the best growth is probably someone using it on a deal and the counterparty on the other end going "wait, what is this? I want this." The counterparty experience matters as much as the owner experience.
If you have thoughts on any of this, or if you've dealt with contract chaos in your own work — I'd love to hear from you in the comments.
-
1
“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!”
-
1
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.
-
1
The gap between "understand the contract" and "sign the contract" is where all the bad deals happen. Good spot to build.
-
1
Thanks Hal! Feel free to give it a try. I'm looking for honest feedback.
-
-
1
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.
-
1
Yeah, you don't know what you don't know so at least hinting stuff is a big improvement.
-
-
1
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?
-
1
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.
-
1
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.
-
1
great work brother honestly , will check out your tool
-
1
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?
-
1
this actually hit harder than i expected
the “which version are we on” thing is way too reali’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 forwardhaving 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
-
1
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!
-
1
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.
-
1
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!
-
1
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.
-
1
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!
-
1
Hi Hani, thanks for your feedback and security advice! Getting this fixed today. Thanks a lot!
-
-
1
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.
-
1
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.
-
1
You are totally correct. The short term goal is to validate the flow with small teams that don't have a process and a legal team. Having a frictionless external workflow is key, or at least that's what I'm focusing on and improving.
-
-
1
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 😄
-
1
I would love if you can give it a try and give me honest feedback about the 1.0 - 🙏
-
-
0
This comment was deleted 5 months ago
-
1
Thanks for the feedback, Rugero! Right now, the PDF parsing is happening with parse-pdf (server side with Node). It's good for 1.0 but further improvements will be needed once adoption 🤞 os higher!
-
Comment