Build with AI

You've learned to get great results from AI. But every time, you're there. Typing. Prompting. Reviewing. The output is good but it depends on you being in the room.

Building means creating something that works on its own. A tool someone else can use without knowing it runs on AI. A page on the internet. A workflow that runs automatically.

Three levels of building without code. Level 1: a saved system. A Claude Project with custom instructions and uploaded files. Level 2: an interactive tool. A website or form built with a no-code builder. Level 3: an automated workflow. Something that runs on a schedule or trigger.

This course covers all three levels. By the end, you'll have built at least one thing at each level.

Build This Now

Think about the prompt or template you use most often. That's your first building project. By lesson 3, it'll be a tool someone else can use without your help.

Claude Projects is where prompting becomes building. Instead of typing your setup every time, you configure it once. Custom instructions tell Claude who it is and how to behave. Uploaded files give it your brand guidelines, templates, data.

The result: you open the project, start typing, and Claude already knows your business. Anyone you share it with gets the same experience.

Walk through a real example: a Client Brief Generator. Upload your brief template and examples of good briefs. Write instructions that tell Claude to ask the right questions and produce a brief in your format. Test it. Share it with a colleague.

That's a product. It took 10 minutes.

Build This Now

Open Claude. Create a new Project. Write custom instructions for the task you do most often. Upload one reference file. Test it with a real request. You just built your first AI product.

AI knows a lot about the world. It knows nothing about your business. The knowledge gap is what makes output feel generic. You close it by uploading the right material.

What to upload: your best work (AI learns your style), your processes (SOPs, checklists), your terminology (industry terms, product names), your constraints (what to avoid, non-negotiables).

What NOT to upload: confidential client data, massive unstructured documents, outdated information.

How to structure it: one topic per file. Use headers and clear formatting. A 2-page focused brief works better than a 40-page handbook. AI parses structured documents dramatically better than walls of text.

Build This Now

Take the Claude Project from lesson 2. Upload one more document: your process for the task it handles. Run the same request again. Notice how much closer the output matches how you actually do things.

Bolt (bolt.new) builds websites and simple apps from your description. You tell it what you want, it creates the code, you see the result instantly. Change anything by talking to it in plain language.

Step 1: describe what you want. Be specific. "A landing page for a consulting service. Header with company name and tagline. Three sections: what we do, how we work, get in touch. Dark background, white text, orange accents."

Step 2: review what Bolt creates. 80% right on the first try. Look at structure, not details.

Step 3: iterate. "Make the headline bigger. Change 'Get in Touch' to a contact form. Add a testimonial section."

Step 4: deploy. Bolt gives you a URL. Your page is live. The whole process: 20-30 minutes.

When Bolt isn't enough: it's great for pages and simple tools. Not great for complex apps or anything with user accounts.

Build This Now

Go to bolt.new. Describe a page you actually need. Something simple: a landing page, an event page, an internal tool page. Build it. Deploy it. Share the URL. You just shipped a website.

Static pages show information. Interactive pages respond to users. The difference: a calculator that estimates savings, a quiz that gives personalized recommendations, a form that produces customized output.

Things you can build without code: a calculator ("Enter your team size, here's how much AI could save you"), a quiz or assessment ("Answer these questions, here's your recommendation"), a form with smart output ("Describe your project, here's a scope estimate"), a decision tree ("What are you trying to do? Here's the best approach.").

How to describe interactions to Bolt: be explicit about what happens when users do something. "When the user enters a number in the team size field, multiply by 4 and display as 'Estimated hours saved per month.'"

Build This Now

Take the page from lesson 4. Add one interactive element. A contact form, a simple calculator, or a quiz. Deploy the updated version. You just built a tool, not just a page.

The simplest connection: copy and paste with intent. Use your Claude Project to generate content, paste it into your Bolt page. Low-tech but fast.

The next level: build something in Bolt that talks to AI directly. Describe it: "When the user submits the form, send their input to an AI and display the response." Bolt can build this.

The level after that: automated workflows with Make (make.com) or Zapier. "When a form submission comes in, send it to Claude, format the response, email it to me." Visual builders, no code.

The honest assessment: connections are where no-code tools show their edges. Simple flows work great. Complex logic gets messy. That's the boundary.

Build This Now

Connect something you built to one other thing. Claude Project to Bolt page. Form to email notification. One connection. That's how systems start.

The thing you have right now is more valuable live than perfect in draft. Real users teach you what to fix. You think the headline needs work. Your users care about the confusing form. You'd never know without shipping.

Speed builds momentum. Shipping one imperfect thing teaches you more than planning five perfect things.

A shipping checklist: Does it do the one thing it's supposed to do? Can someone else use it without explanation? Does it look professional enough? Is there a bug that breaks the core function? If yes to the first three and no to the last: ship it.

Everything else is a future improvement, not a launch blocker.

Build This Now

Share what you've built with one person today. Not next week. Today. Send the URL. Ask them to try it. That feedback is worth more than another week of tweaking.

Signs your project has outgrown no-code: more than a handful of users need it. Real data needs reliable storage. Different people need different access. It needs to be reliably available. The logic is getting increasingly complex.

What happens next. Option 1: the Assisted Coding course. Learn to build production software with AI. Option 2: hire Studio Hyra. We take ideas from concept to production. Option 3: hire a developer. The work you've done here helps you brief them better.

The honest truth: many people never need to go beyond what this course teaches. A Claude Project and a clean Bolt page solve most professional needs. Don't upgrade because you think you should. Upgrade because you've hit a real wall.

Build This Now

Look at what you've built. Is it enough? If yes, keep refining. If you're hitting a wall, identify which sign applies. That tells you which path to take.