
Sign up to save your podcasts
Or


Why you should be offering guarantees.
Ditching Hourly 026: Why You Should Be Offering Guarantees
Hello! and Welcome to Ditching Hourly. I'm Jonathan Stark.
Today, I'm going to talk about offering guarantees.
One of the tactics I advocate for increasing your fees is to offer some sort of guarantee.
This typically horrifies developers.
They immediately have visions of an unreasonable client demanding a 100% refund after six months of work.
Yikes, right?
Still, I think you should consider offering guarantees.
And here's the thing... you probably already guarantee your work!
Ask yourself this:
If you answered YES to any of these, then you ALREADY guarantee your work.
So...
Why not make your guarantee explicit instead of implicit?
How and when to offer guarantees for the kinds of work that software developers typically do is a touchy subject.
Over the years, I have offered different sorts of guarantees for different sorts of products and services.
The type that I choose in a given situation depends on a variety of factors like:
For example:
For fairly fixed scope dev work (e.g., a productized service) that I can finish quickly, I’d offer a 100% money back guarantee on my sales page.
(I’d also price the service accordingly, but that’s another story.)
So, for something like a half day of SQL performance tuning, I’d offer a 100% money back guarantee if the client was unhappy with the outcome.
I see this type of service as analogous to bringing my car to a mechanic to have it tuned up... if the car is still running rough when I leave, I’d expect them to either redo the work or refund my money.
Here's the key point about guarantees:
Explicitily stating up front how you will “make things right” if things go wrong will differentiate you from the vast majority of your competitors.
And remember: if you can’t differentiate yourself from your competitors, you’ll probably end up competing on price.
That's it for today. I'm JS and this is Ditching Hourly. Thanks for listening.
The next time someone asks you for your hourly rate, this is what you should say: "I don't have one." To learn what to say next, visit http://valuepricingbootcamp.com to signup for my free email course. Again, that url is: http://valuepricingbootcamp.com
----
Do you have questions about how to improve your business?
Things like:
Book a one-on-one coaching call with me and get answers to these questions and others in the time it takes to get ready for work in the morning.
Best of all, you're covered by my 100% satisfaction guarantee. If at the end of the call, you don't feel like it was worth it, just say the word, and I'll refund your purchase in full.
To book your one-on-one coaching call, go to:
https://jonathanstark.com/call
I hope to see you there!
By Jonathan Stark4.7
5454 ratings
Why you should be offering guarantees.
Ditching Hourly 026: Why You Should Be Offering Guarantees
Hello! and Welcome to Ditching Hourly. I'm Jonathan Stark.
Today, I'm going to talk about offering guarantees.
One of the tactics I advocate for increasing your fees is to offer some sort of guarantee.
This typically horrifies developers.
They immediately have visions of an unreasonable client demanding a 100% refund after six months of work.
Yikes, right?
Still, I think you should consider offering guarantees.
And here's the thing... you probably already guarantee your work!
Ask yourself this:
If you answered YES to any of these, then you ALREADY guarantee your work.
So...
Why not make your guarantee explicit instead of implicit?
How and when to offer guarantees for the kinds of work that software developers typically do is a touchy subject.
Over the years, I have offered different sorts of guarantees for different sorts of products and services.
The type that I choose in a given situation depends on a variety of factors like:
For example:
For fairly fixed scope dev work (e.g., a productized service) that I can finish quickly, I’d offer a 100% money back guarantee on my sales page.
(I’d also price the service accordingly, but that’s another story.)
So, for something like a half day of SQL performance tuning, I’d offer a 100% money back guarantee if the client was unhappy with the outcome.
I see this type of service as analogous to bringing my car to a mechanic to have it tuned up... if the car is still running rough when I leave, I’d expect them to either redo the work or refund my money.
Here's the key point about guarantees:
Explicitily stating up front how you will “make things right” if things go wrong will differentiate you from the vast majority of your competitors.
And remember: if you can’t differentiate yourself from your competitors, you’ll probably end up competing on price.
That's it for today. I'm JS and this is Ditching Hourly. Thanks for listening.
The next time someone asks you for your hourly rate, this is what you should say: "I don't have one." To learn what to say next, visit http://valuepricingbootcamp.com to signup for my free email course. Again, that url is: http://valuepricingbootcamp.com
----
Do you have questions about how to improve your business?
Things like:
Book a one-on-one coaching call with me and get answers to these questions and others in the time it takes to get ready for work in the morning.
Best of all, you're covered by my 100% satisfaction guarantee. If at the end of the call, you don't feel like it was worth it, just say the word, and I'll refund your purchase in full.
To book your one-on-one coaching call, go to:
https://jonathanstark.com/call
I hope to see you there!

16,121 Listeners

2,452 Listeners

703 Listeners

1,090 Listeners

1,263 Listeners

2,165 Listeners

4,454 Listeners

210 Listeners

856 Listeners

2,655 Listeners

5,553 Listeners

9,938 Listeners

1,328 Listeners

33 Listeners

135 Listeners