You don’t need to learn to code. You need to learn to explain what you want.

Good dev agencies don’t start building the moment you call them. They interview you first. They ask questions you didn’t know you needed to answer. By the time they start writing code, they understand your problem better than you did when you walked in.

Claude Code can do the same thing – if you ask it to.

The Key Prompt

Most people prompt AI like they’re ordering from a menu. “Build me a contact form.” Then they’re surprised when they get something generic.

Instead, try this:

“I’m not technical. Before you build anything, ask me the questions I should be answering.”

That’s it. You’re not asking for code. You’re asking for the conversation that should happen before code.

Discovery Prompts

Start with one of these:

  • “Before you build anything, interview me like a dev agency would.”
  • “Ask me clarifying questions about what I need – and what I might be forgetting.”
  • “I’m not technical. What questions should I be able to answer before we start?”
  • “Help me think through this problem before we jump to solutions.”

Then answer honestly. “I don’t know” is a valid answer. That’s the point – surfacing what you haven’t figured out yet.

Example: A Real Business Problem

“We’re a consulting firm. People visit our website but have no way to contact us except hunting for our email. I want to fix that. Before you build anything, ask me the questions I should be thinking about.”

Claude Code came back with questions like:

  • What information do you need from people who contact you?
  • Should inquiries go to one person or get routed by topic?
  • Do you want to respond automatically or manually?
  • What’s your current website built with?

Ten minutes of Q&A later, I had clarity I didn’t have before – and Claude Code had enough context to build something that actually fit the business.

The Pattern

  1. State the problem – not the solution you think you want
  2. Admit what you don’t know – “I’m not technical” gives it permission to explain
  3. Ask for the interview – let it surface what you’re missing
  4. Answer honestly – don’t pretend to know things you don’t
  5. Then let it build – now it has real context

This Works on Humans Too

Here’s the thing: this is exactly how you should brief a developer, a contractor, or an agency.

The skill isn’t “prompting AI.” The skill is communicating clearly about what you need and why. AI just happens to be patient enough to ask follow-up questions without billing you for the discovery session.

Get good at this, and you’ll be better at working with every technical person in your life.

One More Thing

AI is confidently wrong. It doesn’t say “I’m not sure.” It just generates.

The discovery process helps – Claude Code builds better things when it understands the problem. But you still need someone who can look at the output and know if it’s right.

If you’re experimenting, that’s fine. Play in the browser at claude.ai. Build mockups. See what’s possible.

If you’re building something real, work with a developer. The prompting principles are the same – you’re just handing off to someone who can catch the mistakes.