Yes, it's genuinely possible to build an internal system — like inventory or order tracking — without hiring an outside development shop, though that doesn't mean it can fully replace every kind of system. Where this approach works well, and where you should be careful, is explained step by step below. A growing number of people in online communities have been asking whether tools like Claude can replace outsourced software development for internal business systems. This guide answers that question directly by walking through how to build a working prototype (a first version you build to confirm an idea actually works, before it's used for real) of an internal system using the Claude desktop app, from start to finish.
In a small-business case study published by Anthropic, Liberty Trailers CFO Ashley Wells said, "Dashboards that would take weeks or months, we can now build in a day or two." Not every internal system will come together this fast, but it's a real enough example to make trying it worthwhile.
What you'll be able to do
By following this guide, you'll install the Claude desktop app and build a first working prototype of an internal system you need — for example, a tool that logs inventory counts and stock movements. Getting from install to a working prototype takes roughly 30 minutes to an hour. Keep in mind the result at this stage is a prototype for your own use; turning it into something coworkers can use too requires a separate deployment step (deploy — putting a program on a server so other people can reach it over the internet) afterward.
Before you start
Check these items first.
- A paid plan — The Code tab in Claude Code only opens on paid plans like Pro, Max, Team, or Enterprise. The Free plan only gives you general chat.
- A computer — You'll need a Mac (a universal build supports both Intel and Apple Silicon) or Windows machine (installers exist for both x64 and ARM64). Linux is supported in beta on Ubuntu and Debian.
- A concrete description of what you want to build — Write a sentence or two on what you want to track (e.g., stock counts, order status), who will use it, and what the screen should look like. This single step makes a big difference in the quality of the result.
- (Optional) Reference material — If you already track things in a spreadsheet or have notes on your current process, you can share those with Claude too.
Terms explained
- Claude Code — A feature that lets Claude read your actual files and write and run real code. Unlike a normal chat, it creates working program files inside a folder on your computer.
- Code tab — One of three tabs at the top of the desktop app (Chat, Cowork, and Code). It lets you use Claude Code entirely by clicking — no terminal (a command-line window) required.
- Permission mode — A setting that controls how much approval Claude asks for before changing files. Explained in detail below.
- Diff view — A screen that shows exactly what will change in a file, before and after, side by side.
- MCP (Model Context Protocol) — a connection standard for external tools — An official way to connect Claude to outside services like Google Drive or Slack so it can read and write data directly.
Step-by-step
Install the desktop app, pick a folder in the Code tab, then describe the system you want in a prompt (the request text you type to Claude). Follow the steps below in order.
- Install and sign in — Download the installer for macOS or Windows from claude.com/download, run it, and sign in with your account. Success looks like: the app opens and you see three tabs at the top — Chat, Cowork, and Code. ⚠️ On the Free plan, clicking Code shows an upgrade prompt instead — you'll need a Pro or higher plan first.
- Create a working folder in the Code tab — Click the Code tab, select Local, then click Select folder and choose or create a new folder (e.g., "inventory-system"). Success looks like: you see a workspace with an empty file list and a prompt box.
- Pick a model and write your request — Choose a model from the dropdown next to the send button (for a more complex system, a more capable model generally works better). Then describe exactly what you want. For example: "Build a web page that logs stock counts and restock dates, and shows any item with 10 or fewer in stock in red at the top of the list." Success looks like: Claude explains its plan and starts creating files, and a change indicator (e.g., +12 -1) appears.
- Review and approve changes — In Manual mode, review each change in the diff view and Accept or Reject it. In Auto or Accept edits mode, Claude applies changes first and shows you the result. Success looks like: new files appear in the file list, and the diff reflects the screen you asked for.
- Preview it running — Once Claude starts a dev server, the app opens in the Browser pane so you can see it live. If something's off, just keep going — say something like "move this button up." Success looks like: the screen and features you asked for actually work in the Browser pane.
Reviewing changes safely with permission modes
Claude Code offers four permission modes that control how much approval it asks for before touching your files. For your first attempt, starting with Manual mode — where you review every change — is the safest choice.
| Mode | How it works | Best for |
|---|---|---|
| Manual | Asks for approval every time before editing a file or running a command | Your first sessions, or when you want to check every change individually |
| Auto | A background check flags only risky actions for your approval | Once you're comfortable and want to move faster |
| Accept edits | Applies file changes automatically and shows you the result | Fast, repetitive edits during iteration |
| Plan | Proposes an approach without touching any files | Reviewing the plan before a large structural change |
Common pitfalls and fixes
- Clicking Code just shows an upgrade prompt — Cause: you're on the Free plan. Fix: subscribe to Pro or higher, then try again.
- Signed in, but the Code tab shows a 403 error — Cause: an authentication issue. Fix: restart the app and sign in again.
- The result doesn't match what you wanted — Cause: your first request was probably too vague. Fix: follow up with specifics on what, why, and how. Attaching a screenshot of what you want and saying "make it look like this" also works well.
- The prototype works, but you're not sure how to get coworkers using it — Cause: a local prototype and a live shared system are two separate stages. Fix: from here you need a deployment step to put it on a server others can reach — this is a separate skill to learn. Start with a prototype for yourself and expand scope from there.
- ⚠️ If the system starts handling data that affects real operations — like money or stock counts — add a step where a person double-checks the results before relying on it in production. This matters even more in regulated areas like healthcare or finance.
Going further
Once your first prototype feels solid, get in the habit of using Plan mode to review the approach before large changes — it cuts down on mistakes. Adding a file named CLAUDE.md to your working folder, with the rules this system should follow, also helps: Claude keeps referring back to that context in future sessions. If you want to connect existing spreadsheets or Google Drive files, MCP connections are worth exploring next. In a case study published by Anthropic, business owners with zero coding background have built their own internal tools this way — Norton's owner Cameron Pappas said, "I've never coded anything in my life," while adding that "our design team is more efficient, our buying is better, and the customer is a lot more likely to get what they ordered."
Frequently asked questions
Q. Can I really build a complete internal system without a developer?
A working prototype of an internal tool — like inventory or order tracking — is genuinely realistic. For systems that touch payments or sensitive data, though, it's safer to add a step where a person double-checks the result.
Q. Can I start on the Free plan?
No. The Code tab only opens on paid plans — Pro, Max, Team, or Enterprise. The Free plan only offers general chat.
Q. What if I don't have a Mac or Windows machine?
Linux is supported in beta, limited to Ubuntu and Debian. Installation steps for all three platforms are documented officially.
Q. What else do I need before coworkers can use what I built?
Beyond the local prototype, you need a deployment step to put it on a server others can reach. Starting with a personal prototype and expanding scope gradually is the realistic path.
Rather than assuming this replaces outsourced development entirely, the realistic approach is to test the idea with a small prototype first and expand from there. Start with the five steps above and see how far you get.