How RAZIO works, surface by surface.

Three ways in, all landing in the same place. Website forms post to a key-scoped intake API, so a form on your own site creates a lead without a middleware step. CSV and Excel import handles bulk lists, with de-duplication applied on the way in so a re-imported list merges rather than doubles. Manual entry covers the lead somebody met at a trade show.

Every new lead is routed to an owner automatically by the rule you set, so nothing sits in an unassigned queue waiting for a manager to notice it.

• Stored: contact details, source, owner, and a full activity timeline from the first touch.
• De-duplication: applied at import, on email match.
• Not included: lead scraping, purchased data, or an enrichment provider. Leads come from your forms, your lists and your team.

Today is the screen a rep opens first and, on a good day, the only one they need. It reads every active sequence, works out which steps are due, and produces one list: the calls and emails to do now, in order, with the context for each one attached.

The design rule is one action per lead per day. A lead with three overdue steps still shows once, because a list that shows the same person three times gets ignored. Actions can be filtered by type when a rep wants to batch calls or batch email, and each row has click-to-call and click-to-compose so nothing needs to be copied into another tool.

• Generated, not maintained: nobody builds the list. It is derived from sequence state each morning.
• Skipping is allowed: a skip needs a reason, and that reason is written onto the lead's timeline as the sequence advances. The rep who skipped cannot edit or delete it.
• Empty means done: when the list clears, the day's follow-up is genuinely finished, which is a thing a pipeline view can never tell you.
• Not included: a manager assigning tasks by hand. If you want a rep to do something, it belongs in a sequence.

A sequence is an ordered series of steps attached to a lead. Each step has a type (call, email or task), a delay measured from the previous step, and for email steps a template the owner can edit before it sends.

Advancement is driven by logged work, not by a timer alone. When a rep logs the call, the next step schedules itself. That is the difference between a cadence and a reminder: the sequence knows what actually happened.

• Breakup step: a final message that closes out a lead who never engaged, so the list stays honest rather than accumulating ghosts.
• Six-month re-queue: after a breakup, the lead comes back around automatically. Quiet is not the same as dead.
• Keep-in-touch cadences run against contacts rather than leads, for relationships that are not an active deal.
• Email sends from your own domain, verified by DNS, so replies land in your inbox and deliverability is yours rather than a shared pool's.
• Not included: broadcast email marketing, SMS campaigns, or a drag-and-drop automation canvas. Sequences do sales follow-up, one to one.

Qualifying is one action. It creates the account, the contact and the opportunity together, and carries the entire activity history across, so nothing is retyped and the record does not start from zero. The alternative, in most CRMs, is three creates and a manual re-link.

Opportunities move through stages on a board. Staged flows can require fields before a deal advances, which is how a manager enforces the difference between optimism and a forecast.

• Disqualifying keeps the record. A reason is required, and the lead moves to a disqualified view rather than being deleted, so the same company arriving again has its history.
• Views: active, closed won, closed lost, disqualified.
• Not included: commission calculation or territory management.

Proposals and invoices generate as branded PDFs from the opportunity itself, so the numbers on the document are the numbers on the deal. Files attach to activities, and every attachment, note, call, email and stage change appears on one timeline per record.

• E-sign for agreements, so a proposal can come back signed without a second product.
• One timeline across leads, contacts, accounts, opportunities and vendors.
• Not included: accounting. Invoices are documents, not a ledger, and RAZIO does not reconcile payments.

Four tools, all of them small and all of them inside a screen a rep already uses. There is no separate AI area to visit.

• Note Enhance: rough call notes become structured notes in your house style, with one-click undo. Undo matters, because a rep who cannot reverse it will stop using it.
• Email Polish: tightens a draft before it sends, in every composer.
• Attachment Summarize: reads a spec sheet or a long PDF and writes the summary into the record's notes.
• Lead Auto-fill: reads an inbound email and fills the record's fields, instead of a rep copying them across from the inbox.

Your data is not used to train models. Raz, a copilot that can answer questions across your whole pipeline, is the next thing being built and does not have a date. It is listed here because it is on the roadmap, not because it ships today.

The integration surface is deliberately small and covers the paths a sales desk actually needs: mail in and out, leads in, and events out.

• Outlook: two-way email and calendar sync, so appointments and replies stay in step whichever side you work from.
• Your website: the key-scoped intake API described above.
• Zapier and inbound webhooks: anything that can post a webhook can create a lead, with no custom code.
• Outbound webhooks: fire on the events you choose, so your own systems react when something changes.
• Import and export: CSV and Excel both directions, whenever you want, because leaving should work as well as arriving.

Roles are Owner, Manager and Member. Owners control the organization, managers see the team, members see their own book. Access is scoped by role rather than handed out wholesale.

Two separate things, worth keeping straight. A skip is written onto the lead's own timeline with its reason, and the rep who wrote it can never edit or delete it, which is what makes a skipped step a fact rather than an argument. The audit log is a different record, covering privileged actions: role changes, deletions, moderation, owner changes and reassignments, document lifecycle, payments, sequence changes, lead intake, imports, API keys and logins. It is append-only. An owner can moderate a timeline entry, and that moderation lands in the audit log too.

• Your branding: your logo on the sidebar and the login page, and your own domain on outbound mail.
• Your org, your data: multi-tenant with strict org scoping. Import it in, export it out.
• Modules are switched on per organization, not forced into everyone's bill.