A Pipeline That Reflects Reality
Lead capture from every channel, a pipeline salespeople actually maintain, quotations that become orders without re-entry, and a forecast management can plan against.
Most CRM implementations fail in a specific and predictable way. The system is installed, salespeople are told to update it, and for a few weeks they do. Then a busy month arrives, updating slips, and within a quarter the pipeline on screen describes a company that does not exist. Management keeps reading it anyway, which is worse than having no CRM at all.
The root cause is that the system was designed to report upward rather than to help the salesperson sell. If updating the CRM is pure overhead for the person doing it, no amount of insistence will keep the data clean. If the CRM is where the quotation is produced, where the customer history lives and where the next task is listed, it gets updated because not updating it costs the salesperson time.
iGlobal configures CRM with that principle first. The pipeline stages are the ones your sales process actually has, the quotation is produced from the opportunity, and the order that follows goes straight into operations without anyone retyping it.
Why the forecast is never right
The most common structural fault is stages that describe how the salesperson feels rather than what has verifiably happened. A stage called interested or negotiating cannot be audited, so the forecast becomes a collection of optimism. Stages defined by evidence, such as proposal sent or site survey completed, produce a forecast that can be challenged with facts.
The second problem is leads with no owner and no clock. An enquiry that arrives and is not assigned within hours will usually not be assigned at all, and the company pays twice: once for the marketing that generated it and once for the competitor who answered first.
The third is that the CRM and the order are separate systems. When a won opportunity has to be re-entered as a sales order, the two drift apart, the customer history becomes incomplete, and nobody can answer what a particular customer has actually bought over three years without opening two applications.
- A pipeline nobody believes, including the people maintaining it
- Enquiries sitting unassigned because no rule routes them
- Quotations rebuilt from scratch in a spreadsheet each time
- Customer history scattered across inboxes and notebooks
What the sales system covers
Lead capture from every channel
Website forms, Zalo, email, telephone and imported lists all arrive in one place carrying their source, so nothing depends on somebody forwarding a message.
Assignment rules and response clocks
Leads routed by territory, product or rotation the moment they arrive, with escalation if nobody has acted within the agreed window.
Pipeline stages defined by evidence
Each stage has an entry condition that can be verified, and probability is attached to the stage rather than to the salesperson's mood on the day of the review.
Quotations from the opportunity
Price lists, discount rules and approval thresholds applied automatically, with the document produced in Vietnamese or English and the version history kept.
Won deals flow into operations
A confirmed quotation becomes the sales order, the delivery and the invoice without re-entry, so the customer record is complete by construction.
Forecast and activity reporting
Weighted pipeline by stage, win rate by salesperson and source, average cycle length, and activity levels that show effort rather than only outcomes.
How we deliver it
-
1
Sales process mapping 1 to 2 weeks
We sit with the sales team, not only the sales director, and write down the stages that genuinely exist including the ones nobody puts in the official diagram.
-
2
Configuration and channel wiring 2 to 3 weeks
Pipeline, assignment rules, price lists, quotation templates and the connections to website forms, email and Zalo.
-
3
Data migration and pilot team 2 to 3 weeks
Customers and open opportunities loaded, then one sales team uses the system for real while the rest continue as before. Their complaints are the specification for the rollout.
-
4
Rollout and management routine 3 to 4 weeks
All teams on, and crucially the weekly sales meeting moves to reading the pipeline on screen. A CRM becomes real on the day management stops accepting any other version.
Who this is for
- B2B sales teams of 5 to 100 people with a multi-step cycle
- Companies where quotations are built in spreadsheets
- Businesses receiving enquiries through several channels at once
- Managers who cannot currently trust the sales forecast
Why iGlobal
We configure for the salesperson first
If the system does not save a salesperson time on the day they use it, the data will decay no matter what the policy says. Everything else depends on getting this right.
Stages you can audit
We insist on entry conditions that are facts rather than feelings. It makes the first forecast look worse and every subsequent one worth reading.
One record from enquiry to invoice
Because CRM, sales, inventory and accounting share a database, the customer history is complete without anybody maintaining it.
The best balance of cost, quality, and service
No per-contact or per-record pricing, so growing your database is not a budget event, and the data stays yours in a system you can export from.
Three ways to do this, compared
| What you are comparing | By hand, on spreadsheets | Off-the-shelf software | With iGlobal |
|---|---|---|---|
| Where the sales pipeline lives | In each salesperson's own notebook | In a system people update on Friday afternoon, if at all | Updated as a side effect, because quoting happens inside it |
| A salesperson resigns | Their contacts walk out of the door with them | The records stay, but the context does not | Full history: calls, quotes, objections and why a deal was lost |
| Turning a quotation into an order | Retyped into the sales system by somebody else | An export followed by an import | The approved quote becomes the order, unchanged |
| Cost across three years | Hidden inside salaries, so it never appears in a budget | A predictable licence per user, plus the work it cannot do | Quoted per phase and reviewed with you before each one starts |
| Who holds your data | Scattered across files, inboxes and personal phones | On the vendor platform, exported on the vendor's terms | Your own database, exportable in full whenever you ask |
| When something breaks | The person who built the file, if they still work here | A ticket queue, often in another language and time zone | A named engineer in Hanoi you can reach the same working day |
The two middle columns describe approaches that genuinely work for some companies. Where they win, they win, and we have tried to say so.
What changes after go live
The first visible change is response time to new enquiries. Routing and a response clock typically move a company from answering within a day or two to answering within an hour, and because enquiry conversion is strongly time dependent, this alone often pays for the project.
The second change takes a quarter and concerns trust. Once stages are evidence based and the weekly meeting reads the same screen, the forecast starts being accurate enough to plan production and cash against. Companies underestimate how much operational waste comes from planning against a forecast everyone privately discounts.
The third is institutional memory. When a salesperson leaves, their accounts no longer leave with them. The history of every conversation, quotation and objection stays with the customer record, and a handover takes an afternoon instead of costing a relationship.
- Enquiries answered in under an hour, measurably
- A forecast accurate enough to plan production against
- Quotations produced in minutes from the opportunity
- Customer history that survives a salesperson leaving
Frequently asked questions
Our salespeople resist CRM. How do you handle that?
We treat resistance as information rather than as an attitude problem. It almost always means the system asks for data without giving anything back. The fix is to make the CRM the fastest way to produce a quotation and to see a customer's history, so using it is self-interested. Enforcement alone has never worked and we would rather not pretend otherwise.
Can it connect to Zalo?
Yes. Enquiries from a Zalo Official Account can be captured as leads with the conversation attached, and notifications can be sent back through Zalo where that suits your customers better than email. For Vietnamese B2B this often matters more than any international channel.
How do we handle customers served by several salespeople?
The customer record is shared while opportunities have individual owners, so collaboration is possible without commission disputes. Where territory or product splits overlap, we configure the assignment rules to reflect the commission policy, because a CRM that contradicts the commission scheme loses that argument every time.
Will it work for a long project sales cycle?
Yes, and that is where it earns most. Cycles measured in months need stage ageing, reminders and a record of every contact, because the salesperson who started the deal may not be the one who closes it. We also configure a lost reason list, which after a year becomes one of the most useful datasets the company owns.
Can management see activity without micromanaging?
The reports we build by default show pipeline health, conversion by stage and ageing rather than individual call counts. Activity data exists and is available, but a dashboard that leads with surveillance metrics teaches the team to game the metric, and then both the metric and the pipeline become fiction.
Related solutions
Talk to a senior consultant, not a call centre
Tell us what you are trying to fix and we will tell you honestly whether we are the right team for it.