Why scope and pricing make or break a proposal
A proposal is really two promises: what you will do, and what it will cost. Everything else, the intro, the case studies, the process diagram, is supporting material. If the scope is fuzzy or the pricing is unclear, no amount of polish saves it, because the client cannot confidently say yes to something they do not fully understand.
Scope and pricing also do a second job that shows up after you win: they protect the relationship. A precise scope is what stands between you and months of unpaid "quick favors," and pricing tied to that scope is what makes additional work a normal, paid conversation. Get this right and the proposal keeps working for you long after it is signed, which is why it is the heart of sending a proposal online.
How to define scope clearly
Clear scope is specific and bounded. It says exactly what will be delivered and, just as importantly, what will not. A complete scope covers:
- The client goal the work serves.
- Specific deliverables, each with a definition of done.
- What is explicitly included.
- What is explicitly excluded or out of scope.
- Assumptions the scope depends on.
- Number of revision rounds.
- How out-of-scope requests are handled and priced.
The exclusions are the part everyone skips and later regrets. Writing "this does not include X" feels awkward in the moment, but it is the single best protection against the "I assumed that was included" conversation. Naming boundaries is not defensive; it is a gift to both sides, because it makes the agreement genuinely mutual. Good scope starts with good intake, which we cover in how to collect client requirements before a project.
How to price the work
Pricing is where nerves show. The instinct is to price by hours, because it feels safe, but hours measure effort, not value, and they cap your upside while making the client watch the clock. The stronger approach is to price the scope and the outcome. The common models:
| Model | Best for | Tradeoff |
|---|---|---|
| Fixed price | Well-defined projects | Needs tight scope up front |
| Retainer | Ongoing work | Needs a clear monthly remit |
| Value-based | High-impact outcomes | Harder to quantify |
| Hourly | Genuinely open-ended work | Caps upside, client watches the clock |
Most agencies do best leading with fixed price or retainers and reserving hourly for truly unpredictable work. Whatever you choose, present the price with confidence and tie it to the scope, so the client sees the value, not just a number.
Tying scope to pricing
Scope and pricing should never sit in separate worlds. The client is really asking one question, "what do I get, and what does it cost?", and the proposal should answer it as one thought. Show the deliverables and the price together, so the value is obvious at a glance.
If you offer options, keep them to a small number of clear tiers, each with its own scope and price, rather than an open menu that forces the client to design their own package. And crucially, state what a change to scope costs. When "add another landing page" has a known price, extra work becomes an easy upsell instead of an awkward negotiation.
Preventing scope creep
Scope creep rarely arrives as one big ask. It comes as a trickle of small "can you also" requests, each too minor to push back on, until you are doing a second project for free. The cause is almost always a scope that never drew the line clearly in the first place.
A precise scope with named exclusions and a stated change process is the cure. When a new request lands, you are not being difficult by flagging it; you are following the agreement you both accepted. That turns scope creep from a source of resentment into a normal, often revenue-generating, conversation. It also keeps delivery honest, which connects to handing off a proposal into a project with the scope intact.
How to scope and price, step by step
Pulling it together, the process is short and repeatable:
- Start from the client goal, then list the deliverables that achieve it.
- Define "done" for each deliverable so there is no ambiguity.
- Name exclusions and assumptions to set clear boundaries.
- Choose a pricing model that matches how defined the work is.
- Tie the price to the scope so the client sees what they get.
- State how scope changes are priced, then keep scope and price on one record.
The final step matters more than it looks. When scope and price live on the same record as the eventual project and invoice, you can always check what was agreed against what is being delivered and billed. When they live in a separate document, that link breaks the moment work starts.
Scope and pricing scattered, or one connected proposal
Scope often lives in a doc, pricing in a spreadsheet, the proposal in another tool, and the signature in a fourth, none of them tied to the work. Arpixa keeps scope, pricing, and approval on the client record, connected to the project and invoice.
Scope docs
Pricing
Proposals
E-sign
ArpixaAll of it, connectedHow Arpixa keeps scope and pricing connected
Arpixa lets you build a proposal with scope, pricing, and approval tied to the client record, so the agreed scope and price do not vanish into a separate document once the deal is done. The client reviews and approves it in their workspace, and the agreement stays visible.
The value shows up in delivery. Because the proposal is connected to the client record, the approved scope can carry into the project and inform invoicing, so what you scoped, what you deliver, and what you bill all line up rather than drifting apart. For formal commitment, e-sign documents handle the contract. Note that Arpixa focuses on scope, pricing, and delivery rather than time tracking or project accounting, so pricing here means presenting and agreeing the price, not logging billable hours.
Scope and price on the same record as the work
Start free in minutes, or log in to your Arpixa workspace. See pricing for plan details.
Arpixa has a real Free plan (not a trial), with Starter at $12/month, Pro at $29/month, and Advanced at $89/month. Some capabilities and limits depend on plan, and annual billing lowers the effective monthly cost. The pricing page is the source of truth for current plan limits.
Frequently asked questions
What should a proposal’s scope include?
A clear scope lists the specific deliverables, what is included, what is explicitly not included, any assumptions, and the number of rounds or revisions. The most important and most skipped part is the exclusions: naming what is out of scope prevents the "I assumed that was included" conversation later. Scope should describe outcomes and boundaries in plain language, not vague promises.
How do you write a scope of work?
Start from the client’s goal, then list the concrete deliverables that achieve it, each described by what it is and what "done" means. Add assumptions, exclusions, and the number of revision rounds. Keep it specific and readable: a scope of work is a shared understanding, not legal cover, so both sides should be able to read it and agree on exactly what will be delivered.
How do you price a proposal?
Price the value and the scope, not just the hours. Common models are fixed price for a defined deliverable, a monthly retainer for ongoing work, and value-based pricing tied to outcomes. Whichever you use, tie the price clearly to the scope so the client sees what they get for it, and state what changes to scope will cost, so additions are a normal conversation rather than a conflict.
What is scope creep and how do you prevent it?
Scope creep is the gradual expansion of work beyond what was agreed, usually through small "can you also" requests that add up. You prevent it by defining scope precisely up front, naming exclusions, and stating how out-of-scope work is handled and priced. When the proposal is clear, extra requests become a simple change conversation instead of unpaid work you feel obligated to absorb.
Should you show pricing in a proposal?
Yes. A proposal without clear pricing forces a separate back-and-forth and slows the decision. Show the price tied to the scope so the client understands what they are paying for. If you offer options, present a small number of clear tiers rather than an open-ended menu. Clarity on price, like clarity on scope, speeds up the yes and sets the relationship up honestly.
Fixed price, retainer, or hourly, which is best?
It depends on the work. Fixed price suits well-defined projects and gives clients certainty. Retainers suit ongoing work and stabilize your revenue. Hourly can fit open-ended work but shifts risk to the client and caps your upside. Many agencies use fixed price or retainers for most work and reserve hourly for genuinely unpredictable scopes. Match the model to how defined the work is.
How does Arpixa handle scope and pricing?
Arpixa lets you build a proposal with scope, pricing, and approval tied to the client record, so the agreed scope and price stay connected to the work rather than living in a separate document. When the client approves, that scope can carry into the project and inform invoicing, so what you scoped, what you deliver, and what you bill line up on the same record.
How much does proposal software cost?
Standalone proposal tools price per user per month, and pairing them with a CRM and project tool adds more. When proposals are part of an agency platform, they fold into one plan. Arpixa has a real Free plan, with Starter at $12/month, Pro at $29/month, and Advanced at $89/month, and annual billing lowers the effective monthly cost.