# Improve a Business

> Diagnose and fix a plateaued business — a guided journey that orchestrates 8 AI agent skills, one decision at a time.

Published 2026-07-16 · Updated 2026-08-17 · Guided journey · Free and MIT-licensed
Canonical: https://skills.wondel.ai/skills/improve-business/
Source: https://github.com/wondelai/skills/tree/main/improve-business
Companion guide: https://skills.wondel.ai/guides/improve-an-existing-business-with-ai-skills/

**Install:** `npx skills add wondelai/skills/improve-business --global`

## What is the Improve a Business journey?

When revenue flattens, the fix starts with an honest diagnosis rather than a new initiative. Eight phases name the one challenge capping the business, install a weekly operating rhythm, examine structure and motivation, pick the number that tells the truth, and reprice around value — all of it logged in docs/.

## The 8 phases

1. **Good Strategy Bad Strategy** _(gate)_ — What single challenge is capping the business? → `docs/STRATEGY.md` (https://skills.wondel.ai/skills/good-strategy-bad-strategy/)
2. **Traction EOS** — How do we execute the strategy every week? → `docs/OPERATIONS.md` (https://skills.wondel.ai/skills/traction-eos/)
3. **High Output Management** — How does the operator multiply the team, not bottleneck it? → `docs/OPERATIONS.md` (https://skills.wondel.ai/skills/high-output-management/)
4. **Team Topologies** — Is the org structure itself the constraint? → `docs/OPERATIONS.md` (https://skills.wondel.ai/skills/team-topologies/)
5. **Drive Motivation** — Why has the team quietly checked out? → `docs/OPERATIONS.md` (https://skills.wondel.ai/skills/drive-motivation/)
6. **Lean Analytics** — Which one number tells us the truth? → `docs/METRICS.md` (https://skills.wondel.ai/skills/lean-analytics/)
7. **Negotiation** — Where are we leaking margin, and what do customers truly value? → `docs/CUSTOMER.md` (https://skills.wondel.ai/skills/negotiation/)
8. **Monetizing Innovation** — Are we charging for the value we deliver? → `docs/OFFER.md` (https://skills.wondel.ai/skills/monetizing-innovation/)

## What it produces

- `docs/STRATEGY.md`
- `docs/OPERATIONS.md`
- `docs/METRICS.md`
- `docs/CUSTOMER.md`
- `docs/OFFER.md`
- `docs/IMPROVE-BUSINESS-PLAN.md`

## When to use Improve a Business — and when not to

Reach for it when:

- Figure out why growth stalled before launching new initiatives
- Replace a goals-as-strategy plan with a real strategy kernel
- Install an execution rhythm (rocks, weekly meetings, ownership)
- Stop leaking margin in renewals and vendor deals
- Reprice around value instead of cost-plus guesswork

Reach for something else when:

- Acquisition is the constraint, not execution — Grow a Business builds pipeline; this one fixes the machine you have.
- There is no business yet, only an idea — start with Create a Business and its validation gate.
- You just want quarterly rocks and a weekly meeting cadence — Traction EOS installs that without the other seven phases.
- The problem is one renewal or vendor conversation — Negotiation on its own is the sharper tool.

## Example prompts

- Our revenue has been flat for three quarters — diagnose and fix it with me. using improve-business skill _(Flat revenue diagnosis)_
- Run the improve-business journey; start with the strategy diagnosis. using improve-business skill _(Start the journey)_
- Continue our business turnaround from the tracker. using improve-business skill _(Resume journey)_

## Worked example — Diagnose and Fix a Plateaued Business

Revenue has been flat for three quarters and every fix so far was a guess.

```
Our business has plateaued and every fix so far was a guess. Run the improve-business journey starting with a proper diagnosis. Don't let me jump to solutions before the diagnosis is confirmed.

Use improve-business skill.
```

## Frequently asked questions

### How do I install the Improve a Business journey?

Run `npx skills add wondelai/skills/improve-business --global`. It takes about 30 seconds and needs no account. The Improve a Business skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.

### Which skills does the Improve a Business journey run, and what does it produce?

It orchestrates 8 skills across 8 phases — Good Strategy Bad Strategy, Traction EOS, High Output Management, Team Topologies, Drive Motivation, Lean Analytics, Negotiation, Monetizing Innovation — asking you one decision question per phase. Each answer is written to your project's docs/ folder (docs/STRATEGY.md, docs/OPERATIONS.md, docs/METRICS.md, docs/CUSTOMER.md, docs/OFFER.md, docs/IMPROVE-BUSINESS-PLAN.md), so the journey survives across sessions and you keep the reasoning, not just the output.

### What if the strategy diagnosis gate says my plan is a wish list?

That is the most common result, and it is why Good Strategy Bad Strategy goes first. The gate will not let you proceed to Traction EOS carrying a set of goals dressed as a strategy — it names the single critical challenge and writes the kernel into docs/STRATEGY.md, so the operating-rhythm phases have something coherent to execute. Installing a meeting cadence on top of a wish list only makes the wrong work happen weekly.

### Four of the eight phases write to docs/OPERATIONS.md. Is that redundant?

They answer different questions about the same machine. Traction EOS asks how the strategy gets executed every week; High Output Management asks whether the operator multiplies the team or bottlenecks it; Team Topologies asks whether the org structure is itself the constraint; Drive Motivation asks why people quietly checked out. Each appends its own section, so the file ends up one readable account of how the business runs.

### Can I skip the team phases if I run this solo or with three people?

Mostly yes. Team Topologies and Drive Motivation lose their teeth below about five people, and the skip is noted in docs/IMPROVE-BUSINESS-PLAN.md. High Output Management still earns its place — its subject is your own leverage, which is the binding constraint when there is one of you. The metrics, margin and pricing phases at the end are unaffected either way.

### We tried a turnaround last year and it did not stick. Why would this?

Most turnarounds fail at the same two joints: no diagnosis, so effort scatters, and no rhythm, so the plan dies in week three. This journey gates on the first and spends four phases on the second. It also ends on money — Negotiation finds where margin leaks, Monetizing Innovation asks whether you charge for the value you deliver — which is usually where a plateau is actually resolved.