Revenue Share vs. Hourly: Why I Never Charge Upfront

When I tell people I don't charge upfront for software development, I get two reactions. The first is "that's amazing, let's do it." The second is a squint followed by "what's the catch?"

Fair question. After 25 years in corporate finance, I'm pretty suspicious of anything that sounds too good to be true too. So let me explain why this isn't charity, it isn't desperation, and it definitely isn't too good to be true. It's just better math.

The agency model is a terrible deal (for you)

Let's say you walk into a development agency with an idea for a SaaS product. Here's what happens: a very polished account executive takes you to lunch, nods enthusiastically at everything you say, and two weeks later sends you a proposal for $120,000. Sixty percent upfront. The rest on "milestone delivery." Project timeline: six months.

Now let's think about what you're actually buying. You're paying $120K for someone to attempt to build something that might generate revenue at some point in the future. If it works — great, but they already have your money either way. If it doesn't? Well, that's your problem. They've moved on to the next lunch.

From an FP&A perspective, this is an absurd capital allocation. You're making your largest financial commitment at the exact moment when you have the least information about whether the investment will pay off. It's like putting your entire retirement fund into a stock before reading the earnings report. No finance executive on earth would approve this deal — and yet business owners accept it every day because they don't think there's an alternative.

There's an alternative

In a revenue share model, I build the product on my time and dime. I invest the hours, the expertise, and the infrastructure cost. In return, I earn a percentage of the revenue the product generates — negotiated individually for each project because every business is different and I'm not a vending machine.

The result? My incentives are permanently welded to yours. If your product doesn't make money, I don't eat. If it makes a little money, I eat a little. If it makes a lot of money, we both celebrate — and I'm still there optimizing because my share of "a lot" is more than my share of "a little." Wild concept, I know.

Compare that to the agency that's already cashed your check and has no structural reason to care whether your product succeeds after launch.

"But Tarak, how do you survive without upfront payment?"

This is where the math gets fun. An agency charges $120K because they have $120K worth of monthly overhead whether they're building your product or playing foosball. Office lease. Project managers managing projects being managed by other project managers. Account executives. HR. The legal team that reviews the contract that protects the agency from accountability.

I have none of that. My tools cost about $150 per month. My biggest expense is coffee. I don't have a foosball table, which honestly is the only real downside of this whole arrangement.

Because my fixed costs are nearly zero, I can absorb the upfront investment risk. The bet I'm making isn't reckless — it's calculated. I evaluate the business opportunity before I take it on. If the idea is sound, the market is real, and the product has a clear path to revenue, the expected value of the revenue share exceeds what I'd make on an hourly contract. It's just delayed — which is fine, because I'm playing a longer game than someone who needs to make payroll for 40 people this Friday.

Why this produces better software

Here's the part most people don't think about: the compensation model changes the quality of the work.

When an agency bills hourly, they're incentivized to take longer. When they bill fixed-price, they're incentivized to cut corners. Neither structure rewards them for building something that actually performs in the market.

Revenue share flips this completely. I'm incentivized to build something that generates as much revenue as possible, as quickly as possible, for as long as possible. That means solid architecture (so it doesn't break under load), great user experience (so people actually pay), smart business logic (so the pricing model works), and continuous optimization (so it gets better over time). Every hour I invest in making the product better comes back to me as revenue. It's honestly the most aligned incentive structure I've seen in 25 years of analyzing business models.

When it works and when it doesn't

I'm going to be straight with you: revenue share doesn't work for everything. It works when there's a clear path to measurable revenue — SaaS products, e-commerce platforms, paid tools, lead generation systems. Things where we can both look at a dashboard and agree on how much money came in.

It doesn't work for internal tools with no revenue attribution, vanity projects, or ideas where the business case boils down to "I just think it would be cool." For those projects, hire a freelancer. I'll even recommend some good ones.

I'm selective because the model requires me to be. I'm betting my time on your business — so I need to believe in the bet. If that means I say "great idea, but the market won't support it" before you spend a dime, that's a service the $120K agency would never provide. They want your money. I want your revenue.

One more thing

Every deal is individually negotiated. I don't have a rate card because I don't have rates. I have conversations. We look at the opportunity, we look at the scope, and we agree on a structure that makes both of us excited to build something great. I keep the terms reasonable because I don't need to fund a 40-person operation off your project. I just need a fair partnership with someone who has a real business to grow.

That's it. That's the model. No catch. Just a finance professional who got tired of watching business owners overpay for software that underdelivers — and decided to do something about it.