How to Build an Internal Tool With AI, Step by Step
Describe the workflow, check the first build, add roles, connect your services with your own keys, invite the team and publish. Steps, costs and limits.
You can build a real internal tool with AI by describing your team's workflow in plain words and letting an AI app builder write it as a web app. In Firevibe (we make it), you choose the Website kind, say who does what, and get a working app with its own server, database and email and password sign-in, which you then change by asking in chat. You can build and try it with the free credits; sharing it with your team at a firevibe.dev address needs a paid plan, from $25 a month as of November 2026. Firevibe has no Google Sheets or Microsoft connections and no single sign-on today, so check that before you start.
What is an internal tool?
An internal tool is software your own team uses to run a piece of work, rather than something you sell to customers. Approval queues, admin panels, inventory and order trackers, simple CRMs, onboarding portals and dashboards are the common kinds. Most of them start as a spreadsheet, a shared form and a chat thread where someone asks whether anyone has approved this yet.
An internal tool built with Firevibe is a full web app, not a form on top of a sheet. The code is real React and TypeScript, and every project comes with a backend, a database, sign-in and file storage, built and connected for you. The internal tools page shows the kinds of tools people describe, and if what you need is mostly charts and numbers, the dashboards page covers that case.
How do you know a spreadsheet has stopped being enough?
A spreadsheet has stopped being enough when the work around it matters more than the grid itself. Three signs usually show it:
- People overwrite each other. Two people edit the same row, a formula gets pasted over, and nobody can say which version is right or who changed it.
- Everyone sees everything. Some people should submit, some should approve and only a few should see the totals, and the sharing settings have turned into a workaround.
- The process lives in messages. The status is a cell color, the next step is a reminder someone sends by hand, and the record of who said yes is somewhere in a chat thread.
If none of these is true, keep the spreadsheet. A tool is worth building when the steps, the people and the record of decisions have outgrown rows and columns.
The example in this guide: a purchase approval tool
The example in this guide is made up for illustration, not a customer story. Picture a small company where staff ask to buy equipment and software by adding a row to a shared spreadsheet. Each request has an item, a supplier, an amount and a reason. A manager approves or rejects it, and finance wants a list of everything approved each month.
The tool should replace the sheet, tell the approver when a request is waiting, tell the requester the answer, and keep a record of who approved what and when. Every step below uses this example.
How do you build an internal tool with AI, step by step?
You build an internal tool with Firevibe in six steps:
- Describe the workflow.
- Check the first build.
- Add sign-in and roles.
- Connect the services you already use.
- Invite your team.
- Publish, and add your own domain if you want one.
Step 1: Describe the workflow
Sign up, choose the Website kind, and describe the workflow rather than the screens. Say who uses the tool, what each person does, what the tool must remember, and who can see what. For the purchase approval example, you could type: "A purchase approval tool for our team. Staff sign in and submit a purchase request with the item, the supplier, the amount, a reason and an optional quote file. Managers see the requests waiting for them and approve or reject each one with a comment. Every request keeps a record of who approved or rejected it and when. Finance sees a list of approved requests by month, with a total."
Leave out what you do not know yet, such as colors or rare edge cases. You can add them in chat once the first version exists. The guide on how to write an app prompt goes through what a good first description contains.
Step 2: Check the first build
Firevibe shows a live preview while it builds and gives you a share link. When the first build is ready, walk one request from start to end, the way each person in the workflow would: submit it, approve it, then find it in the finance list. Check that the fields are the ones your team really fills in and that each status means what you expect.
Then change one thing per message. For example: "Add a cost center field to the request form, as a dropdown with Operations, Sales and Product." You can also point at an element on the live preview, such as a column header or a button, and say what should change. One change at a time makes it easy to see what moved.
The tool keeps its records in its own database, not in your spreadsheet. Decide early whether open requests in the old sheet will be finished there or entered again in the tool, so nobody works in both.
Step 3: Add sign-in and roles
Every Firevibe web app comes with its own sign-in, so only people with an account get in. Sign-in is email and password. Ask in chat for the roles you need, for example staff who submit and managers who may approve, and Firevibe builds them into the tool.
For the example, one sentence is enough: "Only managers can approve or reject a request." Then test it from both sides: sign in as someone who should not be able to approve and check that they cannot.
A published tool sits at a public address, and by default anyone who finds it can create an account. Once your team has signed up, ask Firevibe to close public sign-up. Existing accounts keep working, and nobody new can register.
Step 4: Connect the services you already use
Connectors link the tool to services your team already uses, and each one runs on your own account and your own key. You keep your account with the service, add its key to your project, and the connector is on. When you ask for a feature that needs a connector, the agent asks for the key, which is stored encrypted and given only to your app's server.
As of November 2026, the connectors most useful for internal tools are these, each with your own account and key:
- Team messages: Slack, Discord and Telegram.
- Email and texts: Resend, SendGrid and Twilio.
- Data you already keep: Airtable, Notion, Typeform and Zendesk.
- Sales and customers: HubSpot.
- Payments and orders: Stripe, Paddle, PayPal, Square, Shopify and WooCommerce.
The full list is on the connectors page. In the example, two sentences add the notifications: "When a request is submitted, post a message in our purchasing Slack channel with the item and the amount." and "When a request is approved or rejected, email the requester through Resend."
Step 5: Invite your team
An internal tool has two kinds of people around it: collaborators, who change the tool with you in Firevibe, and users, who sign in to the tool to do the work. Collaborators are limited by plan, as of November 2026:
| Plan | Collaborators |
|---|---|
| Free | 1 |
| Starter | Up to 2 per web app |
| Pro | Up to 5, and view-only collaborators |
The people who only use the tool, such as the staff submitting requests and the managers approving them, are not collaborators. They sign in to the tool itself with their own email and password.
Step 6: Publish, and add your own domain
Publishing puts the tool at an address your team can open, and it needs a paid plan. Every paid plan, Starter and up, publishes to a firevibe.dev address. On the Pro plan you can connect a domain you own with a single DNS record, with hosting and SSL included, and Pro allows up to 2 custom domains.
After the tool is live, keep improving it by asking in chat, and publish again to put the latest build on the address. For the purchase approval tool, that might be a new field on the form one week and a second approver for large amounts the next.
Can the internal tool use AI itself?
Yes. Firevibe can build AI features into the tool for text work: summaries, drafted replies, translation, sorting and tagging, and actions that call the app's own functions. It uses models from OpenAI, Anthropic and xAI, and you need no key of your own. What your team uses comes out of your Firevibe credits, under a daily limit you set for each app.
In the example, you could ask: "Under each request, show the approver a one-line summary of the reason." or "Tag each request as hardware, software or services." Built-in AI works with text in and text out: it does not read or make images or audio.
What does an internal tool cost to build and run?
An internal tool costs nothing to build and try, $25 a month or more to share at a firevibe.dev address, and $50 a month or more to run on your own domain, as of November 2026. These are Firevibe's plans, in US dollars:
| Plan | Price | Credits | What it adds for an internal tool |
|---|---|---|---|
| Free | $0 | 200, once | Build and try 1 project |
| Starter | From $25 a month | 2,000 to 8,000 a month | Publishing, reading the code, 2 projects |
| Pro | From $50 a month | 3,000 to 80,000 a month | Your own domain, more collaborators, 5 projects |
| Enterprise | Custom | Custom | Custom |
Credits pay for building and changing the tool, and for any AI features your team uses in it. Bigger, richer apps use more credits, and Firevibe does not publish a credit cost per action. Monthly credits refill every month, and on paid plans you can buy extra credit packs that never expire. Yearly billing charges 10 months for 12: Starter from $250 a year and Pro from $500 a year.
Connected services bill you separately, on your own account with each of them. The pricing page has every tier, and how much it costs to build an app with AI covers the whole bill.
When should you not build an internal tool this way?
Do not build the tool in Firevibe if it depends on a service Firevibe cannot connect to. Google Sheets, Gmail, Microsoft services and single sign-on are not available in Firevibe today. In detail, as of November 2026:
- Google services. There is no connector for Google Sheets, Gmail, Google Drive or Google Calendar. If the tool has to read or write a sheet your team keeps using, Firevibe cannot do that yet.
- Microsoft services. There is no connector for Outlook, Microsoft Teams, OneDrive or SharePoint.
- Single sign-on. A Firevibe web app signs people in with email and password. If your company requires every tool to sign in through its single sign-on, that rules Firevibe out today.
- Other missing connectors. Salesforce, DocuSign and Zapier are not available either.
- Code you must take with you. On paid plans you can read the full source code in the workspace, but you cannot download it, export it or push it to GitHub. If engineering must host the tool on your own servers later, choose another route.
- A product that already fits. If an existing product does the job with little change, buying it is often simpler than building and looking after your own tool.
If you are weighing builders in general, do AI app builders give you a real backend? lists the questions to ask any of them, with Firevibe's answers.
If none of those limits applies to you, the quickest test is to describe the workflow your team runs today and walk one record through the first build. Sign up for Firevibe free, choose Website, and describe your tool.
Frequently asked questions
Can I build an internal tool with AI without an engineer? Yes. In Firevibe you describe the workflow in plain words and it writes a web app with its own server, database and email and password sign-in. You change the tool the same way, by asking in chat.
Can a Firevibe internal tool connect to Google Sheets or Microsoft services? Not today. As of November 2026, Google Sheets, Gmail, Google Drive, Outlook, Microsoft Teams, OneDrive, SharePoint and single sign-on are not available in Firevibe. Sign-in to a Firevibe web app is email and password.
Which services can a Firevibe internal tool connect to? As of November 2026, Firevibe connectors include Slack, Discord, Telegram, Resend, SendGrid, Twilio, Airtable, Notion, Typeform, Zendesk, HubSpot and Stripe, among others. Each connector uses your own account with that service and your own key.
How many people can work on a Firevibe internal tool with me? As of November 2026, the Free plan allows 1 collaborator, Starter up to 2 per web app and Pro up to 5, and view-only collaborators need Pro. The people who only use the tool sign in to it with their own email and password.
What does it cost to build and share an internal tool with Firevibe? You can build and try a tool with the 200 free credits you get once. Publishing it to a firevibe.dev address needs a paid plan, from $25 a month on Starter, and your own domain needs Pro, from $50 a month, as of November 2026.
Can I download the code of an internal tool built with Firevibe? No. On paid plans you can read the full source code of a Firevibe web app in the workspace, but downloading it, exporting it or pushing it to GitHub is not available.
