A Runn alternative for agencies that invoice from approved hours.
Runn (runn.io) plans capacity months ahead, with tentative projects and saved scenarios. We make Opsium, so keep that bias in mind; Runn's limits below are quoted from its own help center.

By Andrii Chernysh · CEO, Founder
16 min read
Both tools plan months ahead. Opsium also carries the plan through approved timesheets to invoices in QuickBooks, with versioned rates that leave past revenue alone, so if your month ends in client invoices, Opsium is the better fit.
- Billed annually: Opsium $12, Runn Standard $11 per person a month
- Opsium on a 2-year term: $10
- Seat minimum: Opsium 25, Runn 20
- Opsium adds timesheet approvals, versioned rates and QuickBooks invoicing
Choose Opsium if
- planned hours must become approved timesheets
- bill rates change mid-project and past revenue must keep the old rate
- the planner should know each person's hours, role and rate on every day, including changes already scheduled
- approved hours should become invoices and vendor bills in QuickBooks Online
- your team logs time in Jira, Tempo or Clockify
Choose Runn if
- you want to save what-if scenarios and switch between them
- you want project budgets tracked against revenue
- you have 20 to 24 people
- you need SOC 2 Type II, or leave synced from BambooHR or HiBob
Feature by feature.
| Feature | Opsium | Runn Standard |
|---|---|---|
| Price per person per month | $12 billed annually, $15 billed monthly, $10 on a 2-year term | $11 billed annually, $13 billed monthly. Lite (no timesheets): $7 / $9 |
| Seat minimum | 25 people, with hands-on onboarding included; placeholders and imported people you don't manage are free | 20 people; placeholders and login-only users are free |
| Free trial | 30 days, no credit card | 30 days, no credit card |
| Hosting and certification | AWS in Frankfurt, data at rest in the EU; not SOC 2 certified | US or EU hosting; SOC 2 Type II |
| Planning ahead | YesTentative projects with a win probability; draft and unconfirmed assignments with their own probability; free placeholders | YesTentative projects and unlimited free placeholders |
| Saved what-if scenarios | NoNone; you choose which assignment statuses count toward utilization | Yes3 per user, visible only to the person who made them |
| Forecast reports | YesForward capacity, booked hours, probability-weighted pipeline hours, and forecasted revenue and cost by month, department, role or client | YesEstimated revenue, cost, margin and budget remaining per project |
| Project budgets | NoStored on each project; not tracked against hours or revenue | YesProject revenue compared with the budget, so you see over or under |
| Change-aware timeline planner | YesA change to a person or project takes effect on a date, past or future; the planner reads each day's hours, role and rate, and Change History shows before and after | PartlyA person's hours, cost rate and default role change through dated contracts; a project's bill rate is not dated |
| Time tracking | YesTimer with pause or timesheet; Jira, Tempo and Clockify worklogs sync in | YesWeekly timesheets (not on Lite), a Chrome extension (EU-hosted accounts only), CSV import or the API |
| Timesheet approvals | YesBy project, person or entry; hours to invoice and to pay approved separately; syncs cannot change an approved entry | NoNone; past weeks can be locked instead |
| Versioned rates | YesEvery rate level is a dated record, from the organization default to a person's rate on a project; past work keeps the rate in effect that day | PartlyA bill rate change rewrites past revenue; cost rates can be dated |
| Invoicing | YesCreated in QuickBooks Online from approved hours; status and balance sync back | NoNo invoicing; no QuickBooks or Xero integration beyond a Zapier or API build |
| Vendor bills | YesCreated in QuickBooks Online at cost rates from the hours approved for pay | NoNo invoicing or bills |
| Jira, including logged time | YesUsers, projects, issues and worklogs, read-only | PartlyProjects and people; time logged in Jira does not sync |
| Clockify and Harvest | PartlyClockify time entries sync in; no Harvest | NoAdvanced plan only, on request (one-way daily sync) |
| Onboarding and data migration | YesIncluded in the price, done by our team: people, projects, rates and past time | PartlyImplementation services "eligible" on annual Standard, no published price |
| Leave synced from HR tools | NoNo HR tool sync | YesApproved leave syncs from BambooHR, HiBob and others |
Runn vs Opsium: what one rate change does to past revenue.
In Runn, a project rate change applies to work already done. Move the sliders to see how much past revenue your plan would report that you never invoiced, and what Opsium's extra dollar per person costs in a year.
Runn would now report $126,000 of past revenue on this project, $12,000 away from the $114,000 you invoiced. Opsium still reports $114,000.
At 50 people, Opsium costs $600 a year more than Runn Standard. A rate change this size on a project with more than 60 hours behind it misstates more revenue than that.
- Opsium$114,000 of past revenue
Past hours keep the rate they were invoiced at: $114,000
- Runn Standard$126,000 of past revenue
The new rate applies to past hours too: $126,000
- Revenue you invoiced
- Revenue the rate change rewrote
How it works: revenue to date is hours worked times the bill rate. Runn's help says the updated rate "applies to both past and future work and will change the historical revenue calculation", so Runn reports the hours at the new rate. Opsium dates the change, so past hours keep the old one. The yearly price difference is each tool's monthly list price for your team, with its seat minimum, times 12. This is revenue your plan reports, not money you lose.
List prices as of October 14, 2026, billed annually. Hours, rates and team size are your inputs, and the starting values are examples.
Runn pricing in 2026: Lite, Standard and Advanced.
Runn charges per resource seat: each person on the planner. People who only log in are free, and so are placeholders. Runn's pricing page lists these prices per person per month, in USD.
| Plan | Billed annually | Billed monthly | What it adds |
|---|---|---|---|
| Lite | $7 | $9 | Scheduling, tentative projects, capacity and utilization charts, project budgets and rate cards. No timesheets, no API |
| Standard | $11 | $13 | Timesheets, the Jira and HR integrations, the API, saved scenarios (3 per user) |
| Advanced | Custom | Custom | SAML SSO, unlimited scenarios, resource requests, Harvest and Clockify sync on request |
| Opsium | $12 | $15 | Timesheet approvals, versioned rates, invoices and vendor bills in QuickBooks Online (two-way); 25-person minimum, onboarding included |
Every Runn plan starts at 20 seats, and the pricing calculator will not quote fewer. Volume discounts begin at 100 seats and are not published. Standard is the only plan you can buy on your own; Lite and Advanced go through Runn's team. The trial lasts 30 days.
There is no free plan for new customers. Runn retired it when the current tiers launched on December 1, 2025, and gave existing free accounts one more year.
Lite has no timesheets, so an agency that tracks hours should compare Opsium with Runn Standard at $11. Opsium is $12 per person per month billed annually, $15 billed monthly or $10 on a 2-year term, and onboarding and data migration are included.
Our seat minimum is 25. Onboarding is done by people on our team and included in the price, and that work doesn't pay for itself on a smaller team. Under 25, we would rather point you to Runn or a spreadsheet than bill you for empty seats.
What the extra $1 per person buys in Opsium.
At list prices, billed annually, Runn Standard is $1 per person cheaper than Opsium at every team size from 25 up. At 50 people it is $550 against $600 a month, a difference of $600 over a year, and at 100 people $1,100 against $1,200.
Below 25 the gap per person is wider, because Runn bills at least 20 seats and we bill at least 25: at 20 people Runn Standard costs $220 a month and Opsium $300. On a 2-year term Opsium is $10 per person, below Runn Standard's $11.
For an agency that bills by the hour, the extra dollar pays for:
- Timesheet approvals, with hours to invoice and hours to pay approved separately.
- Versioned rates, so a rate renegotiated partway through a project leaves last quarter's revenue alone.
- A change-aware planner that measures each day against that day's hours, role and rate, including changes scheduled for later.
- Invoices and vendor bills in QuickBooks Online, built from the approved hours, with status and balance synced back.
- Worklogs from Jira, Tempo or Clockify, synced in. In Runn, Jira time does not sync and Clockify needs the Advanced plan.
- Onboarding and data migration at no extra cost. Runn lists implementation services as "eligible" on annual Standard plans, with no published price.
Monthly cost by team size, billed annually
Runn Standard runs $1 per person under Opsium from 25 people up. Each tool's cost stays flat until the team reaches its seat minimum (20 for Runn, 25 for Opsium). Runn Lite is the cheapest and the only one without timesheets.
- Opsium
- Runn Standard
- Runn Lite
Opsium's columns use the annual rate and the 25-seat minimum, however small the team.
Show the numbers
| Team size (people) | Opsium | Runn Standard | Runn Lite |
|---|---|---|---|
| 10 people | $300 | $220 | $140 |
| 20 people | $300 | $220 | $140 |
| 25 people | $300 | $275 | $175 |
| 50 people | $600 | $550 | $350 |
| 100 people | $1,200 | $1,100 | $700 |
| 150 people | $1,800 | $1,650 | $1,050 |
Runn pricing page (runn.io/pricing). Opsium: opsium.io/pricing.
Planning ahead: both tools do it, and Runn saves scenarios.
Runn is known for forecasting, and it is good at it. Opsium plans ahead too:
- Tentative projects carry a win probability.
- Draft and unconfirmed assignments carry their own probability, from 1 to 99%, and you choose which statuses count toward utilization.
- Placeholders stand in for people you haven't hired yet, free of charge, and convert to the real person when they join.
- Forecasting lives in reports. Capacity, allocation and pipeline reports turn the plan into forward capacity, booked hours, probability-weighted pipeline hours, and forecasted revenue and cost, by month, department, role or client.
Where Runn is ahead is saved scenarios. On Standard each user can save three and switch between them to see how a set of tentative projects would land on capacity; they are private to the person who made them. Opsium has no scenario tool: you filter the one live plan by project status and probability instead.
Runn also compares each project's revenue with its budget. Opsium stores a budget on each project but does not track hours or revenue against it.
Opsium keeps planned, logged, approved and invoiced hours on one project.
At month end, finance wants to know why the invoice says 330 hours when the plan said 320. This example, with made-up numbers, shows where each tool keeps the answer.
A team is planned for 320 hours on a time-and-materials project and logs 352. Twelve of those hours were logged to the wrong project and get approved there instead, so on this project the manager approves 340 hours to pay. Another ten were rework the client won't be charged for, so 330 hours are approved to invoice, and the invoice goes out for 330.
| Number | Runn + accounting tool | Opsium |
|---|---|---|
| Planned: 320 h | Runn's planner | Opsium's planner |
| Logged: 352 h | Runn timesheets, a CSV import or the API (Jira worklogs don't sync) | Opsium time tracking, or synced from Jira, Tempo or Clockify |
| Approved: 340 h to pay, 330 h to invoice | Not in Runn, which has no approval step; past weeks can be locked | On each time entry, as two approved values |
| Invoiced: 330 h | Made in your accounting tool from a CSV export | Generated in QuickBooks from the approved hours |
In Opsium the four numbers sit on the same project: the assignment, the time entries, the approvals and the invoice, which takes its hours from the approval. The approvals screen shows tracked against booked hours for the period, so the 32-hour overrun is visible before anyone approves it.
Runn covers the first two rows. Because it has no approval step and makes no invoices, the decisions that turn 352 hours into 330 are made somewhere else, and someone builds the invoice by hand from an export.
From plan to invoice: which tool does each step
Both tools plan ahead and log hours. Opsium also approves the hours, keeps past revenue at the rate you billed, and creates the invoice and the vendor bill. Runn is ahead on saved scenarios and on budgets tracked against revenue.
| Feature | Opsium | Runn Standard |
|---|---|---|
| Plan people on projects, with tentative work | Yes | Yes |
| Forecast capacity, revenue and cost | Yes | Yes |
| Log actual hours | Yes | Yes |
| Jira worklogs arrive automatically | Yes | No |
| Approve hours before billing | Yes | No |
| Past revenue keeps the bill rate of the day | Yes | No |
| Create the client invoice | Yes | No |
| Create the vendor bill | Yes | No |
| Saved what-if scenarios | No | Yes |
| Track project budgets against revenue | No | Yes |
Runn pricing page and help center.
Versioned rates: past revenue stays what you invoiced.
Bill rates change partway through projects when a client renegotiates or a new rate card takes effect. In Opsium rates are versioned: a change is saved as a record with a date, so work already done keeps the rate it was billed at, and the invoices already in QuickBooks still match the revenue in your plan.
Runn's project rates article says that if a project's rate changes midway, "the updated rate applies to both past and future work and will change the historical revenue calculation." For rates that change every year, the suggested workaround is a new project each year. Bill rates are set per role, and Runn documents a workaround for person-based rates.
Cost rates work better in Runn: add a new contract with a start date and past costs stay as they were (editing the current contract instead can change them).
Say the senior developer rate on a project goes from $95 to $105 an hour on July 1 (illustrative numbers again). Runn recalculates June's revenue at $105. In Opsium June's work stays at $95 an hour, and the June invoice already in QuickBooks matches it. The calculator above shows what that does on a project of your size.
Opsium resolves each rate from several layers, each dated the same way: the organization default, seniority, role, the person, and the project (a flat rate, or a rate card with per-person overrides). A single assignment can also take a custom rate. Rates can be in different currencies, converted at the exchange rate of the day.
Runn's financials overview says its figures are "intended for planning and forecasting" and "may not exactly match your accounting or billing systems." If the revenue in your plan has to match what you invoiced, someone reconciles the two outside Runn.
The change-aware timeline planner knows what changes, and when.
In Opsium a change to a person or a project has a date of change, in the past or the future, and the planner reads the record in effect on each day:
- For a person: hours per day, role, seniority, department, manager, and cost and bill rates.
- For a project: status and probability, start and end dates, managers, billing model, budget and rates.
So when a developer moves to six hours a day from March, March's utilization is measured against six hours, not eight, and a marker on the timeline shows where the change lands. Someone leaving can be archived from a future date, and the planner shows that date.
Every person and project has a Change History tab: what changed, before and after, when, and whether a user or an integration made the change.
Runn dates a person's hours, cost rate and default role through contracts, and its Standard plan keeps a 30-day audit log. A project's bill rate is the part it does not date, as the section above shows.
Opsium approves timesheets and reads Jira and Clockify time.
In Opsium, people enter hours by date and project or run a timer, or they keep logging where they already do: Jira worklogs arrive by webhook, Tempo and Clockify entries sync in, and Opsium writes nothing back to those tools.
A manager works through timesheet approvals project by project and person by person, in bulk or entry by entry, and sets two values on each entry: hours to invoice the client and hours to pay the person. A Jira, Tempo or Clockify sync that would change an approved entry is skipped and flagged. People who under-track get a weekly and a monthly reminder, and time logged without an assignment is flagged.
Runn has timesheets on Standard and Advanced. People fill in a weekly timesheet, day by day or as a weekly total, and an admin can turn on a reminder that goes out every Monday.
Runn has no approval step. Its help article on approvals says "we do not have a timesheet approval feature just yet" and suggests locking instead: timesheets lock automatically after a set number of weeks, or a manager locks a project's timesheets up to a chosen week. Locking stops later edits, but an entry never gets an approved or rejected status (Runn suggests a timesheet note to tell people their timesheets were approved).
Bringing time in from other tools has limits on Standard. Runn's Jira integration imports projects and the people assigned to issues, but not the time logged against those issues. Harvest and Clockify sync one way, once a day or when someone runs the sync by hand, and only on Advanced, on request. Neither syncs bill rates.
Switching from Runn to Opsium: what to check first.
Runn bills every person on the planner, while we bill a person in a month when they are scheduled, track time, appear on an invoice or have access to Opsium. Placeholders, and people imported from integrations who are not actively managed, are free, and a contractor who sits idle for a month does not count that month.
One rule favors Runn: someone who only logs in to Runn, such as a finance lead, is free there, while in Opsium anyone with access to the platform is a paid seat. Count those people before you compare the two bills.
Check your accounting tool before you move, because Opsium creates invoices only in QuickBooks Online. The sync is two-way: invoices and vendor bills go out to QuickBooks, and status and balance come back. If your books are in Xero, you can still plan, track and approve in Opsium, but the invoices stay a manual job.
Runn does not refund partly used annual or monthly subscriptions, so time the switch to your renewal date.
Opsium is hosted on AWS in Frankfurt and data at rest stays in the EU. The few sub-processors outside the EU, such as error monitoring, are listed on our sub-processors page. We are not SOC 2 certified, while Runn hosts in the US or the EU and holds SOC 2 Type II. If either matters to your clients, our security page lists what we have done and what we have not.
The move itself is our work once you subscribe: onboarding and data migration are included. We import people, projects, rate cards and past time from your spreadsheets and exports, connect Jira, Tempo, Clockify, Google Workspace and QuickBooks, and set up your rates.
The free trial is 30 days with no credit card and starts with sample data or an empty organization; the import comes with onboarding, not the trial. Use it to rebuild last month for one of your Runn projects and check whether the approved hours match what finance invoiced. If you'd rather talk it through first, book a demo.
What people ask before switching.
If what you are missing in Runn is timesheet approvals, bill rates that keep their history and invoices created in QuickBooks, Opsium covers those, at $12 per person per month billed annually with a 25-person minimum. It plans ahead too, with tentative projects, draft assignments, placeholders and forecast reports. If you rely on saved what-if scenarios, stay on Runn.
Under 25 people our minimum would have you paying for empty seats, and a well-built spreadsheet may be enough: our free capacity planning template is a reasonable start. Our comparison of agency resource management software sorts the other tools by situation.
Runn Lite is $7 per person per month billed annually ($9 billed monthly), Runn Standard is $11 ($13 billed monthly), and Advanced is priced on request. Every plan starts at 20 seats, so the smallest Standard bill is $220 a month, billed annually. Timesheets start at Standard. Runn discounts from 100 seats but doesn't publish the discounted rates. These figures are from Runn's pricing page.
Because onboarding is included and done by our team. We map your people, projects, rate cards, time entries and history from your spreadsheets and exports, connect your integrations and train your team. That is real work, and on a smaller team the subscription doesn't cover it.
Under 25 people a spreadsheet often still works, and Runn's 20-seat minimum or another tool may fit better. We would rather say so than bill you for empty seats.
No, not for new customers. Runn retired its free plan when it introduced the Lite, Standard and Advanced tiers on December 1, 2025, and gave existing free customers one more year, so some legacy free accounts may last until about December 2026. New teams get a 30-day trial instead. The cheapest paid option is Lite at $7 per person per month billed annually, and with the 20-person minimum that is $140 a month.
An agency that bills by the hour runs into two limits that Runn's help pages describe: there is no timesheet approval feature (timesheets are locked instead), and a bill rate changed mid-project rewrites past revenue. Runn also creates no invoices and has no QuickBooks or Xero integration, time logged in Jira does not sync, and Harvest or Clockify sync needs the Advanced plan.
A team that only forecasts meets none of these limits, and for that team Runn Standard, at $11 per person per month billed annually with a 20-person minimum, costs less than we do.
Mostly, yes. Opsium plans ahead with tentative projects that carry a win probability, draft and unconfirmed assignments with their own probability, and free placeholders for people you haven't hired. Its reports turn that plan into forward capacity, booked hours, probability-weighted pipeline hours, and forecasted revenue and cost by month, department, role or client.
Two things differ. Runn has saved scenarios: you save sets of tentative projects as scenarios and switch between them, while in Opsium you filter the one live plan by status and probability. Runn also tracks project budgets against revenue, which Opsium does not.
Runn tracks actual time but does not create invoices. Time comes in through weekly timesheets (Standard and Advanced), a Chrome time-tracking extension (EU-hosted accounts only), CSV import, the API or, on Advanced only, Harvest and Clockify sync.
On invoices, Runn said in its help center that it "doesn't generate or track invoices and payments", and its 2026 pricing page lists no invoicing. It has no QuickBooks or Xero integration either, short of a Zapier or custom API build, so invoices are made in your accounting tool from an export.
Yes. Jira, Tempo and Clockify stay your time trackers: Jira worklogs arrive by webhook, Tempo and Clockify entries sync in, and Opsium never writes back to them. QuickBooks Online is two-way: Opsium creates invoices and vendor bills there, and status and balance changes come back. Google Workspace imports your people.
There is no Xero, Harvest, BambooHR or Google Calendar integration. If you depend on BambooHR for leave, or on Harvest (Runn's Advanced plan), Runn connects to those and we do not.