Custom CRM and process automation with Cadrant

Generic CRMs force fields, statuses, and workflows that don't always match your company's real vocabulary and processes. Teams end up working around the tool, entering data in misused fields, or maintaining a parallel spreadsheet. Cadrant lets you start from the **real process** — sales stages as they actually exist, follow-ups, support handoffs — then layer data and automation gradually, without sacrificing relevance.

Why custom CRM beats generic tools

A generic CRM works if your sales cycle is standard: prospect, qualify, propose, close. But as soon as your process involves specific stages (technical validation, field trial, buying committee), the generic CRM becomes a constraint. A custom CRM with Cadrant adapts to your vocabulary, your stages, and your business rules — not the other way around.

• Aligned vocabulary: your stages, your fields, your labels — not the vendor's.
• Iteration flexibility: add a field or stage in minutes, not via support tickets.
• Controlled cost: no per-user license that spikes as the team grows.
• Data ownership: your sales data stays in your infrastructure.
• Targeted integrations: connect only the tools you actually use.

Designing the data model

Contacts and companies

The core of a CRM is the relationship between people (contacts) and organizations (companies). Each contact belongs to a company, with fields tailored to your industry: for a software vendor, the contact's technical role matters; for a distributor, it's the geographic zone and order volume. Start with the 10 fields actually used daily rather than replicating a 50-field Salesforce record.

Deals and opportunities

Each sales opportunity follows a journey: from need identification to signature. Model this journey with stages that reflect your reality. A deal is linked to a contact, a company, an estimated amount, and an expected close date. Add specific fields as needed: closing probability, lead source, identified competitor.

Activities and history

Every interaction with a prospect or customer should be tracked: calls, emails, meetings, demos. The activity history gives the sales rep full context before each interaction and lets the manager monitor sales effort. Quick entry (activity type, date, short note) is enough to keep the CRM current without discouraging the team.

Pipeline management

The pipeline is the CRM's strategic view: how many deals at each stage, total amount, which deals risk stalling. A kanban view with stages as columns and deals as cards gives an immediate read. Add health indicators: time in stage, next planned action, overdue close date.

• Kanban view with drag-and-drop to move deals between stages.
• Total amount per stage and per rep visible at a glance.
• Visual alerts for stagnant deals (no activity in X days).
• Filters by rep, period, client segment.
• Forecast view: amount weighted by closing probability.

Task automation rules

CRM automation doesn't mean automating everything. Start with repetitive, low-value actions: reminders when there's been no activity for N days, manager notification when a deal changes stage, automatic follow-up task after a demo. Only automate processes you've already mastered manually — automating an unstable process just accelerates the chaos.

• Automatic reminder if a contact has had no interaction in 14 days.
• Slack/Teams notification to the manager when a deal enters negotiation.
• Auto-create a 'send proposal' task after qualification.
• Alert if a deal stays in the same stage for more than 30 days.
• Auto-assign new leads to the on-duty sales rep.

Email integration

Email remains the primary channel for sales relationships. Integrating email exchanges into the CRM eliminates switching between inbox and contact card. Two approaches: automatic BCC (copy the CRM on every outbound email) or API integration with the mail provider. The first is simpler to set up; the second is more reliable and bidirectional.

Notification systems

Notifications keep the sales team responsive without requiring constant CRM checks. They need to be relevant, non-intrusive, and actionable. Too many notifications cause the opposite effect: the team ignores them. Target events that genuinely require immediate action.

• Channel-appropriate notifications: email for daily digests, Slack/Teams for urgent alerts.
• Daily summary: today's tasks and deals requiring action.
• Real-time alerts for critical events (hot new lead, deal lost).
• Per-user notification preferences.

Reporting dashboards

CRM reporting serves two needs: operational steering (how many calls this week, how many demos scheduled) and strategic steering (revenue forecasts, pipeline conversion rates). Cadrant lets you build these dashboards directly on Supabase data, with trend charts, counters, and filterable tables.

• Pipeline value: total amount per stage and trend over time.
• Sales activity: calls, emails, meetings per rep per week.
• Conversion rate: lead to qualified, qualified to proposal, proposal to close.
• Forecast: expected revenue per month based on closing probabilities.
• Top deals: largest in-progress deals with their next action.

Lead scoring

Lead scoring assigns a score to each prospect based on predefined criteria: company size, industry, engagement (pages visited, emails opened, demo requested). This score prioritizes sales effort on leads most likely to convert. A simple two-dimensional model — profile (fit) and engagement (interest) — is enough to start.

• Profile score: company size (+10), target industry (+15), decision-maker role (+20).
• Engagement score: pricing page visit (+5), demo request (+25), email open (+2).
• Qualification threshold: a lead is 'hot' above 50 points.
• Time decay: score decreases if no interaction in 30 days.

Customer segmentation

Segmenting contacts and customers lets you personalize communication and tailor efforts. Segments can be based on static criteria (industry, size, location) or behavioral ones (last activity, cumulative purchase amount, number of products used). Cadrant lets you create filtered views that serve as dynamic segments, updated automatically.

Integration with billing and invoicing

Linking the CRM to billing eliminates double entry and provides a complete view of the customer lifecycle — from prospecting to payment. When a deal is won, the data (client, amount, terms) flows to the billing system. The CRM then shows payment status, letting the sales rep follow up if needed or support contextualize a request.

• Auto-create quote/invoice when a deal moves to 'won.'
• Sync payment status into the CRM customer card.
• Revenue view by customer, rep, and period.
• Alert the sales rep if a client invoice is overdue by more than 30 days.

API webhooks for integrations

A custom CRM must communicate with other business tools. Webhooks trigger actions in third-party systems when a CRM event occurs (new lead, deal won, contact updated). REST APIs let external systems read and write CRM data. Document every integration point to limit technical debt.

• Outbound webhooks: notify a third-party system on each CRM event (via Supabase Edge Functions).
• Inbound webhooks: receive data from web forms, chatbots, or marketing tools.
• Documented REST API: let internal developers read and write CRM data.
• iPaaS integrations (Zapier, Make, n8n) for no-code connections.

Multi-team CRM

When multiple teams use the CRM — sales, marketing, support, account management — needs diverge. The sales rep wants the pipeline and next actions; the marketer wants segments and campaigns; support wants ticket history. A custom CRM with Cadrant offers different views on the same data, with permissions adapted to each role.

• Team-specific views: sales sees the pipeline, support sees tickets.
• Role-based permissions: the rep sees their deals, the manager sees the whole team's.
• Shared vs team-specific fields: some data is common, other data belongs to a department.
• Structured handoff: when a rep transfers a client to support, key information is passed automatically.

Scaling from simple to complex

The advantage of building with Cadrant is incrementality. Start with a minimal CRM — contacts, deals, pipeline — then add features when the need is confirmed: lead scoring after you've identified what distinguishes your best leads, automations after stabilizing manual processes, advanced reporting after collecting enough data. Each addition is incremental and reversible.

• Month 1: contacts, companies, basic pipeline, activity logging.
• Month 2: simple automations (reminders, notifications), initial reporting filters.
• Month 3: email integration, basic lead scoring, multi-team views.
• Month 4+: billing integration, advanced reporting, APIs for third-party systems.

Conclusion: a CRM that reflects your sales reality

An effective CRM isn't the one with the most features — it's the one the sales team actually uses every day. Cadrant lets you build that CRM starting from your process, with your vocabulary, and enrich it progressively. The result: a tool aligned with your reality, adopted by the team, and evolving at your pace.