There's a number hiding inside almost every proposal you send. The client never sees it. Most days, you don't either. Your hourly rate. Not the agency that bills off a timesheet. That one is at least honest about what it's doing. I'm talking about the quiet version. You hear the project, guess the hours in your head, multiply by a number that felt fair, round it off, and call it a price. You know how it sounds. You've said most of these: "It's about 20 hours, so call it $2,000." "I don't want to overcharge him." "The last guy quoted him $900." "It only took me a weekend. I can't charge $5,000 for that." "AI does half of it now, so I should probably drop my price." "Can you do it for $1,500?" "Yeah, I can make that work." "I'll make it up on the next one." Every one of those is a decision about your hours. Not one of them is about his business. 𝗥𝘂𝗻 𝘁𝗵𝗲 𝗺𝗮𝘁𝗵 𝗼𝗻 𝗮 𝘄𝗲𝗯𝘀𝗶𝘁𝗲 𝗯𝘂𝗶𝗹𝗱 Say you quote a five-page site for a local service business at $2,500. You figured 25 hours. That's $100 an hour on paper. Feels good. Now count the real hours. Discovery call and proposal, say 3. Chasing the content and photos he swore he'd send by Friday, say 5. The build, say 20, because it's never the 15 you planned. Two rounds of revisions that turn into four, say 8. Launch, DNS, and the email that stopped working, say 4. The "quick questions" for the next 60 days, say 5. That's 45 hours. About $55 an hour. And if you read the scope creep Deep Dive, you already know how the worst version ends. Same $2,500 project, a few "while you're in there" requests, and you're sitting at $8 an hour. Here's where it gets ugly. Say you fix all of that. You tighten the scope, you build from templates, you let AI take the first pass at copy. The same site now takes you 12 hours. Hourly thinking says the price should drop. 12 hours at $100 is $1,200. You got faster, better, and more efficient, and your pricing model took $1,300 off the table as a reward. Read that again. Hourly pricing is the only system where getting good at your job is a pay cut.