Insights · Business models

KAGAPSO Framework Explained: Model Before Marketing

By Mehmet Aydın · Published October 27, 2026

A business owner can ask for more inquiries while still being unclear about which customers the business should serve. Another can have a useful offer but no reliable way to move an inquiry into an agreed piece of work. Those situations deserve different responses.

The KAGAPSO framework connects the business model with the work needed to execute it. Developed by Mehmet Aydın, it starts with four decisions about the customer, problem, revenue model and offer. It then connects those decisions to marketing, sales and operations.

The practical output is a set of choices the team can explain and test. The framework helps structure that discussion; results still depend on the choices, evidence and implementation that follow.

What does KAGAPSO stand for?

KAGAPSO uses the initials of seven Turkish terms. The first four form KAGA, the business model. The final three form PSO, its execution.

Write one clear answer to each question. A list of unrelated audiences or revenue models makes it harder to decide what to build. If the business has several distinct models, map each separately before deciding which one deserves attention.

Start by describing the business that exists

Separate the current model from the model you would like to have. Use actual inquiries, accepted work, delivery records and customer language to describe how the business operates today.

For example, an owner might describe the company as a recurring service business while most accepted work consists of one-off projects. That distinction matters. Recurring delivery requires different scheduling, responsibilities and customer expectations from project delivery.

Keep three columns in your notes: current evidence, proposed change and unanswered question. A proposed audience belongs in the second column until the business has evidence that it can reach and serve that audience. This keeps an attractive idea from silently becoming an established fact in the plan.

Define the customer and their central problem together

“Small businesses” may describe a broad market, but it leaves many decisions unresolved. Consider the situation that makes a customer need help, who makes the decision and what work the business is equipped to deliver.

The problem should be specific enough to guide the offer. “Needs growth” is less useful than “cannot reliably hand a qualified inquiry to the person responsible for responding.” The latter suggests questions the owner can investigate: where the inquiry arrives, what information is missing and who owns the next step.

A narrow starting point does not prevent the business from serving other customers. It gives this particular model a coherent focus. Expand the model deliberately when the evidence supports doing so.

Keep the revenue model and the offer distinct

The revenue model explains how the business earns money: for example, a defined project, a subscription, rental or licensing. The offer explains what the customer receives and why it is useful.

“Subscription” does not explain the customer outcome. Likewise, a compelling outcome does not explain the delivery commitment behind an ongoing service. Write both down so the business can examine whether they fit together.

An offer also needs boundaries. State the work included, information the customer must provide, the next step and the circumstances that require a separate discussion. Those details help sales describe the service accurately and help operations recognize the work it has agreed to deliver.

For a deeper examination of these decisions, explore business model consulting.

A hypothetical example: an inquiry handoff service

The following is an illustration, not a customer case study or a record of measured results.

Imagine a consultant who wants to help owner-led HVAC businesses organize their incoming service requests. A first KAGA draft could read:

This draft is narrow enough to test. It also exposes unanswered questions: Does the owner consider this problem important? Which inquiry channels are in scope? Can the existing tools support the handoff? Who will maintain it after the project?

The business should investigate those questions before treating the proposed model as viable. A plausible worksheet does not establish demand, delivery capacity or profitability.

Turn the model into marketing, sales and operations

Once the KAGA choices are clear, map PSO against the same offer.

Marketing needs to explain the selected problem to the selected customer. In the hypothetical example, a useful article might help an HVAC owner spot an unassigned service request. Its next step could lead to a page explaining the inquiry handoff service. The message should match what the service actually covers.

Sales needs a way to establish suitability. The discussion might confirm the customer's current channels, response responsibilities, existing tools and desired scope. A request for a conversation remains a request until an appointment is confirmed. An implementation proposal should describe the agreed deliverables.

Operations needs the context required to deliver: the approved workflow, responsible people, access needed for the work, acceptance checks and an escalation route. The handoff should also explain what happens when a request is incomplete or outside scope.

Review the full journey. A marketing message that promises something operations cannot deliver is a model issue worth resolving before increasing demand.

Decide where AI or automation belongs

Define the task before selecting software. A workflow may benefit from a clearer assignment rule or checklist in the tools the team already uses. Other tasks may justify a scoped automation or AI implementation.

For any proposed automated step, record its input, permitted action, source of approved information and responsible person. Include a way to pause it and a route for exceptions. Test missing information, corrections and unavailable systems as well as ordinary requests.

Automation can change how work is distributed without removing the work altogether. Record the owner's involvement, external partners and human review explicitly. Explore AI consulting for small businesses when the next decision concerns which workflow is suitable for AI.

Use a short worksheet to choose the next action

Complete these prompts for one model:

1. Our chosen customer is ______.
2. Their central problem, in their own words, is ______.
3. Our main revenue model is ______.
4. Our concrete offer is ______.
5. The customer will discover and understand it through ______.
6. A suitable inquiry becomes an agreed purchase through ______.
7. Delivery is owned by ______, with exceptions handled by ______.

Then underline the answer supported by the weakest evidence. Choose a next action that helps resolve that uncertainty. It might be reviewing recent inquiries, speaking with a relevant customer, clarifying an offer or testing a handoff with approved sample information.

Define what you will observe before making the change. An acknowledgment, a customer reply, an accepted proposal and completed delivery are different events. Keep those records separate so the review reflects what actually happened.

When is a KAGAPSO review useful?

A review can help when the business is considering a new customer segment, changing its offer, entering a market or deciding whether another campaign or automation addresses the real constraint. It can also provide a shared map when marketing, sales and delivery teams describe the business differently.

Begin with one model and one unresolved decision. Bring a short account of the current process and evidence relevant to that decision. The aim is to leave with a clearer next action and a way to evaluate it.

Explore the KAGAPSO approach or contact Mehmet Aydın to discuss a specific business question.