An equipment operation tracks assets, customers, reservations, inspections, and deliveries. At first, one sheet seems sufficient. Then the same asset appears in several places, a reservation changes, and nobody can tell which row represents the current commitment.
Evaluate Airtable around linked records and Smartsheet around coordinated sheets and schedules. Build a custom application when the workflow requires authoritative transactions, finely scoped access, or integration behavior that the configured tools cannot reliably provide. The key question is not which interface looks most like a spreadsheet; it is where the operational truth lives.
Compare the operational boundary
Sources were reviewed September 26, 2026. Dollar prices below are published US-dollar seat/member figures with annual billing. Custom capabilities are proposed requirements, not a delivered product.
| Requirement | Airtable | Smartsheet | Build your own |
|---|---|---|---|
| Working model | Platform combines databases, interfaces, and views. Airtable pricing | Sheets include formulas, dependencies, reports, and Gantt views. Smartsheet pricing | Relational database with explicit domain records. |
| Annual price anchor | Team US$20/user/month; Business US$45. Airtable pricing | Pro US$9/member/month; Business US$19. Smartsheet pricing | Quote workflow delivery plus annual operation. |
| Billable participation | Edit access drives Team/Business billing; read-only and form submissions are not charged. Airtable pricing | Pro allows 1–10 members; Business starts at three members. Smartsheet pricing | Count support and infrastructure costs even without per-seat fees. |
| API access | Web API available with plan limits. Airtable API limits | Pricing matrix explicitly marks API calls unavailable on Pro, available on Business+. Smartsheet pricing | Publish only endpoints needed by the workflow. |
| API throughput | Five requests/second per base across plans. Airtable API limits | Validate workload and contracted integration capacity. | Own throttling, queues, and capacity planning. |
| Monthly API budget | Free 1,000 calls; Team 100,000 calls. Airtable API limits | Include premium connectors separately in the quote. Smartsheet pricing | Budget provider calls as well as database traffic. |
| Permission-aware writes | Token scope, resource access, and field/table permissions can all affect writes. Airtable API troubleshooting | Test sharing against confidential fields and external users. | Enforce row/field access in the application and export paths. |
| Automation capacity | Plan caps apply to automation/API usage. Airtable pricing | Pro 250 automations/month; Business unlimited. Smartsheet pricing | Make repeated events safe and failures visible. |
| Export portability | Design extraction around records, links, and attachments. | Excel export converts unsupported column types to values. Smartsheet export documentation | Export data and schema with stable IDs. |
| Scale warning | Vendor says Airtable is not a real-time backend hosting service. Airtable performance limits | Treat report/export limits separately from operational scale. Smartsheet export documentation | Use a transactional system for reservations and other invariants. |
Airtable's own performance guidance is an important boundary, not a claim that it cannot support useful operations. Formula recalculation and integrations can cause pressure before a record ceiling is reached. A base with fewer records can still have a demanding workload. Measure changes and dependent work, not just stored rows. Airtable performance limits
Smartsheet's Pro-to-Business boundary is similarly concrete: API access and automation allowance may matter more than the visible seat difference. A cheap pilot without the integration cannot establish the cost of the production solution. Smartsheet pricing
Model the records before choosing the views
Separate assets, customers, reservations, inspections, and movements. A reservation references an asset and a time interval. An inspection records a result at a moment in time; it is not just a checkbox on the asset that gets overwritten at the next inspection.
Write down the invariant you need. For example, two confirmed reservations must not allocate the same asset for overlapping intervals. A view showing apparent availability is not sufficient if two people can reserve it simultaneously. Test the concurrent action in each configured option. If the solution relies on a person noticing the conflict later, price that operational risk honestly.
Distinguish editable data from derived data. Staff should not manually maintain both a reservation status and several copied availability fields if those values can drift. Establish which record is authoritative and make corrections there. A custom database is useful when it can enforce these rules centrally, but it still needs a usable correction workflow.
Integration and exit tests that change the decision
| Test | What to include | Passing evidence |
|---|---|---|
| Simultaneous reservation | Two users confirm the same asset at once. | One accepted commitment or a deliberate conflict resolution. |
| Bulk import during normal work | Historical records plus active staff updates. | No overwritten changes or silently missing links. |
| Supplier update is repeated | Send the same event twice and out of order. | Stable final state without duplicate movements. |
| Restricted contractor | Search, attachment links, exports, and aggregated reports. | No access beyond assigned work. |
| Formula or schema change | Rename a field used by a report and integration. | Dependency inventory and a controlled migration. |
| Exit rehearsal | Records, linked entities, files, dates, and calculations. | Reconstructed operational totals outside the vendor. |
Airtable returns rate-limit errors when throughput is exceeded, and its documentation calls for waiting before retrying. A third-party connector still needs to handle those conditions correctly; buying the connector does not prove it has done so. Include a visible backlog and reconciliation report in the acceptance criteria. Airtable API limits
Smartsheet's export documentation explains that some formulas and column types do not transfer as equivalent Excel behavior. Its report exports also have a 20,000-row limit. Preserve calculation definitions and split/report reconciliation when those are material to your exit plan. A downloaded workbook is evidence of extraction, not automatically a restorable application. Smartsheet export documentation
What a sensible custom build contains
Build the domain records, transaction rules, role-specific screens, and a small number of operational reports. Retain identity, file storage, email delivery, and accounting. Use a queue for external updates and store source identifiers so a replay can safely complete interrupted work.
The custom option can remove duplicated records and enforce changes in one place. It also creates responsibility for backups, restore tests, schema migrations, and access reviews. A developer should be able to explain how an operator reverses a mistaken reservation or corrects an imported asset without directly editing production tables.
Do not rebuild the entire spreadsheet experience. Formula languages, arbitrary views, collaborative editing, and report designers are products in their own right. If staff need to invent new lightweight workflows every week, Airtable or Smartsheet may remain the right tool even when a separate custom application owns critical transactions.
Choose a system of record, then price the rest
Compare the actual editors or members, required plan, connectors, automation load, implementation, administration, and migration. Separate an operational database from a reporting copy: a custom backend feeding an Airtable interface or Smartsheet report can be a valid hybrid, but it will not eliminate both subscription and engineering costs.
Choose Airtable when linked records and configurable interfaces satisfy the workflow within its documented operating limits. Choose Smartsheet when sheet-based coordination, schedules, and reports match how the team works. Build when a tested invariant or integration boundary requires it, and keep the configurable tools where their flexibility remains useful.
Frequently asked questions
When does a spreadsheet-like system need a custom app?
When correctness depends on relationships and transitions that the current configuration cannot reliably enforce. Row count alone is a poor reason to rebuild; test the business rule that is actually failing.
What would a first custom operations database include?
Model assets, reservations, inspection records, and availability transitions explicitly. Reject conflicting reservations on the server, record who changed a status, and give dispatch and returns staff separate task-focused screens. Import a limited active inventory first and reconcile every item before expanding.
How should we compare the cost of Airtable, Smartsheet, and a custom build?
Include time spent reconciling inconsistent rows and maintaining automations. Budget for migration cleanup and ongoing rule changes in the custom option. Compare the same scope and planning horizon, including implementation, retained services, maintenance, and support. A lower subscription bill alone does not establish a lower total cost.