Weekend Power Deposit: Build Your Pricing Message
This weekend, put the pieces together into one reusable pricing message.
Use this structure:
Thanks for asking.
Pricing depends on [main factors].
Most [service/project/visit] starts at or ranges from [price/range], depending on scope.
That includes [brief value or inclusions].
To give you the right next step, please send [details needed].
Here is a sample:
Thanks for asking. Pricing depends on the type of help needed, location, and timing. Most one-time errand visits start at $____, with recurring support quoted based on frequency and scope. The goal is to give you dependable local help so everyday tasks are handled without adding more stress to your week. To give you the right next step, send your location, what you need help with, and whether this is one-time or ongoing.
Another:
Thanks for asking. Website cleanup pricing depends on the number of pages, the amount of rewriting needed, and whether design changes are included. Basic cleanup sessions start at $____, while larger projects are quoted after review. The goal is to make your website easier for customers to understand, trust, and act on. Send me your website link and what feels unclear, and I’ll let you know what makes sense.
Another:
Thanks for asking. Personal chef pricing depends on household size, menu needs, shopping, cooking time, service frequency, and any special diet requirements. Once I understand the basics, I can explain what type of service would fit best and how pricing would work. The goal is to reduce the stress of meal planning, shopping, cooking, and cleanup. Send a little about your household and what kind of support you are looking for, and we can start there.
That is a pricing message.
Clear.
Calm.
Useful.
Not a panic note.
Not a mystery.
Not a defensive essay.
Save this message somewhere you can find it.
You will use it.
And when you do, you will be glad you are not composing your entire business model from scratch in a text box while someone waits.
Weekend Power Deposit:
Create and save one reusable pricing message for a common pricing question.
Prompt:
Can I explain pricing clearly without apologizing, rambling, or hiding the next step?

