The profit math mistake hiding in almost every freelance rate calculator
Building a rate calculator for my agency ops product and decided to benchmark mine against what's already out there. Spent a couple of nights running real numbers through the popular ones. Found something I wasn't expecting.
Almost all of them treat profit as a fixed dollar amount you stack on top of costs:
salary + overhead + profit_dollars = revenue, then divide by billable hours.
That's not how a real P&L works. Profit is a percentage of revenue, not a flat add. Which means the math has to be iterative. Profit and revenue have to solve together. If you want a 20% margin, your rate has to be high enough that 20% of total revenue lands as profit after salary and overhead are paid.
Quick example so this isn't abstract. Solo operator, $120k income target, $40k overhead, 1,200 billable hours a year, 20% margin. The "add profit at the end" method spits out about $150/hr. The iterative version says $167. If you used the wrong method you'd be under-pricing by 11% and never know unless you laid the math out side by side.
Three other things that surprised me along the way:
AgencyAnalytics 2024 survey: 73% of agency owners raise rates less often than every 18 months. Most regret not doing it sooner.
Industry-standard "good" utilisation sits around 70-75%, not 80+. Anything higher kills your slack for admin, BD, and project overruns.
Small agencies typically run 25-40% overhead as a % of revenue. If yours is way lower, you're probably eating the difference as unpaid founder time.
The version I built is here, free, no signup: https://www.optivationai.com/resources/tools/agency-hourly-rate-calculator?utm_source=indiehackers&utm_medium=community
(Context: I'm building an agency ops product called Ascend. The calculator is a free spin-off from that work. Sharing here because the math felt non-obvious to me and I figure other builders running services on the side will run into the same trap.)
Curious what other founders here use to set their own rates. Gut feel, market comps, or have you actually run the iterative math?
This is a useful wedge because the calculator is not just a lead magnet. It exposes a real agency-ops problem: a lot of small agencies think they are pricing for margin, but the math is quietly turning founder time into invisible subsidy.
That insight probably connects well to Ascend if the broader product is about helping agencies run with cleaner operational visibility. The strongest positioning may be less “rate calculator” and more “agency margin control,” because that moves it from a free tool into a real operating system pain.
One thing I’d watch is the name Ascend. It is clean, but also very broad and crowded. If the product becomes a serious agency finance/ops layer, a sharper brand like Beryxa.com could give it more proprietary weight than a common directional word.
Love this take. You’re right — the calculator works because it exposes a structural ops issue, not because it’s a cute lead magnet. Most small agencies are accidentally underwriting their own business with unpaid founder time.
And yes, the long‑term positioning is absolutely “agency margin control.” That’s where Ascend is heading.
Re: naming — fair call. Clean, but maybe too broad. I’ll keep that in mind as the product sharpens.
Exactly. “Agency margin control” is much sharper because it names the pain agency owners actually feel.
The thing I’d watch with Ascend is that broad names are fine when the category is already obvious, but riskier when the product is trying to create a sharper operating frame.
If this becomes the layer that shows where founder time, pricing, delivery, and margin are leaking, then the name probably needs to feel more proprietary than a general growth word.
That is why Beryxa.com came to mind. It feels more like a serious SaaS/ops brand, while still leaving room to grow beyond one calculator or one finance workflow.
I would not force the naming decision too early, but if the product is already moving toward agency margin control, this is probably the right stage to pressure-test whether Ascend carries enough weight.
Happy to connect on LinkedIn if useful. This is exactly the kind of category and naming shift worth thinking through before the product gets too fixed:
https://www.linkedin.com/in/aryan-y-0163b0278/
Just for clarity the tools and calculators are just for the marketing landing site. Our real SaaS offering is at https://ascend.optivationai.com?utm_source=indiehackers&utm_medium=community . Databases, Forms, time tracking, pages, time-tracking, invoicing. The WWW site is using free tools or engineering as marketing to provide value to our target users.
That actually makes the naming question more important, not less.
If the calculators are just engineering-as-marketing and the real SaaS is databases, forms, time tracking, pages, invoicing, and operating workflows, then Ascend is carrying a much broader promise than I first thought.
That sounds less like a finance tool and more like an agency operating layer.
The risk with Ascend is not that it is unclear. It is that it is too broadly positive. A lot of brands can “ascend.” But if your product becomes the system agencies run delivery, time, data, billing, and margin through, the name may need to feel more proprietary and ownable.
So I’d frame the pressure test differently now:
Do users remember Ascend as a specific agency operating system, or does it feel like another broad growth/productivity brand?
That distinction matters more as the product expands, because the wider the SaaS gets, the more the name has to create its own category memory.