1
0 Comments

πŸš€ How a failed P2P loan app idea accidentally turned into a closed-loop shield for freelancers (and why I stopped listing "features")

Hey Indie Hackers,

Posted about Pacterms yesterday and honestly the response kind of caught me off guard. A few comments really stuck with me β€” people saying they actually quit freelancing at some point because something like this didn't exist to save them from the admin/chasing-payment burnout.

My dad was an independent contractor for years and I watched him go through this exact stuff β€” clients ghosting, no real leverage, just hoping people pay you. So yeah this one's personal, not just a "market opportunity" for me.

Whenever people check out the app they usually ask me to list every feature. I keep avoiding that on purpose. Dumping a big list of tools in front of someone just overwhelms them and honestly it doesn't even explain why the thing works. Pacterms isn't really a bunch of separate tools bolted together, it's more like one loop that keeps feeding itself, and every piece exists to give the worker more leverage at a different point in the job.

Here's roughly how it plays out:

Phase 1 β€” the fast part: No sitting at a desktop uploading PDFs or messing with signature fields. You're on the job site, you type in the basic project details, and it turns that into a proper contract outline in like 30 seconds.

Phase 2 β€” the bilingual handshake: You text the client a link. No app download, no password. They get a clean mobile page, read the terms in English or Spanish (built bilingual from day one since a huge chunk of trade workers are Spanish-speaking and most tools out there ignore that), and sign with a one-tap SMS code. Deal's locked in before you even leave.

Phase 3 β€” deposit enforcement: Once they hit "agree," it splits out the payment milestones automatically (50/50 down, whatever you set). Work doesn't officially start until that deposit actually clears. So no deposit = you're not obligated to show up. Filters out the clients who were never serious anyway.

Phase 4 β€” crew jobs Bigger job, bringing a crew? Instead of everyone signing separate contracts, the lead adds up to 4 people onto one shared agreement, sets everyone's cut, and each person gets a text to confirm their share. Honestly, this bit is doing a lot of the acquisition for me without me having to do anything β€” every crew member added is basically a new user pulled in for free.

Phase 5 β€” proof from the field: Once work starts, there's a start/stop timer and workers upload before/after photos or video. Once the client approves the progress, the progress on milestones moves forward. If the client requests for the re-work or is not satisfied with the work, they can simply click on needs improvement and mention the details. That way if a client ever tries to claim the work was bad, there's already a timestamped record sitting there.

Phase 6 β€” invoicing that just happens: Invoices go out automatically when milestones are hit. Client also gets a soft reminder text before the due date so nobody has to send an awkward "hey following up" message themselves. Right now invoicing is actually free and unlimited for everyone, even non-pro users it just comes with Pacterms branding on it. Honestly, that's on purpose; every free invoice that goes out is basically a tiny ad for the product landing in front of someone new. If you want your own branding instead of ours, that's $0.50 an invoice.

Phase 7 β€” the money side: Once payment clears, it splits the funds per the crew agreement, logs any fees, and drops everything into a running summary so you're not staring at a spreadsheet trying to figure out what you actually made this month.

Phase 8 β€” the evidence pack: When a job wraps, everything signed contract, delivery/verification metadata, payment history, timer logs, before/after media gets bundled and hashed so it can't quietly be edited later by either side. Basically a paper trail neither party can fudge.

Phase 9 β€” last resort: If a client goes quiet after the reminders, you flip it to "demand notice" and it sends a few escalating warnings automatically. If they still don't respond, it compiles everything into a court-ready packet and pre-fills a small claims complaint letter for your state. You still have to file it yourself I'm not trying to practice law here but you're not starting from a blank page either.

Anyway. Still early, still building this mostly solo with AI tools since I'm not a "traditional" coder, but the loop is what I actually believe in more than any single feature. Happy to answer anything.

posted toAvatar for product Pacterms
Pacterms