Billing and plans

EngLedger is priced per tracked person. Each plan includes a set number of people; if a month's activity involves more people than the plan includes, the difference is billed as overage. There are no seats to assign and no licences to shuffle. The count comes from the work itself.

What you're billed for

Plans come in three tiers (Starter, Growth and Scale) billed monthly or yearly in AUD, each with a ceiling of included tracked people. Current prices and ceilings are shown on the Billing page in the app. Larger organisations can talk to us about an enterprise arrangement instead.

A person counts towards a month when their work produced effort in that month: a commit, a pull request, a worklog that became an effort entry. Someone on leave for the whole month doesn't count for it. Someone whose historical work is in EngLedger but who left last year doesn't count either. The number on your invoice is the number of people whose work the ledger actually recorded that month.

Overage

At the end of each month, EngLedger counts the distinct people with effort in that month. If the count is at or under your plan's ceiling, nothing happens. There's no overage line at all. If it's over, each person above the ceiling is billed at a flat per-person rate, invoiced through Stripe alongside your subscription.

The Billing page keeps a running history of these monthly counts, so the overage line on an invoice is never a surprise. You can see the count that produced it, month by month.

If your team is consistently over the ceiling, moving up a tier is usually cheaper than paying overage every month. The history makes that call easy to sanity-check.

The 14-day trial

New organisations start on a free 14-day trial. No credit card is asked for at signup. A billing record isn't created until you choose a plan. The trial clock starts when you connect your first integration, not when you create the account, so time spent reading around before connecting anything costs you nothing.

Trials sync a recent slice of history, enough to see real reports with your own data. When you upgrade to a paid plan, EngLedger automatically runs a full backfill to your plan's history window; you don't need to reconnect anything.

As the trial nears its end you'll see reminders in the app and by email. When it expires, sync pauses. See the next section for exactly what that means.

Managing your plan and payment method

Admins manage billing from the Billing page: choosing a plan goes through Stripe Checkout, and everything after that (changing the card, updating billing details, viewing invoices) goes through the Stripe customer portal, reached from the same page. EngLedger never stores card details itself.

For who can see and do what, see users, roles and access.

When a plan lapses

If the trial expires, or a subscription is cancelled or paused, three things are true:

• Sync pauses. Scheduled syncs skip the organisation and integrations show as Paused on the Integrations page. New commits, tickets and worklogs stop arriving.
• Nothing is deleted. Every report, effort entry and historical record stays exactly where it was. You can keep reading your data; it just stops moving.
• The app tells you. A dashboard alert says sync is paused and links straight to the Billing page.

Reactivating is the same flow as subscribing: pick a plan on the Billing page and complete checkout. The plan takes effect immediately and sync resumes on the next scheduled run (within about half an hour) picking up where it left off. Data that changed at the provider while the plan was inactive is caught up by the normal sync process.

Where billing questions usually land

• "Why did my count go up this month?" More people's work produced effort entries that month. The effort model explains what counts.
• "Sync stopped. Is it billing?" Check the Billing page first; the troubleshooting guide covers the other causes.
• "Do read-only stakeholders cost anything?" No. Logins aren't billed; tracked people are. See users, roles and access.