Revenue Operations

OneBookPlus apps aren't external integrations stitched together with Zapier or n8n — they're native modules installed inside the same platform you already use for invoicing, bookings, CRM, and accounting. That means Revenue Operations reads from and writes to the same customer records, financial entries, and calendar events as every other module, with no scheduled sync delays and no risk of data drift between systems.

Because the marketplace runs inside OneBookPlus, billing is consolidated. Revenue Operations appears as a single line on the same OneBookPlus invoice as your plan, so you don't end up reconciling separate vendor charges across three or four different SaaS subscriptions. Cancellation is one click and never reaches into your data — uninstalling an app removes the feature from the UI but preserves the underlying customer, invoice, and booking records, so reinstalling later picks up exactly where you left off.

Every app in the marketplace is built specifically for the Australian small and medium business context: GST and ABN handling are first-class concerns, dates render as DD/MM/YYYY, currency defaults to AUD, and the underlying compliance plumbing (BAS summaries, ATO-friendly records, AHPRA / NDIS / Fair Work checkpoints where relevant) is shared across modules. New Zealand businesses are supported with NZ tax and timezone defaults using the same code paths.

For a side-by-side of which features ship as core modules versus which require an installed app, see the features page. For pricing across plans and which apps are bundled at each tier, see the pricing page.