Writing a proposal that actually gets a reply

You spent two hours writing a proposal. You hit send. Then... nothing. No reply, no "thanks but no thanks," just silence. It's one of the most demoralizing parts of running a small tech business.

The problem usually isn't your price or your skills — it's the proposal itself. Most proposals are written for the sender, not the reader. Here's how to flip that around.

1. Lead with their problem, not your company

The most common mistake: opening with "About Us." Your client doesn't care about your founding story yet. They care about whether you understand their situation.

Your first paragraph should prove you were listening. Name the specific problem they described, reflect back the stakes involved, and show you grasp what a solved version looks like. Two or three sentences is enough. If they feel seen, they keep reading.

2. Make the scope brutally specific

Vague proposals create anxiety. When a client reads "website redesign and related services," they imagine runaway costs and endless scope creep — and they hesitate.

Instead, list exactly what's included and, just as importantly, what's not. Use a short bullet list:

• Included: 5-page site, 2 rounds of revisions, mobile-optimised build, handover call
• Not included: Copywriting, stock photography, ongoing hosting management

Clarity signals professionalism. It also cuts down on back-and-forth emails after they sign.

3. Show the outcome, not the process

Clients buying tech work don't really want a CRM integration — they want their sales team to stop losing leads in a spreadsheet. They don't want an API build — they want two tools that finally talk to each other.

Frame every deliverable in terms of the result it produces. Instead of "we will configure Zapier workflows," write "your order confirmations will fire automatically without anyone touching a keyboard." It sounds small, but it shifts the client's mindset from evaluating cost to imagining value.

4. Give one clear price, not a menu

Tiered pricing packages sound smart in theory. In practice, they make clients pause to do mental maths, compare options, and loop in a second opinion. That pause kills momentum.

Lead with one recommended option — the one you actually want to do. If you want to offer flexibility, add a single, clearly inferior "lighter" option below it. This makes the main offer look like the obvious choice rather than a gamble. Always show a total number, never "starting from."

5. Tell them exactly what to do next

Your proposal should end with one specific next step, not "let me know if you have questions." That phrasing puts the work back on them.

Try something like:

"If this looks right, reply with a yes and I'll send the contract within the hour. If you want to talk through anything first, here's a link to grab 20 minutes with me: [link]."

One action, low friction, clear timeline. Make it as easy as possible for a busy person to say yes.

---

Writing strong proposals takes real thought — you have to research the client, craft the framing, get the scope right, and then actually write the thing in a way that sounds human. That's a lot of work to repeat for every opportunity.

That's exactly the kind of task you can hand off to your Sidekyk. Send a WhatsApp message with the client's name, what they need, your rough price, and a few notes from your discovery call — and your Sidekyk can draft a polished, client-ready proposal for you to review and send. No back-and-forth emails, no blank-page paralysis. Just a ready draft waiting for your approval. Try it at sidekyk.ai.