Stop Trading Time for Money
Charging by the hour has a hidden flaw: it penalizes your own competence. The faster and better you are, the less you earn. If you solve a $1M problem in 10 minutes because you have seen it a hundred times, an hourly rate at $500/hr pays you $83. A value-based fee pays you $50,000. The client's outcome is identical. Your compensation should not be determined by your speed — it should be determined by the value of the result.
There are three primary pricing structures, each with distinct trade-offs:
1. Hourly Rate (Avoid if Possible)
You charge a fixed rate per hour of work. This is the default that most engineers start with because it feels safe and familiar. The problem is that it creates misaligned incentives: the client wants you to work faster, you need to work longer to earn more. It also makes your income unpredictable and caps your earning potential at roughly 2,000 billable hours per year.
When it makes sense: Open-ended exploratory work where neither party can define scope upfront. Even then, cap the total hours in the contract.
2. The Project Fee (Fixed-Price Engagement)
You charge a flat fee for a defined deliverable. "I will build your MVP backend for $50,000, delivered in 8 weeks."
- Risk: Scope creep. If the project takes twice as long as estimated, you absorb the loss.
- Reward: High margin if you are efficient. A project you estimated at 80 hours that takes 40 hours doubles your effective rate.
- Protection: A tight Statement of Work (SOW) is non-negotiable. Define exactly what "Done" means before you sign.
3. The Advisory Retainer (The Highest-Leverage Model)
You charge a fixed monthly fee for ongoing access to your expertise. "You pay me $6,000/month. In return, I am available for up to 6 hours of calls, architecture reviews, and critical decisions."
This is the most powerful model for experienced engineers because it creates recurring, predictable income. The client is not paying for your time — they are paying for insurance. They want to know that when their architecture decision goes sideways at 2 PM on a Tuesday, they can call someone who has seen this before.
The key mechanics of a healthy retainer:
- Cap the hours explicitly (e.g., "Up to 6 hours per month"). This prevents the retainer from becoming a part-time job.
- Define what counts as a retainer activity (calls, async reviews, document feedback) versus what triggers a separate project fee (hands-on implementation, hiring sprints).
- Require a minimum term (3 or 6 months). Month-to-month retainers create anxiety and make it hard to plan your own capacity.
A single client on a $6,000/month retainer generates $72,000/year. Three such clients — each requiring roughly 6 hours/month — generates $216,000/year from 18 hours of monthly work. This is the math that makes retainers the goal.
If asked "How do you price consulting work?" in a Staff+ or Principal Engineer interview, the answer interviewers want is not "I charge $X/hr." They want to hear that you anchor pricing to business value. Say: "I start by quantifying the cost of the problem — lost revenue, engineering hours wasted, risk exposure — and price as a fraction of that value. Hourly rates are a last resort for undefined scope."