Book a demoStart free
I'm here as

The pager is automated. The planning isn't.

Collect availability once, generate a fair rota, publish it to PagerDuty, and hand payroll numbers nobody has to argue about. For the engineer who answers at 02:13 and the person who closes payroll on the 28th.

Start free — 5 people includedBook a 20-min demo
  • Keeps PagerDuty paging
  • Replaces the spreadsheet
  • Not an alerting tool

No credit card. No migration. Reversible: overrides, not a new source of truth.

On-call schedulePayments API
Week 47 · published
MONTUEWEDTHUFRISATSUN
PrimarySofia A.Karim B.Priya N.
SecondaryTom B.Priya N.Sofia A.
December period11 / 12 answered
Draft ready · fairness balanced over 8 weeks
November pay periodExport ready
14 interventions declared · 2 night, 1 weekend02:13 → 03:04 · declared by Sofia · approved

In pilot since 2026

Platform, payments and data teams of 6 to 40 people, in Paris and Lyon.

Placeholder quote
“The draft explained itself. I stopped getting pinged about the 22nd.”
Tech lead, payments platform
Placeholder quote
“First month I closed payroll without a single screenshot.”
People Ops, 120-person scale-up
Placeholder quote
“I answered once. My shifts showed up in PagerDuty. That's it.”
Backend engineer

A month of on-call, as it usually goes

Sound familiar? Six chapters. We've lived every one.

Chapter 2 of 6: Human Tetris

oncall_FINAL_v7 (2).xlsx· 3 people editing
BCDEF4Nov 20Nov 21Nov 22Nov 23Nov 245SofiaSofiaSofia / KarimKarim???6Tom—Tom?PriyaPriya7Karim: WEDDING 22nd DO NOT SCHEDULE (see tab "notes_old")8weekends so far: Tom 3 · Priya 0 · Sofia 2 · Karim 1 (is that fair?)
NovNov (old)notes_oldSheet14

Pricing

5 on-call people free.
€10 a month per extra seat.

A seat is someone who actually carries the pager. Admins, managers and HR who aren't on call don't count. €96 a year per seat if you'd rather pay once. Add or remove seats any time, prorated.

Start freeBook a 20-min demoSend this page to my lead →

What a 10-person team stops doing

  • One afternoon of the lead's month doing human Tetris~4 h
  • One People Ops email per intervention, plus the replies~14 threads
  • A folder named proof with 23 screenshots0 files
  • The 23:41 message about the 22ndgone

For 10 people: €50 a month. Less than one hour of the lead's time.

Who it is for

Engineers

Answer once. Then go back to work.

Mark the days you're out. The solver does the Tetris and shows its reasoning. Declare the page the morning after, in a minute.

Managers

Publish a rota you can defend.

Fairness over 8 weeks, not from memory. Swaps made in PagerDuty come back to you: adopt or revert. Periods open themselves.

People Ops

Pay-ready, without the screenshot hunt.

Declared working time, night and weekend rates, approved once per pay period. One export in your payroll format.

Send this page to my lead →

One loop, every month.
Nobody approves anything twice.

  1. Period opens

    Automatically, six weeks ahead.

  2. Draft

    Solved, with reasons.

  3. Publish

    Overrides written to PagerDuty.

  4. Declare

    After the shift, by the person.

  5. Export

    Approved once, sent to payroll.

# not an alerting tool, and we'd like to keep it that way

bettercallops→ availability · rota · publication

pagerduty→ detect · escalate · page

bettercallops→ declarations · payroll export

Next month's rota could publish itself.

Connect PagerDuty in 30 seconds, or start from scratch. Or let us walk you through it.

Start free →Book a 20-min demo