notific.me

How it works

From request to proof, in four steps.

A request reaches the right person with its context, they answer with the proof it calls for, and the signed answer goes back to whoever asked.

Request early access

The path of a decision

  1. Someone asks

    A person from the web or the app, a system through the SDK, the REST API or an incoming webhook, or an AI agent through MCP. The request carries a title, the context and a card.

  2. The rules decide who

    The request names people, a group, or a group at an authority level. The organization's rules say who may decide, how many approvals it takes and what happens if nobody answers.

  3. The person answers

    On the phone or on the web, with the options at hand: yes or no, one or several options, text, number or date. The weight of the decision sets the proof, from a tap to biometrics or an authenticator code.

  4. The answer goes back

    The server accepts exactly one answer, signs the reply and delivers it to the code that is waiting or to your webhook. The work carries on, and the evidence trail keeps what happened.

Cards

The context comes with the request

A card shows what the person needs to decide without opening another system: metrics, tables, lists, charts, progress and buttons.

A purchase order approval in the web app with the order total, the budget left and a table of items.
A purchase order asked by the ERP: the totals, the items and whose decision it is.

Kinds of message

Not everything needs an answer

  • Notices

    Something happened and someone needs to know. It arrives with its card and is marked as read.

  • Decisions

    The sender waits for an answer. It has a deadline and a verification level.

  • Live cards

    One card that moves through its states, like a deploy going from building to live, instead of a new notification at every step.

  • Digests

    What is not urgent is grouped into a digest, so the important does not drown.

Digests

One digest instead of five dashboards

A scheduled report arrives as a card, with the numbers, the chart and what needs attention.

A daily finance digest in the web app with three metrics, a line chart and a table of items that need attention.
A daily finance digest sent by an agent: cash position, receivables and what is due.

Rules

Rules keep the noise down

Each workspace decides what happens to what comes in.

  • Notify now

    What matters reaches the right people right away.

  • Group into a digest

    Routine events wait for the next summary.

  • Raise the proof

    The organization can demand a higher verification level than the sender asked for, never a lower one.

Be among the first teams to use it

Tell us what you want to unlock. It helps us decide who to invite first.

Request early access