The operational side, on the same records as the build
Operations teams get boards of their own: tasks, payments, budgets and reminders, sitting next to the software tickets they depend on. The people who run the business stop asking developers for status, because the status is on their board.
A board per team, shaped the way it works
Start from Blank, Team tasks, Software progress or Payments & budgets, then set your own sections, a list or column layout and the widgets you want. A task carries instructions, an owner, a due date, an application and, where it depends on the build, a linked software ticket.
- Private by default; share with chosen people, a team or the whole workspace
- Operations tasks show up on each person's Home next to their tickets
- Board sections never change development stages
Boards never change development stages. Viewers read; only the owner changes sharing.
Invoices and budgets per application
Creating an Operations team sets up its Payments & budgets board once. Record invoices and budgets against the application they belong to, with partial and full payments and unpaid, overdue or void status. Import them over the REST API or through an agent, with your own external references so nothing is entered twice.
- Exact amounts in USD, AED, EUR, GBP and SGD, totalled per currency
- Everyone who can see the board sees the same figures, and viewers change nothing
- No accounting connector yet: entry is manual, by API or by agent
Totals stay separate per currency. There is no exchange-rate conversion and no accounting connector.
Follow-ups that arrive on time, in Slack or in the app
Personal reminders on a board, once, daily or weekly, in your own timezone and correct across daylight-saving changes. Tie one to a software ticket and it stops when that ticket closes. Slack reminders reach you through the Falrow bot.
- Pause, snooze, edit or delete at any time
- No burst of catch-up reminders after downtime
- A reminder is never queued twice
Tell your other systems when something changes
Admins send signed webhooks when tickets, projects or board records are created, updated or deleted, filtered by application, board, changed field or target status. Endpoints and signing secrets are stored encrypted.
- HMAC-SHA256 signature, timestamp and a stable event ID
- Public HTTPS only, no redirects, bounded timeouts
- An uncertain delivery waits for review instead of firing twice
No redirects, no private addresses. An uncertain send waits for an admin instead of firing twice.
Put the operational side on the same plan
Request access. We set up your Operations team, its first board and Slack with you.