18 | Building the proposal builder for freelancers & small agencies @form44app

Joined January 2026
54 Photos and videos
Pinned Tweet
I am 17 & closing in on 10k/m with Form44 Well, not yet. But hear me out... Last year I ran an AI lead gen agency. But I couldn't close clients Turns out sending a Google Doc & a Stripe link as a proposal is a recipe for them ghosting you So I created form44.app
1
1
5
254
day 78 of documenting @form44app, a proposal tool for freelancers & agencies Added proposal version history so you can see what the document looked like at each point it was edited before publish, with a timestamp and the option to restore a previous version. Proposals go through several rounds of edits between the initial draft and the version the client sees, and losing an earlier scope description because a revision overwrote it happens more than it should. For anyone who has needed to reference what the original proposal said and found that version no longer exists, this is the feature that prevents that. sign up → form44.app
1
10
day 77 of documenting @form44app, a proposal tool for freelancers & agencies Shipped bulk send mode so you can send the same proposal structure to multiple recipients with variable substitution, without duplicating and manually editing each copy. Agencies that onboard clients in batches follow the same proposal structure every time, and building a fresh copy for each recipient is mostly just wasted motion on the parts that don't actually differ. For anyone sending the same document to a cohort of clients with only a few variable swaps per copy, this removes the repetitive part of the workflow. try it → form44.app
1
11
day 76 of documenting @form44app, a proposal tool for freelancers & agencies Added auto-archiving for proposals that expire without a response, so they move out of the active dashboard into an archived state without the sender having to manually clean them up. A dashboard full of expired, unanswered proposals creates a low-grade sense of failure every time you open it, even when most of those proposals just went to leads who weren't ready yet. For anyone running a steady volume of outbound proposals, keeping the active list clean is a practical thing, not just an aesthetic one. sign up → form44.app
1
4
day 75 of documenting @form44app, a proposal tool for freelancers & agencies Added internal notes on proposals that only the sender can see, separate from the document content the client reads. Proposals often get sent weeks after the discovery call, and the sender's memory of why the scope is priced the way it is starts fading without something to anchor it. If a client pushes back on a line item three days after signing, you want to remember why it was in there. try it → form44.app
2
day 74 of documenting @form44app, a proposal tool for freelancers & agencies Added customizable accept and decline button labels so the text on the proposal's primary action button can match the language of the agreement rather than defaulting to generic labels. The words on a button affect what a person does with it more than most expect, and a button that says "Confirm project and pay deposit" tells the client what they're committing to in a way that "Accept" doesn't. For anyone sending proposals where the agreement language matters to the client relationship, this is the detail that affects how professional the document feels. sign up → form44.app
day 73 of documenting @form44app, a proposal tool for freelancers & agencies Added webhook support so proposal events like viewed, signed, payment received, and declined can trigger automations in external tools. If you run client work through a CRM or project management tool, connecting Form44 events to that system means you don't have to manually move a deal from "proposal sent" to "deposit paid" every time a signature arrives. For anyone already using Zapier or Make for workflow automation, this is the connection point. try it → form44.app
2
day 72 of documenting @form44app, a proposal tool for freelancers & agencies Spent time this week on the client-facing mobile experience, specifically how the proposal reads and how signing and payment works on a phone. Most freelancers send proposals to clients who open them on a laptop, but a meaningful share of clients open links on their phone first and decide whether it's worth a closer read on that screen. If the mobile view looks broken or unnavigable, the proposal doesn't get a second look regardless of what's in it. sign up → form44.app
4
day 71 of documenting @form44app, a proposal tool for freelancers & agencies Added client-facing comments so a client can leave a question or note directly on the proposal before signing, rather than sending an email that gets disconnected from the document. The back-and-forth between sending a proposal and getting it signed is usually just two or three small clarifications, and doing that inside the document keeps the context in one place. For anyone who has lost track of which version of a proposal a client was commenting on when they emailed separately, this removes the split. try it → form44.app
2
day 70 of documenting @form44app, a proposal tool for freelancers & agencies Added signing order control for proposals with multiple signatories, so you can set whether the client signs first or whether the sender's countersignature follows. Some agreements only make legal sense if the parties sign in a specific sequence, particularly when the client's signature triggers obligations on the sender's side. For anyone sending service agreements where both parties need to countersign in order, setting the sequence explicitly removes the ambiguity. sign up → form44.app
3
I'm still surprised by how long it takes to know if an early decision was right. Thread below.
1
You make a call in the first month of building. You ship it. Three months later you find out if it was correct. By then you've built five other things on top of it. If you got it wrong, you're not just undoing the decision. You're undoing everything that depended on it. I've done this twice on Form44. Both were fixable. Neither was cheap. The lesson wasn't "make better decisions." It was "document why you made the ones you made." Future you doesn't remember the reasoning.
2
Building Form44 solo. When a proposal is published, Form44 takes a snapshot of the document in its exact state at that moment. The client signs the frozen version, not the live editor. If scope is ever disputed, you point at the document they actually signed, not a version you may have edited since.
4
The part of Form44 I thought would confuse users didn't. The part I thought was obvious confuses almost everyone. Thread below.
1
1
The builder canvas I spent weeks on? Most first-time users picked it up in under a minute. The publish step, which sends the proposal live? Most of them forgot it existed. They'd finish writing, copy the URL from the browser, and share it with the client before the proposal was even published. You can't predict which part of the flow will be friction until someone who isn't you tries the thing. The fix was obvious once I saw it happen. But I had to see it happen first.
5
The most useful thing I built into my workflow wasn't a feature. It was a rule: if three separate users mention the same problem, it goes on the list. One mention is a one-off. Two is a coincidence. Three is a signal. Everything else is a guess. A solo founder has a finite amount of time before something runs out. The signal cuts the guess list down to what actually matters.
2
2
38
Got asked if building solo is lonely, and I said no, because customers and competitors give you enough to think about that you rarely notice.
1
3
Building Form44 solo. Shipped field-level validation for client input fields: email, phone, number, date, URL, and custom regex. If a client submits a phone number in an email field, the error should happen at the form, not when you try to use the data later. Now you set what the field accepts before it reaches them.
1
7
Building in public before the product was ready felt premature. I started anyway. Not to build hype. Because public timestamps are harder to fake than launch-day claims. When someone asks how long I've been building this, I have a log that answers. That's more credible than anything I could write in a landing page headline.
1
1
7
PandaDoc Starter doesn't include recurring billing. If a freelancer wants to set up a monthly retainer from inside a proposal, they need Business at $49 a user per month. That's a $49 gate for a workflow most retainer-based freelancers use every month. Form44 includes recurring billing at $24 flat. No upgrade decision needed.
1
6
I set a launch date before Form44 was ready. Deliberately. Thread below.
1
1
4
Without a date, "almost ready" stays almost ready. There's always one more edge case. One more thing to polish. One more feature that would make the launch feel safer. The date ended that. It turned every decision into: is this in the critical path, or is it not? Most things weren't. Most things got cut. The ones that made it are the ones that actually matter. Picking the date was the most useful product decision I made in the build.
1
3