Guides
How to build an internal tool with AI
Approval flows, request forms, admin panels and dashboards. Learn how to describe an internal tool so Kuika AI builds it with the right roles, data and screens.
Kuika AI team4 min read
To build an internal tool with AI, describe the job the tool does, the people who use it and the rules it must follow. Kuika AI turns that description into a working web app with forms, lists, approvals, its own database and role-based access. You review a plan first, then watch the app being built, then refine it by chat or by clicking on the screen.
What counts as an internal tool
Internal tools are the small apps that keep a company running. They rarely get a developer's time, so they often live in spreadsheets and email threads. Typical examples:
- Purchase, leave or expense requests with approvals
- Asset and equipment tracking
- Onboarding checklists for new hires
- A simple admin panel over a list of customers, orders or tickets
- A dashboard that pulls the week's numbers into one place
If you can explain the process to a new colleague in two minutes, you can describe it to Kuika AI.
Describe the process, not the screens
The best prompts for internal tools focus on the process. Say who starts it, who decides, what happens next and what has to be recorded. Kuika AI works out the screens from that.
A useful pattern is: who does what, then what happens, and who sees the result. Add any numbers that matter, such as an approval limit, and any rules, such as "a rejection needs a reason".
Build an internal purchase request app. Employees request an item with quantity, estimated cost and a reason. The request goes to their department head, and to the general manager when the cost is above 5,000 USD. An approved request becomes a purchase order with a chosen supplier and closes when the goods arrive. Show the approval history of every request.
Step by step
- Write the process in the prompt box on the Kuika AI home page and choose Web.
- Leave Plan mode on. Kuika AI asks a few quick decisions, such as whether rejected requests can be resubmitted. Answer them or let Kuika AI decide.
- Check the roles in the plan. An approval tool lives or dies by who can do what. Make sure the plan lists each role you expect, for example employee, department head and general manager.
- Create the app. Kuika AI builds it and fixes build errors on its own while it works.
- Walk through the flow as each person. Use Preview as in the preview tools to switch between roles. Submit a request as an employee, then approve it as a department head.
- Refine by chat. Ask for what is missing in plain words, one change at a time.
Make the data useful
Every app Kuika AI builds has its own database. Open the Database view to see the tables, edit rows, and import or export CSV files. Sample data is filled in for you, so the screens make sense from the first minute. If you need a certain volume to test with, say so in your prompt, for example "fill it with 40 requests across 5 departments".
Lists in Kuika AI apps come with useful table features: choosing columns, filtering per column, search, pagination and selecting several rows. Ask for them when you need them.
Automate the boring parts
Internal tools save the most time when they do the reminding for you. Kuika AI apps can send their own email and run jobs on a schedule. Describe what you want in the chat:
Every weekday at 8:30, email each department head a list of requests waiting for their approval for more than two days. On the first day of each month, export last month's approved purchase orders to a CSV.
You can see and manage these jobs later under More › Scheduled jobs, and set up how the app sends email under More › Email.
Need a printable document?
Many internal processes end in a document: a purchase order, a delivery note, a label. Kuika AI has a report designer for PDF documents with page headers and footers, tables and charts. Open the Reports view and describe the document you need, or build it there.
Roll it out
When the flow works in the preview, publish the app to the Test environment from the Publish menu. Test has its own address and a shared database, so everyone works on the same requests. Before you publish, run the security scan in the same menu. It looks for common problems and can fix several of them at once.
Common questions
What kinds of internal tools can I build with Kuika AI?
Approval flows, request forms, trackers, admin panels, dashboards and checklists are the most common. If the tool is mostly forms, lists, rules and roles around your own data, it is a good fit.
Can different people see different screens?
Yes. Describe the roles in your prompt and Kuika AI sets them up. You can adjust them under More › Users & access and check each one with Preview as.
Can the tool send reminders on its own?
Yes. Ask for scheduled jobs and email in the chat, for example a daily reminder at 9:00. Kuika AI writes the job, and you can run it by hand or change it later.