Welcome to Roiva
What Roiva measures, how initiatives, costs and value fit together, and where everything is in the app.
Guides for running the portfolio, the concepts behind the numbers, and a reference to everything Roiva ships.
What Roiva measures, how initiatives, costs and value fit together, and where everything is in the app.
Create an initiative, record a cost, log value and approve it, to see an ROI number end to end.
What Home's Inbox rows mean, snoozing them, what search (⌘K) finds, what the bell notifies you about, and turning alerts off.
Invite people, what the Owner, Admin and Member roles can do, seat limits, single sign-on and two-factor.
Open the Assistant, what it can look up and change for you, approvals and permissions, conversations, usage limits, and where your data goes.
What assessments are, starting and resuming one, saving answers, recommended templates, editing answers, and the public AI ROI Exposure Assessment.
When a spreadsheet or warehouse build is enough, what one takes to build and run, where home-built trackers break, and what Roiva still leaves to you.
The stages from Identified to Completed, the buttons that move an initiative, and who can approve each step.
Why an initiative shows no value yet: the Setup tab, Missing Inputs, the Inbox, the Submit for Review warning and Home's Inbox rows.
What a template sets up, how to add one, and how to find the right one for your business.
Upload a brief, deck or spreadsheet to create initiatives, the register template and its columns, what Roiva proposes, and an initiative's documents.
What an implementation is, why an initiative needs them to split its costs, its types and statuses, adding one, and how a cost is attributed to one.
The activity feed, adding notes and replies, note types, resolving blockers and their flag, editing or deleting notes, and which notes reach Slack or Teams.
What needs approval, where approvals wait, who can approve, approval chains, delegation and the approval settings.
Deciding what to continue, scale, fix, pause or retire once an initiative is live, and how Portfolio Review keeps those decisions on a schedule.
What each ROI figure means, planned versus actual, the reporting period, and where to drill in.
The Portfolio Snapshot, Board Brief and Value Evidence Register, fiscal quarters, an initiative's review, what they count, and Export history.
Every way spend becomes an initiative's cost, where the same dollar can arrive twice, and what Roiva leaves out, counts anyway, or only suspects.
Record costs and log value by hand, set up recurring costs and vendors, import a spreadsheet, and planned figures.
What an initiative was approved to spend, how its budget is set and revised, who signs off an increase, and how Roiva checks it against the budget in your ERP.
Which vendors' bills book to an initiative, exact name vs contains matching, sharing a vendor, suggestions from your books, recurring costs.
Split a vendor's bills across initiatives with allocation rules, approve rule changes, and lock, reopen and reconcile a month, on any plan.
Where a value figure comes from: formulas, their inputs, when they run, assumptions and Roiva defaults, baselines, and why entries wait for review.
How a metric key is named, what a baseline and a reading are, and where Roiva gets a before-value when nobody wrote one down.
Metrics, baselines, readings, assumptions and value formulas: how Roiva calculates value, and what to record next.
Why a value figure still reproduces after the formula changes: versioned arithmetic, frozen inputs, declared units, and approval before anything counts.
Connect a platform (sign-in, API key, GitHub App or service account), what it brings in, and the sync schedule.
Why a connection books nothing until it's linked, the link each platform needs, mappings and allocation rules.
A connection's tabs, primary and summed sources, Sync Now, pausing, editing a key, Disconnect vs delete, Slack and Teams alerts, and calendars.
Feed a metric from Snowflake, Databricks or BigQuery with a SQL query: what it returns, how it's versioned, what Roiva keeps, how it stays read-only.
Let Claude Code, Cursor or another MCP client read your Roiva figures: tokens, setup, revoking and troubleshooting.
Troubleshoot a connection: its status, reconnecting, sync history, the platform's side, and synced data missing from ROI.
Every platform Roiva connects to: the roles a link can take, what a cost link books, and which metrics it feeds.
For every platform Roiva connects to: what a sync reads, which records Roiva keeps and which of their fields, and how long it keeps them.
Every metric key Roiva ships: what it measures, its type and unit, and which kind of connection feeds it.
Every value formula Roiva ships: what it calculates, its arithmetic, and the reading, baseline or rate each input comes from.
The rates, prices and cadences Roiva ships as defaults, each with the source it was taken from.
Every tool Roiva's MCP server serves an assistant: what each one answers and the parameters it takes.
Every endpoint Roiva's read API serves: what each one answers, the parameters it takes, and every field it returns.
Signing in, Google and Microsoft, two-factor and backup codes, password reset, requiring 2FA, single sign-on through Okta, Entra ID or SAML, and the audit log.
Plans and their limits, modules, upgrading, invoices and payment details, and canceling.
Exporting a table or the whole account, deleting an initiative, leaving an account, deleting yourself, and deleting the account.
Why ROI is $0, importing and exporting, deleting initiatives, visibility, SOC 2, what Roiva keeps from your systems, multiple accounts and the Assistant.
Roiva's own account holds these too, alongside your data and the setup steps for each platform. See a walkthrough.