30-day course
DIGITAL SERVICES PROGRAM

Learn Claude

One step a day

The AI that does not just answer you. It does your work too.

This course is for people who cannot write code. Spend the first 14 days learning Claude, then the next 16 building with it: a website, a chatbot, an agent, and showing up in search. Plain English, one lesson a day, one small task a day.

Read this course in Urdu

The big picture first

The three parts of Claude

There is one Claude, but three ways to put it to work. The whole course turns around these three.

Claude Chat

Chat

You ask, Claude answers. Questions, advice, writing, understanding.

Come here when you want to think or ask.

Claude Cowork

Cowork

You hand over a job, Claude works through the steps itself and returns a finished result.

Come here when you want work done.

Claude Code

Claude Code

You say what to build, Claude writes the software and runs it.

Come here to build a website, an app or an agent.

Models

Which model when

The model is Claude's brain. Claude has several models: some fast and light, some slower but deeper. In the app there is a model menu next to the box where you type, and you switch from there.

Haiku

Haiku

The fastest and lightest.

Small, quick jobs: a short answer, a translation, fixing a message, a simple summary.

Sonnet

Sonnet

A balance of speed and understanding.

Most everyday work: writing, analysis, planning, a normal report.

Opus

Opus

For deep thinking and long work.

A hard problem, a job with many steps, big research, big software.

Fable

Fable

The most intelligent model.

The hardest thinking, and long work that Claude keeps running on its own for a while.

The simple rule: start with Sonnet. If the job is very simple, use Haiku. If the answer feels shallow or the job is hard, use Opus, and if you need to go further still, Fable.

Two things to remember: a bigger model uses up your usage limit faster, so do not pick the biggest model for every job. And which models you get depends on your plan. Model numbers keep changing, but these four levels and the rule behind them stay the same.

Part one, days 1 to 8

Claude Chat

1

What Claude is and how to start

Claude is an AI assistant. You talk to it the way you would talk to a sensible colleague, and it writes for you, advises you and gets work off your plate.

Starting is not hard. Install the Claude app on your phone or open the website on your computer, make an account and type your first question. There is no special language to learn. Write what is on your mind. Write in Urdu and the answer comes back in Urdu.

Today's task: Tell Claude about your business in two lines, then ask which three things you should do this week.
2

Chat: how to ask

Chat

The answer is only as good as your question. Most people type one line and leave it, then say the answer was generic.

Three things make the difference. First, say who you are and who the work is for. Second, say clearly what you need. Third, say what shape the answer should take: short, a list, or a full piece of writing.

The first answer is not the last. If you do not like it, say make it shorter, or write it in simpler words. A conversation with Claude keeps going.

Today's task: Have Claude write a message you would send to a customer. Ask in one line first, then ask again with all three things included. Compare the two answers.
3

The context window

Has Claude ever forgotten, late in a long conversation, something you told it at the start? The reason is the context window.

Think of it as Claude's desk. Everything in one conversation sits on that desk: your messages, its answers, your files. The desk is big, but it has a limit. When it fills up, the older things start to fade.

The fix is easy. New topic, new chat. Do not put ten different jobs into one chat. When a conversation gets long, ask Claude to summarise it so far and carry that summary into a new chat.

Today's task: In one of your long chats, ask Claude for a summary and start a new chat from it.
4

Projects

Writing out your business introduction in every new chat is tiring. Projects solve exactly that.

A project is a separate room made for one piece of work. You put your files in it and write instructions once on how Claude should handle that work. After that, every chat in the project already knows all of it.

For example, make a project for your shop's marketing. Put in the price list, your brand's style and some old posts. Now every new post is written in that same style.

Today's task: Make a project for the job you repeat most, add two files and write four lines of instructions.
5

Artifacts

You read a chat answer and move on. But some things are worth keeping: a report, a presentation, a web page, or a small calculator tool. Claude builds such a thing separately, and that is called an artifact.

An artifact opens in its own panel next to the chat. You can look at it, ask Claude to change it, and send it to others with a link. This course itself began as an artifact.

Today's task: Ask Claude to make a one-page introduction page for your business. Once it is made, ask for one change, such as a colour or the headline.
6

Connectors

Until now Claude knew only what you typed into the chat. Connectors take it to your real work.

A connector is a bridge that joins Claude to one of your apps, such as email, file storage or your calendar. Once it is connected you can say show me today's important emails, or find that file and summarise it, and Claude goes and looks for itself.

Control stays in your hands. You connect it yourself, you grant the permission yourself, and you can remove it whenever you like. Connect only the apps you actually need.

Today's task: Connect your email or calendar and ask which meetings you have this week and which emails are still waiting for a reply.
7

Skills

Teach a new employee how a job is done once and they do it that way every time. Skills do the same for Claude.

A skill is a set of instructions written for one particular job. For example, how your weekly report is made, which sections it has, what the style is. Write all of that into a skill once. From then on, whenever you ask for the report, Claude picks up that method on its own.

Remember the difference between a project and a skill. A project is a place for one piece of work. A skill is a method that travels with you everywhere.

Today's task: Think of a job you do the same way every week. Tell Claude its steps and ask it to turn them into a skill.
8

Plugins

Yesterday we talked about a single skill. Now imagine getting the work of a whole field in one go. That is a plugin.

A plugin is a ready-made pack that brings together several skills and the connectors they need for one role. Install a sales plugin and Claude knows customer research, call preparation and writing follow-ups. Install a marketing one and it knows campaign planning and writing content.

The benefit is that you do not have to build everything yourself. Install it once and Claude becomes an experienced colleague in that field.

Today's task: Find a plugin close to your own work, install it and try one of its jobs.

What else is in chat

  • Files and images: drop a document, a spreadsheet or a picture into the chat and ask about it.
  • Web search: for current information Claude searches the internet and answers with its sources.
  • Voice: speak instead of typing.
  • Memory: Claude can remember the important things you tell it for your next chat. You turn this on and off in your settings.
Part two, days 9 to 11

Claude Cowork

9

Cowork: finished work, not answers

In chat you ask a question and get an answer. In Cowork you hand over a job and get a finished result.

Here is the difference. In chat, Claude tells you how the report would be made. In Cowork it opens the files itself, does the research, runs the numbers and puts the finished report in front of you. Even when the job has many steps it keeps going on its own, and you can watch which step is done as it works.

This is where everything from the earlier days pays off. Connectors give it your data, skills give it the method, and the result arrives as an artifact or a file.

Today's task: Give it a job with several steps. For example, have it research three of your competitors and build a one-page comparison.

Before you start with Cowork

  • To have work done on the files on your computer, you need the Claude app on your computer.
  • Claude works only in the folder you allow. Do not open up the whole computer. Give one folder for one job.
  • Describe the job clearly: what you want, what to build it from, and what shape the result should take.
  • Give a small job first, look at the result, then hand over a bigger one.
10

Schedule

Some jobs happen at the same time every day. Checking the morning's email, the weekly report, the monthly accounts. You do not need to ask each time.

With a schedule you tell Claude once which job to do and when. For example, every morning at eight, go through my email and summarise what matters. After that the job runs by itself at the set time and the result comes to you.

The job starts fresh every time, so write the instruction in full. What to look at, where, and what shape you want the result in.

Today's task: Pick one daily or weekly job and schedule it. Look at the first result and improve the instruction.
11

Dispatch

You are out of the office and remember a file you were supposed to prepare, and it is sitting on your computer. That is the moment for Dispatch.

With Dispatch you write the job to Claude from your phone, and Claude does it on your computer, with the files and connected apps that live there. The same conversation runs on your phone and your computer, so when you get back everything is right there. You do not watch every step. You hand over the job, get on with your own work, and look at the result later.

It needs a paid plan and the Claude app on your computer. The computer has to stay on with the app open. Because Claude is working while you are away, give it access only to the folders it needs.

Today's task: Link your phone and your computer, then go out and send one small job from your phone.
Part three, day 12

Claude Code

12

What Claude Code is

Claude Code is a tool for building software. It reads the files of a whole project, works out which file does what, then on your word writes a new part, finds and fixes a fault, runs the thing to test it and saves the changes.

You say what you want in ordinary language and it does the rest. That means building a website, an app or an AI agent no longer takes years of programming. What it takes is knowing what you want to build and how to give Claude a clear instruction.

It runs in four places: the computer's terminal, the web, the desktop app and mobile. If you cannot code, starting from the app or the web is easier.

If you cannot code, work like this

  1. Say what to build, who it is for, and what it must include. The clearer you are, the better it turns out.
  2. Ask for a plan before the build. Say: first tell me in plain words what you are going to do.
  3. Have one small part built at a time, then run it and look for yourself.
  4. Ask about anything you do not understand. Claude explains the code it wrote in plain words.
  5. If something breaks, copy the error you see and hand it over. It will find the cause and fix it.
  6. Have the work saved after every successful step, so you can go back if you need to.
Today's task: Have Claude Code build a one-page web page for your business with your name, services and contact number. Then ask for one change.
Part four, days 13 and 14

Which one when

13

Chat, Cowork or Code: which one when

Ask yourself one question. Do I want an answer, finished work, or working software? The reply tells you where to go.

What you needWhere to goExample
An answer or adviceChatWriting a message, talking through an idea, understanding something
Finished workCoworkResearch, a report, analysing files, sorting email
Working softwareClaude CodeA website, an app, an agent, repairing existing code
Today's task: Write down five of your jobs for this week and mark each one as chat, Cowork or Code.
14

A full day with Claude

At eight in the morning the schedule runs by itself, and through your connectors a summary of your email and calendar is waiting for you.

At the office you go into your project, where Claude already knows your business. A customer needs a proposal, so you give the job to Cowork, and it follows the method in your skill and produces the finished document.

In the afternoon you are out, so you send the next job from your phone with Dispatch. In the evening a question comes to mind, and chat is there.

None of this is far off. All of it is possible today. At this point you have learned Claude. In the next sixteen days you will use it to build things for your business.

Part five, days 15 to 20

Build a website with Claude

From here the learning ends and the building starts. Each lesson ahead is one idea and one small task, so the whole map makes sense to you.

15

Planning the website

Plan

Most websites turn out weak because the person building them sits straight down to build. Three questions need answers first. Who is this site for? Which pages will it have? And what should the visitor do at the end: call, fill in a form, or buy?

Do this in chat with Claude. Tell it to plan your website by asking you questions one after another. The plan that comes out is what you hand to Claude Code in the coming days.

Today's task: Have Claude plan your website: a list of pages and a one-line purpose for each.
16

Frontend

The frontend is the part of a website people see and touch. Pages, colours, pictures, buttons, text. Think of it as the front of a shop, where the customer walks in.

Give Claude Code yesterday's plan and tell it to build the first page. When it is built, look at it on both a computer and a phone, because most people arrive on a phone. Whatever you do not like, say in ordinary words: make the headline bigger, move the button up.

Today's task: Have the first page of your site built, open it on your phone and ask for three changes.
17

Backend and database

The backend is the part nobody sees but which does all the work. In the shop picture, it is the storeroom and the accounts ledger. When someone fills in a form or places an order, the backend receives it and stores it.

The database is the organised ledger where all of it is written down: customers, orders, messages. You do not write this yourself. Claude Code does. Your job is to decide what the site has to remember.

Today's task: List the information your site needs to store, for example the customer's name, number and what they need.
18

Forms and login

The contact form is the most valuable part of a website, because that is where a visitor becomes a customer. Keep the form short. Name, number and one question is enough. The more boxes there are, the fewer people fill it in.

Not every site needs a login. You need one when each person has their own area, such as the students of a course or members. Remember one thing: do not have a password system built from scratch. Tell Claude to use a proven service for it.

Today's task: Have a contact form built, fill it in yourself and check whether the details reached you.
19

Taking the site live

Deploy

So far your site exists only on your computer. To show it to the world it needs a place on the internet, and that is called hosting. Ask Claude Code to help you take your site live step by step. It will tell you where to make an account and what to do next.

One precaution matters a great deal. The services your site connects to have secret keys. These are never written openly in the code. Tell Claude plainly to keep the keys in a safe place.

Today's task: Take the site live, send the link to a friend and ask whether it opened.
20

Domain and final checks

The domain is your site's address, the name people type to reach you. Choose a short name that is easy to remember, buy it, and ask Claude how to connect it to the site.

Then, before you tell people, go through the whole site yourself once:

  • Does every page look right on a phone?
  • Does every button and every link go to the right place?
  • Does the message arrive when the form is filled in?
  • Does the page open quickly?
  • Are the name, number and prices written correctly?
Today's task: Do these five checks yourself, then ask Claude to look at the site and point out the weak spots too.
Part six, days 21 to 25

Chatbots and agents

21

A chatbot on your website

At two in the morning someone lands on your site and wants to ask the price. Nobody is there to answer, so they leave. A chatbot fixes that, answering every question at any hour, straight away.

A bot is only as good as the information you give it. Give it what it needs to know about your business: services, prices, hours, common questions. And teach it not to guess when it does not know something, but to say I will pass this on to our team.

Today's task: Write down the twenty questions customers ask you again and again, with their answers. That is your bot's knowledge.
22

What an AI agent is

A chatbot talks. An agent acts. That is the whole difference.

A bot tells you tomorrow at four in the afternoon is free. An agent books that slot, writes it in the calendar and sends the customer a confirmation.

An agent is made of three things. The model, which is its brain. The instructions, which say what it should and should not do. And the tools, meaning the apps it can reach, such as a calendar, email or a database. The connectors from day 6 and the skills from day 7 are exactly these tools and instructions.

Today's task: Write down three jobs in your business that are done the same way every time and that an agent could do.
23

Your first agent

Keep your first agent small. One job, clear limits. A good start is a lead-handling agent: when a new enquiry comes in, it asks two or three necessary questions, stores the answers and notifies you.

Make sure the instructions cover three things. What it should do. What it should not do, for example promising a discount. And when to hand the matter to a human.

Before you switch it on, play the customer yourself and ask hard questions. Wherever it answers wrongly, improve the instructions.

Today's task: Write your lead agent's instructions: what it asks, what it must not say, and when it calls you in.
24

Multi-agent systems

Ask one employee to do the research, the writing, the checking and the accounts, and quality drops. An agent is no different. When the job is big, you build a team of agents.

For example, one agent researches, a second writes, a third checks. Above them sits a supervisor agent that divides the work and joins the results.

But not every job needs a team. A team adds both cost and complexity. The rule is to start with one agent, and build a team only when the parts of the job really call for different expertise.

Today's task: Split one of your big jobs into three roles and write who does what and who they pass it to.
25

A complete sales system with AI

AI Sales Operating System

In most businesses a customer is lost because the reply came late or nobody followed up at all. A sales system stops that.

This is the path. A lead comes in. It gets an instant reply. It is asked what it needs. A meeting or call is booked. If no reply comes, a follow-up goes out. And everything is written to the record.

An agent can work at each step, and together they form one system. Closing the deal is still a human's job. The agents make sure no customer drops out along the way.

Today's task: Write down the steps of your sales process and mark the step where you lose the most customers. Your first agent goes there.
Important

Four precautions

  • Never type a password, a bank account number or a national ID card number into a chat.
  • Check important facts, calculations and anything legal or medical yourself. Claude can make mistakes.
  • Grant permissions with thought. Connect only the app and the folder the job needs.
  • Anything that goes out in your name, an email, a post or a payment, read it yourself before it is sent.
Learn Claude, one step a day

Start today

These 30 days show you the whole road. If you want to build the website, the agents and the sales system yourself, step by step with practical examples, the full program is here.