How to Explain Pricing When Every Project Is Different
By Réson
4 min read
In this article
Pricing custom work rarely fits neatly into three cards. A renovation, research project, brand identity or consulting engagement can change substantially once the requirements are understood. Customers still need enough information to decide whether to inquire.
That does not mean the pricing page has to say nothing.
Customers need enough information to judge whether an inquiry is sensible. They want to know what drives the cost, what is included, what could change and what happens before they commit.
A useful pricing explanation answers those questions without pretending to be a quote.
Explain the unit of work
Start with what the customer is actually buying.
“Design services” is broad. “A visual identity project with discovery, two proposed directions and final production files” is more concrete.
For a hypothetical design studio, the first paragraph might read:
We quote visual identity projects after a short scope review. The proposal defines the deliverables, number of review rounds, timeline and usage requirements before work begins.
This explains the process without inventing a minimum price or suggesting every project receives the same deliverables.
If you charge by the hour, day, project or retainer, say so. Explain how that unit relates to the outcome. A retainer should not sound like unlimited work unless that is genuinely the agreement.
Explain the factors behind your pricing
Choose a short list of meaningful cost drivers. Depending on the business, they might include:
- Number and complexity of deliverables.
- Research or discovery needed before production.
- Condition and completeness of the customer's existing materials.
- Number of stakeholders or review rounds.
- Production, travel, installation or third-party costs.
- Timeline and availability.
- Licensing or usage requirements.
Explain the effect of each factor in ordinary language.
“Complexity affects pricing” provides little guidance. “Adapting an approved design into several sizes takes less discovery than developing a new visual direction” helps a customer understand the work.
Avoid framing normal customer questions as a nuisance. The purpose is to clarify scope, not to discourage collaboration.
Use ranges only when you can support them
A range can be helpful if it reflects work you genuinely offer under identifiable conditions. It becomes misleading when the low end describes a rare or unusably narrow version of the service.
If you publish a range, define what it covers and how current it is. Be clear about taxes, third-party expenses and other exclusions where applicable.
When you cannot support a range, explain the quoting process instead:
Send the project goal, expected deliverables and target date. We will review the fit and tell you whether a discovery call is needed before preparing a proposal.
That is more useful than a fabricated “starting at” figure.
Show scope comparisons, not invented customer stories
An illustrative comparison can explain price variation without presenting hypothetical work as a real case study.
For example:
| Illustrative scope | Why the work differs |
|---|---|
| Refresh an existing brochure using approved copy and images | Most source material is ready |
| Develop a new brochure with interviews and original copy | Discovery and writing are added |
| Create the brochure plus several translated editions | Adaptation and language review are added |
Label the examples as illustrative. Do not attach invented prices or imply that they are offers unless the business has approved them.
The comparison should help customers describe their needs more accurately.
Make the next step easy
A pricing explanation should end with a short, practical inquiry checklist.
Ask for the information that genuinely changes the estimate. For many project businesses, that means the desired outcome, deliverables, deadline, existing materials and any known constraints.
If budget information helps you propose an appropriate scope, explain why you ask. Give customers room to say they do not know yet.
Also explain what follows the inquiry. Will they receive an initial response, a discovery call invitation or a paid assessment proposal? Do not promise a turnaround time the team cannot consistently meet.
Keep AI-assisted pricing copy tied to approved facts
Pricing language deserves a careful review. A draft can accidentally turn “typically” into “always,” omit an exclusion or create an attractive package your business never agreed to deliver.
In Réson, keep current approved pricing information separate from exploratory notes. Use the draft as a writing aid, then verify every amount, condition and deliverable before approval. See the Réson help guide for managing the information behind content.
The strongest custom-pricing page does not make every project look simple. It makes the decision to inquire feel informed. Explain how the work is scoped, identify the variables and show customers how to get a proposal they can evaluate.
Explain how changes are handled after approval
Customers may understand the initial quote yet remain unsure about what happens if the project changes. Address that uncertainty before work begins.
Describe the process without turning the pricing page into a contract. For example, a hypothetical video studio could explain that additional filming days or new deliverables require a revised scope and approval before the extra work starts. The actual proposal should contain the applicable terms.
Distinguish a correction from a new request. Fixing a production error is different from changing an approved creative direction. Your business should define that boundary clearly rather than leaving the customer to discover it during an invoice discussion.
Include a simple question in your internal review: could a reasonable reader mistake this package for open-ended support? If the answer is yes, clarify the duration, included review rounds or support arrangement, as applicable.
This explanation protects the usefulness of the original quote. Customers can compare proposals more intelligently when they understand both the initial scope and the process for changing it.
Related reading
Frequently asked questions
Must a custom-service business publish a price range?
Not always. If a range would mislead, explain the cost drivers, quoting process and information needed to assess the project.
What makes a starting price useful?
It should describe an actual available scope, with relevant conditions and exclusions. Avoid a low figure that few customers could realistically obtain.
Can Réson decide what my business should charge?
Use Réson to help explain approved pricing information. The business remains responsible for its prices, scope, terms and final proposal.
About the author
Réson
Réson is an AI marketing workspace for small businesses. It learns your business from your website, drafts posts, campaigns and articles, and waits for your approval before anything goes out.
