Terms and names

The unit you measure, such as seats, GB or API calls. It was called a variable component. The old name remains in API and field names such as variableType, variableSlug and variableId, and old dashboard addresses under /catalog/variables redirect to Settings, Meters. See Meter. The priced rule attached to a meter is still called a Variable Component.

A place you sell, with its own currency. It was called Markets. The dashboard page still lives at /market-config, and Markets survives in internal names such as the add-market screens. See Region.

The CRM list of companies you are talking to, formerly Prospects. The old /prospects address redirects to /companies. The API still says prospect: the public GraphQL mutation is createProspect. See the CRM guide.

A company that is billed. It belongs to one Region and can hold subscriptions. See Client.

A company record in the CRM. It becomes a client when it is billed; until then it is only a company you track.

A deal in flight on a pipeline, with a stage, a value and an owner. A lead is a deal, not a person. See Lead.

A person at a client or company, the human you write to. See Contact.

A versioned set of capabilities and meters. Modules are the building blocks. See Module.

A versioned package of modules sold at one tier, such as Starter or Enterprise. See Bundle.

The everyday word for what a customer buys. In the catalog that is a bundle (or a single module sold on its own); there is no separate plan object.

Every module, bundle and priced meter is a Draft you can edit, then Published, which freezes it, then Archived. A subscription pins the version it was sold on and stays there until you migrate it. A subscription left on an older version on purpose is grandfathered. See Versioning.

A plan you no longer sell that existing customers stay on. See Legacy pricing.

The earlier flat per-region price for a whole bundle or module. See Pricing rule and Scoped pricing.

A negotiated override for one customer. It wins over the catalog price. See Custom pricing agreement.

The signed agreement a subscription is sold under and the committed term it carries. See Contracts.

A bounded, reversible price reduction. Its target is the base price, one component (meter), or the whole invoice. A base-price discount is worked out once over all the base lines together. See Discounting.

Separates when a subscription is invoiced from what it costs, for example a prepaid term or a charge held until go-live. See Billing schedules.

A usage period closes at the end of the billing period. Sealing locks its final billable quantity, after which it can no longer change. See Metered usage.

One meter, one subscription, one closed period. It is Accumulating while late events can still arrive, Awaiting when you must enter a value, Unverified when nothing arrived (never billed as zero), Sealed once locked, and Waived when you release the invoice and bill nothing for it.

A document that gives money back against an invoice, used instead of voiding an invoice that collected payment. See Credit notes.

An append-only record of each moment that moves revenue, with its change in MRR. See Lifecycle event.

Two dates on a lifecycle event. occurredAt is when Revvly learned of it and is what timelines show. attributedAt is the period the movement is counted in; for metered usage it is the start of the service period, so usage lands in the month it was used. See Lifecycle log.

A CRM page of the tasks waiting on you and your accounts, so you can act on them in order.

Your own sorted view of your connected Gmail under Inbox, split into Primary, Needs reply, Other, Snoozed and Done. Private to you, admins included.

Signals about a client, drawn from email and activity, such as a conversation waiting on you or a contact going quiet. They sit under Clients and also show on the client.

The sidebar group for Documents, Forms and Templates. See Document library.

In the CRM, the email thread with a client. Not the same as a Support ticket.

One stretch of goals, usually a quarter. A cycle is Draft, Active, Scoring or Closed. See OKRs.

Where you want to go, in words, at company or team level. An objective is Committed, a promise that missing it is a failure, or Aspirational, a stretch where falling short is acceptable. Aspirational is the default.

How you will know: an owner, a unit (count, percentage or currency), a start, a target and a direction. The value is typed by hand or read from a Revvly metric.

A recurring prompt to post a value and a confidence from 1 to 10 on a Key Result. Delivered by Slack or ClickUp Chat. A separate daily check-in in Slack, not tied to a Key Result, is described in Run daily check-ins in Slack.

A set of questions Revvly asks chosen people in a Slack DM on working days, posting their answers and an end-of-day summary to a channel. Set up under Settings, Check-ins.

One request from a customer in Revvly Support, with a status, public replies and internal notes. See Support inbox.

The back-and-forth inside one ticket, as the end user sees it in your own chat. The ticket is the record; the conversation is how it is shown. See Support chat API.