Smartsheet

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Do not build this if you are in a large organisation. Audit trails and enterprise habits are the product.

What is being bought is not the grid. It is that the tool passes procurement, that every change is attributable, that permissions satisfy an auditor, and that people who have used it for a decade do not have to learn anything. None of that is code, and all of it is why it is chosen.

WHEN TO KEEP PAYING
- Compliance requirements, or an audit that will ask who changed what
- Colleagues who will not adopt a new tool, which is a real constraint rather than an excuse

WHEN TO BUILD
- A team that controls its own tooling and wants the model to fit. Then the shape is under Airtable and Baserow elsewhere in this catalogue

WHAT TO TAKE WHATEVER YOU DECIDE

**An append-only revision log**: every field change with the old value, the new value, the actor and the timestamp, enforced by a trigger so it cannot be edited. That single table is most of what an audit trail means, it costs an afternoon, and it cannot be reconstructed after the fact

**Real columns with real constraints**, not a generic key-value store. Types, required fields, uniqueness and foreign keys enforced by the database. A spreadsheet-shaped tool without constraints accumulates a column where nine hundred rows are dates and forty are the word 'pending'

**Permissions checked inside the query**, per row and per field, with a forbidden field absent from the response rather than hidden in the interface. Default deny

AND THE MIGRATION QUESTION TO ASK EARLY
Export everything and look at what actually comes out: formulas, attachments, comments, the change history and the permission structure. History and attachments are the two most often thinner than expected, and if the audit trail does not export, it never really belonged to you.

THE ONE-LINE VERSION
The habits and the audit trail are the product. If you build, make the revision log the first table.