How to build an internal tool without developers (a step-by-step example with AI)
Every small company has a job that lives in the wrong place. Who has which laptop. Which van is due for a service. Which client asked for what, and who's on it. It sits in a shared spreadsheet, a WhatsApp group and one person's head, and it works until that person goes on holiday. The usual answer is "we should build a proper tool for that", followed by nothing, because there's no developer free…
Small businesses often store essential information in scattered shared spreadsheets, WhatsApp groups, and scattered heads. A developer is not always available to build a dedicated tool, especially for relatively minor tasks. This is where AI-driven app builders come in handy.
To demonstrate, let's build an equipment tracker for a 40-person company step-by-step using an AI app builder. The tracker will keep a record of all equipment items (name, type, serial number, purchase date, condition, location, photo), as well as checkouts and returns (who has the item, when it's due back, and any notes on condition).
Only certain roles have different permissions: all can see items and make requests, office managers check out and check in items, and admins can add, edit, or retire items. The most common questions to answer are "Who has the projector?" and "What's overdue?".
First, write a concise one-page brief describing the tool's purpose and functionality. This will help AI understand the context better. Second, provide the AI with a detailed prompt that lays out the equipment tracker's features, data model, roles, and the primary pages and functions needed. Third, review the AI-generated database model and make necessary adjustments to ensure proper data structure and calculations (e.g., overdue items, current holder status).
Next, import existing data from a spreadsheet into the tool using an admin page. This step is crucial as it saves time and ensures the data is clean and error-free. Fourth, add features that team members will actually use, such as displaying an individual's items, overdue checks, and a request function. Finally, thoroughly test the tool as different user roles, checking for any issues or unintended behaviors. Once the tool is ready, deploy it exclusively for the team.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
