How-to flows for common work.
Step-by-step walkthroughs for the things you’ll do most often. Each guide cross-references the concepts it touches.
Set up your workspace
Settings, people, seats, notifications and your own task list.
Configure your workspace
Every Org Settings tab in one line, then reporting currency, payment terms, working days, invoice header, AI spend, catalog learning, API keys and integrations in detail.
Add a team member
Invite a colleague into your workspace by email, choose their role, and let them set their own password. Manage roles and remove access from the same screen.
Set up teams, seats and invites
Invite people, watch your seat limit and ask for more, change roles, and group people into teams that OKRs and CRM pipelines can use.
Get notified: the bell, push and Slack
What puts something in the bell, how to choose what reaches you, install the app for push, and connect Slack or ClickUp Chat for OKR check-ins.
Work your tasks
Create tasks, read them as a table or board, clear the day in the Work queue, and create or close tasks as you send email. States plainly what a task reminder delivers today.
Catalog and pricing
Decide what you sell and how it is priced, per market, per client and over time.
Choose a pricing model
Flat, volume-tiered, graduated, stairstep, true overage, committed overage, commission, promotional — when to reach for each, with worked examples.
Launch a new Bundle
Add a versioned package to your catalog, pin its modules, ship a per-currency price, run the publish-gap check, and make it available to customers.
Price a component per scope
Global default, bundle override, module override, single-subscription override. How Revvly resolves which price wins at billing time.
Set up multi-currency billing
Sell in local currencies while keeping a single reporting currency. Exchange rates update daily.
Set advance vs. arrears billing
Choose whether a component invoices at the start of the period or the end, once usage is known. Override per product, per subscription, or per Custom Pricing Agreement — changes are always prospective.
Apply a flexible discount
Build a reusable discount template or a one-off, attach it to a base price or a component, choose how long it lasts and how it stacks with others, and preview the next invoice before saving.
Override base or component pricing
Replace the catalog-calculated base price, or write a subscription-scoped component rate, with an immediate-prorated or next-renewal effective date. No catalog guardrails — use a discount instead if you want a bounded, reversible reduction.
Negotiate a private deal
Write a Custom Pricing Agreement for one customer on one component. When it takes effect, what it overrides, how to revoke it.
Version, upgrade, grandfather
How Module and Bundle versions work, how Subscriptions pin to them, when to upgrade vs. grandfather existing customers.
Price a client on an older version
Create the version of a product as it was — last year’s prices, an older module set — and put a client on it. For customers who predate Revvly, or who keep the plan you were selling at the time.
Subscriptions and invoices
Create subscriptions, change and renew them, invoice, collect and correct.
Create a subscription
The four-step wizard from client and plan to first invoice, including backdated starts, excluded meters, custom prices and start-date regeneration.
Handle a mid-cycle change
Migration, plan change, or expansion — how to tell them apart, preview the proration, and choose between applying now or at the renewal boundary.
Bill a prepaid term or a deferred go-live
Sell a year upfront on one invoice, or sign months before the customer starts. What the span pays ahead and what still bills each period, where the prepay incentive applies, what activation does to the term, and what cancellation owes.
Sell a committed term
Record the contract a subscription is sold under — an annual commitment billed monthly, what happens when the term ends, and what leaving early costs. Attach it, roll it, or end it.
Run the renewal cycle
Calendar, approval queue, bulk decisions, dry-run preview — and exactly what Revvly applies at the renewal boundary: pending migrations, agreements, discount roll-off.
Capture metered usage
Close a metered period into a reading, seal it or waive it, and let the held invoice issue. Covers reading states, what an unreported period means per component, and the operator surfaces for working the queue.
Customize your invoices
Put your logo, company and tax details, banking and payment information, payment terms, and currency on every invoice — and see how Revvly numbers them automatically.
Collect tax on invoices
Register where you are liable, publish rates, describe each client's tax position and let Revvly add tax when invoices are issued. Covers the tax report and the ledger.
Collect what you are owed
Read receivables and the cash-flow chart, send invoices and reminders, record partial payments, reopen a paid invoice and send from a shared accounting mailbox.
Give money back with a credit note
Raise a numbered credit against an invoice, then either spend it on an open receivable or record the cash refund. What each state does to receivables and collected cash, and the two paths that raise one for you.
Import historical invoices
Bring billing history in from Excel or Google Drive, then rebuild the subscriptions those invoices imply so analytics reflect the full picture from day one.
Read the lifecycle event log
Every revenue-moving moment is an immutable event with native + reporting deltas. Here is how to query, filter, and reconcile the log.
Merge, delete and undo
Merge duplicate clients, delete clients and subscriptions, roll back an import batch, import invoice lines from a spreadsheet and resolve invoice discrepancies.
Sales and client work
The pipeline, your inbox, documents, forms and client folders.
Run your sales pipeline
Capture prospects — or import people and companies from a spreadsheet — raise deals, and work them across a drag-and-drop board, then convert a won deal into a billing Client. Notes, documents, emails, meetings, and tasks all land on one activity timeline.
Balance client work across your CSMs
See how many clients each customer-success manager looks after, split by status, and which clients have no manager. Work through the unassigned queue and move accounts between managers in one step; only the manager changes. Open to customer-success team leads and workspace admins.
Work your inbox
Your own sorted view of your Gmail: Primary, Needs reply, Other, Snoozed and Done, with the client beside each thread. Teach it where a sender belongs, snooze, reply and clear newsletters in one go, and set a daily digest. Nobody else sees it, admins included.
Reuse documents with the Document library
Upload proposals, decks, and contracts once, keep them current with versions, attach small files to an email, and send large ones as tracked links placed in your text, with a notification when they are opened. Files up to 100 MB are type-checked, and malware-scanned where scanning is set up, before anyone can use them; only admins change what your team sends.
Collect answers with Forms
Build a contact, demo-request or application form, share its link, embed it or build it into your own site, and have each submission create a lead, email your team, reply to the person and post to Slack. Covers publishing, submissions, CSV export and spam limits.
Keep client folders in Google Drive
Give each client and prospect its own Drive folder, file invoices, uploads and attachments there, bring files people add in Drive back to the client, and mark invoices in a folder for import.
See how clients use your product
Read what each client does in your product beside what they pay: who is active, which features they use, how long a visit lasts and how clients compare. Organise the event names your product sends, let the documentation suggest what they mean, set up browser tracking, and erase a person’s events. Open to people with the Product usage feature; admins organise events.
Support
Run the support inbox, the knowledge base, the AI first line and its guidelines, and add chat to your app.
Set up Support for your team
Support roles, ticket types and workflows, teams, agent and customer notifications, client updates and ClickUp task linking, webhooks, and a go-live checklist.
Work the support inbox
The views, filters and search, replying and internal notes with @mentions, taking and assigning, closing with a resolution and reopening, auto-close, attachments, a client’s tickets on the client page, and what each number on the Metrics page means.
Build the knowledge base the AI answers from
Add a help site, a document, or an Intercom or Zendesk help centre, say which roles and plans may read each article, clear the review queue, and keep sources healthy with re-reads, retries and the attention banner. Includes which source to choose.
How the AI first line works
How the support AI answers with cited sources, who sees which article, when it hands over to a person, its guardrails, the per-type and workspace switches and spending cap, what counts as a billable resolution, how to practise in the sandbox, and how to compare it with Intercom’s Fin on your past conversations.
Write guidelines for the support AI
Tell the support AI how to answer: the tone for each kind of customer, context your help articles leave out, when to ask a clarifying question, and which questions to leave to your team. What guidelines are, when to use each type, and how to add, scope, pause and test them.
Add a support chat to your app
Step by step from nothing to a working chat in your product: the settings to turn on, one backend token route, a complete chat script, testing and a go-live checklist. Includes a prompt you can hand to an integration agent.
Sign users in to the support chat
Mint a short-lived token from your backend for the user you have signed in, so your widget or app can chat with your support team as that user. Covers secret keys, claims and roles, refresh, revocation and verifying tokens yourself.
Push help articles to Support
Send the help articles that live in your own system to Revvly Support so the AI answers from them. Covers the knowledge key, adding and updating articles by your own id, stating who may read each one, removing articles, and keeping a source in step with a full refresh.
Goals and team rhythm
OKRs, the bets behind them and the daily check-in.
Run your OKRs
Plan a quarterly cycle, write objectives and Key Results, and let revenue Key Results read themselves from your billing data. Check in weekly in the app or in Slack, get a daily reminder while one is owed, link the ClickUp tasks behind each Key Result, then score and close.
Test your bets with hypotheses
Put the plan under each Key Result: write each bet down, rank it on reach, impact, confidence and effort, see how much of the gap the plan could cover, state the test before running it, and record the verdict in the app or in Slack. Learnings carry from cycle to cycle.
Run daily check-ins in Slack
Ask your team a few questions in Slack on working days, at one time or on each person’s own clock, post each answer to a channel as it comes in, and close the day with a summary of who answered, skipped or was away.
The Revvly Assistant
Ask in plain words, in the app or from Claude.
Work with the Revvly Assistant
Ask the in-product AI about your clients, subscriptions, invoices, and revenue — and have it draft new catalog and subscriptions for you, with a confirmation card before anything changes.
Connect Claude with MCP
Point Claude Desktop, Claude Code, or any MCP client at Revvly. Sign in with OAuth or send an API key, then ask about live billing data for one workspace — and propose writes that a signed-in human must approve in Revvly.
Integrate with your systems
API keys, the public API, usage, payments and webhooks.
Configure integration API keys
Set up credentials, scopes, signing secrets, and safe rotation for GraphQL, usage, event, and payment integrations.
Integrate with public GraphQL
Provision billing clients, read invoices and receivables, and choose the right mutation for clients versus prospects.
Report usage through REST
Apply usage deltas, absolute counts, commission events, or batches with idempotent server-side requests.
Ingest usage events
Stream metered usage from your application. HMAC signing, scoped API keys, deduplication, real-time counters.
Set up product event tracking
From nothing to each client's usage on their Revvly page: switch Product usage on, issue a key, set client External IDs, send events from your backend, and optionally add the browser script with a token route and allowed sites. Includes a prompt you can hand to an integration agent.
Mark invoices paid from your payment system
Post a payment the moment your processor or bank feed sees it — in full, or a part payment that leaves the rest outstanding and still chasing.
Send events out with webhooks
Post CRM lead changes to Zapier or your own server, and Support ticket events to your backend, with signatures you can verify, retries and a delivery log.
Reference resources by your own id
Set externalId at creation and report usage with externalSubscriptionId + variableSlug — never store a Revvly id. Plus the GET discovery endpoints for subscriptions and variables.
Send form prospects to Revvly
Map a form webhook to one public GraphQL mutation that creates a prospect, contact, and pipeline lead. Includes safe retry and validation examples.
More guides
Everything else.