Use cases

Internal tools: replace a spreadsheet with a real app in an afternoon

Published Updated 6 min read

Read in : Français

Contents
  1. Why replace a spreadsheet with an app?
  2. What companies are already doing
  3. Is your spreadsheet a good candidate?
  4. The 5-step method for one afternoon
  5. 1. Clean and export the spreadsheet (30 minutes)
  6. 2. Write the requirements sheet (20 minutes)
  7. 3. Generate the app with a precise prompt (1 hour)
  8. 4. Import the data and test with a real colleague (1 hour)
  9. 5. Run both side by side for a week
  10. Which tool for an internal tool?
  11. The traps of vibe-coded internal tools
  12. Forgotten access rules
  13. The ghost tool
  14. Personal data
  15. Scope creep
  16. Internal tools worth replacing first
  17. Frequently asked questions
  18. Frequently asked questions
  19. Sources

Internal tools are the most cost-effective place to start vibe coding at work: take a spreadsheet that three people fill in badly and turn it into a small app with forms, access rules and a dashboard. For a simple scope, one afternoon is enough to get a usable first version. Here's the method, the prompt and the limits you should know about.

Why replace a spreadsheet with an app?

A spreadsheet becomes a problem when it's used as a shared database. The symptoms are always the same:

An internal app fixes all five: a form controls input, the database holds one version of the truth, roles limit access, and each user gets their own screen.

What companies are already doing

Two case studies published by the vendors show what's possible, with the caution this kind of source calls for.

These cases illustrate the rule: the best internal tools aren't flashy. They fit a process the team knows by heart.

Is your spreadsheet a good candidate?

Before you start, run your spreadsheet through this grid.

CriterionGood candidateKeep the spreadsheet
People entering data3 or moreJust 1
How often it's usedDaily or weeklyQuarterly
Data structureUniform rows (one row = one customer, order, job)Free-form calculations, what-if scenarios
ConfidentialitySome columns shouldn't be visible to everyoneEveryone can see everything
Entry errorsFrequent and costlyRare

If you mostly tick the left column, an app will save time. If your file is mainly a calculation and modelling tool, the spreadsheet is still the best tool in the world for that.

The 5-step method for one afternoon

1. Clean and export the spreadsheet (30 minutes)

One header row, one row per record, no merged cells, dates in a single format. Export to CSV. If you use Supabase as your database, its documentation says you can import a CSV from the table editor, with a 100MB limit for dashboard imports.

2. Write the requirements sheet (20 minutes)

Who uses the tool, which roles exist, what each role sees and edits, and the 3 screens you can't do without. Our guide to writing a spec your AI builder understands gives the format.

3. Generate the app with a precise prompt (1 hour)

I want to replace a Google Sheets spreadsheet with an internal app.
Here are the CSV columns: [list of columns with their types].
Users and roles:
- Admin: sees and edits everything, manages users.
- Team: creates and edits their own rows, sees their team's rows.
- Read-only: views the dashboard, edits nothing.
Screens:
1. A filterable, sortable list of records.
2. An entry form with validation (required fields, dropdowns
   for [fixed-value columns], enforced date format).
3. A dashboard: [3 specific metrics].
Constraints:
- Email login required, no public sign-up.
- Row Level Security enabled on every table according to the roles above.
- Audit log: who changed what and when.
- CSV export button for admins.
Propose the database schema first, then wait for my approval.

4. Import the data and test with a real colleague (1 hour)

Import the CSV, create one account per role, and ask a colleague to do their usual task without your help. Note every hesitation. For a testing method that doesn't require being a developer, see testing AI-generated code.

5. Run both side by side for a week

Don't delete the spreadsheet on day one. A week in parallel uncovers the forgotten cases: the "notes" column everyone used for something else, the colleague who works on a tablet.

Which tool for an internal tool?

ToolStrengths for internal toolsWatch out for
LovableDatabase, login and roles generated by promptInvited collaborators use the owner's credits
ReplitAgent, database and deployment in one place, documented company useAgent costs over time
BoltVery fast prototype to validate the ideaLess suited to fine-grained permissions
Google AppSheetBuilds an app directly on Google Sheets, with GeminiAppSheet licence needed beyond small teams
Claude Code or CursorCode in your own repo, integrates with existing systemsRequires being able to read code

Google describes AppSheet as a no-code platform whose Gemini assistant can build an app from a description, with Google Sheets as a data source. It's worth considering if your data already lives in Google Workspace and you don't want to move it. For a wider comparison, read our guide to the best vibe coding tools.

The traps of vibe-coded internal tools

Forgotten access rules

"Internal" doesn't mean "protected". An app published at a public URL with a misconfigured database exposes your data to anyone. Supabase's documentation says to enable RLS on every table in an exposed schema, and that once RLS is enabled, no data is accessible through the API with a publishable key until you create policies. Read our article on the Supabase RLS mistake before putting customer data in it.

The ghost tool

The app built by someone who then leaves becomes a tool nobody knows how to change. Document who owns it, where the code lives (a company GitHub repository, not a personal account) and how to export it. Our guide to Git for vibe coders helps set that up.

Personal data

If your spreadsheet holds employee or customer data, GDPR (in the UK and EU) applies to the app just as it did to the spreadsheet. Check where the tool hosts data and collect only what you need. We cover this in GDPR and your vibe-coded app.

Scope creep

The first tool works, everyone wants their feature, and three months later the app is unmanageable. Keep a waiting list and add one feature at a time.

Internal tools worth replacing first

You'll find more ideas in our 25 real vibe coding use cases and in our article on automating your business with small homemade tools.

Frequently asked questions

Frequently asked questions

Can you really replace a spreadsheet with an app in an afternoon?

For a simple spreadsheet with a clean structure and three screens, yes: generation takes an hour, import and testing the rest. What takes longer is the week of parallel use to find forgotten cases. A spreadsheet with dozens of tabs and nested formulas will need several sessions.

Do you need to code to build an internal tool?

Not for a first version with Lovable, Replit or AppSheet. You do need to understand roles and access rules, and how to check that a "read-only" account truly can't edit anything. If the tool touches sensitive data, have someone technical review the database configuration.

Does my data stay in Google Sheets?

It depends on the tool. AppSheet can work directly on Google Sheets. Lovable and Replit usually create a real database and you import your CSV into it, so the spreadsheet becomes an archive. A dedicated database is more reliable for simultaneous access and permissions, but you have to accept a change of habit.

How much does a vibe-coded internal tool cost?

The main cost is the vibe coding tool subscription and the credits used during iterations. Lovable's documentation states that invited collaborators use credits from the project owner's workspace. Compare that cost with the subscription for the off-the-shelf software you're replacing, as Productiv did.

Does an internal tool need the same security as a public app?

Yes, if it's reachable from the internet. An internal app at a public URL is exposed exactly like a consumer app. Mandatory login, no open sign-up, RLS enabled on every table and no secret keys in the front end: the same rules as in our security checklist.

Sources