Use case · Replacing spreadsheets
Your spreadsheet became a process. Give it an app.
When a spreadsheet gets emailed around, approved in the comments and fixed by one person who knows the formulas, it's time. Describe it in a chat with Claude, and your team gets a proper app.
Back in control
No longer dependent on the colleague who built it
Every team has one: the spreadsheet only one person really understands. Then that person changes jobs, and nobody dares to touch the formulas anymore.
- ✓Anyone on the team can change the app, by describing it in a chat
- ✓Every change is saved, so you can see what changed and when, and go back
- ✓It belongs to your organisation, not to one person's laptop or account
- ✓IT can see it and take it over if it becomes critical
What you gain
The same information, but now it works like a process instead of a file. Claude adds each of these when you ask for it.
One version for everyone
No more “which file is the latest?”. Everyone works in the same place, and changes show up for the whole team straight away.
Approvals with a record
An approve button instead of a comment, and you can always see who approved what, and when.
The right people see the right things
Colleagues see and change only their part. Managers see the overview. Nobody overwrites someone else's work.
Works on a phone
Request a day off or fill in a checklist from anywhere, without opening a file on a laptop.
Rules that don't break
No more broken formulas or half-filled rows. The app checks the input, so the data stays clean.
It tells people what to do
A message in Teams or an email when something needs approval, instead of someone chasing it.
The overview, at a glance
Totals, who's away, what's waiting: the numbers you used to build by hand are always up to date.
Easy to share and extend
A new colleague, a new team or a new step in the process: describe the change and it's there for everyone.
Spreadsheets that should be apps
Recognise one of these? That's where to start.
From Leave_overview.xlsx
→ Leave planner
Requests, approvals and who's away, in one view.
From Stock_count_week41.xlsx
→ Stock tracker
Counts per location, with alerts when something runs low.
From Hours_project_X_v7.xlsx
→ Project hours
People log their hours, managers see the totals per project.
From Onboarding_checklist.xlsx
→ Client onboarding tracker
Every new client, which step they're at, and who's on it.
From Suppliers_master.xlsx
→ Supplier list
One list everyone works from, with contracts attached.
From Inspection_rounds.xlsx
→ Inspection checklist
Fill it in on a phone, see the results in one overview.
From spreadsheet to app in four steps
1
Share what you have
Tell Claude what the spreadsheet is for, or share it in the chat as the starting point.
2
Describe how it should work
Who fills it in, who approves, who may see what.
3
Try it with your team
Nothing goes live until you say so.
4
Retire the spreadsheet
When the app does the job, the spreadsheet can go.
Questions
“Can I keep using Excel for analysis?”
Yes. This is for the spreadsheet that became a process, not for the one you use to crunch numbers. If someone still needs the data in a spreadsheet, ask Claude to add an export.
“What happens to the data that's already in the spreadsheet?”
Share the spreadsheet in your chat with Claude and ask it to use that data as the starting point. Check the result with your team before you switch over.
“Do I need to know how to code?”
No. You describe how it should work in a chat with Claude. You need a Claude account and a GitHub account, but you don't need to know anything about GitHub itself.
Get your spot in the beta.
We open spots from the waitlist, oldest first. When yours opens, the free tier is a real environment with a real URL. No card.
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.