DECHY logo

Ctrl K or / to search, arrows to move, Enter to open

Platform

Airtable development

Airtable lets a team build its own tracking system without waiting for software to be written. It sits between a spreadsheet and a database. We design the structure so it stays tidy as it grows, and we say honestly when a team has outgrown it.

  • 1,200+ clients helped
  • Building since 2010
  • 15 services, one team
  • 50+ technologies

At a glance

What it is

Airtable is a tool that combines a spreadsheet's ease with a database's structure, so teams can track work, link records, and automate steps without writing code.

What it means

A spreadsheet that understands relationships

Airtable stores information in tables like a spreadsheet, but lets records link to each other like a database. A customer can link to their orders, and each order to its tasks, so one change shows up everywhere.

That structure is what removes the usual spreadsheet problems: the same name typed three ways, a copy that nobody updates, and a formula that someone overwrote.

It is also quick to change. Teams adjust fields and views themselves, which is the main reason it works so well as a first system, and the main reason it needs a clear structure from the start.

A person working at a laptop

Options

Airtable, a spreadsheet, or custom software?

These are the three choices we weigh with teams.

What does your team need?

Choose this when

One or two people use it, the data is simple, and mistakes are cheap.

What you get
Nothing new to learn or pay for.
Keep in mind
Revisit it when a second person starts editing.
Ask for an honest view

Limits

Where Airtable stops

Common limits of Airtable and how we deal with each
LimitWhat it meansWhat we do
Record limits per base Large data sets will hit plan limits. Split data across bases, archive old records, or move large data to a database.
Access control Permissions are coarser than a custom system. Use interfaces for restricted views, and keep sensitive data elsewhere.
Complex logic Long chains of automations get hard to follow. Move heavy logic to a workflow tool such as n8n or Make.
Cost with growth Per-user pricing adds up as the team grows. Review costs yearly against the alternatives.

What DECHY can do

Working with Airtable

Design

  • Base structure that stays tidy as it grows.
  • Field and permission rules.

Build

  • Views, forms, and interfaces for each role.
  • Automations for reminders, hand-offs, and updates.

Connect

  • Links to email, calendars, and customer records.
  • Syncs with other systems through Zapier or custom code.

Look after

  • Clean-ups of messy bases.
  • Training and ongoing support.

Where it fits

Systems that suit Airtable

  1. A content or campaign calendar

    Ideas, drafts, owners, and dates in one place, with a board for status and a calendar for timing.

  2. A client or project tracker

    Clients, projects, tasks, and hours linked together, with different views for managers and the team.

  3. An asset or equipment register

    What exists, where it is, who has it, and when it is next due for service.

  4. A lightweight customer record

    Contacts, deals, and activity for a small team, with forms feeding it from your website.

How we work

Moving a spreadsheet into Airtable

  1. Study how the spreadsheet is used

    We learn who edits it, what the columns really mean, and which mistakes happen.

    What it produces

    • Notes on current use
    • List of problems
  2. Design the structure

    We split it into tables, define links between them, and choose field types that prevent bad data.

    What it produces

    • Table and link design
  3. Build views and forms

    We create views for each role and forms for incoming data.

    What it produces

    • Working base
    • Forms
  4. Move the data and run alongside

    We clean and import the records, and run the old and new together briefly.

    What it produces

    • Imported data
    • Check results
  5. Automate and hand over

    We add the automations that save the most time, and train the team.

    What it produces

    • Automations
    • Guide and training

Worth knowing

A base needs an owner

The most common way an Airtable base goes wrong is that everyone can change its structure and nobody is responsible for it. Within a year there are duplicate fields, unused tables, and views that nobody understands.

We name an owner for each base and agree what members may change, so the system stays as clear as the day it was built.

Technical depth

How we build with Airtable

What we settle early on Airtable work: data design, integration, and governance, so nothing surprises your team later.

We use linked records and lookups instead of copied values, choose single-purpose fields, and keep a clear primary field for every table.

Common questions

Questions about Airtable

Is Airtable a database or a spreadsheet?

A bit of both. It looks like a spreadsheet and behaves like a simple relational database. That blend is its strength and its limit.

Can customers use it directly?

Forms and shared views can collect and show data. For customer accounts with detailed access rules we usually recommend a different tool.

How safe is our data?

Airtable provides security features, and the plan you choose affects what is available. We review it against your requirements and keep truly sensitive data out when needed.

What happens if we outgrow it?

Data can be exported and moved. We design with that in mind so a later move to custom software is straightforward.

Have a different question?

Tell us what you are weighing up and we will answer it plainly.

Ask a question

Already a client? Email support@dechytech.com

Tell us which spreadsheet your team depends on

Describe it and who uses it. We will say how it would look in Airtable, what it would cost to run, and when you would need something more.