How we work

One problem at a time. The right one first.

A business is never finished, so the work is a loop, not a project. Five steps, repeated as the business grows.

The loop

Diagnose, prioritise, decide, implement, review.

Diagnose

We look across the whole business, using evidence rather than opinion, and separate symptoms from causes. The Diagnostic is where this starts.

Prioritise

Of everything that could be improved, we decide what is most painful or most important at this stage. Everything else can wait.

Decide

We agree the right response for the cause: a change in process, people, rules, information, technology, training, or a combination.

Implement

The change is put into daily use, with owners, training and support. Not a recommendation left behind.

Review

We check whether it worked by measuring it, then return to the start with the next problem the growth has revealed.

Then the next problem.

Technology is an intervention, not the answer.

We diagnose the problem first, then decide whether the right response is technology, people, process, training, or a combination. When technology is the answer, KSL can implement it. When it is not, we say so.

Process
People
Rules
Information
Training
Technology

CRM
ERP
Custom software
Websites
Reporting systems
Automation
Other digital tools

Implementation work of this kind is scoped and priced according to the problem it solves.

What it looks like in practice

Typical patterns, drawn from problems the modules address. Illustrations, not case studies: in practice the diagnosis decides the response.

Customer managementSales information is fragmented.

Diagnosis: Customer and lead information is spread across phones, WhatsApp, email and spreadsheets. Nobody can see the pipeline, and customers go quiet when a salesperson leaves.
Solution: Redesign the sales process and pipeline, then the CRM that supports it.
Implementation: Pipeline stages and exit criteria agreed, CRM configured to them, channels connected, staff trained.
Review: Measure adoption and response times, then identify the next constraint.

Modules: M48 Pipeline Management · M27 CRM · M14 Workflow Design

FinanceSales are up and the accounts show a profit. The bank account is empty.

Diagnosis: Cash is trapped in receivables. Credit is agreed case by case and followed up when someone remembers.
Solution: A credit policy, a weekly collections routine and a 13-week cash view.
Implementation: Policy agreed with the sales team, an aged receivables report every week, a named owner for collections.
Review: Track debtor days and the cash position. Then look at stock and supplier terms.

Modules: M33 Cash vs Profit · M35 Receivables and Collections · M34 Working Capital

PeopleEvery decision waits for the owner.

Diagnosis: Approvals, pricing and escalations route to the founder because nobody knows what they are allowed to decide.
Solution: Decision rights with approval limits, and roles defined by the results they own.
Implementation: An approval matrix agreed, role cards written, managers supported as they take decisions, exceptions reviewed weekly.
Review: Count the decisions still reaching the owner. Choose the next handover.

Modules: M08 Founder Dependency · M20 Decision Rights · M19 Designing Roles

OperationsQuality depends on who is on shift.

Diagnosis: There is no written standard. New staff learn by shadowing whoever is available, and inherit their shortcuts.
Solution: Usable procedures for the critical, repeated tasks, with checks where errors start.
Implementation: Procedures written with the people who do the work, staff trained, an error log started.
Review: Measure right-first-time. Move to the next process.

Modules: M13 Standard Operating Procedures · M17 Quality Control · M12 Process Mapping

SystemsThe new system was supposed to fix reporting. Staff still keep spreadsheets alongside it.

Diagnosis: The processes it runs were never defined, and products, customers and suppliers are recorded several ways.
Solution: Fix the process and the data, then the system: in that order.
Implementation: Core processes mapped, master data cleaned with owners, the system reconfigured to the agreed process.
Review: Retire the side spreadsheets. Monitor data quality.

Modules: M26 ERP: What It Can and Cannot Fix · M30 Data · M12 Process Mapping

Management visibilityMeetings are spent arguing about whose numbers are right.

Diagnosis: Every report comes from a different spreadsheet, and key figures are defined differently by different people.
Solution: Single definitions, a short set of KPIs, and a management rhythm that uses them.
Implementation: KPI definitions with owners, a reporting calendar, one dashboard designed for one meeting, a monthly review.
Review: Check that reporting takes less time and that decisions change because of it.

Modules: M41 Management Information · M39 KPIs That Drive Decisions · M42 Management Rhythm

GrowthRevenue grows, but profit does not follow.

Diagnosis: Growth consumes cash and capacity, and nobody knows which lines and customers actually contribute.
Solution: Understand true contribution, then reprice, simplify or sequence growth around it.
Implementation: Contribution calculated by line and customer, a pricing policy with discount limits, a sequenced growth plan.
Review: Watch margin and cash at each step of growth. Address the next constraint.

Modules: M53 Growth Economics · M04 Unit Economics · M50 Pricing

Start with the diagnosis.

Then choose: work through the recommended modules yourself, or apply for KSL to work alongside you.

Take the Diagnostic Or work with KSL