Revvly
Docs
Guide

Run your OKRs.

Revvly runs a quarterly goal cycle beside your billing data, so revenue Key Results read themselves from your subscriptions, invoices and usage instead of being typed in by hand. Write objectives, publish the cycle, check in weekly in the app or in Slack, show the ClickUp work behind each Key Result, then score and close with a comment that carries forward.

01Turn OKRs on

OKRs are part of your plan, and an administrator turns them on once for the workspace. Until then the OKR pages explain what is missing and offer the switch. Slack is optional: connect it now or later, and until you do, values are entered in Revvly. Nothing about your billing data changes when OKRs are on.

Where
  1. Org Settings
  2. Modules

Only an administrator can turn the module on. Anyone else who presses the button is told why it was refused.

02Set up a cycle

A cycle is one stretch of goals, usually a quarter, with a name, a start date and an end date. It begins as a Draft, where everyone in the workspace can read it and nothing is sent to anyone, so teams can write honestly. One cycle is live at a time; you can start drafting the next while the current one is still running. Creating and running a cycle belongs to the Cycle owner role, which an administrator grants, and administrators hold it implicitly.

Where
  1. Strategy
  2. OKR Cycle

03Write objectives

An objective says where you want to go, in words, and carries no number of its own. It is either a company objective or a team objective, owned by one person, and marked committed (we plan to hit this) or aspirational (we would like to). Cycle owners write the company objectives; a team lead writes their own team’s. Everyone else reads.

04Add Key Results

A Key Result is how you will know. It has an owner, a unit (a count, a percentage or a currency amount), a start value, a target value, and a direction, so “reduce churn from 5% to 2%” is as natural as “grow ARR from 480k to 650k”. Progress is always the distance travelled toward the target, capped at 100%, whichever direction the number is meant to move. Most Key Results are manual: the owner types the current value at each check-in. Local work like tech debt or a process fix does not have to ladder up to anything.

05Let a Key Result read itself

For anything revenue-shaped, pick a Revvly metric instead of typing a number. The Key Result then reads its own current value from your subscriptions, invoices, usage and pipeline, refreshes nightly, and shows its own trajectory against the target date, so nobody updates a spreadsheet on a Friday. Metrics available today: MRR, ARR, net revenue retention, monthly revenue churn, monthly expansion revenue, active subscriptions, receivables over 60 days, metered usage revenue for the month, and, for workspaces with the CRM, deals created in the cycle. A metric-backed Key Result skips the value question at check-in, so the owner supplies only confidence and a note. Metrics that read CRM data are hidden from workspaces without it.

06Get help writing it

Before you publish, an AI draft review reads the objective and its Key Results against a short checklist and tells you what to tighten: an objective should open with a strong verb, describe an outcome rather than a task and carry no numbers; a Key Result should name one exact metric, say the unit and which way is better, and have a baseline and a target. You can also talk a draft through with the coach, which reads each target in its own unit, so a percentage is discussed as 5% rather than a bare 5. Both read the short company description you keep in Settings, and only text a person saved there; nothing is pulled from your website into a review without someone approving it first.

Where
  1. Settings
  2. Business

Optional. Without a description the review still works, with less context about what your company does.

07Publish the cycle

Publishing takes the cycle live. Start values freeze at that moment, so “from 480k” can never quietly become “from 520k”. A target can still change when reality demands it, but every change records the old value, the new one, who made it and when, and the Key Result shows that history. Re-baselining mid-cycle is often the right call; it just has to be visible. Owners are told when a cycle goes live and when an objective or Key Result becomes theirs.

08Link team goals to company goals

Alignment is loose on purpose. A team links its Key Results to whichever company Key Results they serve: none, one or several. A link is optional, nothing is scored or rolled up through it, and a team with no links is fine. The Coverage page then shows the one thing a spreadsheet cannot: every company Key Result against every team, flagging company Key Results nobody picked up and teams whose Key Results link to nothing. Cycle owners also see a notice on the cycle page when company Key Results are uncovered.

Where
  1. Strategy
  2. Coverage

Also reachable from the command palette.

09Check in every week

Each owner posts a value and a confidence from 1 to 10, and a note. Confidence is separate from the value on purpose: a Key Result at 60% of target with confidence 9 is a different story from the same 60% at confidence 2. If confidence falls by three points or more since the last check-in, a note is required, because that is the one check-in the cycle owner most needs explained. A Key Result with no check-in for 14 days is flagged stale. Everything you owe is on one page. On an objective’s page, each Key Result shows the date of its last check-in, or for a metric Key Result the date of its last value. Click it to see that Key Result’s five newest check-ins, with value, confidence, author and note, under its row without leaving the page; when there are more, a link opens the full history on the Key Result page. A metric Key Result has no check-ins to list, because it reads its value from the metric each night.

Where
  1. Strategy
  2. My OKRs

My OKRs lists the Key Results you own with a Check in button on each open one, puts the ones owed a check-in first, and shows the objectives you own and the teams you are on.

10Check in from Slack

Connect Slack and the check-in comes to you. Once a week, at each person’s own local hour (Monday at 09:00 by default), Revvly sends a direct message listing the Key Results that are due, with a Start check-in button. It asks for the value, then confidence, then a note only when a drop in confidence needs one, and it understands loose numbers such as 528k, $528,000 or 12%. You can also use /revvly checkin, /revvly mine and /revvly status at any time. Nothing is sent to someone with nothing due, and nothing is sent unless the cycle is live. A redelivered message or a double click can never write two check-ins.

Where
  1. Settings
  2. Integrations
  3. Slack

11Check in from ClickUp Chat instead

If your team lives in ClickUp rather than Slack, an administrator can send OKR messages through ClickUp Chat instead. It is one channel for the whole workspace: while it is on, the weekly prompt, the daily reminder, scoring messages, the digest and the announcements all go to ClickUp, and Slack is used again if you switch it off. Each person is linked to their ClickUp account first. Revvly proposes the matches by email and an administrator confirms them, and someone with no link gets nothing through ClickUp. People answer by replying in the chat, with the same questions as in Slack: reply check in, then the value, then a confidence from 1 to 10. There are no buttons in ClickUp Chat, so each message says what to type, and outside a check-in Revvly only reacts to commands such as check in, status and mine and ignores everything else. Messages are sent as the ClickUp user who connected ClickUp, so connect it with a dedicated ClickUp user if you want them to come from Revvly. Revvly reads replies about once a minute, only in chats where it is waiting for an answer, and not inside a thread, so reply in the chat itself. Check-ins made this way are marked via ClickUp on the Key Result.

Where
  1. Settings
  2. Integrations
  3. ClickUp

Switch on Check-ins in ClickUp Chat once ClickUp is connected, pick an announcement channel if you want company-wide posts, and confirm who is who.

12Get one reminder a day, not a stream

If the weekly prompt is still unanswered, Revvly sends one short reminder each weekday after it, at the same hour, listing what is still owed. It chases a prompt and never starts one: a reminder goes only to someone the weekly message was actually delivered to in the last week, and only while a Key Result that message listed is still open, so a Key Result created or handed to you since is next Monday’s prompt’s to ask about. It stops by itself the moment you have checked in, is never sent on the day of the weekly prompt or on a weekend of your own calendar, and a reminder that failed to send is tried again later the same day. People can mute check-in messages, or pick their own day and hour.

Where
  1. Settings
  2. Notifications

Each person sets their own check-in day and hour here. The workspace default applies to anyone who has not.

13Show the work behind a Key Result

Connect ClickUp once and a Key Result can link the tasks that serve it by pasting a task link. The Work card on the Key Result shows each task stacked: its title, its status in ClickUp’s own colour, its list, assignees and due date, and how many subtasks are closed and open, by status. Revvly keeps a single note on each linked task in ClickUp saying which Key Result it serves, with the timeline, how much is left, confidence and a link back. It is edited in place rather than added to, so watchers are not pinged by every change, and when you unlink it is struck through and says who disconnected it and when. A task being done does not move a Key Result’s number, confidence or score: a person’s check-in does that, and a ticket board does not overrule it. Tasks refresh every thirty minutes, or on demand with the refresh button.

Where
  1. Settings
  2. Integrations
  3. ClickUp

An administrator connects ClickUp for the workspace. Anyone who can edit a Key Result can then link up to 25 tasks to it.

14Put a plan under each Key Result

A Key Result says where you want to be; a hypothesis says how you think you will get there. Each Key Result has a Hypotheses tab where anyone can write down a bet, and the people accountable for it rank the bets, state each test before running it and record what happened. The cycle view shows how many bets each Key Result has and how much of its gap the open ones could cover. Hypotheses have their own guide.

Where
  1. Strategy
  2. OKR Cycle
  3. a Key Result
  4. Hypotheses

See Test your bets with hypotheses in the guides.

15See what needs attention

Each week the cycle owners, and team leads for their own team when you choose to copy them, get a digest of what is stale, falling in confidence, unowned, unattached or failing to refresh, plus how many people were prompted this week and how many answered. A broken connection therefore reads as zero people prompted rather than a fortnight of silence. A digest with nothing in it is not sent. Cycle-level messages (a cycle going live, scoring opening, a cycle closing) go to the people they concern, and a target changing on something you own tells you.

16Score and close

At the end of the cycle the cycle owner moves it into Scoring. Every Key Result owner confirms a final value and writes a required comment, in the app or in Slack with /revvly score. The score is worked out from the final value and never typed in, and can be amended while the cycle is still scoring. Metric-backed Key Results are read once when scoring opens, so the value to confirm is where the metric stands now. Owners are nudged weekly until they have scored. Closing turns the cycle into a read-only record and refuses while Key Results are unscored unless you confirm it. The comment is the part that carries forward.

Life of an OKR cycle
  1. Draft
    Write it
    Everyone can read it. Nothing is sent.
  2. Publish
    Cycle goes live
    Start values freeze. Owners are told.
  3. Every week
    Check-ins
    Value, confidence 1 to 10 and a note. Stale after 14 days.
  4. Scoring
    Owners confirm
    A final value and a required comment for each Key Result.
  5. Close
    Read-only record
    Refuses while Key Results are unscored unless you confirm.
A cycle moves one way, from Draft to a read-only record, and the check-ins happen while it is live.

17What OKRs are not

Scores belong to Key Results, never to people. A person’s page lists the Key Results they own and does not average them, there is no per-person score summary, and a team’s Key Results are never rolled up into a company score, because contributions are not additive and weighting them invites gaming. Everything in a cycle is readable by everyone in the workspace; there are no private objectives. If something cannot be shown to the company, it does not belong in the OKR set.