Networking and Referral Playbook
A recommendation from someone the buyer already trusts is usually the cheapest and most persuasive route to new work in East African markets; this playbook manages the relationships that produce those recommendations, on top of reliable delivery.
Use When
- Most clients arrive by word of mouth: should events and introductions lead the growth plan?
- Plan which business events, chamber meetings or conferences to attend and what to do before, during and after each one.
- Past clients and partners should refer more often, with a simple ask and a thank-you routine.
- Start or join a referral group and agree how members pass leads to each other.
- Build a follow-up system, a map of connectors and a personal board of advisers.
Do Not Use When
biz-dev-lawful-prospecting-outreach for cold outreach sequences, contact-list sourcing and consent handling.
playbook-social-selling for turning an online audience into a sales pipeline.
strategy-personal-brand for an individual's positioning and authority content.
- Stop before adding event contacts to any mailing or WhatsApp list without their consent; keep the follow-up personal.
Required Inputs
| Artefact |
Source/provider |
Required? |
If absent |
| Client business name, industry/sector and country or city |
Client brief |
Yes |
Default the market to Uganda / East Africa; ask for name and sector. |
| Primary goal: new client acquisition, referral activation, community presence, or all three |
Client owner |
Yes |
Plan for all three and ask the client to rank them. |
| Current networking activity |
Client |
Yes |
Treat as none and start from the event routine and referral ask. |
| Budget and time available per week for networking |
Client owner |
Yes |
Stop the channel-mix choice; do not guess time or money. |
| Existing contacts, past clients and referral sources, with a lawful basis for follow-up |
Client CRM or spreadsheet |
For follow-up and gatekeeper lists |
Build the list template only; mark named contacts not assessed. |
Workflow
- Ask the intake questions in networking and referral method and confirm the owner and consent boundary; stop if the goal or weekly capacity is missing.
- Choose the channel mix from what the client has more of: time and relationships, budget, or both.
- Name the specific organisations and events for the next 90 days and set the before, during, straight-after and 48-hour event routine.
- Write the referral activation script, the gatekeeper target list (five professions, two or three people each) and the written-reference template.
- Design the referral group and its tracking log where the client will run or join one.
- Set the dated follow-up schedule, the network map with gap audit and A/B/C/D cadence, and the weekly connector habits.
- Run the quality checks and the anti-slop gate; correct any failed item and rerun before handover.
Channel mix by client resources
| Client has |
Lead with |
Add later |
| Time and relationships, little budget (new firms, independents) |
Networking, speaking, referral cultivation, useful content |
Paid channels once revenue allows |
| Budget, little senior time |
Paid advertising, sponsored placements, direct mail |
A light referral routine run by the account lead |
| Both |
Referral partners and events as the base, paid media to scale |
n/a |
Outputs
| Artefact |
Consumer |
Acceptance condition |
| 90-day networking action plan and short spoken pitch |
Client owner |
Names specific organisations and events; the pitch answers "What do you do?" in 15–30 seconds, benefit-led. |
| Referral activation script and gatekeeper target list |
Client owner |
Script describes the ideal client; list has 10–15 named referral sources with a cultivation plan. |
| Referral group design document |
Group facilitator |
Member profile, meeting structure and referral tracking log are included. |
| Follow-up schedule with message templates |
Client owner |
Every contact type has an action and a specific timing. |
| Network map and cadence |
Client owner |
Groups, gap audit, A/B/C/D plan and a quarterly gathering plan are set. |
Evidence Produced
| Evidence |
Format |
Acceptance condition |
| Referral tracking log |
Table: source, recipient, outcome, value |
Reviewed quarterly; a referral without an outcome is marked open. |
| Follow-up register |
Spreadsheet or CRM with next action and due date |
Each contact has a lawful basis for follow-up recorded or is removed. |
Capability and Permission Boundaries
Read and search only; analysis is read-only. Publishing, spend, live account changes, outreach and personal-data processing need explicit, action-specific client authority. Scripts and lists are drafts; the client makes every personal approach.
Degraded Mode
Without the client's goal and weekly time or budget, return the narrowest qualified result and mark the affected checks not assessed. The event routine, referral script and follow-up timings can still be delivered, with the channel mix and target list left open.
Decision Rules
| Condition |
Action |
Failure or risk avoided |
| A contact has no mutual relevance or permission for follow-up |
Do not add them to a sequence. |
Transactional spam disguised as networking. |
| A client has just had a successful delivery |
Ask for a referral now, describing the ideal client; not at renewal. |
Vague asks that produce nobody. |
| A contact was met at an event |
Send a personal message within 24 hours; a referral gets thanks and an introduction within 48 hours; a proposal gets one call 5–7 working days later. |
Contacts lost for want of a second message. |
| The contact base passes 100 contacts |
Move from a spreadsheet to a CRM or database with next action and due date. |
Missed follow-ups. |
| Networking touches public procurement |
Guard against conflict of interest; never approach evaluators during a live tender. |
Procurement breach and reputational damage. |
| The person knows the client socially but not professionally |
Acknowledge the relationship, say whom you help in one line, and leave the choice with them. |
Seeming to have joined the group to sell. |
Quality Standards
- The action plan names specific organisations and events, not generic "networking events".
- The spoken pitch is specific, benefit-led and memorable, not a job title.
- Referral scripts are direct and comfortable to say aloud, never pressuring.
- The gatekeeper list names professions that genuinely meet the client's buyer first.
- The referral group design includes a tracking mechanism, not just a list of attendees.
- All follow-up timings are specific (24 hours, 48 hours), not "soon".
- Content reflects the relationship-first business culture of Uganda and East Africa.
- The network map names gaps by role and sets a cadence; introductions give value before any ask.
Anti-Patterns
- Selling at the event. Fix: ask more than you tell and keep the sale for the follow-up.
- Asking for referrals from "anyone". Fix: describe the ideal client in one sentence.
- Following up with "let's have coffee sometime". Fix: set a specific next step and date.
- Cold-pitching gatekeepers. Fix: meet them through an introduction or shared event and give value first.
- Attending passively and irregularly. Fix: join a few organisations, take a committee or volunteer role and turn up consistently.
- Calling A-list contacts only when you need something. Fix: call when you have an opportunity for them and make one introduction a week.
- Adding event contacts to a mailing or WhatsApp list. Fix: keep follow-up personal and check the lawful basis first.
References