Product

Recurring work checked where it happens

An obligation says what is owed, by whom and when. When it comes due, SaaS BPM reads the evidence from 9 kinds of source and asks a person only when no tool can tell. Every kept window keeps its receipt.

  • Sources10 kinds
  • AskedOnly when no tool can tell
  • KeptA receipt with a link
  • Late answersCounted against the manager
Receipts with the evidence for each kept obligation
Sample workspace, Northwind Studio. Every name and record in it is fictional.

On screen

Obligations and evidence in the product

Today shows only what needs a person

Missed twice in a row first, then the checks waiting on an answer. Everything kept and verified stays out of the way.

  1. 1 Kept, missed and open this week
  2. 2 The repeat misses, worth a conversation
The Today page
Sample workspace, Northwind Studio. Every name and record in it is fictional.

Every kept window has its proof

The receipt shows the message, the merged pull request or the moved task, with the minute it happened and a link to it.

Receipts with evidence lines
Sample workspace, Northwind Studio. Every name and record in it is fictional.

In detail

How an obligation is judged

  1. A window opens

    Each obligation has a cadence and a time. The window opens before it is due.

  2. The source is read

    The verifier looks for the evidence in the named channel, repository, project, calendar or inbox.

  3. A person is asked only if needed

    When no source can tell, the owner gets one question in the chat with Kept, Missed and Excuse buttons.

  4. The window closes

    Kept, missed, excused or unverified. Unverified counts against the manager’s follow-through.

  5. Why is one click away

    Every state explains itself, down to the message it found or did not find.

Sources of evidence

Checked where the work already happens

Connect the tools the team uses. An obligation names its source in the same sentence that creates it, such as in #client-acme or in owner/repo.

  • SlackA message in the right channel by the right person
  • GitHubA merged pull request, a release or a commit
  • AsanaA task moved or completed
  • JiraAn issue moved to done
  • LinearAn issue completed
  • Google CalendarA meeting held, not cancelled
  • Google DriveA document created or edited in time
  • GmailAn email sent to the right people
  • WebhookA signed call from your own system or a cron job
  • A personSomeone confirms in the chat, and a late answer counts against the manager

Questions

Questions people ask first

Anything else goes to a person, who answers in writing.

Do we need to connect every tool?

No. An obligation without a source is confirmed by a person in the chat. Connect a tool when you want it checked without asking.

Is this time tracking?

No. It records whether recurring work happened, never how long anyone was online.

Describe your company and see its week in a minute

Start free

Free for up to five people. No card, no sales call.