Stop being the integration glue.
Syncs, broken automations, field requests, the Monday report. Custral takes all four off your week.
Sample week
Your tools disagree. Keep one record.
Every team reads the same account, and the tools you keep write onto it.
- Synced data lands on the record as linked tables.
- Rollups and formulas compute on read. Nothing to reconcile.
Retired on the way in: the second CRMthe helpdeskthe sequencerthe schedulerthe call recorderthe wiki
- Stage
- CustomerSales
- Owner
- MCMaya ChenSales
- Plan
- GrowthBilling sync
- MRR
- $4,200Billing sync
- Open tickets
- 3Rollup · Support
- API calls (30d)
- 1,284Usage · your product
- Customer health
- Steady74Grade
Usage lives somewhere else. Wire it in once.
Post an event from your product. Custral totals it on the account and grades the account.
const usage = new CustralUsage({ key, moduleId });
// where the unit is consumed
await usage.track({
productRecordId,
customerRecordId,
quantity,
});A publishable key, so the call can run in the browser.
Task “Kickoff call” created for Maya Chen.
Your automation broke overnight. Run it on the record.
Workflows, sequences and jobs read the records they write, so there's no hop between tools to fail.
Test a step on a real record first.
Wait for a reply, a booking or a pickup.
Work through every record a filter matches.
- SentFailed
- +5sFailed
- +30sFailed
- +2mFailed
- +10mDelivered
- +1hNot needed
- +5hNot needed
- +18hNot needed
What starts a run.
Every trigger that ships today.
Records
- Record Created
- Property Updated*
- Form Submitted
Conversations
- Email Received
- Email Replied
- Conversation Outcome
- Call Disposition
Website chat
- Widget Chat Started
- Widget Visitor Identified
- Widget Keyword Match
Sequences and jobs
- Enrollment
- Query Target
Property Updated watches a value you name. “Stage moved to Won” starts a run. An edit to some other field doesn't.
Every team wants a new field. Add it yourself.
Objects, properties and relations are yours to change the week someone asks.
- Try it in a sandbox, then go live or wipe it.
- Or ask Stella, your AI teammate, to build it.
- Every type: relation, rollup, formula, usage, grade.
| Name | Type | AI auto-fill |
|---|---|---|
| Name | Text | · |
| Stage | Select | Set up |
| Industry | Select | Enabled |
| Open tickets | Rollup | · |
| Net revenue | Formula | · |
| Customer health | Grade | · |
| Renewal riskNew | Select | Set up |
Monday's report, again. Build it once.
Dashboards and views read live records, so the numbers are current whenever someone opens them.
- Chart, table and metric blocks.
- Saved views per team, with sums in the footer.
- A sheet can look an account up by name.
Everything else ops owns.
Model any entity, with no dev sprint.
- ObjectsAccounts, deals, assets, vendors.
- Every property typeRelation, rollup, formula, currency and more.
- Computed fieldsFormulas and rollups recompute on read.
- RelationsOne edit shows in every view.
Runs on the records it reads.
- WorkflowsStart on a new record or a status.
- SequencesWaits, splits and exits on replies.
- JobsA filter, once or on a schedule.
- Action buttonsRun a workflow in one click.
Three integrations to keep, not thirty.
- Linked tablesSynced records mirror into objects.
- ImportCSV and Excel build the objects.
- Provider propertiesProvider data on the record.
- API and webhooksRetries for about 24 hours.
Upkeep you don't have to schedule.
- Stella, your AI teammateBuilds objects, edits views, queries data.
- Auto-fillFills a field on change or a schedule.
- Scheduled sweepsFiltered, and chained agent to agent.
- Required inputsSkips a run when inputs are empty.
- Approval firstWrites wait for your OK.
Built over live records.
- DashboardsCharts, tables and metrics.
- Saved viewsPer team, with inline edit.
- Column calculationsSum, average and count.
- TemplatesReuse a view on another page.
Control who sees and changes what.
- PermissionsObject, view, record or property, per person or team.
- Activity timelineChanges and touches, in order.
- Docs on the recordNotes, whiteboards, sheets and decks.
- SandboxesTrial a change in a copy first.
Questions ops leaders ask.
I have one tool that doesn't fit. Can I keep it?
Yes. The public API and webhooks connect the few worth keeping. The aim is three integrations to maintain, not thirty.
How does data sync between teams?
It doesn't have to. Sales, support, success and finance read the same records, so there is no second copy to sync.
Can I model our own objects and fields?
Yes. Create objects, pick property types, add formulas and rollups, and link records yourself. Start from a template, or from scratch.
Do I still need an automation tool in the middle?
No. Automations run on the records they read, so there's no webhook hop to break. The API and webhooks handle anything outside Custral.
What exactly can start a workflow?
Every trigger in the list above. Property Updated watches for a value you name, rather than any edit to any field.
Can I test a schema change before it's live?
Yes. Try it in a sandbox, a test copy of your workspace, then go live or wipe it.
Is there a migration tool?
Yes. Import the CSV or Excel export from your current CRM, and check the column mapping before it runs.
Your company runs on what you build.
Plan which tools to retire, which to keep, and in what order.
Plans from $39 a seat a month, billed annually. See pricing