Commercial CRM · Capture, follow-up, and management visibility

A conversation does not create business until there is a visible next action.

We built a custom web CRM for Sigmart Group that turns leads captured by Laura into traceable customers, opportunities, activities, and decisions throughout the commercial lifecycle.

Sigmart Group · Multi-business commercial operationPrivate CRM, AI agent, collaboration, and integrations
1shared commercial memory
10modules connected in the architecture
Livereal-time activity and collaboration
2intentionally separated data layers

* Mockup figures are illustrative. This case describes delivered capabilities and does not attribute unaudited commercial results.

The starting point

The information existed, but it did not travel together.

A conversation could start on the website, continue by phone, and end up spread across chats, notes, and spreadsheets. Product, industry, urgency, and commitments were far from the person who needed to act.

The team needed to answer four questions without reconstructing the history:
  • Who needs what, and how urgently?
  • Who owns the next step?
  • What changed since the last contact?
  • Which opportunities are moving, and which are stalled?
The challenge

Connecting capture, commercial execution, and direction.

The system had to help salespeople throughout the day and management make decisions, without turning every record into administrative work or exposing private information beyond the authorized role.

01

Fragmented context

Lead source, customer need, and commercial history lived across different channels.

02

Invisible follow-up

Without an owner, date, and next action, an opportunity could stay open without moving.

03

Manual reporting

Management relied on delayed consolidation to understand pipeline, risk, and performance.

The solution

A continuous circuit from Laura to management decisions.

The CRM receives context captured by AI, lets the team validate it, and turns it into commercial work. Every change feeds the same memory: customer, opportunity, activity, conversation, file, alert, and report.

01

Capture

Laura structures the lead with need, product, industry, and urgency.

02

Validate

The team reviews context and turns it into a customer or opportunity.

03

Move

Pipeline, activities, and workspace preserve ownership and the next step.

04

Direct

Dashboards, alerts, and reports expose velocity, risk, and forecast.

Commercial continuity

Every conversation ends in a visible action.

The experience was designed as a journey, not a collection of isolated modules. Context enters once, is validated by a person, and follows the opportunity through close or post-sale.

conversation.to.next_action
01

Laura listens

Captures the need in natural language.

02

CRM remembers

Preserves source, context, and history.

03

Sales decides

Qualifies, assigns, and defines the next step.

04

Pipeline orders

Makes stage, value, risk, and date visible.

05

Team acts

Alerts and activities maintain momentum.

private.by.designVisibility follows responsibility.

Each salesperson can access only their assigned leads, customers, opportunities, and activities. Other users' private data remains protected; only authorized management roles can access aggregated team views.

Role-based access
The product

A control room that is also built for daily work.

The CRM combines executive visibility with operating tools so data is produced while the team sells—not during a report assembled afterward.

Laura · Leads

An intelligent inbox with division, product, urgency, summary, and search across AI-captured context.

Configurable pipeline

Board and list views with flexible stages, value, probability, priority, owner, and expected close.

Actionable activities

Calls, visits, emails, and meetings with owners, dates, status, and overdue alerts.

Workspace with memory

Messages, notes, files, and stage events gathered inside every opportunity in real time.

Google Chat and Drive

Important events reach the team's channel, and each opportunity can receive an organized document folder.

Dashboard and reports

Pipeline, forecast, conversion, goals, overdue tasks, stagnation, and performance from the same records.

Operating change

From isolated messages to commercial continuity.

BeforeWith the connected CRM
Data scattered across channelsA structured entry for every lead
Sales reconstructs the contextProduct, industry, urgency, and summary available
Follow-up depends on memoryOwner, date, status, and next action
Documents are scatteredFiles linked to the opportunity and Drive
Management requests reportsForecast, risks, and progress visible from operations
Measurable impact

The system instruments improvement.

The project does not fabricate success rates. It prepares the events and relationships needed to measure with real data where speed is gained and where continuity is lost.

measurement.ready
01Capture → contact

Response velocity

Time from Laura registering the lead to the first human contact.

02Lead → sale

Traceable conversion

Progress from capture to opportunity, proposal, and won business.

03Days per stage

Pipeline velocity

Average time and stalled opportunities across each phase.

04Next step

Operating discipline

Opportunities without follow-up, overdue activities, and customers without contact.

management.visibilityIndicators prepared for management
  • Weighted forecast and pipeline value
  • Progress against monthly targets
  • Performance by owner and division
  • Risk, inactivity, and post-sale opportunities

* Indicators are available for future measurement; the source document contains no historical baseline or audited results.

Architecture

Two separate databases, one commercial experience.

React and Vite power the interface; Supabase provides PostgreSQL, Auth, Realtime, Presence, and Storage. A dedicated instance receives Laura's leads, while another protects internal CRM operations, reducing coupling between the public entry point and private data.

React 19ViteSupabasePostgreSQLRealtimePresenceStorageGoogle ChatGoogle DriveApps Scriptdate-fns

Privacy by role and responsibility

  • Each user can access only the commercial information assigned to them
  • No salesperson can view another user's private data
  • Management reaches aggregated views only through an authorized role
  • Supabase Auth and protected routes control session and navigation
  • Signed URLs protect temporary access to files and documents
  • Sensitive amounts can be hidden while screen sharing
Orbi Labs

Does your team sell in one channel and report in another?

We design CRMs around your real process so every conversation keeps its context and every opportunity has a next step.