I cancelled my proposal service this month. Replaced it with something I built inside Mission Control, and it does the things I actually need. It lets me author a proposal, gives the client a clean page to read it on, lets them sign it, and lets them pay through Stripe.
The interesting part is not the cost saving. It is what changed in how I work the moment I owned the surface.
The thing about hosted proposal tools
For years I sent proposals through a hosted proposal service. It worked. Clients could read it, sign it, the file got stored. No real complaints in terms of function.
What I started noticing was friction in a different place. Every time I had an idea for how a proposal could land better, a different opening section, a clearer pricing table, a small bit of context at the bottom, I had to fight the template editor to get it in. And the template editor only let me do what the template editor was designed to let me do.
The proposal was often the first real thing a new client saw from me. And the surface it lived on was someone else's product. That bothered me more than the monthly bill ever did.
What I actually built
The system has two halves. An authoring side inside Mission Control, where I write and edit a proposal the same way I write everything else. And a public portal at offer.alexpfeffer.com, where the client opens a clean link, reads the proposal, signs it, and pays through Stripe.
No template lock-in. No drag-and-drop builder pretending to be a layout engine. If I want to change how a proposal looks, I change it. If I want to add a new section type, I add one. If I want a different structure for one specific client, I can do that without asking anyone for permission.
That is the part I keep underestimating until I use it. Software you own bends to your taste. Software you rent bends to the average of everyone who pays for it.
From the call to a draft I can send
Here is what the actual flow looks like now. I jump on a Zoom call with a potential client. Fathom records and logs the call in the background. By the time the call wraps, a draft proposal is sitting in Mission Control, built from what we just talked about, ready for me to review.
That last part is the one I still find strange. The gap between the conversation and the offer used to be a whole evening of typing. Now it is the time it takes me to read what came out and decide if I would actually send it.
This only works because the call, the draft, the signature, the payment, and the portal that delivers it all live in the same system. Nothing has to be passed between separate products with separate logins. The conversation gets captured, the proposal gets drafted, the client reads and signs and pays, and the whole chain comes out of the same place.
The afternoon test
There is a question I now ask about any tool I depend on for client work. If I have an idea this afternoon, can I ship the change this afternoon?
With the old service the answer was no. I could swap copy in my template. But the actual feel of the page, the typography, the structure of the reading experience, all of that was locked behind the product.
With the new system the answer is yes. The gap between 'I should change this' and 'the change is live' is one sitting. That is not a small thing. Most of what people call iteration in a business is really just the speed at which you can act on a small idea. When that gap collapses, you start iterating constantly without thinking of it as iteration.
What I am not doing
I am not telling anyone else to do this. For most people, a hosted proposal tool is the right answer. The reason it made sense for me is that I already had Mission Control as a foundation, I can add features to it whenever a part of the business needs a new one, and proposals are core enough to my client work that owning the surface mattered more than the build cost.
The pattern under it
This is one piece of a larger move I have been making for a while. Pulling the surfaces that touch my clients back inside my own system. Email replies pre-drafted in my own queue. Content written and reviewed in my own workspace. Proposals authored, signed, and paid through my own portal.
None of these are dramatic moves on their own. Together they add up to something I care about more than any individual tool. The work that represents me to the outside world is happening on infrastructure I control, and I can change any part of it the same afternoon I have the idea.
The point was never to save money on a proposal service. The point was to stop renting the first impression.
