What counts as an internal tool
If its users are employees and it supports a process the company runs, it is an internal tool. Most fall into a handful of types. Each row names a SpringRoll example you can open now, with fictional records.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Type | What it does | Example to try |
|---|---|---|
| Approval and request apps | Someone asks, a named person decides, and the decision is recorded | Purchase Desk |
| Review desks | A specialist checks terms or content before work continues | Deal Desk, Campaign Room |
| Work queues | A team sees what is waiting, takes an item and passes it on | Operations Queue, Support Room |
| Dashboards | A lead sees which area needs attention and why | Operations dashboard |
| Shared team apps | Each person signs in as themselves and sees only what their role allows | Purchase Desk Team |
| Admin panels | Staff look up and correct records in a company system | No SpringRoll example yet; the rollout steps below are the same |
Seven internal tools you can try now
Every example runs in your browser with invented people and records. You can download the source without an account, open it in your coding agent and change it into the tool you need.
Three ways to build internal tools
The choice is less about features than about who builds, where the result lives and what you own afterwards.
SpringRoll belongs to the middle row. It is not a builder: your coding agent writes the app. SpringRoll deploys it, lists it in the App Portal and records its owner, audience, approvals and data access.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Route | Who builds | Where it runs | What you still have to solve |
|---|---|---|---|
| Low-code builder, such as Retool, Superblocks, Appsmith, Budibase or ToolJet | Someone assembling screens in the vendor’s editor | On the vendor’s platform, or a copy you host | Licences for builders and users, and tools that live inside that platform |
| Coding agent, such as Claude Code, Codex or Cursor, with SpringRoll | Anyone who can describe the workflow to an agent | On managed Vercel or Cloudflare, placed by SpringRoll | Reviewing what the agent wrote, and keeping an owner on each tool |
| In-house engineering | Your developers | On infrastructure you run | Hosting, sign-in, access, audit and maintenance, for every tool |
When another route is the better choice
SpringRoll is not the answer to every internal tool. Choose something else in these cases.
- Your builders want a visual editor and nobody is comfortable reading what a coding agent produced. A low-code builder fits better.
- The need is standard, such as payroll, a help desk or a CRM. Buy the product made for it.
- The tool is for customers or the public. SpringRoll is for apps your own people open.
- You want a platform that also designs and writes the app. SpringRoll does not build apps; your coding agent does.
Roll out your first internal tool
Pick one team and one workflow. Start from an example with fictional records, so the first rollout tests the handoff and not your data.
- Connect your coding agent to SpringRoll. You can start as a guest without a SpringRoll account.
- Download an example, or open the project your agent already built.
- Ask the agent to deploy it through SpringRoll, using the prompt below. Review the placement preview and the proposal, then confirm.
- Follow the build to READY and complete the tool’s main task yourself.
- Choose the audience. Ask one colleague inside it and one outside it to open the tool from the App Portal.
- Name the owner and the support contact, and write down who to tell when the tool needs a change.
Use SpringRoll to deploy this project. Show me the placement preview and the deployment proposal first, then follow the build until it is READY.How SpringRoll helps you build and run internal tools
A coding agent can produce a working purchase approval app in one sitting. SpringRoll covers the rest: it gives the agent your company’s rules while it builds, then runs the finished tool for your team.
One limit to know: the App Portal controls who can find and launch a tool. The tool’s own provider address is separate, so a tool holding real records must check sign-in itself. The Purchase Desk Team example does, and its access test results are published.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Stage | What SpringRoll does |
|---|---|
| Build | Your coding agent reads your Company Blueprint: the guidance, approved patterns and supported frameworks an administrator published. It can start from an example’s source, and SpringRoll runs your configured security checks on the release |
| Deploy | The agent deploys through one connection to managed Vercel or Cloudflare. A placement receipt names the provider, plan and estimated cost before you confirm, and nobody on your team needs a provider account |
| Share | The tool appears in the App Portal for the audience you choose: people, groups or the whole workspace. Every tool shows its owner and support contact |
| Use company data | The app owner requests specific fields for one app and one environment, and a data owner approves them. The tool never holds the source credential, and nobody can approve their own request |
| Change and maintain | Each update is a recorded release. On the Staged workflow a named person approves it before Production, and an agent cannot approve its own request |
Frequently asked questions
What are internal tools?
Software a company builds for its own staff, to run a process such as approvals, reviews, queues or reporting. Customers never see them.
What are some examples of internal tools?
A purchase request and approval app, a deal review desk, a support queue, a campaign review board and an operations dashboard. SpringRoll publishes a working example of each that you can open and download.
Is an internal tool the same as an internal app or a business app?
In practice, yes. The terms overlap, along with admin tool and back-office tool. They all mean software for employees, not customers.
Can you build internal tools with Claude Code, Codex or Cursor?
Yes. A coding agent can build a working internal tool from a description. You still need somewhere to run it, an owner, and a way to choose who can open it.
Is SpringRoll an internal tool builder?
No. Your coding agent builds the tool. SpringRoll deploys it, lists it in the App Portal, and records its owner, audience, approvals and data access.
Do I need an account to try this?
No. The examples open without an account, their source downloads without one, and you can connect an agent to SpringRoll as a guest.
