Download as .md Case study

The course as built in Rise 360, lesson by lesson and block by block. It comes from the Storyline storyboard, adapted to what Rise can do. Text in quotes or block quotes is on-screen text, used as written.

Course title: One Task, Start to Finish Course subtitle: Using Claude Code to run your small business Audience: small business owners anywhere in the US who have never used Claude Code. Settings: Theme > Navigation > Restrict Navigation On, so lessons open in order. Continue buttons after a check are set to "Complete Block Directly Above"; after a set of practice checks, "Complete All Blocks Above." The final check requires a passing score to continue, so the plan lesson opens after a pass. Look (2026-10-14): Inter font; lesson headers in the theme tint; author hidden inside lessons (still on the cover); every "do it in your own Claude Code" section has a custom background: #E8F5F7, a light teal, since 2026-10-16 (theme-color link text measures 4.91:1 on it); before that #FBF1ED, a warm tint for the orange theme (4.66:1) and each prompt block is Dark. Permission prompts (2026-10-14, after a Codex review): the real desktop prompt shows Deny and Always allow, with Allow once in the menu next to Always allow. The course teaches Allow once for a new draft: step 3's text, the step 3 practice (a Code block since 2026-10-15; Always allow is a wrong choice there) and step 5's process step. Wrong answers (2026-10-14, after a Codex review): the right answer is no longer always the longest or always last. Step 2's customer-replies check has four believable choices, and step 4's second and third practice checks each have a specific rule that still misses (too narrow, or one that skips the client's question) in place of a second vague one. Practice business: Cedar Row Architects, a fictional three-person firm. Every name, fee and note in the practice is made up. Theme and quotes (R7, 2026-10-13): theme color #C2410C (contrast); changed to teal #25737E on 2026-10-16 at Dean's request (5.48:1 on white). In Rise, answer choices and feedback use curly quotes (“ ”), because Rise announces straight quotes to screen readers as """. This script keeps straight quotes; the text checker treats both the same.

What changed from the Storyline storyboard, and why:

• Rise has no variables, so the learner's typed task can't follow them through the course. Each "Do it for real" section shows the prompt to copy, and the plan at the end is a download they fill in.
• Gate questions are knowledge checks set to "Require correct answer to continue" with unlimited retries, followed by a Continue button. Each choice has its own feedback.
• The step 4 consequence plays out in three practice checks: each fix's feedback shows what the next project's draft looks like.
• Prompts to copy appear as a text block headed "The prompt" (written below as code blocks).
• Five real Claude Code screens were added on 2026-10-14, one per step from step 2 on, each right after the prompt the learner pastes (step 3 also gets the permission prompt after its intro). The screens were taken in the Claude desktop app on a demo folder holding the practice firm, so they match the practice.

Lesson 1: Where do you start?

Block: Text (paragraph)

You've heard Claude Code can take work off your plate. Tonight you finally sit down to try it.

The proposal you promised this afternoon still isn't written.

Block: Knowledge check (multiple choice), not scored

It's 8:04 p.m. Where do you start?

Block: Continue (complete block above; any answer opens it)

Block: Statement

One path, five steps. Dean learned these steps by making the mistakes first, so you don't have to.

Block: Numbered list

1. Pick one task that repeats.
2. Give Claude the details of the task.
3. Run the task and check the result.
4. Update the instructions.
5. Save it for next time.

Block: Text

Every step goes the same way. Learn it, practice it here, then do it for real in your own Claude Code. Pass a short check, and the next step opens.

About 20 minutes here. The real steps happen in your own Claude Code, at your pace.

Block: Note (callout)

The practice uses a made-up business, Cedar Row Architects. The screenshots are real Claude Code screens from a demo folder.

Block: Text

Before step 1: get Claude Code open

• A paid Claude plan. Pro is about $20 a month, paid to Anthropic.
• The Claude desktop app, available from claude.ai/download.
• The Code tab open, with a folder chosen.

Prefer the terminal? Everything here works there too. Open a terminal in your task folder and type claude.

Block: Continue ("I have Claude Code open")

Lesson 2: Step 1, pick one task that repeats

Block: Text

Start with a task you can finish and check. A good first task:

• comes up often, every day or every week
• has steps you could explain to a new hire
• can be checked in a few minutes against something you trust
• goes past you before it reaches a customer

Examples: a proposal from a client's request, each morning's pickup list, replies to the questions customers ask most, and more.

Block: Text (paragraph with heading)

Sort the tasks

A bakery owner wants to hand something off to Claude. Sort each task.

Block: Sorting activity

Block: Continue (complete block above)

Block: Text

Now pick yours

Write down the one task you'll hand to Claude, the way you'd say it. For example: "write proposals from my client intake notes."

Pick one that comes up every day or every week. You'll use it in every step from here.

Keep it on the plan below, and fill in the rest as you go.

Block: Attachment: one-task-plan.pdf (a one-page plan to fill in)

Block: Knowledge check (multiple choice)

Which of these is the best first task to hand to Claude?

Block: Continue (complete block above)

Lesson 3: Step 2, give Claude the details of the task

Block: Text

Claude Code works inside a folder on your computer. Make one for this task.

Then tell Claude how you do it, the way you'd explain it to a new hire. Start with the steps, then add your rules and an example you were happy with.

Type it in, or point Claude to files you already have. Share what this task needs. Passwords and card numbers stay with you.

Claude writes what it learns into an instructions file, CLAUDE.md, and reads it every time it works in that folder.

The easy way to start: ask Claude to interview you about the task, one question at a time.

Block: Text (paragraph with heading)

Sort what Claude needs

Cedar Row Architects is setting up fee proposals in Claude Code. Sort what Claude needs to know.

Block: Sorting activity

Block: Continue (complete block above)

Block: Text

Here's the CLAUDE.md Claude wrote after interviewing the principal.

Block: Code snippet (plain text)

# Cedar Row Architects: fee proposals

We're a three-person firm. We design homes, additions and remodels.
Write the way we talk to clients: friendly, plain and short.
Use the rates in fee-schedule.xlsx.
If the intake notes leave something out, ask me before you write the proposal.
End every proposal with the retainer and billing terms from policies.docx.
Save each proposal as a draft for me to approve and send.

Block: Knowledge check (multiple choice)

The intake notes for a new project leave out how many site visits the client wants. Which line in the CLAUDE.md tells Claude what to do?

Block: Continue (complete block above)

Block: Text

Now in your own Claude Code

1. Make a folder for your task, and choose it in the Code tab.
2. Paste this prompt, with your task in place of the brackets.

Block: Code snippet (plain text)

I'd like your help with a task I do often: [your task]. Interview me about how I do it, one question at a time. When you have what you need, write it into CLAUDE.md and show me.

Block: Image (centered): cc-interview.png (a real Claude desktop screen, taken 2026-10-14 on a demo folder with the practice firm; alt text set in Rise)

What it looks like in the Claude desktop app. Claude reads your folder first, then asks one question at a time.

Block: Text

3. Answer Claude's questions. If you already have a price list or past examples, tell Claude where they are.
4. Read the CLAUDE.md it writes, and correct anything that's off.

Block: Knowledge check (multiple choice)

You're setting up a task for writing customer replies. What should you share with Claude?

Block: Continue (complete block above)

Lesson 4: Step 3, run the task and check the result

Block: Text

Ask for one thing, plainly. Name the job, the details to use, and what to save: "Write a proposal for the Lee project from intake-notes-lee.txt using fee-schedule.xlsx. Save it as a draft."

Read every permission prompt. Claude asks before it creates or changes a file. A new draft in your folder is a yes. Allow it once, from the menu next to Always allow, so Claude keeps asking before each change. Pause when it wants to change your fee schedule or anything outside the folder.

Check the result before you approve it. Compare every number with your own details, then read for anything Claude promised or added on its own.

Block: Image (centered): cc-permission.png (a real Claude desktop screen, taken 2026-10-14 on a demo folder with the practice firm; alt text set in Rise)

A real permission prompt. Claude asks before it writes a file and shows you what it will save.

Block: Legacy scenario (2026-10-14; replaces the heading block and the three practice checks; cut to the request choice on 2026-10-15, when the permission decisions moved to the Code block below). No character; the background is a blurred real Claude desktop screen. Title card:

Practice: ask for the draft

You're the principal at Cedar Row Architects, and Claude Code is open in the Proposals folder. Choose what you'd type.

A correct choice continues; a wrong one shows its feedback and Try again. Choices are listed in the order learners see them.

Scenario dialogue

Claude asks: "What would you like to work on?" Which request do you type?

Scenario end card:

Request sent

Claude starts on the Lee draft. Next, answer its prompts.

Block: Code (2026-10-15; source code-blocks/permission-practice.html; Format: Full width, Auto Resize on; Set completion requirements on). A practice built in HTML and JavaScript, styled after the Claude desktop app's permission card: title, file name, path, the change (green lines added, red removed), and Deny next to Always allow, with Allow once in the menu beside it. Heading lines:

Practice

Read the prompt, then choose

Claude is writing the Lee proposal in your Proposals folder. Three prompts come up. Choose what you'd click on each one.

The three prompts, in order (each wrong choice shows its feedback and Try again; the right one moves on; finishing sends Rise its completion message):

• Prompt 1, "Allow Claude to write proposal-lee.md?", path /Users/you/Proposals/proposal-lee.md, the 9-line draft. Right answer: Allow once. Always allow: "With Always allow, you may not be asked next time, and next time it could be your fee schedule. Open the menu next to Always allow and choose Allow once." Deny: "Claude needs this to save the draft you asked for. A new draft in your task folder is a yes. Allow it once, from the menu next to Always allow." Right: "Right. A new draft in your task folder is what you asked for, and Allow once keeps Claude asking before the next change. Allowing a draft isn't approving it: you check every line next."
• Prompt 2, "Allow Claude to edit fee-schedule.xlsx?", line 4 from $185 to $170 after Claude cites the 2024 Silva proposal. Right answer: Deny ("Right. Your fee schedule is the source, and old proposals can have old rates. Claude stops and waits, so tell it to keep $185."). Either allow: "Claude would change your fee schedule to an old rate, and every proposal from now on would come out low."
• Prompt 3, "Allow Claude to write proposal-lee.md?" again, but the path is /Users/you/Clients/Lee/proposal-lee.md (Claude offers a copy for the client folder). Right answer: Deny ("Right. Same file name, different folder: Clients/Lee is outside your task folder. Keep drafts in Proposals until you approve them."). Either allow: "Read the path: Clients/Lee is outside your task folder."
• End: "All three prompts answered", with what to read in every prompt (the title, the path, the change) and "Choose Allow once for a new draft in your task folder. Next, check the draft."

Block: Continue (complete all blocks above; the scenario must reach its end card and the practice must be finished)

Block: Text (paragraph with heading)

Check the draft

Claude finished the draft. Check it against the notes, the fees and the policies.

Block: Tabs (Notes, Fees, Policies)

• Notes: Kitchen and family room remodel, single-family home. Services: design through the permit set. Estimated hours: principal 10, project architect 32, drafter 56. One site visit to measure. Client asked if we can have the permit by March.
• Fees: Principal architect: $185 per hour. Project architect: $140 per hour. Drafter: $95 per hour. Site visit: $250 each. Optional, only if the client asks: interior finish selections, billed hourly at the project architect rate. Optional, only if the client asks: 3D renderings, $600 per view.
• Policies: A 20% retainer starts the work. We bill the rest monthly for hours worked. Proposals are good for 30 days. The city sets permit timing. We send our design schedule once the retainer is in.

Block: Code snippet (plain text), titled "proposal-lee.md (draft)"

1  Proposal for the Lee residence: kitchen and family room remodel, design through the permit set
2  Principal: 10 hrs × $140 = $1,400.00
3  Project architect: 32 hrs × $140 = $4,480.00
4  Drafter: 56 hrs × $95 = $5,320.00
5  Site visit to measure: 1 × $250 = $250.00
6  Interior finish selections: included
7  Estimated fee: $11,450.00. Retainer to start (20%): $2,290.00.
8  You'll have your permit by March.
9  This proposal is good for 30 days.

Block: Knowledge check (multiple response)

Which lines need fixing before you approve? Select every one.

Feedback (correct): "Right. Line 2 bills the principal at the project architect rate; the fix is 10 hrs × $185 = $1,850.00, which brings the fee to $11,900.00 and the retainer to $2,380.00. Line 6 is a service Claude added on its own, so it comes out. Line 8 promises the city's timing; your policy says: 'The city sets permit timing. We send our design schedule once the retainer is in.'" Feedback (incorrect): "Check the principal's rate against the fees, look for anything the client didn't ask for, and look for a promise your policy doesn't make."

Block: Continue (complete block above)

Block: Text

Now run yours

Paste this into your own Claude Code, with your task in place of the brackets. Then check every line before you approve it, and note anything that was off. You'll use that in step 4.

Block: Code snippet (plain text)

Do [your task] for the next one that's due, using the details in this folder. Save it as a draft for me to approve.

Block: Image (centered): cc-draft.png (a real Claude desktop screen, taken 2026-10-14 on a demo folder with the practice firm; alt text set in Rise)

A real run: Claude's draft for the Lee project. It looks right, and every line still gets your check before you approve it.

Block: Knowledge check (multiple choice)

While drafting a proposal, Claude asks: "Allow edit to fee-schedule.xlsx?" What do you do?

Block: Continue (complete block above)

Lesson 5: Step 4, update the instructions

Block: Text

A fix made by hand stays in that one draft.

Put the fix in CLAUDE.md, and it carries into every run after. A new session starts fresh, and CLAUDE.md loads every time.

Tell Claude what was off and ask it to add a rule. Then run the task again and see if the rule worked.

Block: Text (paragraph with heading)

Make the rule specific

Say exactly what to do.

Vague: Be careful with rates.

Specific: Bill each role at its own rate from fee-schedule.xlsx. Check every rate before you total.

Block: Text (paragraph with heading)

Practice: three fixes

You approved the Lee proposal after fixing three problems. Decide how to handle each one next time. Each answer shows what comes back on the next project, the Kim residence.

Rise's Scenario block was replaced with three practice knowledge checks (2026-10-13), for the same reason as lesson 4. Each answer's feedback shows what the Kim draft looks like after that choice.

Block: Knowledge check (multiple choice), practice

First: the principal was billed at the wrong rate. How do you handle it for next time?

Block: Knowledge check (multiple choice), practice

Second: Claude added interior finish selections on its own. How do you handle it for next time?

Block: Knowledge check (multiple choice), practice

Third: the draft promised a permit date. How do you handle it for next time?

Block: Continue (complete block above)

Block: Text

Now update yours

Take what was off in your run and paste this into your own Claude Code. Then run the task again and see if the rule worked.

If nothing was off, run the task on a new case and check it the same way.

Block: Code snippet (plain text)

Add a rule to CLAUDE.md that handles this next time: [what was off]. Make it specific, and show me the new rule.

Block: Image (centered): cc-rule.png (a real Claude desktop screen, taken 2026-10-14 on a demo folder with the practice firm; alt text set in Rise)

A real rule, added to CLAUDE.md. Claude writes it as steps it follows on every proposal from now on.

Block: Knowledge check (multiple choice)

Claude's proposals keep adding services the client didn't ask for. What's the best fix?

Block: Continue (complete block above)

Lesson 6: Step 5, save it for next time

Block: Text

Once the task comes out right, ask Claude to save the steps as a skill: a saved set of steps with a short name.

Next time, type the name, like /proposal, and the intake notes file. Claude starts from the same steps and the same instructions.

Your part stays the same: read the result, then approve it.

Block: Knowledge check (multiple choice)

Which request saves the proposal task the right way?

Block: Process (summary step hidden)

Each time you run it

Four steps, from typing the name to your approval.

Block: Text

Save yours

Pick a short name for your task, like proposal or morning-summary. Then paste this into your own Claude Code, run it once, and put a reminder in your calendar for when it's due.

Block: Code snippet (plain text)

Save what we just did as a skill called [name]. It should use the details and rules in this folder and save a draft for me to approve.

Block: Image (centered): cc-skill-run.png (a real Claude desktop screen, taken 2026-10-14 on a demo folder with the practice firm; alt text set in Rise)

A saved skill, run by name in a new session. Claude starts from the same steps, and the draft still comes to you to approve.

Block: Knowledge check (multiple choice)

Your /proposal skill works. What's your part each time?

Block: Continue (complete block above)

Lesson 7: Final check (quiz lesson)

Quiz title: Final check

Ten questions, two for each step. Score 90% or higher to pass. You can take it again as many times as you need.

Settings: Passing score 90% (raised from 80% on 2026-10-13: with two questions per step, 80% let a learner miss a whole step and pass). Quiz retries Unlimited. Randomize question order On. Shuffle answer choices On. Reveal answers: Reveal all answers. Feedback by choice on every question. Rise's quiz settings have no draw-from-bank option, so all 10 questions are used. Questions Q1 to Q10 are word for word from storyboard.md ("Final check question bank"); the requests in Q5 and Q8 show in quotes.

Lesson 8: Your one-task plan

Block: Text (paragraph with heading)

Write these down, or fill in the plan below:

• Your task
• What you told Claude
• The rule you added
• Your skill's name
• When you'll run it

Block: Statement

Each time: run it, read every line, approve it. When something's off, update the instructions.

Block: Attachment: one-task-plan.pdf (a one-page plan to fill in)

Block: Attachment: one-task-job-aid.pdf (the five steps on one page)

Block: Survey (two multiple choice items, not required, not scored)

Was this course worth your time?

Which step was hardest?