logo
logo
  • Home
    Home
  • Case Studies
    Case Studies
  • Expertise
    Expertise
  • Reviews
    Reviews
  • Clients
    Clients
  • Blog
    Blog
  • Artwork
    Artwork
  • About
    About
  • Contact
    Contact
  • LinkedIn
    LinkedIn
  • Home
    Home
  • Case Studies
    Case Studies
  • Expertise
    Expertise
  • Reviews
    Reviews
  • Clients
    Clients
  • Blog
    Blog
  • Artwork
    Artwork
  • About
    About
  • Contact
    Contact
  • LinkedIn
    LinkedIn
logo
logo
Claude for Coding Blog Post Feat Image

Claude Isn’t Just A Chatbot. I’ve Been Using It To Build Things.

11/06/2026
-
Process & Expertise
-
Posted by Joe Winfield

I’m a consultant and designer really, coding isn’t my strong suit.

I’ve been doing this job for over 14 years and I’m comfortable saying that. I won’t waste anyones time by saying I’m a senior developer or programmer, etc. Design, strategy, consulting – that’s where I thrive. I can hold my own with code but it takes me a lot longer than a seasoned developer who does it every day.

The problem is I kept having ideas for web tools. Useful ones. I use online tools daily but a lot of them are never perfect (for me anyways). And the gap between knowing exactly what something should do and look like, and it actually being online and free of use, was always a bit of a project in itself.

I’ve recently been using Claude to help bridge that gap.

How It Started

I was doing a career coaching session recently and my coach asked me to fill in a career wheel for the next session. This is essentially a circle divided into sections where you rate different aspects of your dream job, your must haves and nice to haves, so you can envision exactly what your dream job looks like, so you can ultimately go find it! She told me that pen and paper was fine for the exercise and my initial thought was “Nah. I’ll just find a tool online to do it”.

After the session, I spent the next 20 minutes looking for a good digital version instead. Found a few, none of them felt right – too basic, too clunky, too expensive, or not something I’d actually want to use again or recommend to someone else.

So I decided to build one!

For a long time now I’ve seen colleagues and other people online creating amazing web tools using AI and I wanted a piece of the action. I didn’t know where to start, but I used this as my excuse to get started.

I knew what I wanted it to look like. I knew how it should work. What I didn’t have was a strong developer brain or plenty of time to actually code it on my own.

I briefed Claude the same way I’d brief a developer and we worked through it together. That one tool led to a few more. There’s now a website featuring a collection of tools, some ready, some still in development. I’m working on it (…and my portfolio, I know I know) but it’s happening and will be live soon!

What “Together” Actually Means

I want to be very honest about this because I think it’s worth saying clearly. I’m not typing in “build me an online tool that’s easy to use and will make me a millionaire” and walking away with a finished product. That’s not how it works and definitely not how it works well.

The way I’d describe it: “Conceived, designed and directed by me – built with Claude.”

I come up with the idea. I brainstorm it. I design it. I decide how it should feel to use. I write the brief, review what comes back, tell Claude what’s wrong and why, and we go again… and again and again. The creative and strategic thinking is mine. Claude handles the technical execution – the HTML, CSS, JavaScript (all the code).

This is particularly handy when a project doesn’t need a developer on hand or when you’re experimenting with an idea before it’s at a stage where a developer is required. And unlike most people, Claude is available 24/7 and genuinely doesn’t mind going around the same iteration multiple times in the middle of the night, on a weekend, unpaid (…I wouldn’t take kindly to this anyways).

Getting Good Results From Claude

This is probably the most useful bit, so worth slowing down for it.

Most people use Claude like a smarter search engine – ask a quick question, get a quick answer. And that’s fine for quick questions. But if you want to actually build something with it, you need to treat it a bit more like briefing someone on your team.

A few things that have made a real difference for me:

  • Be specific about what you want and why. “Build me a form” is a lacklustre brief. There’s too many assumptions and no context at all. Whereas for example “Build me a single-page form that collects five inputs, shows a summary at the end and submits instantly to the recipient assigned. Make sure it stores no data, only the sender and recipient can see the submission. Here’s a URL for design and functionality inspiration. I need this for internal work communications.” is a much better starting point. Context changes the output significantly.
  • Say what you don’t want as well. If there’s a layout approach or technical solution you want to avoid, say so upfront. Saves a lot of back and forth.
  • Describe the feeling, not just the function. I’ll often say something like “this should feel more straight forward, not as cluttered” alongside the technical requirements. It sounds vague but it actually shapes the result.
  • Review it like you’re about to pay an extortionate price for it. Does it work? Yes. But is it right? No. In that case, continue to provide feedback on exactly what is and isn’t working for you. Be as specific as you can when feeding that back.
  • One thing at a time. I’ve made the mistake of dumping a long list of requirements into one message. It rarely ends well. Build it up in stages, get each bit right before moving on.
  • When something’s wrong, explain why. Not just “that’s not right” but for example “that’s not right because the button needs to be visible before the user scrolls. ” The more specific the feedback, the better the next attempt.

What’s Actually Changed

I’m still a designer and a consultant. Nothing’s changed there.

What’s changed is that I can take an idea and make it real without it becoming a big project or an expensive conversation with a developer. For smaller tools and experiments, that’s genuinely useful.

It’s also made me think differently about what’s within reach. Things I would have filed under “that would be handy someday” are now things I can actually have a go at.

Claude isn’t replacing me or other people, but is doing the work that would’ve slowed me down.

The Short Version

If you’re only using Claude to ask questions and summarise things, you’re not getting the most out of it (unless that’s the only reason you need it, then that’s absolutely fine). It’s worth experimenting with what else it can do, especially if you have ideas that need a bit of technical help to exist.

Anyways, the tools website I’m working on is nearly ready. Watch this space!

Yes, I know I should be working on my portfolio, but like a good mechanic, I never have the time to work on my own car.

Essential Reads
  • What Proper Website Testing Actually Looks Like 30/07/2026
  • Anatomy Of A Project: Brief To Launch 20/07/2026
  • Claude Isn’t Just A Chatbot. I’ve Been Using It To Build Things 11/06/2026
  • I Judge Every Website I Visit (And Here’s What I’m Looking For) 29/05/2026
  • Making Websites That Everyone Can Actually Use (Yes, Everyone) 18/03/2026
Recent Posts
  • What 14+ Years In Web Design, UX & Front-end Development Looks Like 28/10/2026
  • Good UX Is Invisible. Here’s Why That Makes It Hard To Sell. 15/10/2026
  • The First Five Seconds – What Your Homepage Is Actually Saying 31/08/2026
  • I Hired A Career Coach, Here’s What Actually Surprised Me 19/08/2026
  • Content Design Is Part Of The Job (Even If You’re Not A Writer) 11/08/2026
  • What Proper Website Testing Actually Looks Like 30/07/2026
  • Anatomy Of A Project: Brief To Launch 20/07/2026
  • Staying Focused Between Jobs 09/07/2026
  • Turns Out I Needed A Second Brain, Not A Second Monitor 25/06/2026
  • Claude Isn’t Just A Chatbot. I’ve Been Using It To Build Things. 11/06/2026
Categories
  • Career & Personal (4)
  • Industry Culture (2)
  • Process & Expertise (11)
  • UX/Accessibility Deep Dive (7)

Related News

Other posts that you should not miss
14 Years in design blog thumbnail

What 14+ Years In Web Design, UX & Front-end Development Looks Like

28/10/2026
-
Posted by Joe Winfield
Here's my honest account ...not my social media highlight reel. My friends joke that I'm "always in college". They're not wrong. I've…
Read More →
Career & Personal, Process & Expertise
3 Min Read
Invisible UX Blog Post Thumbnail

Good UX Is Invisible. Here’s Why That Makes It Hard To Sell.

15/10/2026
-
Posted by Joe Winfield
When everything works, nobody notices. That's the point!... and also the problem. There's a particular kind of satisfaction in finishing a project…
Read More →
Process & Expertise, UX/Accessibility Deep Dive
5 Min Read
The First Five Seconds. Homepage Analysis Blog Thumbnail.

The First Five Seconds – What Your Homepage Is Actually Saying

31/08/2026
-
Posted by Joe Winfield
Your homepage is your elevator pitch, not a welcome mat. Visitors nowadays scan websites; they don't read them from top to bottom.…
Read More →
Process & Expertise, UX/Accessibility Deep Dive
4 Min Read
Claude Isn't Just A Chatbot. I've Been Using It To Build Things. - Blog - Joe Winfield