As threatened, today I'm going to talk about pricing. This one will likely result in... feedback.
So, as you've probably heard if you've worked with, met, passed on a street, been in the same coffee shop as, or just had a dream about @jonathanstark, "hourly billing is nuts."

I used to disagree vehemently. I no longer do.
Unless you're an attorney, people are going to cap out in terms of what they pay you somewhere around $250-$300 an hour.

That's good money, right? $600K a year assuming 40 hours a week. Let's start there.
First, you're not going to be billing 40 hours a week unless you're working ~90 hours a week. Finding new clients, handling paperwork, and other "non-billable" work eats up your time.

It's easier and a lot less work to just get a job that's within that ballpark.
"You think it's easy to get a job that pays half a million bucks?!" If you've got a skillset you can reliably bill out at $300 an hour? Absolutely.
The first problem here is one of psychology. Every time you want to go play with your kid, or talk to your partner, or even play video games, there's that "you could be making $300 an hour right now instead" at the back of your mind.
It also changes how your customers see you. Instead of asking you your advice before they, for example, drop a database table? They're going to weigh your hourly rate.

Every interaction with you becomes an investment decision.
It's also hard to capture reasonable (and I mean REASONABLE to you or I, not rando VCs) value for what you provide.

If you save a company from a $10 million a year blunder, how do you bill for that reasonably?
Instead of quoting a rate to a customer, dig in. "Why do you care about this thing?" "Why not do X instead? What about Y?" Trust me--they've already considered doing these things. They won't vanish because you asked.

Find out why they care. The answer might surprise you.
You're trying to scope the value of solving the problem as perceived by them. "So improving the latency on this app will make you folks $20 million a year in additional revenue?" If they agree, you now know what the real value of what you're doing for them looks like.
You've got a few options here. I like the "quote different options" model of giving three paths. The first is exactly what they asked for. The second is what you would recommend as The Expert. And the third is the "bells and whistles" version.

All are flat rate.
"Wait! I'm a technical person! Scope creep / risk / I don't know how big of a project this is going to be!"

Start small with a paid discovery project. Timebox it to a day or two, possibly with the fee as a credit towards the actual big project you propose afterwards.
After the big project is done, I'm a fan of retainer projects. Within certain bounds, "unlimited access to me" is what that includes for a fixed monthly fee. That's the closest I ever get to charging for time.
The good clients, the clients you want? They're not going to abuse that.

The folks who will are likely to get sussed out earlier in the process. I'd never open with a retainer offering unless there were extenuating circumstances.
And the benefits of this model are massive. I spent two years independent doing exactly this.

That's how I had time to fix the @awscloud bills, write @LastWeekinAWS, and spend time with @Quinnypiglet.

There wasn't a constant tradeoff around "billable work."
I can predict some responses.

"We charge by the hour." Okay. There are multiple paths.
"You can't scale like that!" Maybe. Maybe not. It continues to work for us.
"Did you ever consider charging by--" yes. I'm going to stop you there. I've spent four years delving deeply into my business. I assure you, I have considered what you're about to suggest and discounted it for one reason or another.
"I can't charge tens of thousands of dollars for a project where 'I show up to be a DBA' is the deliverable!"

That's right, you can't. See yesterday's thread about positioning.
Done correctly, the payoff is massive. My "effective hourly rate" for the time I spent working on client projects was in the thousands. And I didn't have to burn myself out to do it.
Yup! This is why aligning yourself with a *specific* expensive problem is so valuable. It takes WEEKS to get these right the first few times. Once you do, it becomes a standard, almost "productized" offering.

Neither do I. But I sure know how to do a series of smaller fixed-scope projects consecutively for a client!

"This couldn't possibly work!"

*points at the Duckbill Group*

Are you sure about that?

I'll even take it a step further: the @awscloud bill is very far from the only expensive problem in our space that lends itself to this kind of treatment.
Customers prefer it too.

"That flat fee isn't an estimate, it's a quote." If things are easier than you thought? Your margins win! If they take longer? You learned a lesson and the customer is still thrilled.
I mean really--what's easier to get approved? "I will build your website that does FOO for $25K" or "I charge $175 an hour for WordPress development; this should take 120 hours-ish?"
Absolutely. The prerequisites are "the ability to solve a problem that people are willing to pay to make go away."

Fixed fee house painting, lawn mowing, and home organizing all have potential.

Fixed fee for a duration; I like "monthly retainers." In other words, 'you pay some amount of money that has a comma in it in return for unlimited access to me within some defined scope.'

If you don't use me at all that month? More money for me.

And remember the other thread--you are The Expert in this space. Your retainer fee should be significant, because at this point there's a terrific chance that you should only be giving out advice--not doing implementation.

But that's tomorrow's thread if the schedule holds.
This is why car analogies break down like my car in this hypothetical. "Getting your car fixed" is well and truly commoditized. You want to solve an expensive problem! The equivalent would be "you restore very rare Corvettes from years X to Y."

It should be borderline impossible to do a true apples-to-apples comparison of what YOU do vs. what someone ELSE does.

That's not wishful thinking; it's very possible.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Corey Quinn

Corey Quinn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @QuinnyPig

4 Mar
The @okta news is super great and all, but every time I hear their name I’m reminded of the time I had to sign an agreement not to attempt to hire their staff for a year in order to enter their office to speak at a meetup.
This was their “doorway NDA” and is almost certainly unenforceable, but it annoyed me something fierce.
Years ago I had to turn a meeting at @AppDynamics into a meeting at the nearby coffee shop for the same reason because I was at that time actively counseling one of their staff to leave.
Read 5 tweets
4 Mar
A third day, with my thoughts on consulting. This one is probably the most controversial, so let's get to it.

I don't think the best move is to do implementation work. A thread...
Hear me out. In the first thread I talked about finding a positioning that works as "the expert in An Expensive Thing."

In the second, I talk about value based pricing instead of hourly.

So you're now a very expensive expert here to solve a big expensive problem.
In the technology industry, I maintain that implementation opens up Pandora's Box of delivery risk, while simultaneously damaging the perception of your value.
Read 14 tweets
3 Mar
So in that NYTimes profile of me, @daiwaka wrote "Mr. Quinn said Amazon had never tried to rein in what he said."

That's not ENTIRELY true, and I do want to be fair to @awscloud.
While @awscloud has never once tried to stop me from publishing anything incendiary, or urged me not to deliver a Hot Take, they jump with a *QUICKNESS* when I say something that they perceive to be factually incorrect.
Their approach can best be summed up as "shitposters gonna shitpost, but the second it confuses a customer that is A Problem."

And what's more is, they're right. A few examples!
Read 7 tweets
2 Mar
"Join now to watch the Microsoft Ignite keynote!"
There we go. And as an apology for the trouble, @Microsoft has disabled the social profile nonsense.
What kind of crapass "cloud" conference is this?! They've got pre-keynote streams so you feel engaged and involved, they bother to *mention* the virtual sponsor expo hall so customers know it's there...

MS has so much to learn from AWS's approach to half-assing things.
Read 32 tweets
2 Mar
My personal guide for burned-out employees with chips on their shoulders. I recommend none of these. I am guilty of all of these. This is why I'm a terrible employee.
Put expenses on your own credit card and then submit them. If you experience pushback, stare them dead in the eye and say "okay, so don't pay it." See if they call your bluff.

(They almost never will.)
If someone asks you to work late tonight, you have plans. Maybe a date with your spouse. Maybe playing video games. Maybe you plan to cry yourself to sleep. Not their business; they're your plans.

Emergencies aren't "someone else fucked up the planning."
Read 18 tweets
2 Mar
So you want to be an independent consultant. Let’s skip past the stage where I scream “don’t do it!” and onto the next step:

How to position yourself.
It's natural to want to be the jack/jane-of-all-trades; anything within the vague realm of technology being what you do.

It's also a mistake.
Your first deals are going to come from your network--friends, former colleagues, etc. You want word of mouth to spread, because traditional marketing in this space is nightmarish.

Generalists don't get recommended.
Read 19 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!