Introduction
Leverage Principle 02 2 min

Build the first version yourself, with AI

The starting point

A support lead spends her Fridays sorting the week’s requests in a spreadsheet. She has never written a line of code. A developer on her team has to write the page that presents the new offer. He has never written for customers.

Both are waiting for someone else.

The move

Build the first version yourself with an AI, then check it against what you know of your trade.

Why it works

AI has moved the line between trades, in both directions. The support lead describes her sorting to an AI and, within an hour, has a small tool that sorts the requests and produces the Friday summary. The developer has an AI read his page and ask him a customer’s questions, and rewrites it three times before lunch. Each built outside their lane, without waiting for the other.

What makes the difference is what you already know. The support lead sees straight away that the tool files refund requests wrongly: she knows those cases. The developer knows how to check that the page promises nothing the product does not do. AI multiplies your judgement. Without judgement, it multiplies mistakes, faster and with more confidence.

The shortcut is taking a fluent answer for a right one, or skipping the understanding because the result looks finished. Well-written text can invent a refund condition. A clean spreadsheet can add up wrong. Read what matters as the work of a brilliant, overconfident intern.

If you are starting out, AI teaches you fast, as long as you ask it why. Have it explain each step, then redo one without it.

Try this

Pick a task you have been waiting on someone else for more than a week. Build a first version with an AI, in one hour.

Check three things: the facts, the numbers, and what is promised. A sorting tool gets compared to your own sorting for a week before you rely on it; a calculation model gets checked by redoing one key calculation by hand. Show the result to the person you were waiting for. You no longer arrive with a request, you arrive with a draft.

Write down what the AI got wrong and how you spotted it. That tells you where your judgement is solid, and where it is still missing.

To discuss

What have we been waiting weeks for from another team that we could build ourselves this week?

Your notes

Only you read them.