Course: Building AI Apps | Pathway: Builder | Tier: Free | Level: Beginner Estimated Reading Time: 9 minutes
An internal tool is software built for you and your team, not for the public. It doesn't need to look slick. It doesn't need a marketing page. It just needs to work.
Every business has processes that involve shuffling information around — tracking clients, managing stock, logging jobs, reviewing data. Most of the time, this happens in spreadsheets, email threads, or people's heads. Internal tools move that information into something structured, searchable, and shared.
The reason this matters: off-the-shelf software is built for the average business. Your business isn't average. You have specific workflows, specific data, specific needs. An internal tool you build yourself can fit your work perfectly, because you designed it for exactly how your team operates.
Let's look at the most common categories and what they actually look like in practice.
A dashboard pulls together key information in one view. Instead of opening three spreadsheets and an email to figure out how things are going, you open one page.
Example: A small logistics company in Hamilton could build a dashboard showing:
The data might come from a spreadsheet that drivers update, or from a simple form they fill out when a job is done. The dashboard just makes that data visible at a glance.
An admin panel lets you manage data — add, edit, delete, search. It's like a spreadsheet with a better interface and some rules built in.
Example: A training company could build an admin panel to manage their course registrations:
This is the kind of thing that often lives in a messy spreadsheet with colour-coded rows. An admin panel makes it cleaner and harder to break.
A data viewer lets people look up information without being able to change it. Useful when you want people to access data but not mess it up.
Example: A property management company could build a viewer where tenants check:
The tenants can see their information but can't change anyone else's. The property managers update the data through a separate admin panel.
Sometimes the tool you need is a structured way to collect information and route it to the right person.
Example: A manufacturing business could build an incident reporting form:
This replaces paper forms that get lost, emailed PDFs that nobody can find, and verbal reports that are forgotten.
The process is similar to what we did with the chatbot, but the tool is different. Here's the step-by-step approach.
Before you build anything, write down the process you're trying to improve. Be specific.
Questions to answer:
Use plain language. "Sarah checks the spreadsheet every morning to see which jobs are booked for the day, then calls the team to confirm" is exactly the kind of description you need.
Draw a rough sketch of what you want to see on screen. This doesn't need to be pretty — a pen-and-paper sketch is fine. Note:
Open your AI-assisted builder (Replit, Cursor, or similar) and describe what you want. Be specific and practical.
Here's an example prompt for building a client tracker:
Build a web app for tracking client interactions. It should have:
A main page showing a table of all clients with columns for:
- Client name
- Company
- Last contact date
- Next follow-up date
- Status (Active, Inactive, Prospect)
I should be able to:
- Click "Add Client" to open a form and add a new client
- Click on a client name to see their full details and interaction history
- Add notes to a client's record with a date stamp
- Filter the table by status
- Search by client name or company
- Sort by any column
The data should be saved so it persists when I close the browser.
Keep the design clean and simple. Use a neutral colour scheme.
Once the AI generates your tool, go through it carefully:
Once the tool is working, add your real data. Start with a small set to make sure everything works, then add the rest.
If you're coming from a spreadsheet, you can often ask the AI to help you import the data: "I have a CSV file with client data. Add a feature to import clients from a CSV file."
Start smaller than you think. Your first version should do one thing well. A client tracker that just lists names and contact details is more useful than a half-finished tool that tries to do everything.
Don't worry about how it looks. Internal tools don't need fancy animations or perfect design. If the information is clear and the buttons work, it's good enough. You can always improve the appearance later.
Think about who else needs access. If only you use it, a local tool is fine. If your team needs it, you'll want to deploy it somewhere everyone can reach — which we'll cover in Lesson 6.
Protect sensitive data. If your tool contains client information, financial data, or anything personal, think about who can access it. At minimum, don't put it on a public URL without some kind of login. If you're handling customer data, be mindful of the Privacy Act — keep only what you need and store it securely.
Back up your data. If your tool stores important information, make sure you have a way to export or back it up. Ask the AI to add an "Export to CSV" button — it's usually straightforward.
Let's walk through a complete example. Imagine you run an electrical contracting business in Dunedin with a team of four electricians.
The problem: Jobs are tracked in a shared spreadsheet that's constantly out of date. People forget to update it. You never quite know which jobs are in progress and which are done.
The tool:
You build a simple job tracker with:
What it replaces: A messy spreadsheet, three WhatsApp messages per day asking "is that job done?", and a sticky note system for tracking invoices.
Time to build: A few hours, with most of that spent refining the details and entering existing job data.
Let's be honest about limitations:
These aren't reasons to avoid building internal tools. They're just things to be aware of so you set realistic expectations.
In the next lesson, we'll shift to a different kind of project: micro apps. These are small, focused tools that do one thing — and they're often the fastest way to turn an idea into something useful and shareable.
Key Takeaways: