CRM systems

What it is

A sales system shaped around how your deals actually move: enquiry capture, qualification, the stages you use, activity history against the account, ownership and follow-up. The reporting sits on the funnel rather than on a list of contacts.

Why businesses need it

Deals are lost in the gaps — an enquiry nobody owned, a follow-up with no reminder attached, a call nobody wrote down. The point of a CRM is to make that gap visible while there is still time to close it, and to keep the history when the person moves on.

What MIWEBX delivers

• Lead and contact capture from forms, mail, imports and phone
• Account and opportunity records on the stages your process uses
• Assignment rules, round-robin splitting and territory ownership
• Activity timeline: calls, meetings, messages and notes on the record
• Follow-up tasks, reminders and escalation on a deal that has gone stale
• Funnel reporting by owner, source, stage and period

Core features

• Duplicate detection on mail, phone and company name at the point of entry
• Stage rules: what a deal must hold before it may move, and who may move it
• Unassigned queues with the age of every lead visible on the row
• Mail and calendar connection so activity is logged without re-typing
• Source attribution carried from the first touch through to the closed deal
• Pipeline views by owner, team, region and channel

Technical capabilities

• Activity stored as an append-only history so an edit never destroys what happened
• Assignment decided by one set of rules, testable without touching live records
• Reminders and escalation driven by scheduled work, not by an open browser tab
• Search built on indexed fields, with handling for names and company spelling
• Funnel metrics computed from stage-change timestamps rather than current stage alone
• Bulk import with column mapping, a preview run and a report of conflicts
• Field-level trail so a changed value traces to a person and a moment

How we build it

• Walk the real sales process stage by stage with the people running it.
• Define lead, contact, account and deal as separate records with owners.
• Build capture, duplicate control and assignment before any reporting.
• Layer the activity history and follow-up rules on those records.
• Report the funnel and check it against the sales manager's own numbers.
• Migrate the existing sheet or tool with a reconciliation of what moved.

Technology stack

• React
• Next.js
• TypeScript
• Node.js
• PostgreSQL
• Prisma
• Redis
• Webhooks

What you receive

• The system deployed with its stages, fields and rules configured
• Existing contacts and open deals imported and reconciled
• Assignment and reminder rules written out in plain language
• Pipeline, source and owner reporting set up
• Admin access to change stages and fields without a developer

Business benefits

• No enquiry waits unanswered because nobody owns it
• The pipeline reads the same way for every manager
• History survives a salesperson leaving the team
• Channels judged on deals rather than raw form volume