Start with the work, not the competitor
Competitor research helps you understand the range customers may expect, but it does not tell you whether a job is simple for you, messy for your team, or unusually valuable to the customer. Treat competitor pricing as background, not the formula.
Five inputs to write down
Before you name a price, write down the inputs that explain the job. The goal is not perfect precision. The goal is to make the invisible parts of service delivery visible enough to review later.
- Delivery time: estimate meetings, preparation, delivery, revision, admin, and follow-up.
- Direct costs: include materials, subcontractors, travel, tools, or one-off expenses tied to the job.
- Overhead: remember the shared cost of running the business, even when the job looks simple.
- Practical cushion: leave room for normal changes, clarification, and small surprises.
- Customer value: consider what problem the customer is trying to solve and how visible the result will be.
Choose the package shape
Not every service should be sold as an hourly rate. A small job may fit a fixed package. Ongoing work may fit a monthly arrangement. Custom work may need a scope, a revision limit, and a clear approval step before extra work begins.
| Service pattern | Safer pricing shape |
|---|---|
| Repeatable, short work | Fixed package with a clear deliverable |
| Ongoing client support | Monthly scope with review points |
| Unclear custom work | Discovery or first phase before a larger quote |
| Work with many revisions | Package plus defined revision rounds |
Review the price after delivery
The first price is an informed draft. After delivery, compare the estimate with what actually happened. Did meetings multiply? Did revisions take longer than expected? Did the customer need more education before approving the work?
- Keep the estimate and final effort side by side.
- Note where the scope was clear and where it drifted.
- Track customer questions that should become clearer proposal language.
- Adjust the next package instead of blaming one awkward project.
A simple example
Maya offers a small brand refresh. Instead of copying another designer’s rate, she estimates discovery, two design directions, one revision round, file preparation, and handoff. She also notes that extra revisions will need a separate approval.
After delivery, she learns that file preparation was easy, but the revision round took twice as long because the customer shared feedback from four people. Her next package keeps the same outcome, but sets a clearer review process.
What this guide is not saying
This framework does not promise the right price. It helps you explain what went into the number, avoid copying competitors blindly, and improve the next quote with better evidence from your own work.
If a price affects contracts, staffing, or formal obligations, bring in the right reviewer for your situation. For day-to-day service packaging, the useful habit is simple: estimate, deliver, review, and refine.