The proposal-readiness checklist

  • State the business outcome in the client’s language.
  • Distinguish the requested tactic from the underlying problem.
  • Identify systems, assets and deliverables in scope.
  • Identify exclusions and specialist requirements.
  • Confirm who supplies inputs and who approves work.
  • Review timeline dependencies and capacity.
  • Clarify the commercial model and expectations.
  • Record the next decision and participants.
  • Decide whether discovery is required before an estimate.
  • Preserve the original evidence and unresolved assumptions.

A checklist failure should lead to clarification or rejection, not an improvised promise.

When to offer discovery

Offer discovery when material unknowns prevent a reliable scope. Explain what it produces, which decisions it resolves and what it does not guarantee.

Do not sell discovery as a vague prerequisite. A buyer should understand why the missing information matters and how the deliverable stands on its own.

A hypothetical application

A store asks for a redesign and better conversions. The agency learns that product photography, copy and payment reliability are unresolved. The project is not ready for a visual-design-only quote.

The next step is an agreed scope review that separates design from content and technical dependencies. This protects both the proposal and delivery.

Close the loop with delivery

Compare initial qualification with actual project friction. Repeated approval delays may indicate missing stakeholder checks. Repeated scope expansion may indicate unclear exclusions.

Update the checklist based on real delivery evidence. Do not add fields that never change a decision.