modules
CRM
Stop promising dates you can't keep — every commitment verified first.
Every broken delivery promise starts the same way: a rep quoting a date nobody verified. The customer hears confidence; operations hears a surprise. CRM inverts the order — inventory, capacity, and transit check first, and the customer hears a date the business has already proven it can meet. Trust stops being a gamble and starts being a process.
Why gated promises change sales
The most expensive sentence in business is a delivery date that cannot be kept. It burns trust, triggers expediting costs, and poisons the next negotiation. XRP moves the check to before the promise: inventory, production capacity, and shipping lead times verify first, and the rep quotes a date the system has already proven feasible. Behind the promise sits a complete commercial record — flexible objects with custom attributes, list views for every pipeline, record timelines showing every touch, and automation that routes, reminds, and escalates. Loyalty currency, offers, and campaign membership apply at promise time so the commercial terms are real, not reconstructed later.
data Viz
data View
section: thesis
CRM capabilities
- Verified promises
- ATP and feasibility gates admit commitments; refusals return earliest feasible dates
- Flexible objects
- Custom objects and attributes with list views, timelines, and value history
- Full opportunity path
- Open, qualified, solution fit, proposal, negotiation, commit, won — with lost and stalled handled honestly
- Loyalty economics
- Typed currency, balances, tiers, benefits, offers, and coupons on every quote
- Governed engagement
- Voice, video, and messaging sessions with consent preflight and recording policy
- Service rigor
- Cases with SLA, escalation, subrogation-style recovery tracking, and knowledge linkage
- section
- capabilities
Who answers for CRM
Four roles, four anxieties, one customer record answering each.
data Viz
data View
section: personas
Section 1
col Title: CMO
col Cont: Campaigns promise only what ATP proves, loyalty economics apply at quote time, and attribution reads from the same timeline sales works. Marketing spend stops funding apologies for dates operations never approved.
Section 2
col Title: VP Sales
col Cont: Reps quote dates the system already verified. Overrides carry authority and track outcomes, so coaching targets judgment instead of luck.
Section 3
col Title: COO
col Cont: Commercial demand arrives as verified commitments with reservations held — operations plans against promises instead of absorbing surprises.
Section 4
col Title: CIO
col Cont: Attio-class objects, lists, and automation without a separate CRM silo. Imports map with conflict policy and replay proof instead of CSV roulette.
From broken promises to kept ones
subtitle: What each stage feels like after adoption.
layout: alternating
enable Slideshow: false
slideshow Interval: 5000
Promises get gates
date: Phase 1
status: in-progress
Every customer date verifies against stock, capacity, and transit first.
has Learn More: false
Records unify
date: Phase 2
status: upcoming
Accounts, deals, cases, and conversations merge onto one timeline.
has Learn More: false
Loyalty pays out correctly
date: Phase 3
status: upcoming
Currency, tiers, and offers evaluate at quote time with balances checked.
has Learn More: false
Service remembers everything
date: Phase 4
status: upcoming
Cases resolve with full history attached; customers never repeat themselves.
has Learn More: false
CRM in daily operation
Each surface below runs on the same customer record — automation acts on live objects, AI reasons over timelines, and every touch writes back to the account.
data Viz
data View
section: applications
Automation Builder
Visual automation over objects, lists, and timelines: triggers on record change, conditions on attributes and ownership, actions across tasks, sequences, and webhooks. Every run records its inputs and outcomes against the affected records.
AI Engine
Deal scoring, next-action suggestions, and conversation summaries grounded in the account timeline. Model outputs obey participant consent and never override calibrated commercial values — they advise, owners decide.
Sequences and Campaigns
Outbound cadences with steps, waits, and branching on engagement. Replies route to owners with full context; bounces and opt-outs enforce themselves against consent records.
Meetings and Call Intelligence
Meetings, notes, tasks, comments, and call recordings attach to accounts and opportunities. Action items become tracked tasks; commitments link to the quotes and promises they affect.
Email and Calendar Sync
OAuth-backed mailbox and calendar sync threads messages into timelines without copies drifting. Send tracking, open events, and scheduling all write back to the canonical record.
Import and Migration
Notion, Coda, and Attio-class imports map objects, lists, and history into XRP with conflict policy and replay proof. Nothing lands silently — every imported row carries its source identity.
CRM sub-modules
subtitle: Commit carefully, serve completely — assisted or self-service.
data View: crm:sub-modules
Promise Admission
desc: No promise without proof.
link: /sub-modules/promise-admission
Sales and Service
desc: One record, every conversation.
link: /sub-modules/sales-service
B2B Portal
desc: Self-service ordering on contract terms.
link: /sub-modules/b2b-portal
CRM questions
Section 1
Where does CRM end and operations begin?
CRM owns customer and commercial-demand truth. Inventory, capacity, and fulfillment truth stay with their owners; CRM consumes them through gated checks.
Section 2
Can a rep override a refused promise?
Only through a governed override carrying authority, reason, and commercial acceptance of the risk. The override and its outcome stay on the record for review.
Section 3
How does loyalty interact with quoting?
Loyalty currency, tiers, and offers evaluate at quote time with balance and eligibility checks, so the price the customer sees already reflects what they have earned.
Section 4
What governs recorded calls and meetings?
Consent preflight per participant with downstream-use policy. Outputs obey recording consent, model governance, and retention rules before any transcript becomes usable evidence.
Section 5
Our reps will hate gated promises. How do we sell this internally?
Show them the win rate on verified dates versus hoped ones. Reps stop apologizing for missed deliveries and start closing with proof — commission follows kept promises, not hopeful ones.
Section 6
We live in Attio/Notion/spreadsheets. Is migration a rewrite?
No. Objects, lists, and history map with conflict policy and replay proof. Teams keep their pipelines while the record underneath gets honest.
data View
section: faqs
content section
value: A customer gets a consistent answer whether they talk to sales, service, or billing — because all three read the same record. Accounts, contacts, deals, quotes, loyalty, cases, and conversation history sit alongside orders, inventory, and invoicing.
Section 9
Promise admission with ATP, capacity, and transit verification
Section 10
Attio-parity objects, lists, attributes, timelines, and automation
Section 11
Quotes with pricing, loyalty currency, offers, and campaign linkage
Section 12
Opportunity state machines from open through commit to won or lost
Section 13
Service cases with SLA clocks, skill routing, and knowledge linkage
Section 14
Consent-governed voice, video, and messaging engagement sessions
Section 15
Churn-risk, lifecycle, and loyalty telemetry per customer
Section 16
Governed overrides carrying authority, reason, and accepted risk