In short
This Bolt internal tool template covers the dashboards teams build most often: a team directory, a sales pipeline, a companies table, expense tracking, a feedback inbox and a content calendar, plus login and team settings. Pick the screens your team needs, paste them into Bolt with Supabase connected, and replace a pile of spreadsheets with one tool that looks professional.
Who this internal tool template is for
It is also a fast way to prove value before a bigger build. A working tool used by the team for a month tells you exactly which features matter before anyone commits to months of engineering.
Operations, sales and support teams who live in spreadsheets and shared docs, and the founders or developers asked to build them something better without a big project.
Internal tools rarely get design time, which is why most look like database admin panels. Starting from these templates gives your team a tool they actually enjoy using, and adoption is what decides whether an internal tool works.
What each key screen must get right
Tables
Fast search, filters that match how the team thinks, and sensible default sorting.
Boards
Drag and drop that saves instantly and a clear owner on every card.
Permissions
Roles that limit who can see and edit sensitive data like expenses.
Empty states
Clear guidance the first time someone opens a screen with no data.
Internal tool screens, one by one
1. Login
Sign in restricted to your company, with your logo. It sets the tone that this is a real product, not a shared spreadsheet.
2. Team directory
Everyone in the company with role, team, location and contact details, searchable and filterable. A simple screen people open every day.
3. Sales pipeline
Deals as cards across stages with value and owner, dragged between columns. It replaces the pipeline spreadsheet everyone edits differently.
4. Companies
Accounts in a fast, filterable table with owner, status and last activity, opening into the company's details.
5. Expenses
Expenses by category and month with approval status, so finance sees spending and submitters see where their claims are.
6. Feedback inbox
Customer feedback from every channel in one inbox, tagged, assigned and tracked to done.
7. Content calendar
Planned content by date, channel and status, so marketing knows what ships this week.
8. Team settings
Who has access, with roles and invites, so you can open the tool to the whole company safely.
How to build this internal tool in Bolt
Login and roles first
Paste the build prompt with the login template and connect Supabase with sign in restricted to your domain.
One painful spreadsheet
Build the screen that replaces the spreadsheet your team hates most, and import its data.
Add the next screens
Add directory, pipeline, expenses, feedback or calendar screens as the team needs them.
Permissions and polish
Finish with team settings, roles and row level security, then invite the team.
Supabase tables
The data a internal tool needs. Connect Supabase from Bolt's integrations and Bolt creates these for you.
peopleName, role, team, email, start date.dealsCompany, value, stage, owner.expensesAmount, category, submitter, status, receipt link.feedbackSource, text, tags, assignee, status.content_itemsTitle, channel, owner, publish date, status.Bolt internal tool template build prompt
The full Bolt prompt for this internal tool: build order, Supabase tables, row level security, auth and design rules, ready to paste.
Bolt build prompt: Internal toolBuild a internal tool called [product name] for [audience]. Use React, Vite and Tailwind CSS, and connect Supabase from Bolt for any data. DESIGN I will paste a BrowserMoon template for each screen. Match every template exactly: fonts, spacing, colours, corner radius and components. All screens must look like one product. Every screen works at 375px wide with no horizontal scroll.
Common mistakes and how to avoid them
Building everything at once
Start with the one screen that replaces the most painful spreadsheet.
No owner fields
Every record needs an owner, or nobody acts on it.
Open access to everything
Use roles and row level security from day one.
Ignoring imports
Ask Bolt for a CSV import so the team can move existing data in.
How to grow your internal tool after launch
Once the team uses it daily, add automations: reminders for stalled deals, a weekly summary of expenses waiting for approval, and alerts when new feedback is tagged urgent.
Add a simple activity log so people can see who changed what. It settles disagreements and makes the tool trustworthy enough to replace the old process completely.
Internal tool launch checklist
- Only people with your company email can sign in.
- Sensitive tables like expenses are limited by role.
- Existing spreadsheet data imported without duplicates.
- Every table loads fast with real data volumes.
- Every record shows an owner and a last updated date.
- The team has been shown the tool and the old spreadsheet is archived.
Frequently asked questions
Can Bolt build internal tools?
Yes. With Supabase connected, Bolt builds working dashboards with sign in, tables and forms.
Do I have to build all the screens?
No. Pick the screens your team needs; they share one design, so you can add more later.
Can I restrict access to my company?
Yes. Allow sign in only for your email domain and use row level security for sensitive tables.
Is this better than a spreadsheet?
For anything with owners, statuses and history, yes: fewer copy mistakes, permissions per person and a clear view for everyone.
Who should own an internal tool after it is built?
Name one owner on the team that uses it most. They collect requests, decide what comes next and keep the data clean.
Can I connect it to tools we already use?
Yes. Bolt can call other tools' APIs from server functions, for example to pull deals from a CRM or post updates to a chat tool.
Is an internal tool built with Bolt secure?
It can be: restrict sign in to your domain, use roles and row level security, and keep API keys on the server.
Bolt templates by category
More Bolt starter templates