Short answer
To quote a website with an unclear brief, start with one journey a visitor needs to complete. Separate the pages you can describe from features that need discovery. Offer a bounded estimate for the known work and a separate next step for the unknowns, with a person who can approve each decision.
What do you need to quote a website with confidence?
Freelancer u/MtSnowden asked Reddit for help estimating a website for a clinic. An informational site had become a conversation about online appointments and doctors logging in. Those are different projects even if the home page looks exactly the same. The useful question is what a visitor, a receptionist and a doctor must each be able to do once the site is live.
Use the same test outside healthcare. For a workshop site, a calendar showing class times is one job. Choosing a seat, paying, receiving a confirmation and moving a booking is another. Ask the client to walk you through their last real booking and identify the part the website should take over.
What can you send when the client needs a number today?
Give an estimate with a recognizable boundary. For example: “Option A covers a five-page site using the copy you supply and a link to your existing scheduler. Option B starts with a short booking-workflow review. After that review I’ll estimate the account and scheduling work separately.” Describe what the client receives from the review and when they can decide whether to go further.
Be explicit about what would trigger a revision. A change from a hosted scheduler link to taking payments on the site changes the estimate. Correcting a typo in the supplied opening times probably does not. A client can make a budget choice before either side pretends to know the unknown.
| Client expectation | Estimate boundary |
|---|---|
| Open the current scheduler | Connect and test a link to an existing provider. |
| Choose a service and pay online | Confirm who handles payment, confirmation and changes. |
| Staff log in to manage bookings | Scope roles, account access and operations during discovery. |
Which questions change the price?
Ask where the booking ends, where the data goes and who looks after it. A link to the studio’s existing booking provider is a different deliverable from a new reservation system. Find out whether an account already exists and ask to see the relevant workflow before estimating an integration. A screenshot can clarify the job without asking for someone’s password.
Put content in the same conversation. Five pages with approved text are different from five pages that need interviews, writing and review. Record the name of the person supplying each input. A page count helps after the team agrees what a page must accomplish.
How do you keep discovery from becoming the whole project?
Time-box the investigation around a decision. For the workshop example, the output could be a one-page map of choosing a session, paying and receiving confirmation. Name the system responsible for each step and ask the client to approve that map. You can now estimate the parts you would actually build and test.
End the discovery task with one of three decisions: use the existing provider, commission the new feature or defer it. Record who made the choice. A valuable discovery session can end with no custom build at all if the client’s existing service already handles the journey.
How do you turn the estimate into a usable Noddis project?
Capture the agreed outcome and open assumptions in Project Notes. Create one parent for the confirmed site build and children for its actual deliverables. Create a separate discovery task for the booking workflow, with a named contact and a question that can be answered. Leave an implementation date open until the answer changes the estimate.
If you import the proposal, review the generated hierarchy and scope alongside the original text. A sentence like “online booking may be added later” is a condition to preserve. Move it into notes or remove it from committed tasks until the client actually accepts that feature.
For the next step, see Project Scope Baseline Template for Client Work and From brain dump to project plan: how to turn messy ideas into tasks.
Sources and field notes
A freelancer’s first-person account describes a clinic website estimate expanding into booking and account access. The workshop example here illustrates the same decision in another industry. Read the original source.
Freelancers discuss which questions to ask before estimating a client project.
Common questions
Can I give a fixed price for part of the site?
Yes, once both sides agree on the deliverables, inputs and acceptance checks for that part. Price any remaining discovery separately and explain when the rest can be estimated. Write down which features would change the price, who owns the copy and when the client can accept that part of the estimate.
Should an optional feature appear on the project timeline?
Give the decision a place on the plan if someone must make it. Schedule the implementation after the client approves the feature and you have enough information to estimate the work. A decision with an owner and a date can move the project forward while leaving the cost and timing of unapproved implementation open.
What if the client cannot answer the discovery questions?
Ask to observe the current process or speak with the person who runs it. Estimate a bounded discovery deliverable first. Set a date for reviewing its findings and deciding what to build. Ask the person who owns the current process to walk through one recent case. Use that example to identify which feature you would actually have to build.
Katleen is the founder of Noddis. She runs client projects through her app studio, 693 Labs, and builds Noddis around the problems that work creates.
Last reviewed . Feature details reflect Noddis at the time of review.