// riinda — how your team runs

live — core in production

Who’s carrying what, before someone breaks.

The work your team owes, with a name and a date on it. And beside it, the honest picture of who is buried and who can take the next thing.

the day it goes wrong

It lands on whoever answers fastest.

Work gets handed out in the hallway and in chat. Nobody holds the whole picture, so the next thing goes to whoever replies first — and that person is usually the one already carrying the most. You find out they were buried when something slips, not before.

what it does

Your team, looking inward.

// Every line below is running in production today.

  • Team tasks with an owner and a due date — including the ones that belong to no client: closing the month, updating the site
  • One view of the work: the team’s tasks and the CRM’s own follow-ups side by side, with a lens per person and per client
  • Load against capacity, person by person — who is buried, who has room
  • Every task with a life of its own: started, done, cancelled. Nothing is deleted
  • An attention inbox with AI triage that sorts by importance and can suggest who should take it

what it’s wired to

One view, without merging what isn’t the same.

// The CRM keeps its data and Riinda keeps its own — what they share is the screen, not the table.

The client’s follow-ups

The CRM’s activities show up in the same list as the team’s tasks, under a grant — read where they live, never copied.

Your judgement

The triage suggests and a person decides. Delegating on its own is a switch you turn on, and it has to earn it over a measured streak first.

which plan

Riinda ships with Scale.

The plans split by which stretch of the funnel they close end to end — Starter answers, Growth gets paid, Scale delivers. Running the team is what makes delivering repeatable, so it travels with Fiilz and Niima.

See pricing →

What it does NOT do yet

What is running today, and what is not:

  • Running in production: team tasks with owner and due date, the single view with the CRM’s follow-ups, load against capacity, and the triage engine with its policies.
  • The attention inbox is built — priorities, a suggested assignee, turning an item into a task. What isn’t built is the half that feeds it: no module files items into it yet, so today it opens empty.
  • Your client never sees Riinda — not from their portal, not by accident. It is the team looking inward.
  • It does not replace the CRM’s follow-ups. The two share one screen and keep their own data underneath.

// where the work comes from

A team that runs well still needs work coming in.

Miira answers and qualifies every lead over WhatsApp, day or night — so what reaches your team is already worth its time.

See Miira →