Which internal tools you can build with AI today, and which need shared data
Internal tools fall into two groups. Some are personal utilities that happen to be used by staff: a pricing calculator, a pre-shift checklist, a label generator. Others are shared systems: a stock list everyone edits, an approvals queue. Anticode builds the first kind today, as apps that run in each person's browser. The second kind needs logins and a shared database, so it's a prototype here and a project elsewhere.
The test: does anyone else need to see what I entered?
Ask that question of any internal tool idea. If the answer is no, because the tool takes inputs, does something useful with them and gives a result to the person using it, it can run entirely in one browser. If the answer is yes, because a colleague, a manager or tomorrow's shift needs to see the data, the tool needs a server, accounts and a shared database.
| Works on one device today | Needs shared data |
|---|---|
| Pricing or margin calculator for sales staff | Stock or inventory everyone updates |
| Opening and closing checklist on a shop tablet | Holiday requests with manager approval |
| Email signature, label or quote text generator | Shared customer records |
| Training quiz or reference guide | Rotas and shift swaps |
| Measurement or unit converter for the workshop | Incident or fault log reviewed by others |
| Decision helper for a support team's triage | Dashboards over live business data |
Building the one-device kind
These tools are often the most-used software in a small business, and they're usually trapped in a spreadsheet only one person understands. Describe the job, the inputs and the output, and who uses it where: "A margin calculator for our counter staff on a tablet. Inputs: supplier cost, quantity, discount percentage. Show sell price at our standard 35% margin, the margin after discount in red if it drops below 20%, and a copyable quote line. Big buttons, no scrolling."
The model writes it as one app that runs in the browser. Per-device state, such as a checklist ticked off this morning or a tablet's last settings, can be saved in that browser, which is exactly right for a shop-floor device that stays in one place. Publish it and bookmark it, or install it on the tablet's home screen like an app. Because the logic is just code in the page, keep it to rules you'd be comfortable any member of staff reading.
When a form is enough to share
Some tools that seem to need shared data really need only a report back to one person. A checklist that ends with "submit today's close" can send the completed list through Anticode's form pipeline: it arrives by email and in the dashboard, and connectors can append it to a Google Sheet, an Airtable base or a Slack channel. That gives a manager a running log without a database inside the app. It works for reports going one way; it doesn't let staff see or edit each other's entries.
The shared-data kind: prototype, then decide
For tools in the right-hand column, an Anticode build is a single-device prototype. It's still useful: you can design the stock screen or the approvals queue with sample data, put it in front of the people who'll use it, and settle the fields and states before anyone writes backend code. Each browser keeps its own copy of the data, so don't run real operations on it.
When the design is agreed, there are two realistic routes.
- Next.js export
- Exports the app as a TypeScript project with Postgres through Prisma, email sign-in, customer and staff roles, an audit log, row-level security and an admin area with two-factor sign-in. A developer adds the tool's shared tables and screens on top, and you host it yourself, for example on Vercel with a Neon or Supabase database.
- An internal-tools platform
- Products built for internal apps connect to your existing databases and spreadsheets and come with permissions and hosting. They suit teams that would rather configure than code, and they're often the faster path when the data already lives in another system.
The prototype an internal tool workflow walks through agreeing a design with staff before choosing a route.
Limits to keep in mind
- No connection to your systems. The app can't read your database, accounting software, spreadsheets or APIs, because it has no network.
- No logins. Anyone with the link can open a published tool, so don't put confidential figures, staff data or customer details into its code.
- No audit trail of who used it, beyond page views and any forms submitted.
- Per-device data. Two tablets running the same checklist don't know about each other.
Questions people ask
Is Anticode a full AI internal tool builder like the dedicated platforms?
For single-device utilities, it builds complete, working tools. For tools with shared data and permissions, it builds prototypes; the dedicated platforms or the Next.js export cover the real thing.
Can I keep a published internal tool private?
Published sites are public at their address. Keep anything sensitive out of the tool itself, and use it for calculations and checklists that are fine for anyone to see.
Can staff install it on work tablets?
Yes. Every published site can be installed as an app with its own icon, and it remembers that device's saved state.