Hourly pricing puts the focus on your rate. Package pricing puts it on the outcome. That is a different conversation to be having. Prosperus is built around packages as the default format. You are not retrofitting them into a document designed for day rates. They are already the structure.
Hourly billing asks clients to trust the clock. Packages ask them to choose an outcome. That is the whole argument.
The switch from hourly to packages is not about charging more. It is about changing what the client is evaluating. Hourly pricing makes your rate the subject of the conversation. Package pricing makes the deliverable the subject. Prosperus makes it easy to structure two or three tiers, define exactly what each covers, and present them side by side. The client picks the one that fits. You stop defending a number and start presenting options.
FAQs
Yes. Create packages that describe a scope range and build a contingency buffer into the price. Packages do not require identical deliverables. They require defined scope. The two are different things.
Start with what you most commonly deliver and price it as your mid-tier. Define a stripped-down version as the lower tier and an expanded version as the upper tier. Most clients choose the middle. Anchor your pricing accordingly.
Some do, initially. The most common objection is about scope fit. Frame your response around the outcome, not the hours. Prosperus makes the package structure clear enough that most clients engage with it constructively.
Yes. Include a note in the proposal about additional work billed separately, or use the terms section to cover overflow scope. Prosperus does not prevent hybrid approaches.
Nothing needs to change immediately. Start with new proposals. Once you have a few packages working, you can introduce them to existing clients at renewal or scope expansion.