Building Internal Tools for Your Team with Vibe Coding
Which tasks make good internal tools, and how to design flows, roles and audit logs that last, with a warehouse team example from Chonburi.
Every company has at least one Excel file the whole team fears: five people editing it at once, formulas breaking every month-end, and only one person who knows what each tab is for. Meanwhile approvals run through chat until nobody can find the original message. Problems like these are too small to justify buying a big system, but big enough to eat the team's time every week. That is exactly where vibe coding helps most.
What is an internal tool?
An internal tool is software built for people inside an organisation, not sold to customers: a supplies request form, a task status tracker, a sales summary dashboard, or a customer lookup tool for the sales team. What makes them special is a limited number of users who know each other and can give feedback immediately, which suits fast-iterating vibe coding well.
Which tasks make good internal tools
- Spreadsheets used as databases: many people entering data and needing different permissions
- Approval flows: supply requests, leave, discount approvals that currently run through chat or email
- Repetitive lookups: the team opens several systems to answer one question
- Weekly manual reports: copying numbers from several places into one
What you should not start with vibe coding: core accounting, payroll, or tightly regulated systems. Those call for purpose-built software.
Designing internal tools that last
1. Start with the flow, not the screens
Write out how the work moves: who starts it, who approves, who gets notified, what statuses exist. Then have the AI build screens that follow that flow.
2. Roles and permissions
Internal tools usually have at least three roles: requester, approver and administrator. Be clear about what each role can see and edit, and restrict login to company email addresses.
3. Audit log
Record who did what and when, such as who approved or who changed a number. Spreadsheets struggle with this, but it matters a lot when there is a dispute.
4. Connect to existing data
If the master data lives in another system, display it instead of re-entering it. Start read-only. Writing back to the main system should come only after thorough testing.
5. Works where the work happens
Many internal tool users do not sit at a computer: technicians, warehouse staff, field sales. Ask the AI to make the main screens comfortable on mobile, with big enough buttons and only a few steps to fill in.
Example: a distributor's warehouse team in Chonburi
A warehouse supervisor receives spare-part requests in a group chat and has to log them in Excel herself every evening. With vibe coding she builds a site where technicians submit requests with part codes and quantities. She sees pending requests, approves them, and stock decreases automatically, with every action logged with name and time. She first opens it only to the morning shift for two weeks and learns that technicians want to search parts by the nicknames used on the factory floor, so she adds an alternative-name field. After that the whole warehouse stops using chat for requests, and she has more time for stock planning.
A good internal tool does not need to be the prettiest. It needs to make repetitive work disappear from the team's day.
Things to watch out for
- Shadow IT: tell IT or your data owner before starting, and check which AI tools company policy allows with internal data
- Employee and customer data: falls under the PDPA. Collect only what you need and restrict access
- Secrets: keys for connecting other systems must stay on the backend with the lowest permissions that still work
- Single maintainer: if the builder leaves, who takes over? Write short documentation and have at least one backup maintainer
How to get started
- Ask your team which repetitive task eats the most time each week, and pick one
- Write the flow, roles and permissions in plain language
- Build a first version with test data and let a small group of real users try it first
- Get input from IT and plan maintenance before rolling out to the whole team
For a guided, step-by-step internal tool project, try the course Build a stock management app with Lovable on Plants.work, and read more about automating repetitive workflows in AI Workflow Automation.