Use Cases

No-code projects with Claude Code

Build projects without coding knowledge using Claude Code: websites, tools, automations, and data processing.

Automation, even without coding

Automating doesn't mean programming. With Claude Code, automating simply means giving clear instructions to get a reproducible result. These three tutorials guide you step by step, from opening the terminal to the final result.

Prerequisites

These tutorials assume Claude Code is installed and working on your machine. If not, follow the Getting started guide first.

Tutorial 1: Automate a weekly report

Goal: every Monday, generate a structured activity report from your week's notes.

Estimated time: 15 minutes the first time, 5 minutes going forward.

Set up your working folder

Create a folder on your computer, for example weekly-reports. This is where you'll store your notes and generated reports.

Open your terminal and navigate to this folder:

cd weekly-reports

Create your notes file

Each week, jot down your activities in a simple text file. No special format needed; write as you would on a sticky note:

# Notes week of March 10, 2026


- Client meeting Maison Duval, mockups approved
- Team training on new CRM tool (8 people)
- Critical billing bug, fixed Tuesday
- 3 new inbound leads via website
- Q2 budget preparation underway
- Paul on leave Wednesday and Thursday

Save this file as notes-week-march-10.md.

Launch Claude Code

In the terminal, type:

claude

Claude Code opens. You can now give it instructions.

Give instructions for the report

Paste this prompt:

Read the file notes-week-march-10.md and generate a weekly report.


Report structure:
1. Week summary (3-4 lines)
2. Accomplishments (bullet points, 5 max)
3. Blockers or delays
4. Next week priorities (infer from notes)
5. Key figures if available


Format: Markdown, ready to send by email.
Tone: professional and concise.
Length: 250-350 words.


Save the result in a file called report-week-march-10.md

Review and adjust

Claude Code generates the report and saves it. Open the file, read through it, and if something doesn't look right, just say in the terminal:

Update the report: add "finalize Q2 budget by Friday" to priorities and make the tone slightly less formal.

Claude Code updates the file directly.

Repeat each week

The following week, create a new notes file (for example notes-week-march-17.md) and run the same prompt with the new filename. The whole process takes 5 minutes.

To go further, you can create a report-template.md file with your preferred structure and reference it in your prompt: "Use the structure described in report-template.md."

Tip: the CLAUDE.md file

If you place a CLAUDE.md file in your weekly-reports folder with your preferences (tone, format, length), Claude Code will apply them automatically in every session. No need to repeat them in the prompt.

Tutorial 2: Create an email template system

Goal: have ready-to-use email templates for recurring situations, customizable in seconds.

Estimated time: 20 minutes for setup, 2 minutes per generated email.

Identify your recurring emails

List the 5 to 10 types of emails you send most often. For example:

  • Follow-up after a quote
  • Appointment confirmation
  • Sending meeting minutes
  • Information request to a vendor
  • Post-meeting thank you
  • Polite decline of a solicitation

Write this list in a file called email-types.md.

Create your reference file

Create a file email-context.md with your information:

# Context for email generation


## My profile
- Name: [Your name]
- Position: [Your position]
- Company: [Company name]
- Industry: [Your industry]


## Writing rules
- Formal address throughout
- Professional but warm tone
- Signature: [First Last, Position, Phone]
- Maximum length: 10 lines for standard emails
- No overly formal closings
- Sign-off: "Best regards" or "Talk soon"

Generate your base templates

Open Claude Code in the folder containing your files and paste:

Read the file email-context.md and the file email-types.md.


For each email type listed, generate a template with:
- The email subject
- The email body with [placeholders] for variable elements
- A short variant (3-4 lines) for urgent cases


Save all templates in a file called email-templates.md

Claude Code generates a complete file with all your templates.

Use a template in daily work

When you need to send an email, open Claude Code and simply say:

Generate a client follow-up email. Read the template from email-templates.md.


Details:
- Client: Martin & Sons Ltd
- Quote sent on: March 3, 2026
- Amount: 12,500 euros excl. VAT
- Project: company website redesign

Claude Code fills in the placeholders and produces an email ready to copy.

Improve your templates over time

If a generated email needs tweaks, ask Claude Code to update the template:

The client follow-up template is too formal. Edit it in email-templates.md to be more direct and less ceremonious. Keep formal address.

Your templates improve with use.

Tutorial 3: Generate a presentation outline and content

Goal: produce a complete presentation outline with content for each slide, ready to paste into PowerPoint or Google Slides.

Estimated time: 15 minutes for a 10-15 slide presentation.

Gather your information

Before launching Claude Code, prepare a file with the raw information:

# Presentation - CRM Migration Project Review


## Context
- Project started September 2025
- Migration from Salesforce to HubSpot
- Team: 4 people + 1 external contractor
- Initial budget: 85,000 euros


## Results
- Migration completed February 28, 2026 (2 weeks late)
- 12,000 contacts migrated, 0 data loss
- User adoption: 87% after 1 month
- Projected savings: 2,200 euros/month on licenses


## Issues encountered
- Incompatible custom fields (3-week delay)
- Resistance from the sales team initially
- Final cost: 92,000 euros (8% overrun)


## Audience
- Executive committee (6 people, non-technical profiles)
- They want to know: did it work? How much did it cost? What's next?

Save it as presentation-brief.md.

Generate the presentation outline

Open Claude Code and give the instructions:

Read the file presentation-brief.md.


Generate a complete outline for a presentation of 12 slides maximum.
Presentation duration: 15 minutes.


For each slide, include:
- Slide number and title
- Content (3-4 bullet points or short text)
- Visual suggestion (chart, icon, image, screenshot)
- Presenter notes (what to say out loud, 2-3 sentences)


Rules:
- First slide is the title, last slide is for questions
- No more than 4 bullet points per slide
- Favor numbers and visuals over long text
- Narrative structure: context, challenges, results, next steps


Save to presentation-plan-crm.md

Dive deeper into specific slides

If a slide needs more detail:

For slide 7 (key results), generate a before/after comparison table with:
- Monthly license cost (before vs after)
- Number of active users
- Average time to enter a contact
- Rate of duplicate data


Update the file presentation-plan-crm.md.

Generate presenter notes

To help you present without reading your slides:

For each slide in presentation-plan-crm.md, expand the presenter notes:
- What to say (3-4 natural, spoken-style sentences)
- Transition to the next slide (1 sentence)
- Questions the audience might ask at that point


Save to presenter-notes-crm.md

Copy into your presentation tool

Open your tool (PowerPoint, Google Slides, Keynote) and create the slides following the outline. The content is ready: you just need to copy-paste it and add visuals.

For charts, you can ask Claude Code to generate the data in the right format:

Generate the cost evolution chart data as a CSV table I can import into Google Sheets to create a chart.

Tip for recurring presentations

If you give similar presentations each quarter (project review, status update, committee meeting), create a presentation-template.md file with your standard structure. For each new presentation, give this template to Claude Code along with the new data. The outline will be consistent from one time to the next.

The 5 principles of no-code automation

After these three tutorials, here are the principles to remember for automating other tasks.

1. Start with what you do every week. The gain is immediate and you learn gently.

2. Create reference files. Your context (company, tone, format) in a file that Claude Code reads every session. You never repeat it.

3. Ask for the result to be saved to a file. It's more practical than copying from the terminal, and it creates a history.

4. Improve your prompts gradually. The first version works. The fifth version is excellent. Note what's off and adjust.

5. Keep a human in the loop. Claude Code produces the draft, you validate the final result. That combination delivers the best outcomes.

Next steps

Previous

Success stories