Qualification
The opportunity opens on the same identity as the ERP account card.
FAB CRM · Sales
CRM Software
Every sales move from first contact to proposal in one place.
A CRM that unifies customers, opportunities and quotes in one data model and makes visible where the sales funnel actually stalls.
- Customer history is not locked in one person
- Funnel stages are measured
- Quote versions are preserved
Product tour
FAB CRM, screen by screen.
FAB CRM · Pipeline
Run your sales process from one place.
Every opportunity moves through defined stages; time in stage and bottlenecks stay visible.
- Opportunity funnelStages, time spent per stage and the point where deals stall.
- Loss reasonsA closed list of reasons; free text produces no analysis.
FAB CRM · Customer 360°
The customer’s whole history on one card.
Contacts, opportunities, quotes and activities; orders, invoices and collections from the same ERP account card.
- Shared customer with ERPOne customer record; CRM and ERP do not keep separate lists.
- Activity historyCalls, e-mails and notes attached to the customer record.
FAB CRM · Quotes
Every revision a version, every approval on record.
Lines, discounts, validity and approval thresholds; in a price dispute the sent version is on record.
- Quote versioningEach revision is a version, with a record of which one was sent.
- Manager approval above the discount threshold, stored with the version
FAB CRM · Manager dashboard
See where the funnel gets stuck.
Open pipeline, expected closing, win rate, rep performance and loss reasons.
- Authority and portfolioReps see their own portfolio, managers see the whole team.
- Time in stage and bottleneck
- Loss-reason distribution from a closed list
How it works
One record from first contact to collection.
Needs analysis
Calls, emails and notes attach to the customer record.
Quote
Lines, discount and validity; each revision is a new version.
Approval
Quotes above the discount threshold go to the manager; approval is recorded.
Negotiation
Time in stage is measured; bottlenecks show in reports.
Won / lost
Loss reasons come from a closed list; free text produces no analysis.
ERP order
Orders and invoices are created in ERP and show on the customer card.
Collection
Collection status comes from bank integration.
Who uses it?
Every role sees its own screen.
- SSales manager
Sees the whole team; tracks funnel, approval thresholds and loss reasons.
Manager dashboard - SSales rep
Sees their own portfolio; manages opportunities, activities and quote versions.
Pipeline · Quotes - GGeneral manager
Sees open pipeline, expected closing and win rate at a glance.
Manager dashboard - FFinance
Sees open balance, terms and collection status on the customer card.
Customer 360°
In a day
A sales manager’s morning in FAB CRM
Open opportunities
With stage, quote version and waiting time.
Delayed quotes
The quote stage takes twice as long as others.
New opportunity
In qualification, linked to the existing account card.
Team performance
Open opportunities, win rate and cycle per rep.
Integration surface
The product is not an isolated island.
Data ownership, error handling, security and audit trails are designed as part of the implementation.
- ERP and accounting
- Email and messaging
- E-commerce and marketplaces
- Identity and authorisation
- BI and reporting
- REST API · Webhook
What is the CRM and when is it needed?
A CRM is not a task list for the sales team but the institutional memory of the customer relationship. The need becomes obvious when a sales rep leaves and the customer history leaves with them.
Which problem does it solve?
- History lives with a person. Who discussed what, and which price was quoted, is not recorded.
- Nobody knows where the funnel stalls. Total quotes and total sales are known; the loss between them is not.
- The same customer exists twice. The company in the CRM does not match the account in the ERP.
How it works
The core design decision: the customer account is one record. The CRM keeps no separate customer list; it uses the same identity as the ERP account. With two lists, the merging work never ends.
Opportunities move through defined stages, and each transition is recorded with a date. That answers "how many days from first contact to quote" and "how long do quotes sit". For lost deals the reason is chosen from a closed list; free text produces no analysis.
Quotes are versioned. A revision does not overwrite the previous version, and which version was sent when is recorded. Price disputes end there.
Modules
- Customers: accounts, contacts, addresses, segments.
- Opportunities: stage, estimated value, close date, owner.
- Quotes: lines, discounts, validity, versions, approval.
- Activities: calls, e-mails, notes, reminders.
- Reporting: funnel, win rate, rep performance, loss reason distribution.
Integrations
ERP (accounts, orders, invoices), e-mail, the dealer portal, field sales tracking, bank integration for payment status, and web forms.
Architecture and authority
- Reps see their own portfolio, managers the whole team, enforced by data scope.
- Changes to customer records leave an audit trail.
- Access and retention policies are defined for personal data fields.
Usage scenarios
- Project-based selling in manufacturing: long opportunity cycles and quote-to-work-order links.
- Dealer network management: visit planning and prospective dealer tracking.
- Service selling: quote versions and scope change management.
- Health tourism: alongside the health tourism platform for case-level tracking.
Roll-out
- Data model: account matching, segment definitions, stage list.
- Sales process: stage rules, quote templates, approval thresholds.
- Reporting: funnel, win rate, loss reasons.
- Extension: e-mail and field integrations.
Frequently asked questions
Why this instead of an off-the-shelf CRM?
An off-the-shelf CRM covers most needs. The difference appears when you need a shared customer record with the ERP, industry-specific quoting logic (bills of material, configuration, tolerances) or data exchange with your existing systems. For standard needs we recommend a packaged product, and we say so at the start of the project.
What if the sales team does not use it?
An unused CRM produces no data. What works in practice is reducing the number of fields and putting the parts that help the seller first: quote generation, visible price history, reminders.
How many funnel stages should there be?
As many as you can measure. The more stages, the weaker the entry discipline. Five or six is enough for most B2B sales processes.
See the product with your process
See the CRM live →