Skip to content
Opsium
Sign InBook a Demo
Comparison

A Float alternative for agencies that bill by the hour.

Float (float.com) is resource management software built around a scheduling calendar. We make Opsium, so read this as a vendor's comparison; Float's prices and limits come from its own site and help center. We compare Float Pro, the plan with time tracking.

By Andrii Chernysh · CEO, Founder

16 min read

On this page1. Feature by feature16 min read
The short answer

For an agency that bills by the hour, Opsium is the better buy. Float schedules the work; Opsium plans it on a timeline that keeps every change on its date, then takes approved hours to the invoice.

  • $12 per person a month on both, billed annually; Opsium $10 on a 2-year term
  • Seat minimum: Opsium 25, Float none
  • 30-day free trial on both, no credit card
  • Opsium only: timesheet approvals, versioned bill rates, QuickBooks invoicing

Choose Opsium if

  • hours have to be approved before they reach a client
  • rates get renegotiated and past months must keep the rate you billed
  • people's hours, roles and rates change, and the plan should follow on the right date
  • month-end means building invoices and vendor bills in QuickBooks by hand
  • your developers log time in Jira, Tempo or Clockify

Choose Float if

  • you have fewer than 25 people
  • you need two-way Google Calendar or Outlook sync, or Slack notifications
  • you want project budgets tracked against logged hours
  • you need a public API or a SOC 2 report today

Feature by feature.

FeatureOpsiumFloat Pro
Price per person per month$12 billed annually, $15 billed monthly, $10 on a 2-year term$12 billed annually, $14 billed monthly. Starter: $7 / $8.50, no time tracking
Seat minimum25 people; hands-on onboarding by our team is includedNone
Free trial30 days, no credit card30 days on Pro, no credit card
Hosting and complianceAWS in Frankfurt, data at rest in the EU; not SOC 2 certifiedGoogle Cloud in the US; GDPR, and SOC 2 Type I per its Trust Center
Scheduling and capacityYesDrag-and-drop planner; each person's utilization per day, against that day's capacityYesDrag-and-drop Schedule with capacity, time off and over-capacity warnings
Change-aware timeline plannerYesChanges to people and projects take a date, past or future; the planner reads each day's hours, role and rate; change history on every member and projectPartlyWork hours, roles and cost rates change from a chosen date; bill rates don't
Planning aheadYesTentative projects with a win probability; draft and unconfirmed bookings with a probability; unlimited free placeholders; forecasted revenue and cost in reportsYes5 free placeholders on Pro, extras billed as seats; tentative and draft projects
Time trackingYesTimer with pause, or manual entry, plus hours from Jira, Tempo and ClockifyYesTimesheets pre-filled from the schedule, with auto-log and a mobile app
Timesheet approvalsYesBy project, person or entry; hours to invoice and hours to pay approved separately; syncs cannot change an approved entryNoNo approval step; logged time can be locked after a set period
Versioned ratesYesEvery level dated, from the organization default to each person and project; past work keeps the rate in effect on the day it was donePartlyCost rates are dated, bill rates are not; a project or phase rate edit reprices past time
InvoicingYesCreated in QuickBooks Online from approved hours; status and balance sync back. No XeroNoNo invoicing, no QuickBooks or Xero; NetSuite and Pegasus Edge via partners
Vendor billsYesCreated in QuickBooks Online at cost rates from the hours approved for payNoCost rates, but no bills and no QuickBooks connector
JiraYesWorklogs by webhook; issues, projects and people imported; nothing is written backPartlyNative integration is legacy; new connections go through Zapier
Project budgets and marginNoBudget stored on each project; nothing tracks hours against itYesFixed fee and fixed hours budgets tracked against logged time on Pro, with margin
Calendar syncNoNoneYesTwo-way Google Calendar and Outlook sync on every plan

Float Pro vs Opsium: what month-end really costs.

From 25 people, Float Pro and Opsium cost the same per person. The difference is the work Float leaves you at month end: building every client invoice and vendor bill by hand. Put in your own numbers.

50 people
15
20 min
$50 an hour

At 50 people, Opsium costs $250 a month less than Float Pro once month-end work is counted.

The subscriptions are the same from 25 people. Float Pro leaves you about 5 hours a month of building invoices and bills, worth $250 at your hourly cost.

  • Opsium$600 a month

    Subscription only: invoices and vendor bills are generated in QuickBooks from approved hours

  • Float Pro$850 a month

    Subscription, plus 5 hours of building invoices and bills by hand, worth $250

  • Subscription
  • Month-end work at your hourly cost

How it works: each subscription is the tool's list price per person times the people on the plan, and Opsium bills at least its seat minimum. Month-end work is the invoices and bills you build each month, times the minutes each takes, times your hourly cost. Opsium generates them from approved hours, so it counts no build time; you still review the batch before it goes to QuickBooks.

List prices as of October 14, 2026, billed annually. People, counts, minutes and hourly cost are your inputs, and the starting values are examples.

Float pricing vs Opsium: the same $12, with invoicing included.

From 25 people up, Opsium and Float Pro cost the same per person. The difference is what the price includes. Here are the list prices from Float's pricing page, next to ours:

PlanAnnualMonthlyTime tracking
Float Starter$7$8.50No
Float Pro$12$14Yes
Float EnterpriseOn requestOn requestYes
Opsium$12$15Yes, with approvals

Starter has no time tracking, so it can't tell you how many hours a project took. The plan an agency buys is Float Pro, at the same $12 as Opsium: $600 a month for 50 people, $1,200 for 100.

For that price Opsium also approves the hours, keeps versioned rates so past months stay at the rate you billed, and creates the client invoices and vendor bills in QuickBooks. Onboarding and data migration are included, done by our team.

On a 2-year term Opsium is $10 per person per month, less than Float Pro billed annually; Float publishes no multi-year price. Our pricing page also lists an Enterprise rate for 100 or more people, the size Float pitches its own Enterprise plan at.

Who counts as a paid seat differs. Float bills everyone on the Schedule, and Pro includes 5 free placeholders before extra ones are billed. Opsium placeholders are free and unlimited, and so are people imported from Jira, QuickBooks or Google Workspace whom you don't actively manage. Opsium bills anyone who is scheduled, tracks time, appears on an invoice or has access to the platform. Float lets people who aren't scheduled join as free guests.

Opsium has a seat minimum of 25, so below 25 people Float is cheaper outright. The minimum comes from onboarding: every plan includes hands-on setup by our team, who migrate your data, configure the account and train your people. That is real work, and for a team under 25 it doesn't make financial sense for us. So under 25 people, we'd point you to Float.

Monthly cost of Float and Opsium by team size, billed annually

At list prices, billed annually, Float Pro and Opsium cost the same from 25 people up. Below 25, Opsium's minimum holds it at $300 a month.

  • Opsium
  • Float Pro
  • Float Starter

Opsium's columns use the annual rate and the 25-seat minimum, however small the team.

Show the numbers
Team size (people)OpsiumFloat ProFloat Starter
10 people$300$120$70
25 people$300$300$175
50 people$600$600$350
100 people$1,200$1,200$700
150 people$1,800$1,800$1,050

Float pricing page. Opsium: opsium.io/pricing.

Opsium's planner knows what changes, and when.

Both tools plan on a drag-and-drop board, and both handle work that isn't certain yet. Float has tentative and draft projects. In Opsium a tentative project carries a win probability, and each booking can be confirmed, unconfirmed or draft, with draft and unconfirmed ones carrying a probability of their own. Placeholders stand in for people you haven't hired yet, and convert to the real person when they join.

What sets Opsium's planner apart is that it is change-aware. A change to a person or a project takes a date of change, in the past or the future:

  • For a person: hours per day, the billable split, role, seniority, department, manager, and bill and cost rates.
  • For a project: status and probability, start and end dates, managers, billing model and rates.

The planner reads the record in effect on each day. A developer who moves from 8 to 6 hours a day next month is planned against 8 hours until then and 6 after, and each person's utilization is worked out against that day's capacity. The board marks the days someone's details change, and when a person starts or is archived.

Every member and every project has a Change History tab: what changed, before and after, from which date, and whether a person or an integration made the change. Past records can be edited, and deleting one asks whether to extend the previous record or shift the next.

The plan also feeds the reports. Capacity, allocation and pipeline reports turn it into forward capacity, booked hours, probability-weighted pipeline hours, and forecasted revenue and cost by month, department, role or client.

Float applies a change to someone's work hours from a chosen date too, from the start of a week, and a role change takes an effective date. Bill rates are where the two part ways, as the section on versioned rates below shows.

Opsium approves timesheets; Float can only lock them.

In Opsium, a manager approves tracked time by project, then person, then entry, in bulk or one at a time. Each entry carries two approved values: hours to invoice the client and hours to pay the person.

Say a contractor logs 160 hours in a month. You approve all 160 for the contractor's pay and 152 for the client's invoice, with a note that 8 hours went on rework the client shouldn't pay for. The approvals screen shows the period's tracked hours against booked hours, the hours approved for invoice and for pay, and the income they add up to.

Approved means final. If a Jira, Tempo or Clockify sync would change an approved entry, Opsium skips the change and flags it, so the invoice still matches what the manager signed off.

Float Pro has no step where a manager approves or rejects hours. Its time tracking settings control "whether your team can log actual hours", "whether time is logged automatically" and "when logged time can no longer be edited". Managers can review and edit time on the Log team page and lock a period after a set number of days. Float's only approval step is for time off, so somebody still checks the hours before they reach a client, usually in a report or an export.

Both tools remind people about missing time: Float by daily or weekly email once you switch it on, Opsium with weekly and monthly reminders to anyone who under-tracks.

Versioned rates: past months keep the rate you billed.

In Opsium every rate level is versioned. A change is a record with a start date, and the old value stays in force for the days before it. That holds at every level: the organization's default rate, seniority and role rates, each person's bill rate and cost rate (hourly or salaried), and a project's flat rate or rate card. Each record keeps which fields changed and whether a person or an integration changed them.

Invoices use the rate in effect on the day the work happened, so renegotiating a rate never moves revenue you have already billed.

Float dates cost rates but not bill rates. Its bill rates article says so: "Unlike cost rates, bill rates do not support point-in-time effective dates." What happens on a change depends on where you make it:

  • A new bill rate on a person applies only to new projects and phases.
  • Updating a rate card updates every project that uses the card.
  • A change at the project or phase level "will apply to past and future time on that project or phase."

Suppose a time-and-materials project bills a developer at $100 an hour (the numbers here are made up), and the 400 hours logged so far were invoiced for $40,000. In July you agree $110 with the client from then on and change the project rate in Float. Float now values those 400 past hours at $110 each. The project shows $44,000 of billable work against the $40,000 you invoiced, and its margin to date goes up by $4,000 you never earned. In Opsium the first 400 hours stay at $100 and only new hours bill at $110.

You can work around this in Float by starting a new phase in July with its own rate, since a phase rate applies to that phase only, but every renegotiation then means a new phase. Float handles promotions in part: a role change takes an effective date, and a person who inherits their role's rates moves to the new ones from that day, but custom person, project and phase rates don't change.

Opsium works out which bill rate applies from six levels: the organization default, seniority, role, the person, the project (a flat rate, or a rate card with per-person overrides) and a custom rate on a single assignment. Rates can be in different currencies, converted at the exchange rate of the day the work was done.

Opsium creates invoices and vendor bills in QuickBooks.

At month end, Opsium does the part Float leaves to you. Pick a billing period and Opsium lists every project and every person who worked on it, priced from approved hours at the rates in effect when the work was done. Edit the hours or the rate on any row, add custom lines, and generate the batch. Each client's default payment terms carry onto its invoices.

Contractors are paid from the same hours. Opsium creates their vendor bills in QuickBooks too, priced at cost rates from the hours approved for pay. One approval feeds both documents, so the client's invoice and the contractor's bill can't drift apart.

The QuickBooks Online sync runs both ways. Invoices and vendor bills go out to QuickBooks, and edits you make in Opsium follow them. Each invoice's status (open, paid or overdue) and its balance come back into Opsium.

Float doesn't create invoices on any plan. Its page for teams leaving Harvest says: "We don't do invoicing, but we integrate nicely with finance tools that do." A help article on profitability says the feature "supports forecasting and monitoring but does not replace accounting systems." Float's integrations directory has no QuickBooks or Xero connector; the only finance systems it lists are NetSuite, through the partner Staria, and Pegasus Edge. With your books in QuickBooks, someone takes the logged hours out of Float through a report or the API and builds each invoice by hand.

Opsium needs QuickBooks Online for this: it doesn't produce PDFs, email invoices or collect payment, and it has no Xero integration. Float Pro is ahead on budgets. It tracks fixed-fee and fixed-hours budgets against logged time, and Opsium stores a budget on each project but doesn't report against it.

From schedule to invoice: which tool does each step

Float covers the planning steps, and Pro tracks budgets against logged hours. Neither Float plan approves hours or creates the client invoice or the vendor bill.

FeatureOpsiumFloat ProFloat Starter
Schedule people and see capacityYesYesYes
Log actual hoursYesYesNo
Approve hours before billingYesNoNo
Versioned bill rates, dated to when the work happenedYesPartlyPartly
Create the client invoiceYesNoNo
Create the vendor billYesNoNo
Track project budget against logged hoursNoYesNo

Float pricing page and help center.

Jira, Tempo and Clockify hours sync into Opsium.

Opsium reads Jira directly: users, projects, issues and worklogs. Jira sends new worklogs by webhook, so they arrive as they are logged. Tempo and Clockify sync people, projects and time logs too, and Tempo brings its assignments. All three are read-only: your developers keep logging time where they already do, and nothing is written back.

Google Workspace imports your people, and QuickBooks is the one two-way connection. When the same person, client or project arrives from two tools, Opsium merges them into one record.

Float's native Jira integration is now legacy. Its Jira help article says it is "available to teams that already have it connected", and new connections go through Zapier, which needs a Zapier account and, for some setups, a paid Zapier plan.

Float covers more of the rest of the stack. It syncs both ways with Google Calendar and Outlook, sends Slack notifications, and has a public REST API on every plan. Opsium has no calendar or Slack integration, and no public API yet.

Opsium flags unbilled hours and keeps salaries private.

Opsium watches for the mistakes that leak revenue before the invoice run. It flags an assignment booked at a zero rate and hours logged with no assignment behind them, and it reminds people who under-track every week and every month.

Rates are private by permission, and the server enforces it. Anyone without rate permission gets every rate field hidden in what Opsium sends them, so a project manager can plan the team without seeing salaries or cost rates. Roles are yours to define, with permissions you allow or deny for each group.

Each person carries a cost rate and a bill rate, each in its own currency, and is marked as in-house, partner or contractor, paid hourly or on salary. Custom fields on people and projects (text, numbers, dates, yes or no, and lists) filter the approvals screen, so a manager can approve one client's or one department's hours at a time.

Opsium keeps your data in the EU.

Opsium is hosted on AWS in Frankfurt and data at rest stays in the EU. Some sub-processors sit outside the EU (error monitoring, for example), and our security page links the full list. Float's privacy policy says the service runs on Google Cloud Platform in the United States, with EU transfers covered by the EU-U.S. Data Privacy Framework.

Float's Trust Center lists SOC 2 Type I, and Float states that it is GDPR and SOC 2 compliant. We are not SOC 2 certified yet; the same security page sets out what is on our security roadmap. If your procurement team requires a SOC 2 report, Opsium can't pass that check today.

Switching from Float to Opsium, with migration included.

Float charges upfront and doesn't credit or refund the difference when you downgrade or remove seats, so the cheapest moment to move is your Float renewal date.

Onboarding and data migration are included in the Opsium price from the day you subscribe. We import your people, projects, rate cards and, if you want the history, past logged hours from your Float data and your own spreadsheets, then set the account up with you and train the team. If you'd like to talk the move through with us before you start, book a demo.

Then connect what you already run: Jira, Tempo or Clockify start sending hours in, and QuickBooks brings in your customers and projects so invoices have somewhere to go. Google Workspace fills in anyone still missing.

Before you cancel Float, test Opsium on real work. The trial is 30 days with no credit card, so start the free trial when your Float renewal is a few weeks out, and choose a blank organization rather than the sample data.

We import your data after you subscribe, not during the trial, so set up one or two live projects yourself. Track a week or two of hours in Opsium (or let the Jira, Tempo or Clockify connection bring them in), approve them, and check the approved hours against what you'd have billed from Float for the same days. Opsium creates invoices in whichever QuickBooks company you connect, so generate them only once you're ready to bill from Opsium.

What people ask before switching.

Ready to take control of your operations?

Free 30-day trial. Cancel anytime.

Start Saving Time

Sign in to Opsium

Choose the workspace you want to open.

No account yet? Start a free trial