A facilities manager calls a pump supplier in Nairobi. Three weeks ago a salesperson promised to arrange an inspection before replacing a booster set. The salesperson is away, the quotation is in a shared folder and a service coordinator has never heard of the inspection. The company knows the customer’s name and telephone number. What it has lost is the promise. That is a better starting point for CRM software development in Kenya than a request for another contact list.
A customer relationship management system can connect enquiries, accounts, opportunities, quotations and follow up. The value depends on which promises the system preserves and who receives them when responsibility changes. A distributor selling technical equipment may have a long buying cycle, several people involved in one decision and service obligations extending well beyond the invoice. A generic pipeline can make that work look simpler than it is.
Follow a fictional pump supplier through an enquiry, site visit, revised quotation, purchase and subsequent service handover. The example shows how to design a CRM around the relationship the business actually maintains. It can help a buyer evaluate an existing package, decide which changes deserve custom development and run a pilot that exposes missing context before customers have to repeat their story.
Define the relationship before importing contacts
The facilities manager works for a property management company. The building belongs to a separate owner. A procurement officer may issue the purchase order, while an on site caretaker provides access for inspection. These people have different roles in the same opportunity. If the CRM treats each phone number as an independent customer, several salespeople may contact the same purchasing group without recognising the connection.
Start by identifying the account, relevant sites and people. An account may manage several buildings, and a person may influence decisions at more than one site. Decide which relationships require separate records. A caretaker who changes employers should retain an accurate history of the earlier visits without remaining the current contact for the old site. A well structured CRM makes it possible to update today’s relationship without rewriting yesterday’s events.
Choose a practical account matching rule. Similar company names do not always represent the same legal or commercial customer. Different branches may buy independently under a larger group. Give a data steward responsibility for suspected duplicates and provide evidence before merging records. A merge can accidentally combine confidential quotations or confuse responsibility for a service promise. Test a difficult pair rather than relying solely on a clean demonstration list.
Record only the customer details your staff need for the business purpose. Ask which roles should see personal contact information, quotation margins or internal notes. Define how access changes when someone moves from sales to service or leaves the company. Review applicable obligations through the organisation’s own data governance process. A useful design makes authorised work straightforward without turning every employee’s address book into a universally visible database.
Turn an enquiry into an owned next action
The facilities manager asks whether an existing booster set can be repaired or must be replaced. Sales cannot answer until someone inspects the equipment and the site’s demand. Create an enquiry with the customer, site, initial question and next action. Assign a person responsible for arranging the inspection and a time by which they will update the customer. A contact record without that obligation will not protect the promise.
Distinguish the source of the enquiry from its current owner. A website form, telephone call or referral may bring in the lead. A particular salesperson may qualify it, and a technical colleague may later own the site inspection. Preserve the source for analysis while transferring responsibility for the next task. Otherwise a reassignment can make the original marketing channel disappear or leave two people thinking the other will call.
Decide what qualifies an enquiry for a sales opportunity. A customer asking for a manual may need service help without entering the sales pipeline. A customer discussing budget and a site inspection may justify an opportunity even though the final solution is unknown. Define the threshold in terms sales staff recognise. Counting every incoming call as a deal makes forecasting impressive and unreliable at the same time.
Handle unqualified enquiries respectfully. A prospect may be too early, outside the service area or asking for something the supplier does not offer. Record an appropriate disposition and any agreed follow up. Avoid forcing salespeople to create a fictitious opportunity simply to keep the contact history. The CRM should distinguish staying in touch with a person from claiming that the business expects to win a sale.
Give pipeline stages evidence that a colleague can verify
A salesperson moves an opportunity to inspection scheduled. What evidence makes that label true? The site, proposed time, responsible technician and contact for access should be known. If a date has merely been suggested, the appropriate stage may still be arranging inspection. Stages become useful when people can verify them from a record and know what action follows.
Choose a few meaningful stages. Enquiry qualified, inspection agreed, findings reviewed, quotation issued and commercial decision pending might suit the example supplier. Do not add a stage for every telephone call. Calls are activities and may happen several times within one stage. The stage should describe the buying or delivery state, while activity records explain how people are working toward the next decision.
Define what happens when a deal moves backwards. The customer may request a new inspection after a revision changes the recommended equipment. A CRM that permits only forward movement may encourage staff to pretend the revised quotation is ready. Allow a legitimate return to an earlier stage with a reason. Management can then distinguish an opportunity delayed by missing technical information from one simply waiting for a customer decision.
Look at stage age carefully. An opportunity in commercial review for a month may be progressing on the customer’s procurement timetable or may be forgotten. The next agreed action and evidence of recent contact provide context. A report of old opportunities should lead the sales manager to a decision about support, qualification or closure. It should not encourage staff to change stages solely to make the dashboard look fresh.
Connect the site inspection to the quotation
A technical representative attends the building, records the pump model and identifies a constraint in the plant room. Sales needs those findings before recommending a replacement. Agree which facts must be recorded, who reviews them and whether the customer receives a separate inspection summary. A long free text note may be easy to create but difficult for the next salesperson to translate into a reliable proposal.
Preserve uncertainty. The technician may be unable to verify a pipe dimension during the visit. The record should say what remains unknown and who will confirm it. A compulsory numeric field can tempt someone to enter an estimate without marking it as such. If the estimate affects equipment selection, the quotation should carry the appropriate condition or wait for confirmation under the supplier’s process.
Link photographs and other evidence to the relevant site and opportunity, using the business’s agreed permissions. A photograph of a plant room from one building should never become supporting evidence for another building merely because both belong to the same customer. Test the record with a property manager overseeing several sites. The salesperson should be able to tell exactly where the observation applies before presenting a recommendation.
Define how findings become an approved quotation. The technical representative may recommend equipment, while sales selects a commercial offer and a manager approves a discount. Each decision should remain identifiable. The CRM can carry an accepted proposal into the order process without requiring a salesperson to retype technical conditions in an email. Ask the developer to demonstrate that the service coordinator will later receive the same conditions the customer accepted.
Preserve quotations as versions, not overwritten files
The customer receives a proposal for a new booster set and asks for an alternative that retains part of the existing installation. Sales prepares a revision with different equipment, scope and price. The earlier proposal was genuinely issued and may still be in the customer’s inbox. Create a new version linked to the same opportunity, and show which version is current for the next decision. Avoid replacing the earlier document without history.
Identify what changed. A useful quotation record distinguishes the revised equipment, added or removed work, delivery assumptions and approval state. A customer’s purchasing team may compare versions carefully. The salesperson covering an absent colleague needs to explain why the price changed. A revised total alone will not answer either person’s question. The CRM should retain enough context to reconstruct the commercial conversation.
Consider partial acceptance. The customer approves the inspection and one replacement component while deferring the full installation. The opportunity may need to create an order for the approved portion and retain a follow up for deferred work. Closing the entire opportunity as won could exaggerate revenue and lose the deferred promise. Closing it as lost would hide the real order. Ask how the proposed system represents a mixed decision.
Test a quotation expiry or changed assumption under the business’s rules. A customer confirms an earlier version after a supplier price has changed. The salesperson needs to recognise the mismatch and obtain a decision instead of automatically creating an order at the latest price. Keep the customer’s communication linked to the version they actually accepted. A clear exception process protects both the relationship and the internal commercial review.
Give follow up a purpose beyond reminders
A reminder saying call customer on Friday is useful only if the person making the call knows what was promised. Attach the reason, relevant opportunity, expected response and owner. The customer may be waiting for revised drawings, an inspection date or an answer about installation access. A replacement salesperson should see enough context to continue the conversation without asking the customer to repeat information already supplied.
Decide which reminders should be automated. A follow up due after a promised quotation can help the team. A generic message sent automatically while the customer has an unresolved complaint may harm the relationship. Record conditions that suppress or redirect routine outreach where appropriate. The customer should experience coherent communication across sales and service, even when different employees own the tasks.
Set a rule for overdue actions. When the owner is absent, a supervisor may reassign the action with its history and deadline. Avoid creating a duplicate reminder while the original remains open. Ask the developer to show an employee starting leave with several live opportunities. Can the manager identify promises due during the absence, select a deputy and later return responsibility without losing the intervening activity?
Review the quality of follow up through examples. A salesperson might complete every reminder by marking it done without recording the customer’s answer or next commitment. Decide what evidence matters for a meaningful completion. A brief note saying the site manager confirmed Tuesday access and requested a revised delivery date can be enough. Do not demand a long narrative for every routine call. Collect the context another colleague actually needs.
Keep forecasting honest when the date changes
An expected closing date expresses a judgement, not a promise from the customer. Ask how salespeople choose the date and what customer event would support it. A procurement meeting scheduled for next month is better evidence than a salesperson hoping to close before the end of this month. The CRM should distinguish an estimated date from a confirmed order, particularly when the forecast influences stock purchases or staffing.
Record changes in expected value and timing. The supplier may first estimate a full installation, then learn that the customer intends to purchase in phases. If the pipeline retains only today’s value, management cannot understand why last month’s forecast changed. Preserve enough history to explain major revisions without overwhelming staff with paperwork. A significant value change or delayed decision can warrant a short reason and a new next action.
Avoid assigning universal probabilities without evidence. A company may use weighted forecasting if it has a meaningful basis for the assumptions, but a default percentage attached to a stage can create false precision. Review actual outcomes over time and distinguish new business, repeat orders and service driven opportunities if their patterns differ. When evidence is thin, show ranges or categories consistent with what the team genuinely knows.
Show both movement and inactivity. A pipeline report should reveal opportunities with a customer decision scheduled, quotations awaiting revision and opportunities with no credible next action. Give the sales manager a way to investigate the underlying records before revising the forecast. A meeting focused solely on the largest total may encourage staff to leave weak opportunities open. A meeting focused on evidence can improve decisions about stock, staffing and customer attention.
Build the sales to service handover
The customer approves a replacement component and agrees to a Saturday installation window. The purchase order identifies the building but omits an access condition discussed during the inspection. The service coordinator needs the accepted scope, site contact, access requirement, outstanding questions and promised installation time. A won flag on a sales opportunity cannot carry that information by itself.
Create a handover record or workflow appropriate to the business. Identify the person transferring responsibility, the person accepting it and the minimum evidence required. The receiving coordinator should be able to ask for clarification without reopening the entire commercial negotiation. If the customer later changes the date, record the new agreement in the service workflow and make it visible to sales where relevant.
Test a mismatch between the customer order and the quotation. The purchase order refers to the right equipment but omits a separately priced installation item. The coordinator should not begin work by assuming the omission is accidental. Route the difference to the person authorised to resolve it and retain the answer. A CRM that closes an opportunity and immediately loses all exceptions will create avoidable disputes at delivery.
Verify the actual customer’s experience. Ask a colleague to play the facilities manager calling while the original salesperson is away. Can another employee identify the accepted version, the inspection finding and the next scheduled action? Can they explain what remains under review? If they must ask the customer to resend the quotation and retell the site history, the handover still depends too heavily on one person’s inbox.
Link service issues back to the relationship
A month after installation, the customer reports an unusual noise. The caller may not remember the original opportunity reference, but can identify the building and equipment. The service team needs to locate the installation and its supporting history. The sales representative may need to know that a complaint is open before proposing another project. The CRM should connect the records while respecting the different responsibilities of sales and technical support.
Decide where service tickets belong. A separate service platform may already manage visits, technical evidence and resolutions. The CRM might need only a linked reference, status and customer communication summary. Duplicating the whole technical ticket in both systems can lead to conflicting updates. Define which system owns each fact and how staff discover an update that has not yet crossed the boundary.
Handle dissatisfied customers with care. A complaint may involve disputed scope, an actual equipment fault or a misunderstanding about operation. The system should record the customer’s concern accurately, assign a responsible person and preserve the outcome. Avoid labelling the customer as difficult because one complaint remains open. A reliable relationship history helps the next employee respond fairly and see the evidence behind an earlier decision.
Track promises made during resolution. If the service team commits to send a technician on Wednesday, the responsible person and time should be visible just like the original sales promise. Closing a complaint should confirm the agreed action occurred or record why the case ended. A customer relationship continues after the purchase. The CRM’s ability to support that continuity is a better measure of its value than the size of the imported contact list.
Pilot migration with records that could go wrong
Select examples that include multiple sites under one account, similar company names, former employees, revised quotations and opportunities with no current owner. Import them into a test environment and ask staff to inspect the result. Count accounts and opportunities, but also follow an individual customer through their actual relationships. Totals can match while a site or quotation has been attached to the wrong organisation.
Keep a record of rejected or ambiguous rows. A telephone number with missing context may belong to a caretaker, a purchasing office or a former employee. Assign a person to resolve uncertain records rather than silently guessing. Determine which historic data has a legitimate ongoing purpose and which should be handled under the business’s retention process. Importing everything into a new searchable system is a decision with consequences.
Run a rehearsal for open actions. An enquiry promised a callback tomorrow should remain visible to an assigned employee after migration. If the source spreadsheet stored reminders in notes, a simple contact import may lose the obligations hiding inside them. Sample the busiest salesperson’s open work and reconcile it against the new task list. Customers will notice a missed promise sooner than they notice a beautifully cleaned account name.
Plan the transition day. New enquiries will continue arriving while records are migrated. Name the temporary capture method, the person who enters late changes and the check for duplicates. Tell staff when the new CRM becomes the official source for a given type of record. Running two live systems without clear authority can quickly create two versions of the same customer commitment.
Evaluate the developer through one complete opportunity
Give the developer a deidentified enquiry, site note, quotation revision and service handover from the same illustrative deal. Ask for a walkthrough showing how the records connect. Introduce a salesperson’s absence, an approved partial order and a complaint after installation. Observe whether the proposed design preserves the customer’s story or merely moves names through a pipeline diagram.
Compare configuration with custom work explicitly. Many CRM products support accounts, contacts, tasks and stages without bespoke development. A custom extension might be justified for a site inspection, complex quotation handover or an integration with an existing service system. Ask which requirements work in the standard product, which can be configured by your administrator and which require maintained code. The distinction affects cost and your ability to change ordinary rules later.
Ask for a proposal separating discovery, migration, training, integration, support and recurring services. Identify who will clean ambiguous customer records and who owns external accounts used for communication. Check export and handover with a real sample. A usable export should preserve relationships between accounts, sites, quotations and open tasks, not merely produce a flat contact list that loses the very promises you commissioned the system to protect.
Set acceptance evidence with sales and service together. A relief salesperson finds the inspection promise. The service coordinator sees the accepted quotation condition. The manager can explain a forecast revision. A duplicate account is resolved without exposing the wrong commercial history. Continue the pilot until ordinary employees can perform these tasks with their normal access. Those observations provide a practical basis for deciding whether to expand.
Test the handover against a colleague’s first day back
Imagine the original salesperson returning on Monday after a week away. A deputy arranged the promised inspection, received a revised customer instruction and passed a partially accepted quotation to service. The returning salesperson should be able to see which actions are complete, which remain open and which colleague now owns the installation. Handing every task back automatically would be as confusing as leaving every task assigned to the deputy. The CRM should support an intentional transfer of the remaining responsibilities.
Ask the salesperson to reconstruct the opportunity before speaking to the deputy. They should find the site manager’s confirmed access window, the accepted quotation version and the condition still under review. Then ask the deputy to describe the same opportunity independently. Where the accounts differ, determine whether the CRM lacks a record or whether a colleague made an agreement outside the process. The remedy may be an improved handover field, an operating rule or a simpler way to record a telephone commitment.
Introduce an extra complication. The property management company has a second building with a similar booster set and the same purchasing contact. A quotation for the second building is still provisional. The returning salesperson must distinguish the accepted work at the first site from the proposal at the second. If the customer account screen simply lists documents in date order, a newcomer may open the latest file and assume it applies to the current call. Clear site and opportunity references prevent a plausible but damaging mistake.
Ask the service coordinator to identify their own obligations without reviewing every sales activity. They need the accepted scope, installation conditions, contact and scheduled visit. They may also need a specific unresolved question. They do not necessarily need the salesperson’s whole negotiation history. A good handover summarises the working instruction and retains links to underlying evidence for authorised staff. This makes service simpler while preserving the context needed when a customer challenges a detail.
Give a sales manager a review that changes tomorrow’s work
Select five open opportunities for a short weekly review. Choose one with a promised site visit, one with an overdue quotation, one awaiting a customer procurement decision, one with no clear owner and one with a partial order already placed. Ask each owner to identify the next customer relevant event and the evidence supporting its date. The manager can then decide whether to provide technical help, reassign work or revise the forecast.
Pay particular attention to the opportunity with no owner. It may be an imported record that never received an assignment or a customer enquiry passed between departments. The manager should be able to identify the gap, appoint a responsible colleague and check that the customer receives a follow up. Merely assigning a salesperson does not complete the commitment. Record the action due and confirm later that someone actually contacted the customer.
Examine the partial order separately. The won portion belongs in the order or service process, while the deferred portion remains under discussion only if a credible next action exists. A sales manager who counts the whole quotation as both won revenue and an open opportunity can overstate performance in two places. Ask the CRM to show the relationship between the original offer, accepted lines and deferred work before deciding what belongs in the pipeline.
Close the review by selecting one promise to verify during the following week. The service coordinator might confirm that the Saturday access condition reached the technician. The salesperson might obtain a decision on the deferred component. The manager should see who owns each action and how the result will be recorded. A sales meeting becomes more valuable when its outcome reaches the people who will actually keep the customer’s promise.
Try the review once with the sales manager absent. A deputy using the agreed permissions should be able to see the five opportunities, identify the owners and assign the follow ups within their authority. The deputy should also know which forecast decisions require further approval. If the review works only because the manager interprets a collection of private shorthand, the organisation has moved its spreadsheet into a new interface without transferring its knowledge. Revise the definitions and examples until the incoming colleague can explain the opportunities from the records. Then compare their account with the customer’s most recent communication to check that the CRM reflects what the customer actually agreed. A dependable review gives both sales and service an opportunity to correct the record before the customer has to intervene again.
Start with the promise a colleague nearly missed
A useful conversation about CRM software development in Kenya begins with a real customer commitment that almost disappeared between people or departments. Remove identifying details and take the enquiry, quotation and follow up note to discovery. Ask sales, service and management what each person must know to keep the promise. Their answers define a better first release than a broad request for more customer data.
If a new employee can answer the facilities manager’s call, find the right building and explain the inspection without asking the customer to begin again, the CRM has achieved something customers can feel. Use that call as your first acceptance exercise. Explore further buyer guides on designing business applications around actual working relationships in the ZamaCore blog.