Modules
Tools for everydaybusiness tasks.
Find the work modules that help prepare calls, conversations, invoices, operations, people, documents and decisions. Each one names its inputs, what it prepares and where your team decides.
The Nexus workbench · ten modules, one foundation
Module TELE: reception RIVA: customer conversations Crew: HR Books: receivables Helm: operations Saul: legal intake Strata: pricing Cortex: connected business information Ledger: activity record Pulse: live operating view Selection explains a module; it approves nothing.
Front office TELE Capture missed calls and prepare the next conversation.
Front office RIVA Keep customer conversations and follow-ups grounded in context.
Back office Crew Prepare repeatable people and onboarding work.
Back office Books Keep overdue invoices visible and prepare follow-ups.
Back office Helm Surface blockers before everyday operations stall.
Back office Saul Log incoming documents and route the decisions that need review.
Back office Strata Prepare quote context without publishing a price automatically.
Foundation Cortex Connect the context a workflow needs.
Foundation Ledger Keep a record of decisions and attributed outcomes.
Foundation Pulse See what is waiting, blocked, or ready for review.
Front office · reception
TELE Capture missed calls and prepare the next conversation.
Calls are logged with their reason and related context; callback and booking requests wait for approval.
← →
01 Inputs
What it reads Events: CallReceived · LeadResolved · FollowUpProposed
02 Preparation
What it prepares Call reason Related caller context Callback draft
03 Review
Where people decide Messages and bookings stay in review until your team approves them.
✓ Prepare Read permitted account activity and draft internal notes.
◷ Review Sending a message or booking a request requires approval.
⊘ Blocked Cannot alter contract terms or commit a customer externally.
Works with RIVA · Cortex · Pulse · Availability confirmed during scoping.
Front office · customer conversations
RIVA Keep customer conversations and follow-ups grounded in context.
Conversation threads, intent, and follow-up work stay connected to the customer history your team already has.
← →
01 Inputs
What it reads Inbox threads Customer profile Conversation history Events: ConversationOpened · IntentCaptured · FollowUpDue
02 Preparation
What it prepares Unified conversation Follow-up draft Review request
03 Review
Where people decide Outbound messages and review requests stay visible for human approval.
✓ Prepare Read permitted conversations and classify intent.
◷ Review Outbound messages and review requests wait for a human.
⊘ Blocked Cannot make refunds or change customer records without approval.
Works with TELE · Cortex · Ledger · Availability confirmed during scoping.
Back office · HR
Crew Prepare repeatable people and onboarding work.
Onboarding preparation can be organized automatically; employee-facing communication and scheduling remain reviewable.
← →
01 Inputs
What it reads Employee record Start date Policy documents Events: OnboardingCreated · ReviewDue · CertificationExpiring
02 Preparation
What it prepares Onboarding checklist Owner reminder Escalation draft
03 Review
Where people decide Employee-facing messages and scheduling stay with an owner.
✓ Prepare Create internal checklists and prepare reminders.
◷ Review Employee-facing messages and review scheduling require approval.
⊘ Blocked Cannot change compensation, status, or employment terms.
Works with Cortex · Helm · Pulse · Availability confirmed during scoping.
Back office · receivables
Books Keep overdue invoices visible and prepare follow-ups.
Invoice activity is organized into an aging trail; payment reminders and collection escalations pass through approval.
← →
01 Inputs
What it reads Invoice feed Account terms Payment history Events: InvoiceIssued · InvoiceOverdue · PaymentReceived
02 Preparation
What it prepares Aging trail Payment-reminder draft Collection-risk flag
03 Review
Where people decide Payment reminders and collection escalations require approval.
✓ Prepare Read invoice activity and update an internal aging trail.
◷ Review Payment reminders and collection escalations require approval.
⊘ Blocked Cannot move money, waive terms, or alter an invoice.
Works with Ledger · Cortex · RIVA · Availability confirmed during scoping.
Back office · operations
Helm Surface blockers before everyday operations stall.
Stalled work and blockers are summarized with the context an owner needs for the next step.
← →
01 Inputs
What it reads Work orders Ticket queue Service levels Events: TicketStalled · WorkOrderUpdated · BlockerDetected
02 Preparation
What it prepares Blocker summary Owner alert Next-step draft
03 Review
Where people decide Changes to priority, ownership, or service levels stay reviewable.
✓ Prepare Read queue state and prepare internal summaries.
◷ Review Escalations that change priority or owners require approval.
⊘ Blocked Cannot close work, change service levels, or delete a record.
Works with Crew · Cortex · Pulse · Availability confirmed during scoping.
Back office · legal intake
Saul Log incoming documents and route the decisions that need review.
Inbound documents are organized on receipt; anything needing legal judgment is flagged for a human by default.
← →
01 Inputs
What it reads Inbound documents Matter metadata Policy rules Events: DocumentReceived · MatterMatched · ReviewRequired
02 Preparation
What it prepares Logged document Matched matter Review route
03 Review
Where people decide Legal interpretation and external responses require counsel review.
✓ Prepare Log receipt and attach documents to a known matter.
◷ Review Legal interpretation and external responses require counsel review.
⊘ Blocked Cannot accept terms, sign, or send a legal commitment.
Works with Cortex · Ledger · Strata · Availability confirmed during scoping.
Back office · pricing
Strata Prepare quote context without publishing a price automatically.
Quote requests are logged and drafts are parked for human approval.
← →
01 Inputs
What it reads Quote request Catalog Account terms Events: QuoteRequested · PriceContextResolved · QuoteDrafted
02 Preparation
What it prepares Resolved context Quote draft Approval route
03 Review
Where people decide Quotes, discounts, and terms remain with an approver.
✓ Prepare Read catalog and account context for a draft.
◷ Review Every quote draft and discount requires human approval.
⊘ Blocked Cannot publish a price, change terms, or accept an order.
Works with Cortex · Ledger · TELE · Availability confirmed during scoping.
Foundation · connected business information
Cortex Connect the context a workflow needs.
Relevant events, records, and policy definitions are assembled into connected business information for each workflow.
← →
01 Inputs
What it reads Typed events Entity graph Policy definitions Events: ContextCaptured · EntityResolved · PolicyEvaluated
02 Preparation
What it prepares Connected context Policy evaluation Prepared proposal
03 Review
Where people decide New action paths and policy overrides require an operator.
✓ Prepare Resolve entities and assemble context for a decision.
◷ Review Policy overrides and new action paths require an operator.
⊘ Blocked Cannot execute external actions or bypass the event log.
Works with Pulse · Ledger · TELE · Availability confirmed during scoping.
Foundation · activity record
Ledger Keep a record of decisions and attributed outcomes.
Events, decisions, and operator-attributed outcomes remain traceable; the system does not invent ROI.
← →
01 Inputs
What it reads Event log Decision records Operator attribution Events: ValueAttributed · DecisionRecorded · OutcomeReconciled
02 Preparation
What it prepares Decision record Reconciled outcome Traceable history
03 Review
Where people decide Attributed outcomes are confirmed by an operator.
✓ Prepare Append immutable event and decision records.
◷ Review Value attribution changes require an operator’s confirmation.
⊘ Blocked Cannot rewrite history or invent a financial outcome.
Works with Cortex · Books · Pulse · Availability confirmed during scoping.
Foundation · live operating view
Pulse See what is waiting, blocked, or ready for review.
A live operating view surfaces workflow state and exceptions using real counts or honest zeros.
← →
01 Inputs
What it reads Live event stream Module health Ledger outcomes Events: MetricUpdated · ModuleStateChanged · GraphRefreshed
02 Preparation
What it prepares Operating view Exception signal Graph view
03 Review
Where people decide The view surfaces state; it does not change source records.
✓ Prepare Read live state and surface exceptions to operators.
◷ Review Dashboard annotations and shared views require approval.
⊘ Blocked Cannot change source records or represent missing data as fact.
Works with Cortex · Ledger · Helm · Availability confirmed during scoping.
START WITH THE WORK
Choose a task.Keep its context. Modules prepare different kinds of work. Each needs relevant information, a useful output and a clear review boundary.
01 Conversations
Prepare the next conversation. A call or conversation becomes a follow-up draft with the customer context attached.
TELE · RIVA Customer history Message review 02 Operations
Make the next operating step visible. Invoices and work orders need current records, a responsible owner and a prepared next step.
Books · Helm Account & work records Owner review 03 Documents
Connect information to the work. Relevant documents should be linked and understood before they shape a consequential decision.
Document context Source trail Human judgment