Questions, answered

The questions operations teams usually ask before trying a new tool — answered plainly. Each answer below is published content the owner maintains, and a clearly labeled synthetic fixture.

We already live in chat and spreadsheets. Why add another tool?

Chat is where operations happen by accident. SignalDesk keeps the sequence — what happened, what was decided, who is next — on one timeline your whole team can read later, instead of an argument scattered across threads and sheets. It replaces the spreadsheet you keep meaning to tidy, not the chat you keep.

Do we need an engineer to set it up?

No. A workspace is ready when you sign up: invite your teammates, write your first runbook, and forward your first alert. There is no infrastructure to deploy and nothing to install on your servers.

What happens to our data if we leave?

Your workspace is yours. You can export your timeline, runbooks and rota at any time, and deleting the workspace deletes the data with it. There is no export fee and no notice period.

Is the free plan actually usable, or a demo?

Crew is the real product on one workspace: up to three operator seats, the timeline, runbooks and the signals inbox, free for as long as you like. You only pay when a second workspace or a bigger rota is worth money to you.

Can we change plans later?

Yes. Move up when your rota outgrows its seats, and back down at the end of a billing period. Plan changes take effect from the next period; nothing is prorated mid-cycle.

Who is SignalDesk actually for?

Small operations teams — two to fifteen people who keep a service running: support rotations, infrastructure on-call, fulfilment, studio operations. If your team keeps incidents in chat and the rota in a spreadsheet, it is you.