The pipeline that updates itself.
Reps stop logging activity. Stages move from the call, the email, the contract send, and the implicit signal that a champion left for a competitor. The forecast is what actually happened, not what someone hoped.
Five things, and only five.
CRM is built on one belief: reps will not enter data, and asking them to is a tax on revenue. We solved that by reading the data directly.
Email, calls, meetings, deck shares, contract sends. Pulled in automatically and linked to the right deal.
"Sent eval doc" moves the deal to Eval. "Procurement included on a thread" moves it to Procurement. No rep clicks required.
If your champion stops opening your email or leaves the company, the deal is flagged. The reason is named, the next play is suggested.
Forecast is rolled up from real signal velocity, not commit categories. Last-mile rep overrides are tracked and graded by accuracy.
Quote, redline, sign, and provision from the same record. No round-trip to a separate CPQ. Contracts is the back end. Tasks owns the handoff.
Three steps. No data entry.
Reps spend a day a week in admin. We replace that with three automatic loops that run every time a signal hits the workspace.
Ingest from every surface
We tail your mailbox, calendar, dialer, LinkedIn, and contract tool. Events arrive automatically. The resolver attaches them to the right contact, deal, and account.
Promote stages from signal
The classifier ships each event through a rule plus model layer. High-confidence transitions are automatic. Low-confidence ones are queued for a one-tap confirmation from the rep.
Forecast updates per signal
Every signal nudges the forecast. The commit and best-case are derived from signal velocity, not commit color codes. Rep overrides are tracked and accuracy-graded.
Six features that compound.
Each below is shipping today. None require a separate plan or a separate tool to bolt on.
Account graph
Companies, contacts, parents, subsidiaries, and inherited account-level fields. Resolves shared email domains and aliases.
Plays library
"Champion gone" play, "stalled in legal" play, "MQL to AE in under 4h" play. All trigger from signal, not from cron.
One-touch decks
Generate a buyer-specific deck from the live account state, the past 3 calls, and the pricing config.
Quote and sign inline
CPQ-grade quote, approval routing, redline diff, and signature. No round-trip to a separate vendor.
Territory and access
Row-level permissions by region, segment, ICP. Federated SSO.
Pipeline analytics
Cohort-by-source funnel, stage velocity, win-rate by champion type. No separate BI required.
Wired into revenue.
CRM is the spine of the GTM stack. Six modules feed it and read from it.
Six surfaces all read the same deal
An email opens a thread in Inbox. The thread links the deal. The meeting attaches the transcript. The contract attaches the redline. The task chases the procurement step. Analytics reads the same row.
Programmatic pipeline.
Subscribe to stage changes. Push deals from your own systems. TypeScript shown.
// Stream every stage change in your pipeline, in real time. import { Wrx } from "@wrxstack/sdk"; const wrx = new Wrx({ token: process.env.WRX_TOKEN }); for await (const ev of wrx.crm.stream({ object: "deal" })) { if (ev.kind === "stage_change" && ev.to === "Procurement") { // Auto-spin a contracts workspace, attach last MSA, ping legal. const contract = await wrx.contracts.spawn({ deal: ev.deal_id, template: "MSA_v3", reviewers: ["legal@acme.com"] }); await wrx.tasks.create({ title: `Procurement: ${ev.deal.name}`, links: [{ kind: "contract", ref: contract.id }], due: "+3d" }); } } // Or push a deal in from your own data layer. await wrx.crm.upsert({ object: "deal", external_id: "sfdc-006XYZ", account: "acmerobotics.com", amount: 184_000, stage: "Eval" });
CRM vs. Salesforce.
Salesforce is a database with workflows. wrxstack CRM is a graph that updates itself.
wrxstack CRM vs. Salesforce
| Capability | Salesforce | wrxstack CRM |
|---|---|---|
| Activity capture | Add-on (Einstein Activity) | Native and automatic, no add-on |
| Stage transitions | Rep clicks the picklist | Signal-derived w/ confidence |
| Champion tracking | Custom field | Built-in, flagged on departure |
| Forecast model | Commit categories | Signal-velocity model |
| Quote-to-cash | CPQ add-on | Native, in the deal record |
| Time to first value | Months of configuration | Connect your tools and go |
| Admin burden on reps | Manual logging every week | Auto-captured from real activity |
Common questions.
Six things heads of revenue ask in their first call.
Can we run dual-write with Salesforce during migration?
Yes. The dual-write connector mirrors deals, accounts, contacts, and activities. Conflicts resolve per rule. Dual-write can run through your migration window, then you cut over. Migration history (won deals, stage transitions, owner changes) is preserved.
How does the signal classifier decide what moves a stage?
A combination of rules and a domain-tuned classifier. Rules cover deterministic moves (contract sent, signature). The classifier handles fuzzy ones (legal cc'd, procurement language). Every transition is reversible and audited. Reps can disable auto-promotion per pipeline.
What about custom objects, custom fields, and process builder logic?
Custom objects and fields are first-class. We support inheritance, formula fields, and validation rules. The workflow engine handles approvals, escalations, and time-based triggers. Existing process-builder logic ports without a rewrite.
How is the forecast actually computed?
Per pipeline, we fit a velocity model on the last 8 quarters of historical signal-to-close transitions. The forecast is a Monte Carlo over open deals, weighted by their current signal density. Commit and best are p50 and p80. Rep overrides are tracked separately and scored for calibration over time.
Do you support territory, segmentation, and team rollups?
Yes. Territories are typed with rules (region, segment, ARR band, named accounts). Rollups respect group membership. Field-level masking is available per role. Row-level enforcement is applied on every read.
What happens when an account is acquired, merged, or split?
The account graph supports parent, subsidiary, and merger edges. Open deals reconcile automatically when a merge is recorded. Closed-won history is preserved at the original entity. Reports can roll up across legal entities or hold them separate, your choice per workspace.
Pairs well with.
CRM is sharpest with Inbox, Meetings, and Contracts in the same workspace.
Who this is not for.
CRM keeps your pipeline current without data entry. If you need a full sales-engagement platform with a built-in dialer, multi-step outbound sequences at scale, and territory and quota management, a dedicated CRM will fit better. CRM is for teams that want the record to stay accurate, not a large revenue-operations build-out.
Stop paying reps to enter data.
Free to start, no credit card. Connect your Gmail, calendar, and dialer in 10 minutes. The first auto-captured deal lands the same day.