Features

FelagarAccount Pulse & automation

See company health with reasons, then turn the same signals into triggers your studio actually runs.

In practice

Account Pulse & automation

Account Pulse moves past a vague score. Each company gets healthy, attention, at risk, or critical, with explicit reasons drawn from overdue approvals, ticket age, budget burn, quiet days, stalled deals, and more. A curated trigger catalog lets you turn those same signals into actions: notify a user or team, create a task, send Slack, or call a signed webhook. Firings cool down so a sticky condition does not spam you every sweep.

Pulse answers what is going on with this client. Automation answers what should happen when the same condition fires. Both read one signal pass so health badges and trigger firings never argue.

Highlights

What stands out when this becomes part of how you run client work.

How it works

Pulse and automation share one signal pass. Configure triggers once; the worker evaluates them on a schedule.

  1. 01

    Open a company and read the Pulse badge plus the reasons list: waiting reviews, burn, quiet days, stalled deals, and more.

  2. 02

    In Settings → Automation, enable the triggers you care about and pick actions for each.

  3. 03

    Let the scheduled sweep evaluate signals across companies, or run a manual sweep when you want an immediate pass.

  4. 04

    Review firings and follow the linked work. Cooldown keeps persistent conditions from re-notifying every fifteen minutes.

We run the platform. You run the studio.

Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.