Build internal tools with AI: four prompts and what to decide first
Every team has a tool it needs and never gets: an admin page, an approval queue, a stock register. The people who need it can now describe it. Four prompts, and the questions to settle before anyone logs in.
Internal tools are important and never urgent, so they go to the bottom of the engineering list and stay there. Meanwhile somebody keeps a forty-tab spreadsheet alive, approvals happen in chat threads that get buried, and a month-end figure depends on one person remembering to copy something. The tool is usually small. Waiting for a developer to have time is what makes it feel big.
A builder lets the person closest to the problem write it down and get a first version the same day. Here are four prompts in a shape that works. They are written to name the records, the stages and the people, which is what the builder needs from you. This post explains why.
Four prompts to adapt
An admin panel
Build an admin panel for managing user accounts. Show a searchable
table with name, email, plan, signup date, and status (active or
suspended). Include a detail view for each user with their activity
log and a button to reset their password.An approval queue
Build a purchase request approval tool. Employees submit requests
with item description, amount, vendor, and urgency. Managers see a
queue of pending requests and approve or reject with a comment. Show
total spend this month, pending count, and average approval time.A stock register
Build an inventory tool for a warehouse. Track items with SKU, name,
quantity, location, and reorder threshold. Show low-stock alerts and
items by category. Include a form to log stock in and out with
timestamps.A support board
Build a customer support board. Show open tickets in columns: New,
In Progress, Waiting on Customer, Resolved. Each ticket has a
customer name, issue, priority, and assigned agent. Include filters
by priority and agent, and summary counts at the top.Adapt them to your own paperwork. For an Indian business the stock register often wants a goods-received note against each purchase, and the approval queue may need a GST invoice number on the request. For a US business the same queue might need a purchase-order number and a cost centre. Putting the word in the prompt is how the field gets created.
Settle access before you build
An internal tool nearly always holds data that not everyone should see. Decide before the first build who logs in and what each person can do: who submits, who approves, who sees everything. Say it in the prompt. “Managers approve, employees only see their own requests” changes how the whole app is built.
Real sign-in and shared data need a database, which is on the Builder plan and above. Until then, the tool can run for one person with data saved in their browser, which is fine for a trial and wrong for a team. When you do connect a database, protect it. A tool full of salaries or customer records is exactly what row-level security is for, and the patterns post shows the rules for owner-only and workspace-wide access.
Start smaller than you think
Build the one screen people will open every day and add the rest as changes: a CSV export, an email when a request is approved, colour for urgent tickets. Each is a short message to the builder, and each is a small edit rather than a new build. You will also learn what the team actually uses, which is rarely what the first brief imagined.
It will not replace everything. If a tool needs to plug into a payroll system or an ERP that nobody here can reach, expect that part to need an engineer. The records, screens and approvals around it usually do not.
Describe the tool your team keeps asking for
Pick the one that causes the most spreadsheet pain. Describe it, read the estimate, build it.
Describe your toolHow to write the promptFound something wrong or out of date? Write to hello@wyberai.com and we will fix it and say so here. Rules, fees and rates mentioned in our posts change, and this one was last checked on 18 November 2026.