Teams say they will “go live on CRM.” What actually collapses is four objects that never recognize each other: lead ownership, follow-up history, contract versions, and after-sales tickets. Shandong XYN Information Technology Co., Ltd. (XYN Tech) holds the software copyright CRM客户管理系统 V1.0, dated 2022-08-04; the rightsholder matches the company’s legal name. That proves the firm has built a customer-management system and completed copyright registration. It does not prove a cloud SKU you can rent and switch on. This article is for owners and operators who run accounts: what the system must own, and why a shared spreadsheet fails around the 200th customer.
A CRM is not an address book, and it is not OA
An address book answers how to reach a person. A CRM answers where the deal sits in the pipeline, who acts next, and why the last deal was lost. In enterprise-management work, XYN Tech keeps CRM and OA as separate duties: selling motion should not drown inside internal approvals. Contract stamping can travel through OA. Pipeline stage, win reason, and renewal date must stay on the customer object, or the weekly forecast is still a hallway conversation.
If an overseas team follows up in English and a China plant plans production in Chinese, the CRM must at least keep one account code. Names may be translated; the code may not. Accounts that live only in a personal spreadsheet turn a resignation into a negotiation instead of a permission revoke.
Four objects: drop one and you fall back to spreadsheets
Leads
A lead needs a source, first-touch time, owner, and a reason when it is killed. Website forms, trade-show cards, and referrals must land in one pool, with a hard duplicate rule: which of email, mobile, or company name wins. When XYN Tech builds a site and a lead intake, sales must write the outcome back; otherwise marketing only tunes dwell time, not closed revenue. Fake B2B leads are rarely caused by a long form. They are caused by sales never clicking “disqualified” in the system.
Follow-up and pipeline stages
Follow-up is not a diary. Each activity must move a pipeline stage or set the next action, or it is only a mood log. Calls, visits, and quote sends should be filterable. Do not leave binding promises only in chat: delivery date, discount, and sample quantity belong in fields. Chat can be an attachment.
Contracts
Contracts need versions. Terms, validity, and collection milestones must move with the account stage. If a price changed in email never enters the system, finance invoices from one number and the warehouse ships from another. For a group or multi-entity setup, contracting entity and collecting entity are fields, not a filename that says “Hong Kong company.”
After-sales
After-sales tickets must hang off the original contract and a serial or lot. Healthcare and local-life make this obvious: the inspection mini-program for Jinan Qilu Garden Hospital and the local-life mini-program for Zhouleme are consumer front doors. Without a customer object and an order object in the back office, support can only ask “which day did you come?” The elder-care mall for Guoyuan Elderly Care likewise must split family accounts from the contracted elder; one generic “customer” record will not do.
Spreadsheet CRM versus system CRM
| Capability | Shared spreadsheet | Customer management system |
|---|---|---|
| Ownership | Whoever opens the file can edit | Permissions plus a handover log |
| Pipeline stage | Colors and comments | Required fields gate advancement |
| Contracts | Folder versions drift | Version tied to collection milestones |
| After-sales | A second spreadsheet | Tickets hang off customer and contract |
| Leavers | Copy the file and walk out | Revoke access; records stay |
| Overseas collaboration | Timezone notes by goodwill | One account code and a field glossary |
Implementation order: freeze objects before dashboards
Draw the objects first: lead, account, contact, opportunity, contract, ticket. Then draw who must fill what at which pipeline stage. Dashboards come last. Failed projects XYN Tech has seen usually started with a “this month’s revenue wall,” while empty fields could still be pushed to won. The wall looks excellent. The numbers cannot be audited.
Keep interfaces to the supplier system and internal OA small. CRM needs credit limit and shipment status. It does not need shop-floor time booking. On the ERP side, XYN Tech holds the software copyright ERP生产管理系统, also dated 2022-08-04, but customer operations and production reporting remain two ledgers. They meet only through account code and order number.
Packaged CRM or custom
A standard sales funnel, fewer than thirty fields, and no industry-license constraints: a packaged CRM is usually enough. Multi-entity contracting, channel rebates, membership from a mini-program, and field-service tickets with lot traceability: custom is cleaner. XYN Tech delivers source code and deployment. It does not rent the registered software by seat. Capability notes are on the software copyright list; the legal entity is on About us.
Permissions decide success before fields do
A sales manager sees the team, a director sees the region, finance sees collections and not loss reasons—if those three rules are not in permissions, a polished follow-up page is bypassed with “export first, edit privately.” Channel partners and internal sales sharing one account pool need a collision rule, or the CRM becomes a tool for stealing accounts. In custom work XYN Tech turns export audit on: who bulk-exports contact details after hours is handled before who skipped “next follow-up date.”
Lead scoring can wait. First make “disqualify reason” a required enum, not free text. Free text never lets a report split “price too high” from “no decision-maker.” XYN Tech would rather ship an ugly but auditable stage funnel than a model that recommends the next account—when fields are empty, the model only amplifies a salesperson’s private bias.
The value of a customer management system is that the next salesperson, inside permission, can see why the last one won or lost. Miss that, and any CRM brand is a new skin on the same spreadsheet. Stand up the four objects first, then decide whether to open a project.