The 4C Framework

The 4C framework is Kafkai's patented method for deciding what to write next. Every recommendation Kafkai computes is one of four kinds: Compete — where to fight head-on, Catch-up — what to catch up on, Consolidate — what to merge, and Complement — what to add next.

Most content decisions come down to one of those four moves: fight for a topic, catch up on one, merge what overlaps, or add what is missing. Teams already make these calls — in meetings, by feel. The 4C framework makes them from data, per topic, with the reasoning attached.

Compete — where to fight head-on

Topics where you and a competitor both appear in the search results. The market already counts both of you as relevant; the question is which of these head-to-head pages deserves another pass, and which are fine as they are. Kafkai returns the list, with the overlap that puts each topic on it.

Catch-up — what to catch up on

Where you are behind. A competitor is being found for a topic you also cover, and you are not — or your own page attracts searches it does not actually satisfy. Each item is either a page you have not written or a page not doing its job. Together they are the clearest writing list the data can produce.

Consolidate — what to merge

Articles on your own site competing with each other: near-duplicates, overlapping coverage, three posts doing one post's work. The recommendation is to merge and redirect — fewer, stronger pages in place of several weak ones. This is one reason Kafkai keeps your published archive: nobody can recommend merging two articles without knowing both exist.

Complement — what to add next

The open ground next to what already works. When one of your pages visibly earns its readers, Complement points at the topics beside it that nobody has covered properly yet. It is how a content plan grows by extension instead of imitation.

A list is not a decision

Keyword tools return lists. A list is not a decision. The same topic means different work depending on who already ranks for it, what you have already published, and what happened after you published it. The 4C framework carries that context, so every recommendation arrives as a move — fight, catch up, merge, or add — with the reasoning attached. The writing order falls out of the data instead of out of a meeting.

Where it runs

The 4C analysis runs inside Kafkai. Register your site, name your competitors, and Kafkai computes the recommendations from live search results and your own published archive. Through the Kafkai MCP server, your AI agent can request the same analysis directly and reason over the result: Kafkai does the counting, your agent does the thinking. It works with the LLM you already use — no bundled model, no new subscription, prepaid credits.

It is built for teams that have to decide, week after week, what gets written next — on one site or across a portfolio of client sites. The rest of what Kafkai does around the framework is on the features page. What a conversation with it looks like is on the Example Prompts page.

What the 4C framework does not do

• It does not track rankings. Rank data on young domains is unreliable, and we do not sell numbers we cannot stand behind.
• It does not promise rankings or traffic. It puts your options in order; what happened after publishing is measured, not predicted.
• It does not write your articles. It tells you what is worth writing. The writing stays with you, or with your agent.

The patent

The 4C framework and the competitive-analysis technology underneath it are covered by Patent No. 7701764, granted by the Japan Patent Office on 24 June 2025 (the announcement). KAFKAI® is a registered trademark of Kafkai Giken, Inc., Reg. No. 6661421. When we say the method is patented, that is the number to check.