# Build your own job and bid tracker

> Researched. Small business · Intermediate · Operations. Updated 2026-11-16.

Canonical page: https://www.aisetupsthatwork.com/setups/build-a-small-job-and-bid-tracker-app-with-claude-code/

## What it does
Build a small job and bid tracker with Claude Code that runs on your own computer, so you can drop a paid tracker you only use for lists and follow-up dates.

## Who it's for
Solo trades and small shops that pay for a job tracker but only use it to list jobs, bids, statuses and follow-up dates.

## Tools
- Claude Code, in the terminal or the desktop app
- A new, empty folder for the app
- An export of your jobs from the paid tool, if it offers one
- A second place to keep backup copies of the data file

## Steps
1. Check whether the paid tool lets you export your jobs, usually as a CSV file. Do this first. If it does not, stop here and keep the tool.
2. Write down what you actually use, in a short list: the fields on a job, the statuses, the views and the reminders. Anything not on the list stays out of the app. Invoices, payments and customer messages stay in the tool or in your usual process.
3. Make a new folder and open Claude Code in it in Manual mode (cd into the folder, then claude --permission-mode manual). In Manual mode Claude Code stops and asks before most consequential actions, such as editing files or running commands, though not before every read. Newer versions start in auto mode by default, so check the mode indicator.
4. Paste the prompt below with your fields and statuses. Read what Claude Code wants to do and approve each action.
5. Start the app as Claude Code tells you. Load the made-up jobs, then check each view, the follow-up list, the search and the export.
6. Check the network behavior. Look at the address the app is listening on and confirm it is the local address only, then try opening it from another device on the same network; it should not load. Do this before any customer data goes in.
7. Import your real export only after those checks pass. Compare the number of jobs in the old tool with the number in the app, and spot-check a handful of jobs against the originals.
8. Run both tools for a full cycle of jobs. Cancel the paid tool only after that, and keep the export file.
9. Set up the backup. Copy the data file to a second place on a schedule you can keep, and try a restore once.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
Build a small job and bid tracker that runs only on this computer. Use a language and tools you can run here. Keep it simple.

What it must do:
- A web page I open in my browser, served only on this computer (localhost), so nobody else on the network can open it.
- One data file in this folder, in a format I can open in a spreadsheet (CSV is fine). All jobs live in that file.
- Each job has: customer name, phone, address, job type, status, bid amount, date bid sent, follow-up date and notes.
- Statuses: Lead, Bid sent, Follow up, Won, Lost, Done.
- Views: all jobs, a "Follow up today or overdue" list, and a search by name or address.
- Add, edit and delete a job, with a confirm step on delete.
- A button to export all jobs to a CSV, and a button that saves a dated backup copy of the data file.
- An import from a CSV with the same columns, which shows how many rows it will add before it adds them.

What it must not do:
- No sending of email, text or anything else. No internet access. No accounts or payments.
- No change to files outside this folder.

First load 5 made-up jobs so I can try it, for example "Pat Ortiz, 14 Birch Lane, furnace repair, Bid sent, 850, sent Nov 9, follow up Nov 16". Then tell me how to start it, and what to check. Before you run anything, say what you will do.
```

## Guardrails
- What it touches: Chat input you provide (Claude Code, in the terminal or the desktop app; A new, empty folder for the app).
- Needs your OK: Send, pay, publish, delete, and CRM updates stay with you unless you explicitly opt in.
- Safety level: Adds sheet rows
- What this does and does not replace: This replaces a tracker you use only as a list of jobs, bids, statuses and follow-up dates. It does not send invoices, take payments, schedule crews or message customers, and it is not on your phone. If you use any of that in the paid tool, keep the tool.
- Your data is on one computer: The data file lives in one folder on one computer. If the computer fails and there is no backup, the jobs are gone. The file holds customer names, phone numbers and addresses, so treat the folder like any customer list and back it up.
- Keep it in Manual mode while it builds: The Claude Code docs say that in Manual mode Claude Code stops and asks before most actions that edit files, run shell commands or reach the network. The prompt says not to touch files outside the folder. That is an instruction, not a lock, so read each action before you approve it.
- What was checked: The Claude Code claims were checked against the Claude Code docs on Nov 16, 2026: the quickstart, permission modes and best practices. The app was not built or run for this page. The sample jobs and customers are made up.
- Claude Code adds features you did not ask for. Say what to remove, and keep the "must not do" list in the prompt.
- The import adds rows twice. Check the row count before and after, and keep the old export untouched.
- The data file gets overwritten by a mistake. Back it up before every change, not only on a schedule.
- The app stops working after a computer update. Keep the prompt and the data file, and ask Claude Code to rebuild or repair it.
- The paid tool costs less than the plan you pay for Claude Code. Then this does not save money.

## Tips
- Ask Claude Code for a short test list at the end, so you can check the app after any change.
- Keep the prompt. When you want a change, paste it again with the change, so the file format stays the same.
- Add features one at a time, and re-run the checks after each.

## Estimates (labeled, not measured)
- Time saved: Not stated in sources.
- Money saved: Not stated in sources.
- Tool cost: Claude Code needs a paid Claude plan (Pro, Max, Ultra, Team or Enterprise) or a Claude Console account. See claude.com/pricing. This only saves money if the paid tracker you leave costs more than the plan you already pay for.

## Sources
Summaries use the public sources below, not independent verification.
- Anthropic: https://code.claude.com/docs/en/quickstart (Claude Code quickstart (read Nov 16, 2026): install commands, plans that include it (Pro, Max, Ultra, Team or Enterprise, or a Claude Console account), start it with cd into a folder then claude.)
- Anthropic: https://code.claude.com/docs/en/permission-modes (Claude Code permission modes (read Nov 16, 2026): in Manual mode Claude Code stops and asks before most actions that edit files, run shell commands or reach the network; start in Manual with claude --permission-mode manual; auto mode is the built-in starting mode on current versions.)
- Anthropic: https://code.claude.com/docs/en/best-practices (Best practices for Claude Code (read Nov 16, 2026): tell Claude what it cannot see and give it a check to run, which is why the prompt asks for made-up jobs and a list of things to check.)

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-build-a-small-job-and-bid-tracker-app-with-claude-code

Related:
- [Track the bids you sent and follow up](https://www.aisetupsthatwork.com/setups/track-sent-bids-and-follow-up/index.md)
- [Job emails to a sheet with Claude Code](https://www.aisetupsthatwork.com/setups/turn-job-emails-into-a-spreadsheet-with-claude-code/index.md)
- [Track inventory in a spreadsheet with reorder alerts](https://www.aisetupsthatwork.com/setups/inventory-tracker-with-reorder-alerts/index.md)
