Try it yourself

Start with one idea you can safely test.

A page of your own website is a good first project. Use fictional or public information, and follow your organisation's AI policy.

1

Read the story

Fifteen Years Inside the Template: what changed when I stepped outside the tools I knew.

Read the article ↗
2

Let AI interview you

Paste this into ChatGPT, Claude or similar. It asks one question at a time and drafts a first brief.

Show the prompt
# Context

I want to explore building something small with AI. I am learning, so explain unfamiliar terms in plain language and keep the first project manageable.

My idea is: [describe it, or write "I need help choosing"].
The people it could help are: [describe them].
My experience and tools are: [describe them].

# Task

Interview me one question at a time. Wait for my answer before asking the next question.

Help me understand the problem, what people do now, why it matters, and what a useful result would look like. If I do not have an idea, help me identify up to three small, low-risk problems from information I choose to share. Do not assume you can access my past chats.

Help me choose the smallest useful first version. Keep separate lists of what belongs in that version, what can wait, and what still needs an answer.

# Boundaries

Ask what information, accounts, access, costs and permissions the idea would require. Follow my organisation's AI and data policy. Use fictional or approved public information for early testing.

Do not request passwords, API keys or private records. Do not connect accounts, install tools, spend money, write code, change files, send messages or publish anything at this stage.

Flag security, privacy, accessibility and maintenance questions. Do not treat a working prototype as proof that it is safe or ready for real use.

# Output

After the interview, write a short first-draft brief with:
- The problem and who it affects
- The main task the first version should support
- What is included and what can wait
- Inputs, outputs, access and permission needs
- How we could test whether it helps
- Risks, assumptions and unanswered questions
- A suggested next step, including where expert help may be needed

Ask me to review and correct the brief before suggesting a build. Start with your first question.
Before you build: five quick checks
  • Does the brief describe the problem you meant to solve?
  • Can the first version do one useful thing?
  • Can you test it with safe information?
  • Do you know what needs permission or expert review?
  • Who would update and maintain it?

Build with me

Have an idea you want support with?

Book 15 minutes and we'll talk through the problem and the first useful version. That could lead to paid one-to-one support or a custom build for your organisation.

Prefer to write?

Keep confidential information out of your first message.

Need something to show a funder?

For selected projects, I'll build a small first version (an MVP) at no cost, so you can demonstrate the idea. The funded version would then be a paid project. Mention it when you book or write.

How this works

We agree the scope and time commitment before starting. It's a prototype, not a complete production system or ongoing free support, and it doesn't guarantee funding. We'll discuss the paid arrangement for the funded version before the prototype starts, and agree any later scope and fee separately.

Bring your idea, who it would help, what the first version needs to show, and any funder you have in mind. Keep confidential information out of your first enquiry.

We're in the age of possibilities. Start with one idea, or bring it to me and we'll work out a useful first step.

Free on-demand resources are separate from paid live support and custom builds. The prototype offer is agreed project by project.