The Skill Soup Manifesto

For twenty years the career advice was specialize. Pick one lane. Become the best at it. That advice was built for a world where deep knowledge was scarce. That world is gone.

The business problem is sustainability. Consultants who sell one skill get commoditized the moment an LLM can do half of it. Consultants who combine skills in non-obvious ways become harder to replace. The skill soup is how you stay useful in a rising tide.

The thesis

A skill soup is the set of competencies you hold at the same time. It is not a list. It is a pot. The value comes from the way flavors blend.

My current pot:

• Django and TypeScript for systems that ship
• Python scripting for glue work
• Brand and document design for client-facing deliverables
• Sales and discovery for the front of the funnel
• AI tooling across every layer

None of those are rare alone. Together they let me run a full engagement solo.

The math

If I have five skills and a client problem requires three of them in combination, the number of competitors who match drops fast. Five pick three is ten combinations. Most competitors master one lane. I only need to be adequate in each.

How to build a soup

1. Pick skills that share a base. I use code in every one of mine.
2. Add one adjacent skill every quarter.
3. Kill any skill you have not used for a client in a year.
4. Write about each skill publicly. Writing forces integration.

What it is not

A skill soup is not dabbling. Each skill has to pass a bar. You have to ship production work with it. Otherwise it is a hobby and clients smell it.

The consulting edge

Clients do not buy depth. They buy outcomes. A soup lets you own the outcome from discovery to deploy. See David Epstein's Range for the academic case. My case is practical. I have a pot. I keep stirring it. It feeds me.