Questions to Ask a Client Before Quoting

The best questions to ask a client before quoting cover seven areas: scope, expected results, timing, access, client decisions, revisions, and delivery risks. The answers tell you what work belongs in the offer, what depends on the client, and which unknowns could expand the job after the price is sent.

Table of contents

• How to use this checklist
• Questions about scope
• Questions about results
• Questions about timing
• Questions about access and inputs
• Questions about client decisions
• Questions about revisions
• Questions about delivery risks
• How one missing question changes the price
• Turn the answers into a clear quote
• Check your offer before sending it

How to use this checklist

You do not need to ask every question in a long call. Start with the questions that can change the size, sequence, or ownership of the work. Send the rest in writing when the client needs time to collect details.

Record the answer in the words the client uses. If the answer is uncertain, write the uncertainty into your scope. A useful note could say, 'The client expects five page types, subject to confirmation after the content audit.' That is more precise than quietly assuming five pages and discovering twelve later.

The aim is to describe the work you can price now. If a material part remains unknown, use a paid discovery stage, a stated assumption, or a separate optional item. Do not hide the unknown inside a fixed scope.

Questions about scope

Scope questions identify the units of work. For a digital service, those units may be pages, screens, templates, integrations, campaigns, content items, user roles, or data sets.

• What exactly do you want delivered? The answer determines the deliverable list and prevents broad labels such as 'website refresh' from covering several different jobs.
• How many pages, screens, templates, or content items are included? The quantity changes production time, review effort, testing, and the final scope.
• Which existing materials should be kept, changed, or replaced? Reusing approved material requires different work from rewriting, redesigning, or rebuilding it.
• Which features or tasks are required for the first release? The answer separates essential work from ideas that can become optional items or a later phase.
• Which devices, browsers, languages, or formats must the work support? Each required environment adds preparation, adaptation, and testing.
• Are any related tasks handled by another supplier or your internal team? The division of work changes handoffs, dependencies, and the responsibility included in your quote.

Ask the client to name concrete outputs. 'Improve our online presence' could mean a new landing page, revised copy, analytics setup, search work, or a monthly content service. Each version has a different boundary.

Questions about results

A result explains why the client wants the work. It also helps you judge whether the requested output is enough for that purpose.

• What should be different after this work is delivered? The answer shows whether the client expects a file, a working implementation, a launch, or support after launch.
• Who will use the result, and what should they be able to do? The audience and intended action affect structure, content depth, accessibility, and testing.
• How will you decide whether the project has worked? The success measure may add tracking, reporting, research, or a comparison with the current state.
• Is there a current version, baseline, or example we can review? Existing evidence can reduce discovery work or reveal problems that need to enter the scope.
• Which result matters most if time or budget forces a tradeoff? The priority helps you protect the core outcome while moving secondary work into options.

Questions about timing

A deadline affects more than the final delivery date. It determines when inputs, feedback, approvals, and access must arrive.

• Is there a fixed launch date or a preferred completion date? A fixed date may require a tighter sequence, reserved capacity, or a smaller first release.
• What event creates that deadline? The reason shows whether partial delivery is useful and which parts must be ready first.
• When can the client provide all required materials and access? The starting condition determines whether the proposed schedule is realistic.
• How quickly can feedback and approvals be returned? Slow review cycles extend the calendar and may interrupt planned production time.
• Are there dates when key people will be unavailable? Known absences can change review windows, workshop dates, and launch support.
• Does any other supplier need to finish work before you can begin? External dependencies may require a later start, a staged quote, or an explicit schedule assumption.

Write dates beside client actions as well as your own tasks. A deadline built only around supplier work leaves half of the schedule invisible.

Questions about access and inputs

Digital work often depends on accounts, files, brand assets, data, and technical information held by the client or another supplier.

• Which files, brand guidelines, content, and source materials already exist? Missing or unusable inputs may add research, recreation, conversion, or writing work.
• Who controls the accounts and systems needed for delivery? The owner affects how quickly access can be granted and whether another party must join the project.
• Can you provide working access before the project starts? Delayed or restricted access can block an audit, implementation, testing, or launch.
• What format and condition are the current files or data in? Clean, structured inputs require less preparation than incomplete exports, scans, or mixed versions.
• Will real content and data be available for testing? Placeholder material can hide layout, import, or workflow problems that appear with real inputs.

Questions about client decisions

Projects expand when decision ownership is unclear. Several people may comment, while only one person can approve.

• Who is the final decision maker for scope, content, and design? The answer defines whose approval completes each review stage.
• Who should attend discovery and review meetings? Missing stakeholders can cause repeated explanations and late changes.
• Will feedback be collected into one agreed response? Consolidated feedback reduces conflicting instructions and duplicate revision work.
• Which decisions have already been made? Confirmed choices reduce exploration, while open choices may add workshops, concepts, or comparison work.
• What needs approval from management, compliance, IT, or another team? Extra approval paths add lead time and may create specific documentation or testing needs.

Questions about revisions

Revision questions define how feedback becomes work. They also separate corrections from new requests.

• How many review rounds do you expect? The number of rounds changes the time reserved for discussion, updates, checking, and presentation.
• What will be reviewed at each stage? Reviewing structure before visual detail prevents approved foundations from reopening during final production.
• Who will combine comments before they are sent? One agreed feedback set avoids several people submitting overlapping or contradictory requests.
• What counts as a correction, and what counts as a new request? The distinction protects the quoted scope when the client adds pages, features, audiences, or deliverables.
• What happens if an approved direction is reopened? The answer lets you state how additional work will be assessed before it begins.

Describe revision limits by round and subject. 'Two rounds of copy revisions on the six listed pages' is clearer than 'revisions included.'

Questions about delivery risks

Risk questions expose conditions that can increase effort or stop delivery. They belong in the conversation before the price becomes the client’s reference point.

• What is still unknown about the project? Each material unknown may need an assumption, a discovery task, or an optional allowance.
• Has anyone tried this work before, and what caused difficulty? Previous problems can reveal hidden stakeholders, technical limits, poor inputs, or unresolved expectations.
• Are there systems, policies, or technical limits we must work within? Constraints may change the method, testing effort, or feasible deliverable.
• What would make the project late or incomplete from your side? The answer identifies dependencies that need dates, owners, and schedule consequences.
• Which part of the brief is most likely to change? A volatile area may be better priced after discovery or isolated as a separate option.
• What needs to happen after handover? Training, documentation, launch support, maintenance, or internal rollout can add distinct deliverables.

Turn every serious risk into a visible line in the offer. Use a scope item, client responsibility, assumption, exclusion, optional item, or starting condition.

How one missing question changes the price

Consider a hypothetical website project for a consultancy. The initial request is 'Design and build a new five-page website.' Based on five supplied pages, one language, existing brand assets, and a simple contact form, the supplier prepares a hypothetical price of 3,200 EUR.

One missing question is: Who is responsible for the content?

The client expected the supplier to interview three team members, define the message, write five pages, source images, and enter the approved copy. That answer adds discovery, interview preparation, three calls, copy structure, drafting, review, image research, and content entry. It also creates a client dependency because interview availability and copy approval now affect the schedule.

With that work included, the hypothetical price becomes 5,100 EUR. The difference is 1,900 EUR, even though the website still has five pages. The page count stayed fixed, while the responsibility inside each page changed.

The supplier can now offer a clear choice. The client supplies final approved content before design begins, keeping the original scope. Or the supplier owns the listed content work for the revised price and schedule. Both versions are understandable because the missing responsibility is visible.

Turn the answers into a clear quote

After the conversation, sort your notes into six parts:

1. Deliverables: Name every page, screen, file, setup task, workshop, and handover item.
2. Client responsibilities: List materials, access, decisions, feedback, and approvals with due dates.
3. Assumptions: State the facts used to price work that you have not yet verified.
4. Exclusions: Name adjacent work that could otherwise look included.
5. Revision limits: Define the number, subject, and method of review rounds.
6. Options: Separate useful additions from the core scope.

Read the list against the client’s words. If a requested outcome has no matching deliverable, the scope may be incomplete. If a deliverable has no clear owner or acceptance point, the quote may still contain an open edge.

Check your offer before sending it

Use the free OfferForBusiness offer preview to check your own offer for missing scope, unclear client responsibilities, revision gaps, and delivery risks before you send it.