There is an uncomfortable truth lurking behind the excitement around artificial intelligence. The technology is genuinely remarkable, but it is not magic. It is a mirror that reflects the quality of your thinking straight back at you. 

I have watched businesses pour money and hope into AI tools expecting transformation, only to be left wondering why the results feel flat. The answer is almost always the same. They treated the prompt as an afterthought rather than the main event. 

When you use AI to design a website or build software, roughly 80 per cent of the value comes from getting the prompt right. The remaining 20 per cent is the AI doing what AI do well. Get that ratio the wrong way round, and you will be forever disappointed. 

Garbage in, garbage out! 

Anyone who worked in computing a few decades ago will remember the old maxim GIGO: garbage in, garbage out. It was true of mainframes, and it is just as true of the most sophisticated AI models today. 

An AI LLM does not know what you want. It cannot read your mind, sense your brand or intuit the commercial pressures sitting behind a project. It only knows what you tell it, and it will fill any gaps you leave with its own assumptions. 

Feed it a vague instruction, such as “build me a website,” and you will get something generic, forgettable, and almost entirely useless. The fault does not lie with the AI. It lies with the brief. 

This is the part so many people miss. They expect brilliance from laziness. They want a world-class outcome from a one-line request and then conclude that AI is overhyped when it fails to deliver. 

The quality of what comes out is dictated almost entirely by the quality of what goes in. That single idea, properly understood, changes everything about how you work. 

Why is the prompt the project? 

If you accept that 80 per cent of the work sits in the prompt, then your entire approach has to shift. The prompt stops being a quick question and becomes the project itself. 

Think about how you would brief a talented but brand-new designer or developer on their first morning. You would not simply say make it nice and walk away. You would explain the business, the audience, the goals, the constraints and the things you absolutely cannot live without. 

That preparation is exactly what a good prompt demands. The difference is that the AI will act on your brief instantly and without complaint, which makes the clarity of that brief all the more important. 

When we approach a new website or software build, we invest significant effort up front in defining what success actually looks like. What is the purpose of the site? Who is it speaking to? What tone, what structure, what functionality and what should it deliberately avoid? 

Answer those questions properly, and you are no longer hoping for a good result. You are an engineer. 

Context engineering and cascading prompts. 

The most powerful idea I have come across in this field is what some AI experts are beginning to call context engineering. It is the discipline of feeding the AI the right information, in the right order, so that every response is grounded in reality rather than guesswork. 

A single prompt, however well written, rarely carries enough context to produce something exceptional on its own. The real skill lies in building that context deliberately and then cascading your prompts so each one builds on the last. 

In practice, this means starting broad and then narrowing with intent. You establish the foundations first, then refine, then refine again, layering detail with each step rather than trying to capture everything in one impossible instruction.

  • Begin by setting the context: the business, the goals and the audience the work must serve.
  • Then define the structure and the rules the output must follow.
  • Then generate, review and feed your corrections back in as fresh, specific instructions.
  • Finally polish, tightening tone, detail and consistency until it is genuinely fit for purpose.

Each prompt informs the next. By the time you reach the end of that cascade of prompts the AI is operating with a rich understanding of what you actually want, and the results can be truly remarkable.

You are not writing one prompt. You are conducting a conversation that compounds in value with every exchange.

The same principle applies to code

None of this is limited to design. When building software the discipline matters even more, because vague instructions do not just produce something ugly. They produce something broken and unworkable.

An AI asked to write code with no context will make sweeping assumptions about your architecture, your data and your intentions. It might give you something that runs but does the wrong thing entirely, which is often worse than something that fails outright.

Give it the proper context though and the picture changes completely. Describe the existing system, the conventions you follow, the edge cases you care about and the standard you expect, and the AI becomes an extraordinarily capable collaborator.

It still needs an experienced software developer to review and direct it. But that hand spends its time guiding genuine craftsmanship rather than untangling avoidable mistakes.

Effort in, brilliance out

The businesses winning with AI are not the ones with access to better tools. The leading tools are increasingly accessible to many businesses, though cost, integration and data-privacy considerations still vary widely. They are the ones willing to put the thinking in at the front.

This is genuinely good news. It means competitive advantage still belongs to those who understand their customers, their objectives and their market well enough to articulate them clearly. AI rewards clarity of thought, and clarity of thought remains a distinctive human strength.

So if you are exploring how AI might design your website or build your next piece of software, resist the temptation to rush the brief. That is precisely where the value hides.

Put the effort into the prompt and the outcome will not just be acceptable, it will be outstanding. Treat the prompt as the afterthought and you will get exactly what you put in, which is to say very little at all.

The Pareto Principle — the observed tendency for roughly 80 per cent of outcomes to stem from 20 per cent of inputs — has informed business thinking for generations, though it is an empirical pattern rather than a universal law. In the age of AI it has never been more relevant. Master the 80 per cent that is the prompt and the technology will handle the rest with results that, frankly, can be mind-blowing.

← All insights

Ready to talk?

Let’s start with a conversation.

A 30-minute discovery call — no slides, no pitch. Just a conversation about what you’re working on and whether we’re the right fit.