Project scoping note

Project scoping note quote template: scope and price a discovery engagement clearly

This Project scoping note quote template is a Markdown-ready proposal for consultants, project managers, product teams, and agencies selling an upfront scoping engagement. It sets out the discovery work required before delivery begins: stakeholder interviews, requirements review, workshop facilitation, assumptions, dependencies, risks, and a recommended project approach.

Use this template to charge for the time and expertise behind a scoping note rather than treating planning as unpaid pre-sales work. It helps you quote fixed-fee discovery packages, hourly advisory work, or workshop-based scoping services, with clear deliverables such as a scope statement, phased roadmap, effort estimate, budget range, and decision log.

Why use this project scoping note quote template

• Protect paid discovery work. Separate the scoping phase from implementation, build, or delivery so the client understands what they are buying before committing to the larger project.
• Set boundaries early. Define included research, interviews, workshops, revisions, and documentation—and identify what falls outside the engagement.
• Make assumptions visible. Record client responsibilities, access requirements, available documentation, approval timelines, and third-party dependencies that affect the scope.
• Create a usable handoff. Price a scoping note that gives sponsors and delivery teams a practical basis for prioritization, budgeting, vendor selection, or project kickoff.
• Reduce scope disputes. Tie the fee to specific outputs and acceptance criteria instead of relying on vague wording such as “strategy support” or “initial analysis.”

What the template includes

• Client and project details: The client name, project title, key contacts, quote date, validity period, and expected scoping start date.
• Project context: A concise description of the business problem, current situation, intended outcomes, and decisions the scoping exercise must support.
• Objectives and success criteria: The questions to answer during discovery, measurable priorities where available, and the definition of a completed scoping note.
• Scope of services: The activities you will perform, such as document review, stakeholder interviews, requirements gathering, process mapping, technical discovery, or a facilitated alignment workshop.
• Deliverables: A clearly itemized list that may include a project scoping note, in-scope and out-of-scope items, proposed workstreams, milestone plan, budget estimate, RAID log, and next-step recommendations.
• Timeline and client inputs: Planned sessions, draft and final delivery dates, required client attendees, system access, source materials, and review windows.
• Fees and payment terms: Fixed package fees, day rates, hourly rates, workshop charges, expenses, deposit terms, and invoicing milestones in US dollars.
• Assumptions, exclusions, and change control: Items not covered by the quote, such as solution implementation, detailed technical design, legal review, procurement support, or additional interview rounds.

How much to charge for a project scoping note

Pricing depends on project complexity, stakeholder availability, the maturity of existing requirements, and whether the work includes technical or operational analysis. These are North American market benchmarks to adjust for your seniority, sector, and the level of decision-ready detail the client needs.

• Hourly advisory rate: $150 to $300 per hour for independent consultants conducting interviews, analysis, and documentation.
• Daily scoping rate: $1,200 to $2,500 per day for senior project, product, operations, or technology consultants.
• Single discovery workshop: $1,500 to $4,000 for preparation, a half-day or full-day facilitated session, and a concise workshop summary.
• Light scoping package: $3,500 to $7,500 for document review, 3 to 5 stakeholder interviews, and a short scoping note with recommendations.
• Complex multi-stakeholder scoping engagement: $8,000 to $20,000 or more for several workshops, process mapping, technical dependencies, phased estimates, and executive-ready documentation.

For fixed-fee work, state the number of interviews, workshops, and revision rounds included. Charge separately for travel, specialized research, additional stakeholder groups, or requests to turn the scoping note into a full statement of work.

Who this template is for

• Independent project managers and PMO consultants defining a new initiative before mobilization.
• Product consultants scoping discovery for a new digital product, platform, feature set, or service redesign.
• Software agencies assessing requirements before quoting implementation, integration, migration, or custom development.
• Operations and process improvement consultants mapping workflows, constraints, roles, and delivery risks.
• Strategy consultants preparing a decision brief, phased roadmap, or investment case for leadership teams.
• Internal transformation teams that need a formal quote for cross-functional discovery or planning support.

Frequently asked questions

Should a project scoping note be free?

Not when it requires structured analysis, stakeholder time, workshops, or a written recommendation. A brief introductory call can be free, but a scoping engagement should be quoted as a defined professional service with its own deliverables.

What is the difference between a scoping note and a statement of work?

A scoping note clarifies the problem, proposed boundaries, assumptions, risks, and likely approach. A statement of work is typically the contractual document for the delivery phase, with final deliverables, responsibilities, timeline, and commercial terms.

How many stakeholder interviews should be included in the quote?

For a focused project, include 3 to 5 interviews. For a cross-functional or enterprise initiative, specify a larger number or price interview blocks separately, since analysis and scheduling time increase quickly.

Can I provide an implementation estimate in the scoping note?

Yes, but label it as a budgetary estimate based on documented assumptions. Make clear that the final implementation fee and schedule may change after requirements, technical constraints, and ownership decisions are validated.