How to Improve an Existing Business with AI Skills

A stalled business is a confusing place to stand. Revenue is real, customers are real, payroll clears every month — and yet the line has gone flat. You are working harder than ever and the company is not getting better. The instinct is to look for the one missing tactic: a new channel, a new feature, a heroic quarter. But businesses that have plateaued rarely lack effort. They lack a clear diagnosis of what is actually holding them back, and a disciplined operating system to act on it week after week.

This guide is for the owner or operator of a company that already works but has stopped moving. The problem is almost never a single thing. Strategy has decayed into a list of ambitions. The team is busy but pulling in different directions. Meetings produce updates instead of decisions. Pricing was set years ago and never revisited. Your best people are quietly disengaging. Each of these compounds the others, which is why poking at one tactic at a time never breaks the plateau.

The fix is to work the layers in order — strategy, then execution cadence, then management, then team structure, then motivation, then measurement, then the two highest-leverage commercial levers, negotiation and pricing — and to do it with an AI agent that carries the actual frameworks, not a generic chatbot guessing. Each of the eight skills below packages a specific, battle-tested business book so your agent (Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw, or Hermes Agent) can apply its real method to your real numbers. You install a skill once with npx skills add wondelai/skills/<slug> --global and invoke it by telling the agent to use it.

A plateau is not a lack of effort. It is a lack of diagnosis, compounded by an execution system that forgot how to choose.

Worked top to bottom, this is roughly a two-quarter turnaround: a week of honest strategy work, a quarter to install the operating rhythm and fix how the team is led and shaped, and a parallel track to repair what you measure, how you negotiate, and what you charge. Let’s go layer by layer.

Phase 1 — Diagnose the real challenge before you touch anything

Start with strategy, because everything downstream inherits its mistakes. The single most common reason a working business stalls is that its “strategy” is a goal list wearing a strategy costume: grow 30%, expand to a new region, launch the AI feature, lift NPS to 60. None of those is a strategy. They are ambitions with no diagnosis of the obstacle and no choice about where to concentrate.

This is the exact territory of Good Strategy Bad Strategy. Richard Rumelt’s argument is that good strategy has a simple, almost boring structure he calls the kernel: an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and a set of coherent actions that carry the policy out. Bad strategy is not the absence of strategy — it is an active substitute for it: buzzword fluff, a refusal to name the actual obstacle, and laundry lists of forty “priorities” that concentrate nothing. The work is choice: pressing your scarce resources onto the one or two pivot points whose movement unlocks everything else.

Hand your agent the plan you actually have — last year’s deck, the OKR sheet, whatever passes for direction — and have it audit the plan as strategy, not cheerlead it.

The skill scores strategies 0–10 against the kernel and reports what is missing. Expect a low score the first time; most real plans land at 3–4 because they are mostly goals and vision with no diagnosis. The valuable output is the diagnosis itself. Rumelt’s example is Lou Gerstner reframing IBM’s 1993 crisis from “mainframes are dying, break up the company” to “our advantage is integrated capability; the obstacle is internal coordination” — and everything downstream changed. Your stalled business has an equivalent reframe waiting, and naming it is the pivot of the whole turnaround.

Once you have a diagnosis, sharpen it with two more moves the skill knows well. First, find your pivot point — the place where a small concentrated effort is amplified. Rumelt’s chain-link idea is decisive for stalled businesses: in a system whose performance is capped by its weakest link, investing in the strong links is wasted until you fix the weak one. A plateau is usually one jammed link masquerading as a general malaise.

Second, force the choice. Have the agent write the explicit no-list — the things this strategy says you will not do — because a guiding policy that rules nothing out is a platitude. If a competitor could paste your guiding policy into their own deck unchanged, it is not a policy. The output of Phase 1 is one page: a diagnosis, a guiding policy, three to five coherent actions, one proximate objective, and a list of what you are deliberately stopping.

Phase 2 — Install an execution rhythm that survives Monday

A perfect strategy dies if the company has no machinery to execute it. This is the gap between vision and traction, and it is exactly what Traction EOS — Gino Wickman’s Entrepreneurial Operating System — exists to close. Wickman’s blunt framing: great vision without traction is hallucination; traction without vision is aimless. EOS connects the two through a weekly operating rhythm built on six components — Vision, People, Data, Issues, Process, Traction.

For a stalled business the two components that move the needle fastest are Rocks and the Level 10 Meeting. Rocks are the 3–7 most important priorities for the next 90 days, each with one owner. Ninety days is long enough to finish something meaningful and short enough to keep urgency. The discipline is brutal scoping: a maximum of seven company Rocks, each SMART and binary (done or not done, no partial credit), aimed squarely at the proximate objective you set in Phase 1.

Then install the meeting that makes Rocks real. The Level 10 Meeting is the same day, same time, same 90-minute agenda every week: segue, scorecard, Rock review, headlines, to-do list, then sixty minutes of IDS — Identify, Discuss, Solve. Most stalled companies have meetings that are 90% status and 10% problem-solving; EOS inverts that. The point of the meeting is to solve issues permanently, not to narrate them. The IDS track itself is a skill the agent can run: ask “why” until you reach the root cause, state the issue in one sentence, give everyone input but not equal time, then decide and assign an owner.

If you only adopt one thing from this layer, make it the Level 10 cadence. The recurring rhythm is what converts a one-time strategy offsite into a company that actually changes its behavior. Protect the meeting; never cancel it. A stalled business that starts solving its real issues to root cause, weekly, feels different within a month.

Phase 3 — Fix how the business is managed for output

You now have direction and a cadence. The next plateau-breaker is leverage: a manager’s job is not to be busy, it is to multiply the output of everyone around them. High Output Management is Andy Grove’s operating manual for exactly this, and its core equation is the one most stalled-business owners have never internalized: a manager’s output equals the output of their organization plus the output of the neighboring teams they influence. Nothing you personally do counts in itself — it counts only through how it raises that combined output.

That reframe is uncomfortable for founder-operators because it indicts the habits that feel productive: doing the work yourself, approving everything, being the bottleneck everyone routes through. Grove names these negative-leverage activities — meddling (supervising an expert in detail), waffling (stalling a decision others are waiting on), and broadcasting your own gloom — and shows they multiply downward through the team. Start by auditing your own week.

Two specific Grove tools repay the most in a stalled company. The first is the one-on-one, which Grove insists is the subordinate’s meeting: they own the agenda and bring it, you listen and take the notes, and the real issue usually surfaces in the last five minutes when you ask “what else is on your mind?” Frequency is set by task-relevant maturity (TRM), not seniority — weekly for someone new to a task, monthly for a veteran, never less. The second is delegation without abdication: delegate the tasks you know best because monitoring them costs you least, then monitor at the task level, sampling deeper when TRM is low and lighter as it rises.

The third Grove idea — output indicators paired with quality counterparts — overlaps with the measurement work in Phase 6, so hold it for now. The management layer’s job is to convert your own scarce hours into the team’s multiplied output, and to make delegation safe enough that you can finally step off the critical path.

Phase 4 — Reshape teams so work stops getting stuck between them

Sometimes the plateau is not strategy, cadence, or management — it is structure. If every meaningful change requires three teams to coordinate, if handoffs eat weeks, if “who owns this?” has no clean answer, the org chart itself is the bottleneck. Team Topologies by Matthew Skelton and Manuel Pais is the skill for this, and its founding observation is Conway’s law: organizations ship their communication structure. Your systems and processes are a mirror of how your teams actually talk, so if the output is tangled, the team boundaries are tangled.

The skill reduces every team to one of four types — stream-aligned (owns a flow of business value end to end; the default and the majority), enabling (grows a capability in other teams, then leaves), complicated-subsystem (encapsulates deep specialist knowledge), and platform (provides an internal product that reduces everyone else’s load). The diagnostic value for a stalled business is enormous: most plateaued orgs are full of ambiguous charters — “the operations team,” “the data team” — that accumulate work belonging nowhere and interact unpredictably.

The second lever is cognitive load. Teams thrash not because they are too small but because they own too many domains. The heuristic is concrete: at most one complicated domain per team, and never split a single complicated domain across two teams. When a team is drowning, the fix is fewer domains, not more headcount. And the cheapest load to remove is extraneous — the tooling, environments, and process friction that a thin internal platform or a few paved paths can eliminate without any reorg at all.

A word of judgment: a reorg is disruptive, so reach for this layer only when the evidence points at structure — handoffs dominating lead time, the same coordination meetings recurring, shared ownership making everything everyone’s-and-no-one’s. If your teams already deliver cleanly, skip ahead. Team Topologies is the right tool precisely when the work keeps getting stuck between people rather than within them.

Phase 5 — Re-motivate the people who quietly checked out

A stalled business has a morale signature: your best people are still showing up, but the spark is gone. The reflexive fix — a spot bonus, a contest, a new incentive plan — usually makes it worse, and Drive Motivation explains exactly why. Daniel Pink’s research is that for any task requiring even rudimentary cognitive effort, “if-then” rewards either do not work or actively degrade performance: they extinguish intrinsic motivation, narrow focus, crush creativity, and foster short-term thinking. The carrot-and-stick model is built for routine algorithmic work, and almost nothing in your business is routine algorithmic work anymore.

What actually sustains performance is intrinsic — Pink’s three pillars of Autonomy, Mastery, and Purpose (AMP). Autonomy is choice over the four T’s: task, time, technique, and team. Mastery is the chance to visibly get better at something that matters, calibrated so the challenge sits between boredom and anxiety. Purpose is the sense of serving something larger than the next quarterly number. Audit your current setup against all three.

The compensation principle is worth stating plainly because it contradicts most operators’ instincts: pay people enough to take money off the table — fair, ideally above market — and then stop using money as the lever. Beyond “enough,” more money does not increase motivation for cognitive work; it just resets expectations. Replace “if-then” bonuses (“hit the target and you get X”) with “now-that” recognition (“you hit the target — here’s an unexpected thank-you”), which delivers the reward without the pressure and gaming that come from dangling it in advance.

This layer pairs naturally with Phases 3 and 4: the autonomy Grove’s delegation creates and the clear ownership Team Topologies establishes are themselves powerful motivators. When you stop being the bottleneck and give people a domain they genuinely own, you are not just improving flow — you are rebuilding the autonomy and mastery that a plateau erodes.

Phase 6 — Measure the one number that actually tells you the truth

By now you have direction, cadence, leverage, structure, and motivation. The risk is that you are still steering by the wrong instruments. Stalled businesses are usually swimming in data and starving for insight: a dashboard of forty metrics, every meeting citing a different number, and nobody able to say whether last month was good. Lean Analytics by Alistair Croll and Benjamin Yoskovitz is the discipline that fixes this, and its core principle is ruthless: focus on the one metric that matters right now — everything else is noise that feels like progress.

The skill teaches you to separate good metrics from vanity metrics. A good metric is comparative, understandable, a ratio or rate (not an ever-growing total), and behavior-changing — if a number will not change what you do next, stop watching it. The single most reliable vanity tell is the cumulative up-and-to-the-right chart: total signups, total users, total revenue all rise even while the business bleeds. Start by purging the dashboard.

The second move is the One Metric That Matters (OMTM) with a counter-metric and a line in the sand. The OMTM is the number that tells you whether the riskiest part of the business is working right now; it rotates as you pass stage gates. You pair it with a counter-metric so it cannot be gamed — activation speed paired with 30-day retention, sales velocity paired with refund rate. And you draw a line in the sand with three parts: a target number, a date, and a pre-committed answer to “what do we do if we miss?” decided before the results arrive, so the goalposts cannot move.

This layer is the feedback loop for everything above it. The chain-link constraint from Phase 1, the Rocks from Phase 2, and Grove’s paired output indicators from Phase 3 all become testable here. Without a real OMTM, every result gets rationalized and no experiment can fail — which is its own quiet kind of plateau.

Phase 7 — Stop leaking margin in every negotiation

The last two layers are the highest-leverage commercial moves in a business that already has customers, because they drop almost entirely to the bottom line. Start with the conversations you are probably handling on instinct: renewals, vendor contracts, big-deal terms, and the relentless pressure to discount. Negotiation packages Chris Voss’s tactical-empathy method from Never Split the Difference, and its governing idea is that the path to a good outcome runs through making the other side feel understood — not through logic, argument, or splitting the difference. Voss’s hard rule: no deal is better than a bad deal.

The most immediately useful pattern for a stalled business is the renewal under price pressure, where the operator’s instinct is to cave on price the moment a customer mentions a cheaper competitor. The skill arms you with the accusation audit (preemptively voicing every negative the other side might be thinking, which defuses it), calibrated questions (“how am I supposed to do that?” is the most powerful pushback that isn’t a no), labeling (“it sounds like…”), and the Ackerman bargaining structure of decreasing increments ending on a precise, non-round number plus a non-monetary sweetener.

The deeper payoff is Black Swans — the hidden pieces of information that transform a negotiation once you find them. Voss’s claim is that every negotiation has roughly three lurking: secret constraints (their boss capped the budget), hidden motivations (this deal saves someone’s job), or unknown context (a competitor just moved). The competing bid is rarely the real story; tactical empathy and calibrated questions are how you uncover what is. The same skill works on vendor renewals, where the discipline of never conceding without getting something in return can claw back real cash from your cost base.

Phase 8 — Reprice around the value you actually deliver

The final and often largest lever is the one most stalled businesses are most afraid to touch: price. If your pricing was set years ago from cost-plus math or by copying a competitor, you are almost certainly leaving money on the table, charging the wrong segments the wrong amounts, or both. Monetizing Innovation by Madhavan Ramanujam and Georg Tacke is the skill for repricing, and its core finding is sobering: 72% of new products miss their revenue targets, and the common root cause is treating price as an afterthought. Price is the clearest measure of how much customers value what you offer — which makes it a diagnostic, not just a number.

The skill’s first contribution is naming which monetization failure you are drifting toward. There are four: feature shock (cramming so much in that value and clarity collapse), minivation (the right product priced too timidly — its signature is a near-100% win rate and zero price pushback), hidden gem (a valuable offering nobody monetizes because it has no owner), and undead (a product kept alive past the evidence). A stalled business with a high close rate and no pricing objections is very often minivating — quietly undercharging — and does not realize it.

The second contribution is segmentation by willingness to pay and leader-filler-killer packaging. Customers differ in what they value and what they will pay, so one offer at one price overcharges some and undercharges the rest; the fix is three or four offers built on WTP clusters, not demographics. Within those tiers, every feature is a leader (drives the purchase), a filler (modest value), or a killer (actively reduces willingness to pay if customers are forced to fund it). The classic mistakes a stalled business makes are giving the leader feature away in the cheapest tier, so nobody has a reason to upgrade, and bundling a killer that gives buyers a reason to reject the whole package.

Before any price change ships, have the agent design a willingness-to-pay conversation you can run with real customers — the acceptable / expensive / prohibitively-expensive probes, purchase-probability on a 1–5 scale where only the top box counts — so the new pricing rests on evidence, not nerve. Repricing is the move with the shortest path to profit in a business that already has demand; done from validated WTP rather than gut feel, it routinely breaks a revenue plateau on its own.

Your checklist

• Run a good-strategy-bad-strategy audit of your current plan; score it and write a one-page kernel — diagnosis, guiding policy, coherent actions
• Identify the single binding chain-link constraint and set one proximate objective against it
• Write your explicit no-list: what this strategy says you will stop doing
• Translate the strategy into 5–7 quarterly Rocks with one owner each, using traction-eos
• Install the weekly Level 10 Meeting and start running IDS on recurring issues to root cause
• Audit your own calendar for leverage with high-output-management; cut the negative-leverage habits
• Set up subordinate-owned 1:1s on a TRM-based cadence and delegate-with-monitoring off your critical path
• If work keeps getting stuck between teams, classify them with team-topologies and realign to value streams
• Check team cognitive load — at most one complicated domain per team — and shed or platform-ize the excess
• Audit incentives against Autonomy, Mastery, Purpose with drive-motivation; replace if-then bonuses with now-that recognition
• Purge vanity metrics with lean-analytics; pick one OMTM, a counter-metric, and a line in the sand
• Build cohort retention tables and confirm whether you’ve actually passed the stickiness gate
• Prepare your next big renewal with negotiation: accusation audit, calibrated questions, an Ackerman plan
• Diagnose your monetization failure with monetizing-innovation and reprice from validated willingness to pay

Common mistakes

Jumping to tactics before the diagnosis. The plateau tempts you to grab a channel or a feature. Without Phase 1’s honest diagnosis, you will pour effort into a strong link while the weak one stays jammed. Do the strategy work first, even though it feels slower — it is the thing that makes everything else land.

Treating the strategy offsite as the finish line. A kernel that lives in a deck changes nothing. The Level 10 cadence from Phase 2 is what converts a one-time decision into a company that behaves differently. If you adopt one thing, adopt the weekly rhythm — and never cancel it.

Confusing being busy with creating output. The hardest habit for a founder-operator to break is doing the work themselves. Grove’s whole point is that your output is your organization’s output. Every hour you spend as the approval bottleneck is negative leverage multiplying downward. Delegate the work you know best, monitor by task-relevant maturity, and get off the critical path.

Reorganizing when the problem isn’t structure. Team Topologies is powerful, but a reorg is disruptive and seductive — it feels like decisive action. Only reach for Phase 4 when the evidence points at structure: handoffs dominating lead time, recurring coordination meetings, ownership that’s everyone’s-and-no-one’s. If teams already deliver cleanly, skip it.

Throwing money at disengagement. A contest or a spot bonus to re-energize the team usually backfires. If-then rewards crowd out the intrinsic motivation that actually sustains cognitive work. Pay fairly enough to take money off the table, then rebuild autonomy, mastery, and purpose instead.

Steering by vanity metrics. A cumulative chart that only goes up will hide a business that’s quietly decaying. If a number won’t change a decision, it’s noise. Pick the one metric that reflects your riskiest assumption, guard it with a counter-metric, and commit to a miss response in advance.

Discounting on instinct at renewal. Caving the moment a customer names a cheaper competitor leaves margin on the table and trains them to push every time. The competing bid is rarely the real story — hunt the Black Swan, and never concede without getting something back.

Repricing from cost or competitors instead of value. Cost-plus and copycat pricing anchor on the wrong thing entirely. A high win rate with no price pushback is the signature of undercharging. Reprice from validated willingness to pay, segment by it, and make sure your cheapest tier doesn’t give away the leader feature.

Frequently asked questions

Which skill should I start with if I can only install one?

Good Strategy Bad Strategy. Every other layer inherits the quality of your diagnosis. If you skip it, you risk installing a flawless execution rhythm (Phase 2) around the wrong objective, or repricing (Phase 8) without knowing which constraint is actually capping the business. An hour spent forcing your plan through the kernel — diagnosis, guiding policy, coherent action — reframes everything that follows. If you want a fast second, add traction-eos, because the Level 10 cadence is what makes the strategy stick.

How long does this realistically take?

Plan for two quarters. Phase 1 is about a week of focused strategy work. Phases 2 through 5 — installing the operating rhythm, fixing how you manage and shape teams, and re-motivating people — take a full quarter to bed in, because cadence and behavior change need repetition. Phases 6 through 8 (metrics, negotiation, pricing) run as a parallel track and can produce results faster, since fixing your OMTM or repricing from validated willingness to pay can move numbers within weeks. The eight skills combine into one workflow, but you don’t install them all on day one — work the layers in order.

Do these skills work for a services or brick-and-mortar business, not just SaaS?

Mostly yes, with judgment. The strategy, EOS, management, team, and motivation skills are model-agnostic — good-strategy-bad-strategy, traction-eos, high-output-management, and drive-motivation were written for general business and apply cleanly to an agency, a clinic, or a manufacturer. lean-analytics and monetizing-innovation lean toward digital and subscription models but carry frameworks (the OMTM, willingness-to-pay segmentation, leader-filler-killer packaging) that translate well — a services firm absolutely has an OMTM and a WTP curve. team-topologies is the most engineering-specific; treat it as the optional structural layer and apply it only if you run technology teams.

What’s the difference between this guide and the “grow” guide?

This guide is about improving a business that has stalled — fixing the internal machinery (strategy clarity, execution, management, motivation, pricing) so it can move again. The companion guide, grow an existing business with AI skills, focuses on expansion once the engine is healthy — acquisition channels, demand generation, and scaling what already works. Improve first, then grow: pouring growth effort into a business with a jammed chain-link or a leaky retention bucket just burns money faster.

How do I actually invoke a skill once it’s installed?

Install it once with npx skills add wondelai/skills/<slug> --global — for example npx skills add wondelai/skills/lean-analytics --global. Then in your AI agent (Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw, or Hermes Agent) you invoke it by writing a prompt that names it, exactly like the prompt blocks throughout this guide: “Use the lean-analytics skill to…”. The skill loads its full framework into the agent’s context so it applies the real method — Rumelt’s kernel, Grove’s leverage equation, Voss’s tactical empathy — to the specific numbers, plans, and conversations you paste in. Be concrete: reference your actual dashboard, your real renewal, your current pricing page.

Get started

A stalled business doesn’t need a hero quarter. It needs an honest diagnosis, a cadence that survives Monday, a manager who multiplies instead of bottlenecks, and the discipline to measure, negotiate, and price from reality. These eight skills give your AI agent the actual frameworks to do all of it with you — free, open-source, and MIT-licensed.

Install the whole library in about thirty seconds:

npx skills add wondelai/skills --all --global

Then start with Phase 1: paste your current plan into your agent and tell it to use the good-strategy-bad-strategy skill to audit it as strategy. The diagnosis you get back is usually the first time the real obstacle has been named out loud — and that’s where every turnaround begins.

When the engine is running clean again, move on to grow an existing business with AI skills to scale what works. If your stall is on the product side rather than the business side, improve an existing app with AI skills covers the engineering equivalent of this playbook.