Build Your First Sellable Demo
You will create a safe demo preview using one fake customer message and one structured assistant output. Build a demo preview that shows the business value without connecting real accounts, exposing customer data, or promising automatic results.
Start here
Make one useful thing with your AI agent.
You do not need to memorize the technical work. Understand the goal, paste the lesson prompt, inspect what the agent made, and save one useful result.
Read the short explanation and inspect the lesson screenshot. Skip the optional technical detail unless you need it.
2Paste the agent promptOpen the real project or notes in Codex or Claude Code and let the agent complete the work it can do safely.
3Check and save demo summaryYour fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Keep this as a conservative service exercise: no guaranteed income, guaranteed clients, private-data demos, or unmanaged live automation.
1. Understand the useful idea
Learn only what you need before the agent works.
Read the plain-English explanation, inspect the example screenshot, then use the copy-ready prompt. Technical detail is optional unless you want to understand what the agent is doing underneath.
The simple version
You will create a safe demo preview using one fake customer message and one structured assistant output.
Your job
Give the agent your niche, workflow, notes, and constraints. Answer only the questions needed to make the result specific.
Let your AI agent handle
Complete the practical work for Build Your First Sellable Demo and turn it into a clear artifact the student can inspect, improve, and use.
Check only these things
- The agent used fake or anonymized input and produced a visible result.
- A human reviews anything that could affect a customer or public channel.
- You saved one screenshot, output, or checklist a buyer can understand.
How this supports a paid offer
A $300-$750 lead follow-up draft pilot: summarize each sample lead, extract details, flag missing information, draft a reply, and require owner approval before sending.
Visual walkthrough
Turn a messy inquiry into a review-ready draft.
Students understand what a safe demo output looks like before connecting any real account.
Your AI does the heavy lifting
Copy this prompt. Let the agent do the work.
Let the agent do the building and testing. Your job is to describe the buyer problem and judge the result.
A $300-$750 lead follow-up draft pilot: summarize each sample lead, extract details, flag missing information, draft a reply, and require owner approval before sending.
Act as my practical AI implementation partner for "Build Your First Sellable Demo".
I am a non-technical beginner. Do the technical, research, drafting, or implementation work you can do inside this workspace. Do not turn this into a lecture and do not ask me to type commands you can safely run yourself. Explain only decisions or account approvals that genuinely require me.
Business goal:
A $300-$750 lead follow-up draft pilot: summarize each sample lead, extract details, flag missing information, draft a reply, and require owner approval before sending.
Your job:
Complete the practical work for Build Your First Sellable Demo and turn it into a clear artifact the student can inspect, improve, and use.
Lesson action:
Create one fake inquiry, sketch the output sections, and write one sentence explaining why the output is useful to the business.
Artifact to finish and save:
Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
How to work:
1. Inspect the current project, files, or notes before changing anything.
2. Ask no more than two short questions, and only when a missing answer would block useful work.
3. Make the smallest useful version first with fake or anonymized data.
4. Run the checks you can run yourself. Never claim a test passed unless you actually verified it.
5. Fix clear problems before reporting back.
Rules:
- No secrets, API keys, passwords, private customer data, or live credentials.
- Use fake data or anonymized examples until a real client gives written approval.
- Do not promise revenue, leads, guaranteed outcomes, or automatic customer-facing action.
- Ask for human approval before sending, publishing, buying, deleting, or changing live systems.
- Human approval is explicit before customer-facing use.
When finished, give me:
- A plain-English summary of what you made
- The finished artifact or exact file path
- The checks you ran and what passed or failed
- One screenshot or proof item I should save
- Anything that still needs my approval or a later domain/hosting step- 1
Open the real project or notes in Codex or Claude Code.
- 2
Paste the main prompt and answer only the questions that block progress.
- 3
Inspect the result, run the review prompt, and save one proof item.
What a good result looks like
- The agent used fake or anonymized input and produced a visible result.
- A human reviews anything that could affect a customer or public channel.
- You saved one screenshot, output, or checklist a buyer can understand.
Improve and quality-check the result
Review the work you just completed for "Build Your First Sellable Demo" as both a cautious buyer and a launch QA reviewer.
Check for:
- Confusing language a non-technical buyer would not understand
- Missing proof, tests, edge cases, or human approval steps
- Scope that is too large for a beginner's first paid project
- Secrets, private data, unsupported claims, or actions that should wait
- A weak connection between the work and a real buyer problem
Fix everything you safely can in the current workspace. Then give me only:
1. What you fixed
2. What still needs my decision
3. The strongest buyer-readable proof
4. The one next action that moves this closer to a paid offer
Do not invent client results, income, completed tests, or production readiness.Turn the work into a small paid offer
Turn the finished work from "Build Your First Sellable Demo" into the smallest honest paid offer I could test with a real prospect.
Use the completed artifact and proof already in this workspace. Do not invent testimonials, clients, revenue, demand, or technical checks.
Return:
1. Best-fit buyer
2. Painful repeated workflow
3. One-sentence offer in plain business language
4. Fixed deliverables and clear exclusions
5. Proof I can show using fake or approved data
6. A conservative test price or pricing method, clearly labeled as an estimate rather than a market fact
7. One short outreach message with an easy yes/no next step
8. What must wait for owner approval, live accounts, domain, hosting, or production setup
Keep the offer small enough that a beginner could deliver it carefully. Include human review and no guaranteed outcome.Safety rules the agent must follow
- No secrets, API keys, passwords, private customer data, or live credentials.
- Use fake data or anonymized examples until a real client gives written approval.
- Do not promise revenue, leads, guaranteed outcomes, or automatic customer-facing action.
- Ask for human approval before sending, publishing, buying, deleting, or changing live systems.
- Human approval is explicit before customer-facing use.
Optional: extra examples and implementation detailOpen only when you want the explanation behind the agent's work.
Core idea: A sellable demo preview has six parts: fake input, assistant role, structured output, safety limits, a clear next action, and a visible human approval reminder.
Claude/Codex operating note: Use Claude Code to map the workflow, edge cases, approval point, and buyer problem before building. Use Codex to inspect the implementation notes, tests, reusable docs, and handoff structure. Use OpenClaw when a fake-data lab run makes the workflow visible. Save one buyer-readable proof note that shows what a first paid version would include and what it would not promise.
Lesson visual asset
Support visuals
Step-by-step
This free lesson has two jobs:
- Give you a small "I get it" demo moment.
- Show the difference between a demo preview and a real, tested OpenClaw build.
- Pick the business type and workflow from Free Lesson 1.
- Write one fake customer inquiry with realistic messiness: timing, price question, missing detail, and source.
- Write the assistant role: it helps the owner review the inquiry; it does not speak for the business automatically.
- Ask for five output sections: lead summary, extracted details, missing details, draft reply, and next action.
- Add safety limits: do not invent price, availability, policy, discounts, medical/legal/financial advice, or guarantees.
- Add a human approval reminder at the end.
- Review the output as if you were the business owner. Circle what saves time and what still needs human judgment.
Worked example
Input: 'Hi, I need a quote for cleaning a 3-bedroom apartment next Friday near downtown. Do you have availability after 5 PM, and what is the price?' A safe output summarizes the request, extracts apartment size/date/location/time, asks for missing cleaning type and exact address, drafts a polite reply, and reminds the owner to confirm price and availability before sending.
Owner-facing explanation: This demo does not replace your team. It turns a messy inquiry into a cleaner review screen: what the lead wants, what details are missing, a draft reply, and what a human should check before responding.
Demo prompt shape: The full course gives you the guided build and testing path. For the free preview, only sketch the shape: the assistant should summarize the inquiry, list details already provided, find missing details, draft a reply for human approval, recommend the next action, and remind the owner not to send anything until they review it.
Before/after check: Before the assistant: the owner has to read, interpret, remember missing details, and write from scratch. After the assistant: the owner reviews a clean summary, edits a draft, and decides what to send.
90-second demo talk track:
- Here is a fake customer inquiry.
- Here is what the assistant organizes from it.
- Here are the missing details it catches.
- Here is a draft reply the owner can edit.
- Here is the safety boundary: nothing goes to the customer until a human approves it.
If you can explain the demo in 90 seconds, you have a clear idea. If it takes ten minutes, make the workflow smaller.
Demo quality scorecard:
- The before problem is obvious.
- The output is organized and easy to scan.
- Missing details are clearly surfaced.
- The draft reply avoids price, availability, policy, discounts, guarantees, and sensitive advice unless approved facts are supplied.
- The human approval step is visible.
- The business owner knows the next action.
Strong demo preview:
- one fake input
- one organized output
- one decision point
- one human approval rule
Weak demo preview:
- vague "AI automation" claim
- too many workflows at once
- invented prices or policies
- no clear next action
- no safety boundary
What this free preview does not include:
- OpenClaw installation
- dashboard setup
- onboarding walkthrough
- complete assistant instructions
- test cases
- pricing guidance
- outreach scripts
- proposal templates
- client onboarding
- handoff process
That separation is intentional. The free preview helps you understand the opportunity and design the demo idea. The paid course shows you how to build, test, package, and deliver it responsibly.
This is why the full course is worth paying for if you want to continue. The difficult part is not imagining an automation. The difficult part is turning it into a working, tested, bounded service offer without overpromising.
Common mistakes to avoid
- Making the demo too broad.
- Letting the assistant invent price, availability, policy, or guarantee details.
- Showing a clever AI response without a business workflow behind it.
- Using a real customer's message in the free demo.
- Treating the preview prompt as the full paid-course implementation. The paid course covers setup, testing, packaging, and client delivery.
Money skill upgrade: Treat this lesson as one buyer-facing asset, not a generic AI demo. The money path is a small workflow improvement with proof, a human approval point, and no income/client guarantee. Any dollar ranges are practice anchors, not promised market rates. The app path is a narrow tool that supports that workflow.
Service move: Leads arrive through forms, DMs, email, or missed calls, then wait too long because the owner has to read, extract details, and write replies from scratch. Starter offer: A $300-$750 lead follow-up draft pilot: summarize each sample lead, extract details, flag missing information, draft a reply, and require owner approval before sending.
Agentic workflow pattern: Prompt chain plus evaluator: extract details, draft response, then review against approved facts and forbidden claims before a human sends anything.
Discovery questions:
- What information do good leads usually include, and what is often missing?
- Which reply details must come from approved facts only, such as price or availability?
- What response-time or review-time improvement would make the pilot useful?
Proof and metric: Save this proof: Five fake or anonymized lead examples with before messages, assistant summaries, missing-detail lists, draft replies, and approval notes. Track or discuss: speed to first draft, missing details caught, reply consistency, manual review time.
Web app extension: A lead review web app: intake form, lead table, summary field, missing-detail checklist, draft reply, status, owner notes, and approval button.
App-building workflow: Build the smallest CRUD loop: create fake lead, generate or paste draft output, mark review status, save owner note, and test that only the right account can see it.
Platform stack to learn: Next.js for the interface, Supabase for Auth/Postgres/RLS/Storage, Vercel for preview and production deploys, domain DNS through the registrar or Cloudflare, and Cloudflare DNS/SSL/Turnstile basics when needed.
Deployment and domain proof: A Vercel preview showing fake leads moving from new to reviewed, plus Supabase RLS notes and a domain plan for a future client portal.
Delivery artifact: A lead follow-up demo packet with sample messages, output examples, test cases, approval rules, and known limits.
Buyer conversation starter: I can show how your lead messages could turn into summaries, missing-detail checklists, and draft replies for your approval.
Safety and promise boundary: Do not promise clients, income, revenue growth, automatic decisions, or fully autonomous business operations. Use sample data first and keep a human in the loop. Web app boundary: Never commit secrets, expose service-role keys, weaken RLS, launch a live domain, or collect real customer data before auth, permissions, support, legal pages, backup/export, and QA are checked.
2026 field upgrade: Plain-English translation: This means: decide how much control the AI gets, choose the smallest workflow that solves the problem, test it with messy examples, save a simple proof trail, explain the buyer value, and leave Codex clear instructions so the work can be repeated safely.
Autonomy level: Draft and triage only. The system can organize the work and suggest outputs, but sending, escalation, and customer-facing decisions stay human-approved.
Pattern to practice: Use prompt chaining plus routing: extract, classify, draft, then evaluator review. Parallelization can compare two drafts or two summaries before a human chooses.
Error analysis and eval: Create a test set with normal, messy, missing-detail, angry/customer-risk, and out-of-scope inputs. Error analysis should explain why each bad output happened before changing the prompt.
Observability and tracing: Save a lightweight trace: input, tool or screen used, output, human decision, error, and next fix. This is beginner observability and tracing, not a promise of enterprise monitoring.
Business case: Name the workflow compression before the price: The business case is workflow compression: faster review, fewer missed details, clearer prioritization, and a cleaner handoff. Avoid claiming revenue growth you cannot prove.
Codex operating habit: Prompt Codex with goal, context, constraints, and done-when checks. When the work becomes repeatable, add a tiny AGENTS.md or project-instructions note with commands, safety guardrails, tests, and do-not-touch boundaries.
Pause and do this now
Create one fake inquiry, sketch the output sections, and write one sentence explaining why the output is useful to the business.
Quick quality check
- Would a busy business owner understand the before/after?
- Is the demo useful even without automatic sending?
- Did you avoid real customer data?
- Did you avoid invented prices, availability, or guarantees?
- Do you know what you still need the paid course to teach?
Free worksheet download: Download or copy the Free Preview Action Checklist to keep your service map and demo preview in one place. The full course workbook and implementation templates stay inside the paid course.
Completion checkpoint
You have a safe before/after demo that a non-technical owner can understand in under two minutes.
Save this for your final project
Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Next step
The paid course installs OpenClaw, opens the dashboard, sends the first safe message, builds this lead follow-up demo inside the real beginner workflow, tests it safely, and turns it into one client-ready service offer. The course is $49.99. It does not promise clients or income; it gives you the guided setup, examples, worksheets, templates, and final project path so you are not guessing.
The free preview has done its job if you can now say: "I know the workflow I want to test, I know what a safe demo should show, and I know the full course is where I build it for real."
Claude/Codex skill drill
- Claude Code: Ask Claude Code to map the workflow behind "Build a demo preview that shows the business value without connecting real accounts, exposing customer data...", list edge cases, and define where human approval belongs.
- Codex: Ask Codex to turn the plan into inspectable implementation notes, tests, documentation, or a small reviewable change list.
- OpenClaw lab proof: Use OpenClaw as the fake-data demo surface only when the workflow needs visible proof in a dashboard, gateway, or channel.
- Money angle: Package the result as a paid service outcome: fewer missed leads, faster replies, cleaner reports, safer handoffs, or less repetitive work.
- Done when: Save Your fake inquiry, demo output shape, safety note, and one-sentence business explanation. plus one Claude Code planning note and one Codex inspection, test, or documentation note.
- Safety boundary: Use fake or sanitized data only; never paste API keys, customer records, private inboxes, billing screens, or live client systems into an assistant.
2. Inspect and saveCheck what the agent madeUse the finished agent output, check it, and save one useful piece of proof.Short assignment
Beginner decoder
New to this? Read these meanings before the steps.
These are the terms in this lesson that can sound technical before they become useful. Keep the plain meaning in mind, then do the action.
Workflow
The repeatable business task you are trying to make easier, such as answering leads or sorting messages.
Fake data
Practice information that looks realistic but does not belong to a real customer, client, or account.
Human approval
A person checks the AI output before anything reaches a customer or changes a live system.
Claude Code
A coding assistant you can use to reason through plans, instructions, errors, and implementation choices.
Codex
A coding agent used to edit, test, review, and document app or course work in a controlled workspace.
Short assignment
Check the agent's work and save one useful result.
You are reviewing the result, not rebuilding it by hand.
Inspect
Input: 'Hi, I need a quote for cleaning a 3-bedroom apartment next Friday near downtown. Do you have availability after 5 PM...
Check
Compare your draft against the common mistakes before moving on.
Save
Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Ready to continue when
- Action step finished.
- Checkpoint passes: You have a safe before/after demo that a non-technical owner can understand in under two mi...
- Artifact saved: Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
- Human approval is explicit before customer-facing use.
Knowledge check
Check the money lesson before you mark this complete.
Answer from memory first, then open the model answer. This is practice, not a grade: the goal is to make the tool move, buyer proof, and safety boundary easy to say out loud.
What buyer pain does this lesson help you address, and what proof should you save?
Reveal model answer
A service business or internal team with a repetitive workflow that wastes attention every week. Proof to save: Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Strong answers name a real buyer, one painful workflow moment, and one artifact a buyer could inspect.Which tool leads the thinking, which tool verifies the work, and where does OpenClaw fit?
Reveal model answer
Claude Code plans the buyer context, assumptions, workflow, and risk; Codex inspects the artifact, tests, docs, or implementation notes; OpenClaw is used only when fake-data lab proof makes the workflow easier to trust.
Strong answers keep Claude Code and Codex as the primary operating pair and treat OpenClaw as lab proof, not the whole course.What is the smallest honest paid conversation this lesson can support?
Reveal model answer
Sell a narrow fake-data prototype: one workflow, one input type, Claude Code planning, Codex inspection, and a human approval step. Price boundary: Price the prototype, tests, and handoff as the paid deliverable...
Strong answers stay small, proof-backed, and buyer-readable. They do not imply guaranteed clients, revenue, or live automation.Flashcards
Claude Code role
Say the Claude Code job in this lesson in one sentence.
Use Claude Code to clarify buyer context, assumptions, workflow steps, risk, and the first human-approved scope.Codex role
Say the Codex verification job in one sentence.
Use Codex to inspect the artifact, tighten reusable docs or tests, and verify the work is reviewable before sharing.Buyer proof
Name the artifact that turns the lesson into marketable proof.
Demo summary: Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.Safety boundary
Name the promise, data, or approval limit before sharing this work.
This is a commercial practice path, not a promise of revenue: keep the scope fixed, use fake or approved data, and never promise guaranteed clients or guaranteed income.Ready when
- You can explain the buyer pain without tool hype: Leads, inbox items, support questions, reports, or handoff notes arrive messy and someone has to clean them manually.
- You can show the proof asset: Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
- You can say what Claude Code did, what Codex verified, and why OpenClaw is only lab proof when used.
- You can ask for a small next conversation without guaranteed income, guaranteed clients, or unmanaged live automation.
Artifact notebook
Save the useful work while it is fresh.
This draft feeds the demo summary part of the final project. Use it for the service map, demo notes, offer language, tests, or handoff proof created in this lesson.
Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
- Specific enough that a reviewer knows the niche, workflow, decision, or next action.
- Shows how Claude Code or Codex helped inspect, draft, test, document, or improve the work.
- Includes proof: Fake-data input and output
- Human approval is explicit before customer-facing use.
- Readable by a busy business owner without tool jargon or income promises.
3. Connect it to moneyTurn this into a paid offerTranslate the result into a small offer a real buyer can understand.Optional sales step
Money path
How this can become a safe first paid conversation.
Use this as the selling lens: name the buyer pain, show proof, keep the scope small, and make Claude Code/Codex evidence visible before asking for trust.
A service business or internal team with a repetitive workflow that wastes attention every week.
Leads, inbox items, support questions, reports, or handoff notes arrive messy and someone has to clean them manually.
Sell a narrow fake-data prototype: one workflow, one input type, Claude Code planning, Codex inspection, and a human approval step.
Show the before/after: messy input, safer draft/output, review rule, and the exact work the buyer no longer has to start from scratch.
Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Quote the prototype, tests, and handoff notes as the paid deliverable; live rollout is a separate decision after QA.
Offer builder
Turn this lesson into a buyer-ready mini offer.
Use this worksheet to convert the lesson artifact into a concrete service promise: one buyer, one workflow, one proof asset, Claude Code/Codex evidence, and a conservative price boundary.
I help service teams turn one repetitive workflow into a fake-data AI prototype with proof, tests, and human approval before rollout.
Deliverables
- One before/after workflow demo using fake or approved sample data.
- Test notes, edge cases, and a human approval rule.
- A short handoff note that explains what the prototype does and what it does not do.
Proof checklist
- Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
- A buyer sees a concrete workflow improvement: messy input becomes a cleaner review step, draft, report, or decision aid.
- The demo shows messy input, safer output, review rule, and the work the buyer no longer starts from scratch.
Use Claude Code to clarify buyer context, assumptions, workflow steps, risk, and the first human-approved scope.
Use Codex to inspect the artifact, tighten reusable docs or tests, and verify the work is reviewable before sharing.
Use OpenClaw only as selected fake-data lab proof when a visible dashboard, gateway, or workflow demo makes the claim easier to trust.
Keep the buyer or operator in the approval seat before anything customer-facing, live, or sensitive happens.
This is an offer-building exercise, not an income claim: no guaranteed clients, guaranteed income, fake testimonials, private-data demos, or unmanaged live automation.
Client script
Turn this lesson into a buyer-safe conversation.
Use this before outreach or discovery. The goal is not pressure; it is a clear conversation about pain, proof, a small first scope, and what the AI should not do.
I help service teams prototype one repetitive workflow with a safe, reviewable AI draft instead of a vague automation promise.
I can show the before input, the safer draft output, the human approval rule, and the Claude Code/Codex review notes behind the prototype.
Discovery questions: Ask these before pitching
- Which repeated message, report, inbox item, or handoff takes too much manual cleanup right now?
- What does a good draft need to include before a person is willing to approve it?
- What kind of mistake would make this workflow unsafe or not worth automating?
Would you want a small fake-data prototype for one workflow so we can judge usefulness before touching production?
Send the before/after demo, approval rule, test cases, exclusions, and a small fixed pilot scope.
The lesson proof to bring into this conversation is: Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.
Optional helpSee an example or use a downloadOpen a finished example or download when you need another model to follow.Examples and files
Lesson kit
Use the format that helps you finish the action step.
Audio companion
Free Lesson 02 Build Your First Sellable Demo
Visual proof brief
8 supporting lesson figures plus a source-backed proof target.
Students understand what a safe demo output looks like before connecting any real account.
1 owned asset / 1 generated diagram
- Source targetOwned free-preview demo output visualsAcademy-owned asset by Agentic AI Automation Academy
- Source targetLead follow-up demo system screenshotCourse diagram by Academy generated or owner-created demo
Safe screenshot boundary: hide tokens, local paths, client data, live inboxes, billing details, and private account details.
Recommended downloads
Keep the workbook or worksheet open while you complete this lesson.
4. FinishComplete and continueConfirm the result is clear, mark the lesson complete, and move to the next useful action.About one minute
Final clarity check
Before you mark complete, make sure the lesson is usable.
Strong courses use quick reflection and feedback loops so beginners do not silently move forward confused. Use this last pass to confirm you can explain, show, and safely ask for help when something is unclear.
Explain the move
Say the buyer outcome, the Claude Code or Codex move, and why this lesson matters in one plain sentence.
Check the proof
Confirm your saved artifact is specific, fake-data safe, buyer-readable, and connected to the final project area: Demo summary.
Name the confusion
If a step is still fuzzy, write the unclear part before continuing. A precise blocker is easier to fix than a vague feeling of being stuck.