SMF·SMARTSUITE
Can a prompt replace SmartSuite?
Databases — spreadsheet databases and operational data apps
Exhibit tracking slip
Verdict
SmartSuite positions itself as work management rather than a spreadsheet, and the difference that matters is that a record moves through a process: states, allowed transitions, fields required before a transition is permitted. Implementing that as a real state machine — rather than a status dropdown anyone can set to anything — is a genuinely different build from the other database tools here, and enforcing it in the API and the import path as well as the interface is where the fortnight goes.
Exhibit A — The prompt
Received on31.07.2026Build a records application where each table carries an enforced status workflow.
Schema: tables with fields typed as text, long text, number, date, boolean, single select, multi select, user, attachment, and link to another table with lookups and rollups.
The workflow, which is the point of this build. Per table, define:
- A set of states, ordered, each with a colour and a category (open, in progress, done, cancelled).
- Allowed transitions as explicit pairs — from state A to state B. Anything not listed is forbidden. A status field where any value can be set from any other is a dropdown, not a process.
- Per transition: fields that must be non-empty before it is permitted, an optional condition over the record's own values, and whether a note is required.
- Optional automatic side effects per transition: set a field, stamp a timestamp field, or assign to a user.
Enforcement everywhere, not just in the interface. Write tests for each path:
- The record editor offers only the transitions permitted from the current state, and shows which required fields are blocking the others rather than hiding them.
- The API rejects an invalid transition with an explanatory error naming the rule.
- A CSV import that would place records in a state they cannot legally be in is rejected with a per-row report, not silently accepted.
- A bulk update across a filtered selection applies the transition per record and reports which records were skipped and why, rather than failing the whole batch or forcing all of them through.
History: every transition recorded with the actor, timestamp, from-state, to-state and note. From that history, compute per-table cycle-time metrics — average time in each state, and the state where records sit longest. That measurement is the reason to define a process at all and most tools in this category never surface it.
Views: grid, kanban with columns as states where dragging a card performs a transition and is refused with an explanation when the transition is not permitted, calendar on a date field, and a timeline.
Forms: a form creates records in a declared initial state, exposing only fields writable at that state.
Dashboards: per-table counts by state, records stuck in a state beyond a threshold, and a cycle-time chart.
Out of scope: a template library of pre-built processes, third-party integrations, real-time collaborative editing, granular per-field permissions, and any hosted multi-tenant deployment.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the template library of ready-made business processes
- B.2 the integration catalogue connecting to other systems
- B.3 real-time collaboration and granular team permissions
- B.4 managed hosting, backups and support
Prior art
Exhibit C — Why people still pay: data model flexibility, collaboration, and integrations
Because a process tool is bought by a team, and its value is that everyone follows the same steps. A self-hosted state machine with one user is a very well-engineered personal to-do list.
Questions
Can I export a SmartSuite solution?
Records export as CSV per table. The solution structure — fields, links, permissions and any automations — has no portable export, so the schema and the workflow are rebuilt by hand. Writing the state machine down explicitly is usually a useful exercise in itself.
Why enforce transitions rather than using a status dropdown?
Because an unconstrained status field drifts. Records end up marked done without the fields that make done meaningful, and the cycle-time numbers computed from that history are worthless. Requiring the transition to be legal is what makes the history trustworthy.
What does it cost to run?
A VPS with PostgreSQL, ten to twenty dollars a month regardless of how many people use it, against a per-seat price. The saving grows with team size and is paid for in being the person who maintains it.
What is the one thing that does not survive the rebuild?
Everyone using it. A process tool works because the whole team is inside it, and adoption comes from templates, integrations and someone else guaranteeing it stays up. A correct state machine that only you use has solved the easy half.
Related tools
Receipt