Revenue

Revenue operations

Run the daily follow-up queue, keep prospect accounts structured, manage partnerships and formal documents, and migrate Base or CSV records safely. These workflows live under Revenue and use the same services whether a Member or an AI Employee does the work.

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.

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, 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.

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. 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.

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.

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 CSV migration

Open Revenue → Imports to move contacts, accounts, deals, or partnerships from a Genosyn Base or a CSV file:

Choose the resource type and source Base table or CSV.
Map source columns to native fields.
Run a dry run to see creates, duplicate matches, skipped rows, and the reason for every decision.
Commit only after reviewing the preview.

Every committed batch stores the field mapping, duplicate decisions, and source-row to native-ID map for reconciliation. Rollback deletes only records that are still safe to remove; anything that gained activities, contacts, deals, documents, or finance history is kept and reported as blocked.

Controlled values must exist before import.

Deal sources and partnership type/status are validated through the lists in Revenue → Setup. Add the values first or the dry run will tell you which rows cannot be created.

AI-native operation

Grant an AI Employee Revenue access from Revenue → AI access. Its granular tools can list the follow-up queue; create, assign, complete, and recur follow-ups; own and update accounts or deals; read and set typed fields; manage partnerships and contacts; link formal documents; and preview, run, reconcile, or roll back a Base migration.

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.

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.