Price the Outcome, Not the Hours
Hourly billing punishes fast builders and rewards slow ones, which is why every engagement I sell is a defined outcome with a fixed price and a clean exit.
An invoice for forty hours tells you exactly one thing: it took forty hours. It does not tell you whether anything works, whether anyone owns it, or whether the store is better than it was last month. After a decade of selling work as an agency owner and years of buying it as an operator, I have landed on a simple position. Hourly billing is a bad deal for everyone except slow vendors. Price the outcome instead.
Hourly billing punishes the builder you want
Think about what an hourly rate actually prices: time on task. Now think about who wins under that model. The builder who has solved your problem fifty times finishes in a week and bills a week. The builder seeing it for the first time takes a quarter and bills a quarter. The market rewards the wrong one, structurally, every time.
Speed is compressed experience. When I ship something in days that takes others months, that pace is twenty years of automotive pattern recognition plus the engineering skill to act on it. Hourly billing converts that experience into a discount for the client and a penalty for me. The better I get, the less I would earn.
It also quietly rewards everything you already hate about vendors: discovery phases that discover nothing, status meetings that exist to be billable, scope that mysteriously grows in month three. Nobody on either side of an hourly contract is incentivized to finish. Read that again, because it explains most of your vendor frustration. The dealer pays for time. The builder sells time. The outcome, the only thing that ever justified the invoice, ends up being nobody's actual job.
I have signed both sides of this invoice
This is not a builder complaining about clients. I co-founded OOMDO and ran it from 2012 to 2023, with 20+ employees and $60M+ in client sales over the decade. I priced engagements, scoped them, defended them, and lived with the margins. I know exactly how agencies think about billable time, and I know where the waste hides.
I have also been the buyer. As a marketing director and later as a director of search marketing responsible for 18 dealership sites, I read vendor invoices for a living, and at Lia we ultimately brought SEO and SEM in-house rather than keep renting it. The pattern I saw from the buyer's chair is the same one I had to fight from the seller's chair: activity invoiced as if it were progress.
Run both sides long enough and you arrive at one conclusion. The unit of value is never the hour. It is the working system standing at the end.
What a productized engagement actually is
A productized engagement has three properties: a defined outcome, a fixed price, and a hard boundary.
Defined outcome means the deliverable is named in writing before anything is signed. Not improve lead handling. A specific system, doing a specific job, observable in your store, with a definition of done that both sides can point at.
Fixed price means the cost is known on day one. If I finish faster because I have built it before, I am rewarded for competence instead of punished for it. You pay for the result, not for the privilege of watching me work.
Hard boundary means the engagement ends. There is a handoff, documentation, and a day on the calendar when you do not need me anymore. That last property is the one most vendors will never offer, because their business model is the dependency. Mine is the outcome. It is why the pricing page on this site is called Engagements and lists scopes, not rates.
What a well-scoped AI engagement looks like for a dealer
Here is a hypothetical to make it concrete. Imagine a dealer who cannot answer one basic question: which lead sources actually produce sold units, and where do leads die in the funnel? A well-scoped AI engagement against that problem has three parts.
One: a clear deliverable. A working pipeline that pulls the relevant data, reconciles it, and surfaces the answer in plain language, defined in a one-page scope both sides sign before work starts.
Two: an owned system at the end. The code in your repository. The accounts in your name. The prompts, the data, the documentation, all handed over. If the vendor disappears tomorrow, the system keeps running and the next builder can pick it up.
Three: no perpetual retainer dependency. Training for your team, a defined support window, a clean exit. Ongoing help should be a choice you make because it is valuable, never a hostage situation you cannot afford to leave.
The test is one question. Ask any AI vendor to describe the day you no longer need them. Watch the face. If they cannot answer, you are not buying a system. You are renting one, and the rent only goes up.
But hourly feels safer
The usual objection: fixed price sounds like fixed disappointment, because everyone has a horror story about a flat-fee project that shipped garbage. Fair. But notice what actually failed in those stories. It was never the pricing model. It was the scope: vague deliverables, no definition of done, no named owner of the outcome.
Hourly billing does not protect you from that. It just spreads the disappointment across more invoices, and you pay for the failure by the hour while it happens. A defined outcome with a fixed price does the opposite: it forces the scope conversation up front, while you still have leverage, instead of in month three when you are already committed.
Outcome pricing changes the incentives on both sides
Price the outcome and the whole relationship rewires.
The vendor takes delivery risk instead of you taking calendar risk. If the build runs long, that is my problem, not your invoice. Speed becomes profitable for both sides: I want to finish because the price is fixed, you want me to finish because the outcome is the point. Scope gets disciplined before the work starts. And quality aligns, because a system you own and operate is a referenceable artifact for me, not a recurring line item I am protecting.
Hourly billing means the vendor's revenue grows when your problem stays alive. Outcome pricing means the vendor's reputation grows when your problem gets solved. Pick which incentive you want sitting across the table from you.
See how it is structured
Every engagement I sell works this way: defined outcome, fixed price, owned system, clean exit. The current scopes are on the Engagements page, and the proof behind them is at /work. If the problem in your store is worth solving, it is worth pricing by the solution. And if it is not worth solving, no hourly retainer was going to save it anyway.
