Skip to main content
Project profitability

Know which projects
are actually making you money.

Project profitability tracking built into the same board where the work happens. Margin by client, sorted worst first. Cost rates you can derive from salary data instead of typing in by hand. And the visibility to hand a real number to finance without handing everyone's pay to the whole team.

Hourly, fixed-fee & retainer Cost rates from salary data From $8/user/month
app.harmny.ai/profitability

The profitability blind spot

You bill by the hour, the retainer, or the fixed fee. You still find out margin at quarter close.

The cost-rate chore

A PSA tool only knows what you type in.

Someone maintains a cost-rate spreadsheet by hand, and it drifts the day a raise happens. Nobody remembers to update it until the margin number stops making sense.

The wrong basis

A month-old retainer looks like a disaster.

Judge every project on the same monthly window and a subscription that just launched reads as underpriced the day the build cost hits the books, when the actual run rate is fine.

The visibility problem

Margin data is either locked to finance or wide open.

Managers who run the work day-to-day either see nothing, or they see cost rates that are really just everyone's hourly pay with a markup on top.

Harmny already holds the two halves of this problem: what people cost, from compensation data, and what work costs, from the boards it runs. Profitability connects them instead of asking you to reconcile a third tool.

The differentiator

Cost rates, derived from what people actually earn.

A standalone profitability or PSA tool only knows a cost rate if a person typed it in. Harmny already stores compensation data for running reviews and career ladders, so it can suggest one instead. Monthly salary, divided by that person's effective monthly hours, times an overhead multiplier you control, 1.2x by default, adjustable between 1x and 3x for taxes and benefits.

Effective hours already account for anyone working below full capacity, so a part-timer's derived rate does not come as a surprise. You review the suggested rate per person before anything is written, and apply it explicitly. Nothing changes in the background. The salary itself never leaves the calculation; only the derived hourly rate lands on the rate card.

  • Derived from salary, reviewed per person, applied on request, never automatic
  • Or set billable and cost rates by hand, per person, per project, or as an org default
  • Salary figures never leave the calculation. Only the derived rate is stored

Suggested cost rates · preview

Account lead, full-time

salary ÷ monthly hours × 1.2x

$62/hr

suggested

Designer, 80% capacity

effective hours adjusted

$58/hr

suggested

Strategist, full-time

salary ÷ monthly hours × 1.2x

$71/hr

suggested

Review each rate, then apply. Salary values are never exposed. Only the rate above is saved.

Job costing, on the right basis

Fixed fee, retainer, and hourly don’t earn the same way. They shouldn’t be judged the same way either.

Every project carries a pricing type, and margin is calculated on the basis that pricing type actually earns money.

Hourly

Windowed

Revenue and cost both follow whatever date range you have open. Billable hours times the billable rate, against logged hours times the cost rate, for that period.

Fixed fee

Lifetime

Judged on the whole contract value against whole-of-project cost, because a fixed price buys the entire engagement. Hours still show for the period so you can see recent pace, and effective hourly rate and breakeven hours are tracked alongside.

Recurring

Run rate

This month’s recurring revenue against the trailing 30 days of cost, independent of any date filter, so a subscription in its first week isn’t marked underpriced by a build cost. A separate payback figure shows whether the build has earned itself back.

Internal

Cost only

No revenue is expected, so none is invented. Margin and verdict come back empty, not zero, and internal projects are excluded from every rollup that means "is the business healthy."

A project below a 15% margin reads Underpriced. Above 40%, Overpriced, worth checking the price or the tracked hours. Between the two, Fair. Every project sits in one of these bands, or shows exactly why it can’t yet: no contract value on record, no monthly revenue set, or no hours logged.

Admin / HR · full view

Margin $4,120 · 27%

Labor $8,900 · Expenses $1,200 · Revenue $14,220

Manager · health view

Fair · index 104 · trend up

No dollar figures shown

Everyone else

36.5 hrs · $14,220 revenue

No margin or verdict shown

Three tiers, one project

A number finance can use. A signal managers can act on. Nobody's pay in either.

Admins, HR, and anyone granted the cost-rates capability explicitly see the real numbers: labor cost, expenses, cost price, margin, margin percent. Managers get a middle tier by default: a pricing verdict, a health index scored against the org average, and a trend arrow, with every dollar figure stripped out. That tier is an org-wide toggle, so it can be turned off.

Below that, everyone sees hours and revenue only. And on any project worked by fewer than three people, the health tier shows nothing at all. A two-person team's margin is close enough to two salaries that even a band isn't safe to show.

Profitability by client

Every client's projects roll up into one number, sorted worst first.

Projects group under the client (or account, or department) they belong to, and the client itself carries a blended margin: revenue and cost summed across every project, not an average of percentages, so one small underpriced job doesn't hide inside a healthy account and one large healthy account doesn't get dragged down by a rounding error. Clients are then sorted by their worst project first, so the account that's bleeding is the first thing you see, not something you find by scrolling.

Why teams track profitability in Harmny

Margin by client, worst first

Every account rolls up to one blended margin, sorted so the bleeding client is the first thing you see.

Judged on the right basis

Hourly is windowed, fixed fee is lifetime, retainers run on trailing 30-day rate. No pricing type gets the wrong yardstick.

Cost rates from real comp data

Derive suggested rates from salary already in Harmny instead of maintaining a second spreadsheet by hand.

Visibility that protects pay

Full numbers for finance, a verdict for managers, nothing that reconstructs an individual salary.

Time entries, not clock-in

Cost is built from hours logged on tasks, the work that was actually done, not attendance records.

Internal work stays honest

Cost-only projects report no revenue and no margin, and never drag down a client’s numbers by mistake.

Built for billable work

Marketing and creative agencies get the most out of it first.

Profitability tracking was built around how agencies actually structure work: a client (space) holding several channels or workstreams (projects) running on a mix of retainers, fixed-fee deliverables, and hourly overflow. That is also the shape of most professional-services billing: consultancies, studios, and dev shops working project-to-project for outside clients. Agency profitability lives or dies on those relationships, and most of the time nobody can say which ones are carrying the others. If you bill by the hour, the retainer, or the fixed fee and you want to know which of those relationships is actually worth keeping, this is built for you.

Margin data stays internal by design. It never flows into a client portal. Share the client-facing view (status, KPIs, deliverables) through the portal, and keep what the relationship actually costs you in the tier that's meant to see it.

See the full agency workflow

Project profitability · common questions

What teams ask before trusting Harmny with margin data.

Clarity. Motivation. Growth. For your whole team.

Free forever for up to 10 users. No credit card required. Full access from day one.

By signing up you agree to our Terms of Service and Privacy Policy.