Memuat
Memuat
Want to go deeper?
Join one of our courses or ask us directly on WhatsApp.
Picked from the software, topic, and level of “Claude from Zero to Expert Class #50: Practice: A Monthly Report Ready to Send”.
Other ways we can help with Claude.
Learn with a mentor
Scheduled AI & Machine Learning courses with live guidance and a certificate.

Midjourney Course: Create Stunning AI Images from Text
★ 4.9

DALL-E Course: Creating Professional AI Images from Text
★ 4.9

Stable Diffusion Course: AI Art from Beginner to Professional
★ 4.9
Have it built for you
No time to learn Claude? Our team can do the project for you.

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production
★ 4.9

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business
★ 4.9

AI Image Creation with Midjourney — Cinematic AI Art for Business
★ 4.9
Get notified about new Claude classes
At most one email a week. Unfollow anytime with one click.
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Hi, and welcome to the closing practice of the data analysis session. Today we combine everything we've learned into one real result: a monthly report that's ready to send. We'll help Dewi from Maju Bersama Co., from setting up a Project, processing the October data, and building the report and chart, to writing the email and saving a template for next month.
Here's our work map for today. First, clean this month's data, as we learned at the start of the session. Second, analyze: find the key numbers and insights, complete with a comparison to last month. Third, a chart with one message per chart. Fourth, build the report as a one-page Artifact. Fifth, send it with a short email. Dewi will do these five steps in one and the same Project. Because this report is made every month, Dewi sets up a dedicated Project called Monthly Sales Report. The first file is the September data, for comparison. The second file is the September report that was already sent. It's an example of the format the director likes, so Claude can match its style. The third file is the standard data rules: official category names and the date format, just like the cleaning rules at the start of this session. The fourth file is the new October data, one thousand two hundred eighty-four rows. The customer contact name and phone columns have been removed, leaving only customer codes. The project instructions on the upper right set the reader, the report structure, how to write numbers, and the rule to always compare with last month. These instructions will be used again every month.
Let's peek at the October data before processing it. Each row is one transaction: date, customer code, category, item, quantity, and total. In the first row, customer K07 buys forty reams of A4 paper. In the second row, the stationery category is written in lowercase. A classic problem we already know. In the third row, the date format is different. And the fourth row is suspicious: the same customer, item, and total as the second row, just one day apart. It could be a duplicate order, or it could be a regular order. The standard rules in the Project will help Claude decide, and ask about anything doubtful. Data like this exists in almost every office. The good news is that we already know how to clean it. Inside the Project, Dewi asks for two things at once: clean the October data according to the standard rules, then calculate sales by category and compare them with September. Claude reads both files and runs the analysis. The result starts with a cleaning report: fourteen duplicate rows removed and category names standardized. Then a table by category in millions of rupiah. Paper is up almost eleven percent, while stationery and ink and toner are down about four percent. The total is up three point one percent. All the numbers here are examples. Before going further, Dewi matches the total against the office register system. The numbers are the same, three hundred thirty-two million. This step is simple, but it gives Dewi confidence that the whole report stands on the right numbers. Numbers alone aren't enough. Dewi asks for the causes, and asks for facts to be kept separate from guesses, as the project instructions say. The fact is that most of the paper increase came from three office customers. The guess is that they're stocking up for year-end. The stationery drop is spread across small customers, with a guess that some have switched to online stores. Dewi will confirm these guesses with the sales team before writing them in the report.
Now the report. Dewi only needs to write one sentence: build the October report following the structure in the project instructions. The details are already in the Project. The report appears in the right panel. The title delivers the message right away: sales are up three point one percent, driven by paper. Below it are four key number cards, then a chart of sales by category, complete with a note on the source and period. Dewi checks every number against the analysis table. They all match. The structure set in the project instructions keeps the report's shape the same every month, so the director can compare easily. The bottom part of the report holds the insights and recommendations. Dewi finds two things to fix: the second insight is still a guess but isn't marked, and the second recommendation is too general. In version two, the second insight is marked as a guess. The second recommendation is now concrete: the sales team calls ten small customers before November fifteenth to ask why. Notice how every lesson from this session shows up: clean data, insights kept separate from guesses, a chart with a message-driven title, and recommendations that can be acted on right away.
The report is ready. Now the cover email. Dewi asks Claude to write a short draft, then copies it into the office email app. In the inbox we can see that draft, above the director's reply to last month's report. The draft opens. It has only three parts: a concluding sentence with the most important numbers, one decision requested from the director, and a note about the attachment. An email this short respects the director's time. The details are in the attached report, while the email just answers two questions: what happened, and what needs to be decided? Before hitting send, run a final check. First, the total matches the register system. Dewi has already done this. Second, the numbers in the email match the numbers in the report. A one-digit typo in the email can make the director doubt the whole report. Third, guesses are marked and not written as facts. Fourth, there are no customer names or personal contacts. The report only has codes like K07. Fifth, the attachment is correct. A classic mistake is attaching last month's report. Sixth, the recipient is correct and the email's tone has been reread. Dewi presses the send button herself. Claude prepares; a person decides and takes responsibility.
To make next month faster, Dewi saves one template prompt. Only the file name in the data section needs to be changed. The first and second tasks: clean the data, report the changes, then calculate by category and compare with last month. The third and fourth tasks: build the report following the project instructions, and write a cover email of five sentences at most. The limits protect quality: Claude must stop and ask if the total differs from the register figure, and must mark every guess. This one prompt runs the whole flow we learned in this session. The work isn't over once the report is sent. First, note the recipient's response. The director's questions today are material for next month's report. Second, in the next report, check last month's recommendations: were they done or not, and what happened? A report that follows up on itself is trusted much more. Third, if the director asks for a different format, update the project instructions. That way the change automatically applies to every report after that. Let's sum up this session. One Project that's reused every month, complete with instructions and comparison data. Five work steps: clean, analyze, chart, report, and send. And one template prompt for next month. Dewi can spend the time she saves on the things Claude can't do: talking with customers and the team. Apply the same flow to reports in your own business or office.
The data analysis session is complete. We've built a full monthly report from our own data, from the Project and raw data to an email ready to send and a template for next month. In the next session, Claude connects directly to work apps such as Google Drive, Gmail, and your calendar through Connectors, so we no longer have to upload files one by one. See you there!
Try these on your own after watching to lock in what you learned.
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
Notes are saved with the current video time and are only visible to you.
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.

Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
See our clients →