# Spreadsheets > The tool people reach for anyway, built into the platform - so a plan sketched in a grid is connected to the data model, the process and the org structure instead of living in a file Source: https://aipril.dev/docs/spreadsheets ## Why a spreadsheet is in here at all Because people reach for one anyway. Ask a team to sketch a plan, size an idea, work out what the number would be under three different assumptions, or capture something there is no system for yet - and they open a spreadsheet. Not because they are avoiding the proper tool, but because for that kind of work the grid *is* the proper tool. It is faster than any form. There is nothing to design first. You can put a rough column in, change your mind, and delete it, and the tool does not object. And half the working population already knows the formulas. A platform that ignores this does not stop the behaviour. It moves it somewhere it cannot see: a file on somebody's laptop, a shared drive, a Google Sheet a whole department depends on and nobody owns. ## What usually happens next The spreadsheet works - and then it has to meet the rest of the company. The plan needs the actual employee names, so somebody pastes them in, and they go stale. The numbers need to reach a report, so somebody exports and uploads, weekly, by hand. The rows need approving, so they get copied into a ticket. Two people edit the file at once and one of them wins. Nobody can tell which version the meeting is looking at. The usual answer is a chain of transfers: a sheet feeding a script feeding a database feeding a dashboard, held together by somebody who remembers how it works. It is not that the spreadsheet was the wrong tool - it is that it had no way to be connected to anything. ## What is different here The grid is the same. What changed is what a cell is allowed to be, and where the contents go. - **The formulas people already know work** - the same function library, so nobody has to relearn what they could already do. - **A cell can be a real reference** and not typed text: an employee from the org structure, a position, a legal entity, a value from a dictionary, a row from a dataset, a task in a process, a linked record, an attachment. - **What is entered becomes data**, immediately: queryable by [analytics](https://aipril.dev/docs/analytics.md), readable by a [process](https://aipril.dev/docs/processes.md), usable by an automation - without an export step and without a nightly job. - **A workbook can ship as part of an application**, versioned with everything else, so "the planning sheet" is a defined thing rather than a file that was once attached to an email. The result is that a whole category of awkward plumbing stops being necessary. The spreadsheet is not a thing to get data out of any more; it is one of the places data lives. ## Everyone in the same sheet, at once A plan is almost never written by one person, and a shared grid is only as good as what happens when two of them are in it at once. **Several people edit the same sheet at the same time.** You can see who else is in it, and their changes appear as they are made. There is no file to send, no copy to reconcile, no question about which version the meeting is looking at, and no save that silently overwrites what somebody else just typed. **The discussion sits on the numbers.** A [comment](https://aipril.dev/docs/collab.md) attaches to a cell or a range, so a question about one figure lives on that figure instead of in a message thread somewhere else. `@`-mention someone and it reaches them through their own channel - email, Telegram, Slack - with an inbox of what is waiting for them, instead of depending on their having the right screen open. **A thread is a record, not a chat.** Reactions, quoting and replying, edit history, attachments, and resolve-and-reopen. Six months later, "why is this row 40 and not 35" has an answer that is not somebody's memory of a conversation in a messenger. That is the part people underestimate until they have it. Most of the cost of a shared spreadsheet was never the typing - it was the reconciling, the asking, and the remembering. ## Where to go next - [What you can do](https://aipril.dev/docs/spreadsheets/what-you-can-do.md) - the grid itself: formulas, column types, collaboration, and working with a sheet day to day. - [Beyond Excel and Google Sheets](https://aipril.dev/docs/spreadsheets/beyond-excel.md) - a straight comparison with the tools people use today, and the two sheets you cannot build in Google Sheets. - [AI in spreadsheets](https://aipril.dev/docs/spreadsheets/ai.md) - the assistant builds the model itself: the sheets, the links and the formulas, arriving with its approval route attached. - [Connected to the rest](https://aipril.dev/docs/spreadsheets/connected.md) - what changes when the sheet is wired to the data model, the processes and the org structure, and which round-trips it removes. - [Under the hood](https://aipril.dev/docs/spreadsheets/under-the-hood.md) - how simultaneous editing is kept consistent, how rows become queryable data, and how a shared formula is stopped from becoming an attack.