The spreadsheet isn't the problem. It's the prototype.
It proved what the business needs to track. It just can't run the part that happens after someone types a row — and that's the part that starts costing you when the team grows.
Same data. One version. Everyone's view.
Bring the sheet in as it is. What it gains is everything a file can't hold: a real owner per record, permissions per person, and a history of what changed.
- Each record has an owner, a status and a next step
- Give staff, contractors and clients only what they should see
- Comments, files and tasks stay on the record they belong to
- Full change history — no more “who edited this?”
- Table, board, calendar and report views over the same data
The work moves without anyone chasing it
A spreadsheet waits. A system acts. Set the rule once and the follow-up, the handoff and the reminder happen whether or not anyone remembered.
- Chase the overdue invoice automatically
- Assign the new job to whoever is next
- Warn you a fortnight before the certificate expires
- Email the customer when their status changes
- Escalate anything sitting untouched too long
A spreadsheet can't talk to anyone. This can.
Data only ever enters a sheet when a human types or pastes it, and nothing leaves until a human sends it. Sharing a file decides who can look at the box — it doesn't let the box do anything.
- Put a form on your own website that files straight into a table
- Send email out automatically, and log the replies against the record
- Let customers and suppliers update their own details, safely
- Connect to the systems you already run, by API or webhook
- Give your AI assistant real access to real business data
Inviting the rest of the team shouldn't be the expensive part
Most tools charge you more precisely at the moment the system starts working — when everybody needs to be in it. We don't.
Start with the one sheet that's hurting
Not a migration project. One process, working properly, this week — then the next one when it's ready.
Bring the sheet
Import the spreadsheet you already have, or install a template and start from it.
Add what it was missing
Owners, statuses, permissions, a form for intake, and the views each person needs.
Let it run
Turn the reminders and handoffs you do by hand into rules that fire on their own.
Or don't build it yourself — send us the sheet
Share the spreadsheet that runs your work today and we'll build the first working version for you: your data as proper tables, the views your team actually works from, an intake form, and a couple of automations.
Worth being honest about
InfoLobby suits a real, repeated process that several people touch. It is not the answer to everything.
A good fit if
- A spreadsheet or inbox is running something the business depends on
- More than one person needs it, with different levels of access
- Things get missed because nobody is reminded
- Your process doesn't match what off-the-shelf software assumes
- You want to change it yourself when the business changes
Not a good fit if
- You want a personal to-do list or a one-off calculation
- You need heavy spreadsheet modelling, pivots and formulas
- You want a deep vertical suite with every industry feature pre-built
- You want a full sales CRM with dialers and lead enrichment
- Nobody on your side wants to shape the process at all
Common questions
Do we have to give up spreadsheets?
No. Keep them for what they're good at — modelling, analysis, one-off working. Move the process that other people depend on, and export back out whenever you want.
How long does this take to set up?
Importing a sheet and getting a working table takes minutes. Adding owners, a form and your first automation is usually an afternoon. Start with one process, not all of them.
Is this just Airtable or a database?
There is a real database underneath, but the point is the operating layer on top: permissions, automation, forms, email, comments, tasks and an API — without per-user pricing.
Do we need someone technical?
Not for daily use, and not to build most of it. When you do hit something unusual, there's a scripting layer and a full API rather than a feature request.
What if our process is unusual?
That's the normal case here. You define the tables, fields, stages and rules — and change them later without waiting on a vendor roadmap.
Can people use it on their phone?
Yes. Records, comments, tasks and notifications all work on mobile, so the person out on a job can update the thing rather than text someone to do it.
Start with the sheet that's causing the most trouble
See what it looks like when it can remind, assign and chase on its own. Or have a look round the app first — no signup needed.
14-day free trial. No credit card required.