How to write a strong proposal when the job post is basically empty

Vague job posts are everywhere: “need a website,” “looking for a developer,” “must be fast and professional.” Your proposal still has a clear job: prove you can think under uncertainty, show relevant experience without bloating the message, and make it painless for the client to reply with the missing details. This guide walks through a structure that works on Upwork-style posts, short buyer requests, and one-line DMs. Then it covers mistakes that get you ignored, and how to handle pricing when you genuinely do not know scope yet.

Why empty posts happen (and what clients are really testing)

Clients often post quickly because they are busy, because they are shopping for price, or because they do not know how to specify technical work. Some are testing who will ask good questions versus who will paste a generic pitch. A strong response signals: I have done this before, I know what usually goes wrong, and I will not waste your time.

Your goal is not to pretend you understood more than you did. It is to show judgment (a sensible default plan), clarity (specific questions), and momentum (a conditional next step once they answer).

A structure that works

Use the same skeleton every time so you write faster; swap in details from their post and from your niche.

1) Restate what you can infer in one short paragraph

Open by mirroring their outcome in plain language, then state one or two assumptions you are making. That proves you read the post and gives them an easy correction hook.

Example pattern:

I understand you want [outcome they hinted at]. I am assuming [constraint or context] (e.g. timeline, platform, who maintains it after launch). If any of that is off, tell me and I will adjust.

If the post is really empty, it is fine to say you are inferring from the title only. Honesty reads as confidence, not weakness.

2) Offer a sensible default approach

Even when details are missing, propose a reasonable path in 3-5 bullets or a short paragraph. This is where you demonstrate experience: what you would do first, what you would validate early, and what “done” usually includes in similar work.

You are not committing to a fixed scope yet; you are showing how you think. For example, for a vague “website” post you might outline: clarify goals and audience → agree on pages and content → design or theme direction → build → review → handoff and training. Adjust to your stack and service.

3) Ask 3-6 highly specific questions

Avoid lazy questions clients see in every pitch (“What is your budget?” with no context). Prefer questions that unlock scope and reduce rework:

• What does “done” look like on your side (who signs off, and on what artifact)?
• What do you already have (brand, copy, hosting, domain, design files, API access)?
• What is the hard deadline versus “nice to have”? Is anything immovable?
• Who are the end users or visitors, and what should they do on the site or app?
• Are there examples you like (or hate) for look, tone, or functionality?
• What does success look like 30-90 days after launch?

Group questions so they are easy to answer in one message (numbered list is fine).

4) Give a conditional next step

Tie your offer to their answers so the conversation moves forward:

If you confirm [A / B / C], I can [concrete milestone] in [realistic timeframe], then we can lock scope and schedule.

If you cannot quote a price yet, say that clearly: you will provide a fixed quote or range after they answer the questions, not after a dozen back-and-forth messages with no structure.

Pricing when you do not know scope yet

You have three honest options; pick one and state it plainly:

1. Ballpark range + conditions: e.g. “Similar projects recently landed between X and Y depending on integrations and content readiness.” Only use if you have real comps.
2. Paid discovery / small paid milestone: a short paid step to clarify requirements (common in consulting-heavy work).
3. Free outline after answers: you will reply with a scoped proposal once they answer your questions.

What fails is a giant table of rates with no tie to their outcome, or a demand for a call before you show any thinking. Many clients will skip you for that.

What to avoid

• A wall of questions with no point of view: you must still show how you would approach the work.
• Demanding a call before you demonstrate understanding: a short written plan builds trust first; then a call can be the next step.
• Pretending you understood more than you did: it creates mismatches and bad reviews later.
• Copy-paste intros: even strong structure should include at least one sentence that could only apply to this post or this client type.

Before and after (shape, not a literal template)

Weak: “I am interested in your project. I have many years of experience. Please share more details.”

Stronger: Restate their goal → 3-step approach → 5 targeted questions → conditional milestone. Same length as a lazy pitch, but packed with signal.

Quick FAQ

Should I still send if the budget says $5? Only if you want that client. Otherwise, politely pass or propose a smaller slice of work that fits reality.

How long should the proposal be? Enough to show thinking; rarely more than one screen on desktop. Dense beats rambling.

They did not mention the tech stack. State what you work in by default, and ask if they have constraints (hosting, legacy system, in-house team).

When you are ready to send, it helps to have a generator fill in the repetitive scaffolding so you can focus on the questions and proof points that actually sell you.

Related reading: why clients ignore your proposals · freelance proposal examples · the proposal checklist