I stopped building unpaid client demos before checking these 6 signals

Saksham Sarda — Sun, 14 Jun 2026 16:26:06 +0000

The expensive mistake in freelance web design often happens before the
proposal.

A lead asks, "Can you show me something?" You want to be helpful, so you spend
unpaid hours making a homepage concept. Only later do you learn that the budget
is vague, the person cannot approve the project, or the company is just
collecting ideas.

Demos are not always a bad sales tool. The problem is increasing effort before
the opportunity becomes more concrete.

I built a small pre-proposal scorecard to make that decision explicit. It
checks six observable signals and recommends one bounded next move.

The six signals

1. Conversation stage

A first message is not the same as completed discovery.

First message or cold inquiry: 0
Intro call booked: 2
Discovery complete: 4
Asked for scope and price: 5

2. Credible budget

"We are flexible" is not a budget.

Unknown or avoided: 0
Under $1,000: 1
$1,000-$3,000: 3
$3,000-$10,000: 4
$10,000+: 5

The numbers are not a statement about what every freelancer should charge.
They measure whether the likely project value can justify custom pre-sale
effort.

3. Decision access

If the person reviewing the demo cannot approve the project, the demo can
become an internal mood board instead of a buying decision.

No decision access: 0
Not clear yet: 1
Speaking with a decision-maker: 4

4. Business-problem clarity

"We need a better website" is a preference. "Qualified buyers cannot
understand which service fits them" is a problem you can design around.

Vague improvement request: 0
General goal named: 2
Measurable business problem is clear: 4

5. Timeline

Urgency is not pressure. It is evidence that the buyer has an actual decision
to make.

Just exploring: 0
This quarter: 1
Within a month: 3
Within two weeks: 4

6. Asset readiness

A concept made without copy, brand assets, or useful imagery often creates
more questions than answers.

Nothing ready: 0
Some assets exist: 1
Core copy, logo, and imagery are ready: 3

The hard caps matter more than the total

A pure point total can still reward a structurally weak opportunity, so I use
three caps:

No decision-maker access caps the score at 14.
No credible budget caps the score at 14.
A cold first message plus a vague problem caps the score at 7.

That means strong assets and a fast timeline cannot compensate for missing
authority, budget, or problem clarity.

Four bounded responses

22-25: Build one focused direction

Choose one business problem and one primary page flow. Show one direction, not
a menu of unpaid concepts. Pair it with a fixed next step, scope boundary,
timeline, and price.

15-21: Run discovery first

Confirm the decision-maker, budget range, and the single business outcome the
project needs to improve. More design cannot repair missing commercial facts.

8-14: Send a ballpark

Send a concise range with assumptions and exclusions. Ask the prospect to
confirm budget fit before you invest in custom design.

0-7: Pause

Ask for the business goal, budget range, decision-maker, and timeline. Use one
relevant portfolio example instead of creating new unpaid work.

Try the scorecard

I published the scorecard as a free browser tool:

It has no account, analytics, API key, or backend. Form values stay in the
current browser tab. The code is MIT licensed.

The result is a decision aid, not a prediction that a prospect will reply,
approve a proposal, or buy.

Disclosure: I built DemoSprint Lite. There is also an optional paid production
bundle for creating demos, proposal pages, pricing, and handoff materials, but
the qualifier is independently useful and free.

If you try it on a real opportunity, I would be interested in one thing: which
of the six signals was hardest to answer?

DEV Community: Saksham Sarda