Revenue operations

Follow-ups

Open Revenue → Follow-ups for one chronological queue across deal follow-up dates, partnership follow-up dates, and task activities. Switch between Overdue, Today, and Upcoming rather than opening every deal to find what needs attention.

A deal carries a dedicated Next follow-up and optional reminder alongside its plain-language Next step. A follow-up task adds the task controls: due date, open/completed/cancelled status, Member or AI Employee assignee, priority, reminder, and daily, weekly, or monthly recurrence. Completing a recurring task creates the next occurrence automatically.

Filter by arbitrary assignee or unassigned, priority, resource type and ID, status, due-date range, age, Deal Stage/status, or closed Deals. Select rows to complete, cancel, reassign, reprioritize, or reschedule them together. For filter-wide dry runs and rollback, use Data quality → Bulk operations.

Prospect and customer accounts

Revenue → Accounts is the company record from first prospect conversation through billing and renewal. Create a prospect without creating an invoice, then keep the same record when it becomes a customer. Issuing its first invoice promotes a prospect to Customer automatically.

Firmographics

Domain, website, industry, employee count, headquarters, parent company, and account status.

Relationship

A Member or AI Employee owner, account notes, contacts, and open deals.

Finance

Billing details, ACV, invoices, contracts, and statements on the same Customer row.

Domain is normalized and used for duplicate protection. Contacts keep their free-text company name too, because a person's employer and the legal billing entity can differ. Accounts with linked Revenue or finance history cannot be hard-deleted; archive them so their timeline remains intact.

Typed custom fields

Open Revenue → Setup to add company-specific fields to contacts, accounts, deals, or partnerships. Fields can be text, number, date, yes/no, URL, single select, or multi-select. Mark a field required when every record must carry it.

Values are stored separately from notes and normalized for exact filtering, so product interest, current stack, company size, geographic requirements, competitor, procurement status, Stripe IDs, qualification signals, and custom tags stay reportable. AI Employees read and write the same typed values through Revenue tools.

Each current value also shows field-level provenance: source type and label, extraction method and observed date, confidence, verification state, verifying Member or AI Employee, and the number of earlier evidence records. Direct Member edits are verified writes. Imports and bulk updates carry stable batch or operation sources; unverified proposals must pass through the review queue before they can replace a current value.

Use Install Base migration fields in Setup or Imports to add the recommended definitions for current monitoring stack, competitor/current provider, product interest, infrastructure size, geographic/compliance requirements, Stripe customer ID, qualification score and signals, procurement/security status, and original Base row ID. The action is idempotent, so running it again does not duplicate definitions. Definitions can be renamed, reordered, required, or archived from Setup; their stable keys do not change.

Controlled classifications

Revenue → Setup also owns the controlled lists for deal source, buying committee role, partnership type, and partnership status. Each option has a stable machine value and an editable label. Deal source includes Self-Serve Upgrade by default. Archive an option to remove it from pickers without changing historical records.

Use these lists instead of free typing classifications. One inbound value with an Inbound label keeps reports whole; separate Inbound, inbound, and website strings do not.

Add, relabel, reorder, archive, or restore classifications in Setup. Deal Stages are managed there too: add and edit stages, change their forecast probability, reorder the board, and archive an unused stage. A stage with an open Deal cannot be archived until those Deals move elsewhere.

Formal document links

Contact, account, deal, and partnership pages carry a Documents panel. Link a proposal, RFP, security questionnaire, contract, email attachment, or other formal document as an uploaded file or external URL. The relationship is structured, so Members and AI Employees can find the right document without parsing a description field.

Signed customer contracts still have their dedicated Customers workflow. Revenue document links cover the wider pre-signature and relationship context.

Use the pencil action to change a document's kind, title, notes, or external URL. A linked file can be downloaded directly. Removing the document unlinks the Revenue record; it does not rewrite the source mail message or Base record the file originally came from.

Mail sync can also classify relevant attachments and queue reviewed links with source and hash provenance. See Revenue document capture.

Company-wide activity audit

Open Revenue → Activities to search activity subjects and bodies across the company, filter by kind and date range, inspect a row by its ID, or export the filtered history as CSV. Contact and Deal pages remain the fastest way to understand one relationship; Activities is the audit and cleanup surface.

Notes, calls, meetings, and task activities can be corrected or deleted. Mail, Deal Stage, Sequence, suppression, and Signal activities are immutable because reports and compliance use them as evidence of what the system did. Correcting a manual activity recalculates the linked record's latest-activity date.

Partnerships

Partnerships are not deals. Open Revenue → Partnerships for a partner-specific record with controlled type and status, a separate follow-up date, integration and channel context, notes, custom fields, documents, and its own activity timeline.

Add multiple Revenue contacts, choose one primary contact, and mark every address that belongs on Reply-All. Those explicit rules stop a partner conversation from silently dropping the technical, channel, or commercial stakeholder.

Base and file migration

Open Revenue → Imports to move data from a Genosyn Base or upload a .csv, .json, .jsonl, or .ndjson file directly. Genosyn inspects the source first and shows its fields and row count before any mapping or write. Use Linked Account + Contact + Deal when each legacy row contains all three:

1. Install the recommended migration fields, then choose the source Base table or upload a CSV, JSON, or NDJSON file.
2. Map the Account, Contact, and Deal fields from the same source row, including Deal Stage and Source when they exist.
3. Run a dry run to see creates, duplicate matches, skipped rows, and the result for each of the three resources. Every Deal decision shows the resolved target Deal Stage and Source. Changing the source, resource type, table, file, or field mapping clears that preview, so the committed rows always match what was reviewed.
4. Commit only after reviewing the preview. All three resources and their links are written in one database transaction.

The importer reuses an Account by normalized domain or name and a Contact by normalized email, then links the Deal to both. Rows from the same batch also reconcile with each other, so ten people from Acme create one Acme Account. The original Base row ID is written into the recommended custom field automatically. Choose Contacts, Accounts, Deals, or Partnerships instead when a source table genuinely contains one resource only.

Base select and multi-select cells are resolved from their stored option IDs to the labels shown in the Base before Revenue validates them. Deal Stage accepts an existing Deal Stage name; the common legacy labels Lead, Demo Scheduled, and Proposal Sent resolve to New, Demo, and Proposal. If Deal Stage is not mapped, the preview explicitly shows the default Deal Stage that will be used.

Every committed batch stores the field mapping, duplicate decisions, and source-row to native-ID map for reconciliation. Source IDs remain stable across retry and replay, whether they came from a source field, JSON object, NDJSON line, or CSV row. Open Report to page through decisions without loading the whole batch. For a Base import, Migrate attachments copies the source row attachments into Revenue Documents after the structured records exist; the pass is idempotent and reports failures separately. Rollback deletes the linked Deals, Contacts, then Accounts only when they are still safe to remove; anything that gained activities, documents, or finance history is kept and reported as blocked. The Roll back action always asks for destructive confirmation and records the outcome in the reconciliation report.

The history list loads summaries rather than every source decision. Open one Import ID for its mapping, page and filter the row-level decisions, or download reconciliation CSV/JSON. Historical Deal timestamps use the separate Historical Deal import.

AI-native operation

Grant an AI Employee Revenue access from Revenue → AI access. Its granular tools can administer custom-field definitions, classifications and Deal Stages; own and update Accounts, Contacts, Deals, and Partnerships; preview and merge every core record type with explicit conflict choices; resolve tombstone redirects; archive, restore, bulk triage, audit, reconcile, and undo; search and correct manual activity; manage Sequences and Signal definitions; inspect Deal-history coverage and the commercial-value backlog; review duplicate, domain, firmographic, commercial-value, and Gmail document evidence; export native and immutable Revenue datasets; and preview, run, reconcile, attach, or roll back Base, CSV, JSON, NDJSON, linked, and historical Deal migrations.

• Read exposes the queue, records, classifications, custom fields, documents, activities, and reports.
• Write allows the employee to perform the same service-backed updates as a Member. Every write is audited and journalled.
• A Base migration also requires access to the source Base, so a Revenue grant cannot be used to read an unrelated Base.
• Finance-derived proposals additionally require a Finance Grant; Stripe evidence requires a Grant to the chosen Stripe Connection; firmographic lookup requires a Grant to the chosen People Data Labs Connection; Gmail capture requires the relevant Mail Grant. Exporting Gmail document candidates also requires the source Mail Account ID and a read Grant to that exact mailbox. Revenue access never bypasses those boundaries.

A useful sales Routine

Give a sales AI Employee a morning Routine that reads overdue and today's follow-ups, checks the latest mail and deal activity, updates the next step, drafts the recommended outreach, and creates the next assigned follow-up. Sending still follows the Revenue and mailbox grant levels described in Sequences.