The Kernel operational library
Working remotely. Belonging fully.
Role-specific guides that turn a new arrival into successful collaboration. Prepare your organisation, equip your collaborator and give your team a shared set of practical expectations.
SDR.
BDR.
Sales Executive.
The sales team playbook
Onboard and support a remote sales professional
SDRs, BDRs and Sales Executives: from the first account login to the first prospect, create a clear working environment and a shared sales process.
- Role and responsibilities
- Onboarding and equipment
- Sales tools and partners
- 90-day plan and checklist
Code. Data.
DevOps. QA.
20 categories · 60 tools
The technology team playbook
Onboard a remote technology engineer
Developers, data scientists, data engineers, DevOps, SRE and QA: from a reproducible setup to a controlled first delivery.
- Git, environments and code review
- IP, VPN, Zero Trust and secrets
- AI, quality and role-specific methods
- 30/60/90-day journey and checklist
Listen.
Resolve. Retain.
20 categories · 60 tools
The support and CSM team playbook
Onboard and support a remote customer service team
Understand your offering, make informed decisions and build a coherent customer experience, from the first ticket to the success plan.
- Product learning and customer journeys
- VoIP, helpdesks and decision trees
- Customer Success, quality and capacity
- CSAT, NPS, effort and a 90-day plan
Explore the support guide
Find.
Qualify. Decide.
20 categories · 60 tools
The recruitment team playbook
Onboard and support your remote recruiters
From intake to actual start: search, qualify and coordinate hiring without losing quality, confidentiality or clear decision ownership.
- Onboarding, accounts and team vaults
- ATS, CRM, sourcing and CV qualification
- Interviews, assessments and candidate experience
- Data, AI, metrics and a 90-day plan
Explore the recruiter guide
Experience becomes a practical method.
These guides draw on hundreds of our clients’ experiences. Kernel brings together practical approaches to help businesses work with collaborators across all 54 African countries. Our conviction is straightforward: the quality of collaboration is shaped well before the first day. Recruitment starts the relationship; working conditions, shared information and ongoing support give it the foundations to last. The guides make those foundations visible, discussable and actionable for the people responsible for the new arrival.
Understand the role
Each guide starts with the collaborator’s actual responsibilities, outputs and key contacts. Two people with the same title may have different remits. Before discussing tools, we help you clarify what will be expected, what should be agreed together and how good work will be recognised. A shared understanding prevents uncertainty from becoming a performance problem later.
Work across geographies
Distributed teams need simple, explicit rules: shared hours, communication channels, documented decisions and a clear approach to urgency. The guides encourage you to build these expectations with the people concerned rather than require permanent availability. Respect for local constraints and agreed working time remains central. The aim is predictable collaboration, not a constant stream of meetings or status messages.
Prepare the working environment
A computer alone does not make an operational workstation. Connectivity, headsets, confidentiality, software, permissions and support should be considered together. We explain how to validate these conditions and when to involve Kernel for equipment, preconfigured shipping or a workspace suited to the role. Testing the real setup before the start date is more useful than assuming a list of specifications will be enough.
Make room in the team
Onboarding is not just sending a folder. Announcing the arrival, introducing colleagues, appointing a manager and buddy, explaining the business and scheduling regular conversations all matter. The collaborator should understand their place, priorities and support network without having to guess. Existing team members also need to know how responsibilities and handovers will work.
A guide to use, not just read.
01
Before the arrival
Share the guide with the manager, HR team and whoever prepares the tools. Identify what already exists and what is missing. Assign an owner and deadline to each preparation: equipment, accounts, documentation, the schedule and the team announcement. Use the guide as a common basis for discussion rather than a task list handed only to the new collaborator.
02
During onboarding
Work through the stages with the collaborator. Test access from their actual workstation, demonstrate the tools and connect your explanations to real situations. The checkpoints help questions surface early. Adjust the pace and level of support to the individual’s experience instead of assuming internal habits are obvious. Ask for feedback on what is clear and what remains difficult to understand.
03
Over time
Use the guide’s milestones to discuss progress, quality and autonomy. Distinguish organisational problems from training or equipment needs. The proposed practices are not universal quotas: adapt them to your market, workflow and agreed objectives. Keep a record of decisions that will help the relationship develop. A useful review should result in a clear next step, not simply a score.
Useful tools, without subscription overload.
Different roles have different needs. The sales guide covers targeting, calling, follow-ups and CRM. The technology guide covers Git, IP access, VPN, AI, development, data, DevOps and QA, with 60 tools across 20 categories. The support guide covers VoIP, helpdesks, Customer Success, decision trees, quality and satisfaction, with 60 tools across 20 categories. The recruiter guide covers briefs, ATS workflows, sourcing, CV qualification, structured interviews and candidate privacy, with 60 tools across 20 categories. All share the same foundations: communication, documents, equipment and secure access. Solutions include their logo and a link to their official website so you can investigate them without confusion. Keep your current environment when it meets the need; the aim is successful integration, not replacing every application your team already knows.
Sales-tool partners are identified in the sales guide. Technology, support and recruitment tools are editorial selections, with no partnership implied. Interested clients can contact Kernel before subscribing to discuss applicable preferential pricing and conditions. Features and offers depend on the vendor, plan, country and eligibility. Your contact confirms the arrangements before you commit; the presence of a logo should not be interpreted as a specific discount or a promise that every feature is included.
A collection built one role at a time.
Sales, technology, support and recruitment guides address different roles with the same priority: prepare the work, access and team relationship. Each role brings its own practices and tools. Only guides that are actually available are shown here. Have a particular situation? Discuss it with Kernel to clarify the context, responsibilities and useful services through an approach combining technology and local teams.
Prepare my organisation with Kernel