Mwangaza
Templates & Tools

The Weekend Build Pack: 10 Useful Things You Can Build with Claude Code

Kye · · 11 min read

These are ten tools you can build in a weekend, grouped by the work you do. Each one comes with a prompt to paste into Claude Code, a rough time and a description of what you have at the end.

If you haven’t installed Claude Code yet, start with Getting Started with Claude Code. It takes you from nothing to a working budget tracker in about an hour, and everything below assumes you’ve done that once.

How the prompts work

Every prompt asks for the same kind of result: one HTML file you open by double-clicking. It runs in your browser with no server, no account and nothing else to install. They also work offline, because they ask for no external libraries.

The tools that keep records save them in your browser. That data lives on one computer, in one browser, and clearing your browsing data deletes it. So every prompt that stores records also asks for an export button. Use it.

For each tool: make a new folder, open a terminal in it, type claude and paste the prompt. When the first version appears, test it with real numbers from your work, then ask for changes in plain English. The times below are for a first working version plus a round or two of fixes.

For engineers

1. Site inspection report generator

For: anyone who walks a site with a notebook and spends the evening typing it up.

Try this prompt: “Build a site inspection report tool as a single file called inspection.html, with no external libraries. Fields at the top: project name, site location, inspector, date, weather. Below that, let me add inspection items, each with a location or chainage, a description, a condition rating (Good, Fair, Poor, Critical), a recommended action and an optional photo that I pick from my computer. Show a summary table with a count of items by rating, Critical items first. Add a Print button that lays the report out cleanly on A4, with photos under their items. Save everything in the browser, and add buttons to export and import the data as a JSON file.”

Time: about 1 to 2 hours.

You end up with: a report you fill in as you go and print to PDF when you’re done. The photos are the fiddly part. If they come out too large on the page, ask for them to be resized to a fixed width.

2. Bill of quantities checker

For: engineers and quantity surveyors reviewing a contractor’s bill of quantities, where one wrong multiplication can hide in 300 lines.

Try this prompt: “Build a bill of quantities checker as a single file called boq-check.html, with no external libraries. I paste rows from a spreadsheet with these columns: item number, description, unit, quantity, rate, amount. The tool recalculates quantity times rate for every row and highlights any row where the stated amount is wrong, showing the difference. It also recalculates the section totals and the grand total and compares them with the totals I enter. Flag rows with a missing quantity or rate, and rows with the same description and different rates. Add a button to export the flagged rows as a CSV file.”

Time: about 1 hour.

You end up with: a checker that does the arithmetic review in seconds and leaves you the engineering review. Test it first on a bill where you’ve planted two mistakes yourself, so you know it catches them.

3. Traffic count tally sheet

For: anyone running a manual classified traffic count who is tired of tally marks on a clipboard.

Try this prompt: “Build a manual traffic count tally sheet as a single file called traffic-count.html, with no external libraries. At the top: station name, direction, observer, date. Show one large button per vehicle class: motorcycle, car, minibus, bus, light goods vehicle, medium goods vehicle, heavy goods vehicle, articulated truck. Tapping a button adds one to that class. Group counts into 15-minute intervals that start and end on their own based on the clock, and show the current interval’s counts and the running totals. Add an Undo button for the last tap. Save everything in the browser and add an Export CSV button that gives one row per interval with a column per class.”

Time: about 1 hour.

You end up with: a counting board that produces a clean CSV instead of sheets you type up later. Change the vehicle classes to match the classification your client or roads authority uses before you take it to the field.

For finance and business

4. Budget-vs-actual variance checker

For: anyone who reports each month on spending against budget and builds the same variance table by hand every time.

Try this prompt: “Build a budget-vs-actual variance checker as a single file called variance.html, with no external libraries. I paste two tables from a spreadsheet: the budget (budget line, amount) and the actuals (budget line, amount). Match the lines by name and show a table with budget, actual, variance in money and variance as a percentage. Colour overspends red and underspends of more than 20% amber, and let me change both thresholds. List any lines that appear in one table but not the other. Show the totals at the bottom and add a button to export the table as a CSV file.”

Time: about 1 hour.

You end up with: a variance table built in the time it takes to paste two ranges, with the lines that need an explanation already marked. The mismatched-lines list is the useful surprise. It catches the budget line someone renamed halfway through the year.

5. Loan repayment schedule

For: anyone comparing loan offers or explaining repayments to a client or a committee.

Try this prompt: “Build a loan repayment calculator as a single file called loan.html, with no external libraries. Inputs: loan amount, annual interest rate, term in months, start date, and a choice between reducing balance and flat rate interest. Show the monthly payment, total interest and total paid, then a full schedule with one row per month: payment date, payment, interest, principal and remaining balance. Let me enter up to three loan offers and compare them side by side. Add a Print button and a button to export the schedule as a CSV file.”

Time: about 1 hour.

You end up with: a schedule you can print for a meeting and a side-by-side view of what each offer costs in total. Check the first two rows of the schedule against a spreadsheet you trust before you rely on it. Interest calculations are where confident-looking code is most likely to be quietly wrong.

For public service

6. Procurement bid comparison sheet

For: evaluation committee members who need a clear, defensible comparison of bids.

Try this prompt: “Build a bid comparison sheet as a single file called bids.html, with no external libraries. At the top: tender reference, description, and the evaluation criteria with a weight for each (I set the criteria and weights, and the tool warns me if the weights don’t add up to 100). Then let me add bidders, each with their name, bid price, a pass or fail for each mandatory requirement, and a score for each weighted criterion. Calculate each bidder’s weighted technical score, show which bidders failed a mandatory requirement, and rank the rest. Keep a notes field per bidder for the committee’s reasons. Save in the browser, add export and import as a JSON file, and add a Print button for a clean summary page.”

Time: about 2 hours.

You end up with: a comparison that shows its working, which is what an audit asks for. Set the tool up to match your procurement rules, not the other way round. If your process scores price with a formula, describe that formula in a follow-up prompt.

7. Meeting minutes and action log

For: whoever takes the minutes and then has to chase the actions.

Try this prompt: “Build a meeting minutes tool as a single file called minutes.html, with no external libraries. For each meeting I record: title, date, attendees, apologies, and agenda items, each with discussion notes and decisions. Each agenda item can have action points with an owner, a due date and a status (Open, Done). Keep a separate Actions view that lists every open action across all meetings, sorted by due date, with overdue ones highlighted. Add a Print button that formats a single meeting as standard minutes. Save in the browser and add export and import as a JSON file.”

Time: about 1 to 2 hours.

You end up with: minutes and a running action list in one place, so the next meeting starts with what’s overdue. The Actions view is the part people keep using after the novelty wears off.

For small business

8. Customer follow-up tracker

For: owners who lose sales because nobody called the customer back.

Try this prompt: “Build a customer follow-up tracker as a single file called follow-ups.html, with no external libraries. For each customer: name, phone number, what they asked about, date of last contact, next follow-up date and notes. The home screen shows three lists: overdue follow-ups, due today and coming up this week. Each customer has a ‘Contacted today’ button that updates the last contact date and asks for the next follow-up date. Add search by name or phone number. Save in the browser and add export and import as a CSV file.”

Time: about 1 hour.

You end up with: a daily list of who to call. Open it first thing each morning and work down the overdue list.

9. Invoice and receipt generator

For: anyone still making invoices in a word processor and doing the sums by hand.

Try this prompt: “Build an invoice and receipt generator as a single file called invoice.html, with no external libraries. Save my business details once: name, address, phone, email, tax number and payment instructions. For each invoice: client name and address, invoice number (suggest the next number automatically), date, due date, and line items with description, quantity and unit price. Calculate line totals, subtotal, tax at a rate I set and the total. Let me mark an invoice as paid and print a receipt for it. Keep a list of past invoices with their status. Print cleanly on A4. Save in the browser and add export and import as a JSON file.”

Time: about 1 to 2 hours.

You end up with: numbered invoices, receipts and a list of who still owes you. Put your own details in first and print a test invoice. If it wouldn’t pass as your business’s paperwork, say what looks wrong and ask for a fix.

10. Stock tracker with reorder alerts

For: shops and small suppliers who find out an item is finished when a customer asks for it.

Try this prompt: “Build a stock tracker as a single file called stock.html, with no external libraries. For each item: name, unit, quantity in stock, reorder level, supplier and cost price. Let me record stock coming in and going out, with a date and a note, and keep that history for each item. The home screen shows items at or below their reorder level at the top, then everything else. Show the total value of stock at cost. Save in the browser and add export and import as a CSV file.”

Time: about 1 hour.

You end up with: a reorder list that builds itself as you record sales and deliveries. It is only as accurate as what you record. Do a physical count after the first week and compare.

When something goes wrong

The first version will get something wrong. Describe the problem as specifically as you can: “the total ignores the last row” gets a fix, “it doesn’t work” gets a guess.

Check the numbers yourself at least once. Every tool here does arithmetic, and Claude Code can write code that runs without errors and still calculates the wrong figure. You know what the right figure is.

If a tool stops saving, or you move to a new computer, use the import button with your last export. That is why every prompt asks for one.

Tell me what you built

Pick the tool closest to a job you did by hand last week and build that one first. Then change it until it fits your work exactly. That part is yours, and it’s where the tool becomes worth keeping.

When you’ve built something, reply to the newsletter email and tell me what it was and what you changed.

How this was written: Drafted with AI (Claude), edited and verified by the author.