Client portals

A portal on your Airtable base, for people who will never open Airtable.

Clients, suppliers and staff log in to a portal built for the job they do. Airtable stays the source of truth underneath, every record is checked against what that user is allowed to see, and every change is logged.

Fixed scope, fixed price. You own the code and the accounts.

Sound familiar?

When sharing the base stops working.

Seats

Paying for seats people barely use

Everyone who needs to see or edit a few records gets a full Airtable seat, or a share link that shows more than it should.

Access

Filtered views are not permissions

A view filtered to one client is a convenience, not a lock. The moment the data is sensitive, you need each record checked on the server, not hidden in the interface.

Fit

Portal builders hit a wall

Airtable Portals, Softr and the like are quick to start. Then you need data from two bases, a view they do not offer, or a rule about who can edit what, and the builder runs out.

What we have built

A portal in front, Airtable behind.

Airtable interfaces for people without Airtable

A distribution business gives staff the screens they work in (purchases, contacts, contracts, price lists) without Airtable accounts. The portal reads and writes the base directly; Supabase only handles logins, permissions and the audit log.

Each user sees only the interfaces assigned to them

NEXT.JS AIRTABLE SUPABASE

Edits that never overwrite each other

If someone changed a field in Airtable that a portal user was also editing, nothing is overwritten. The portal shows both values and the user chooses.

Every write logged with old and new value

NEXT.JS AIRTABLE

A cash flow view Airtable cannot draw

Daily liquidity, pending payments and the weekly and monthly flow, combining the Airtable base with the treasury spreadsheet finance already keeps, in a layout no Airtable interface supports. This is where a custom portal earns its cost.

Airtable and the treasury sheet in one view

NEXT.JS AIRTABLE SUPABASE

How it works

Four weeks from first call to a portal people log in to.

  1. 01

    Discovery (Week 0)

    30 minutes. We map your current tools, the bottlenecks, and what "done" looks like. You leave with a written scope and fixed price.

    • Discovery call
    • Tools & bottlenecks
    • Written scope
    • Fixed price
  2. 02

    Build (Weeks 1–3)

    We build the system on Airtable + n8n + your existing stack. You see weekly demo videos; nothing is built in a vacuum.

    • System build
    • Weekly demo videos
    • Integration testing
  3. 03

    Launch (Week 4)

    We deploy live, train your team, and ship documentation written for humans, not engineers.

    • Deploy live
    • Team training
    • Documentation
  4. 04

    Maintain (Ongoing)

    Optional retainer for changes, monitoring, and the next system. Most clients stay.

    • Monitoring
    • Changes & fixes
    • Next system

Not sure if you need a custom portal or just Airtable Portals? That is the first call.

Book a call

Questions

What people ask before building a portal.

Why not just use Airtable Portals or Softr?

Use them if they fit. They are quicker to set up and cheaper to start. A custom portal is worth it when you need data from more than one base, permissions checked record by record, a screen those tools cannot build, or more users than their pricing makes sensible. We'll tell you which side of that line you are on.

Do we have to leave Airtable?

No. Airtable stays the source of truth and your team keeps working in it. The portal reads and writes the same base, so formulas, rollups and automations keep running.

What happens when we rename a field in Airtable?

Nothing breaks. The portal refers to every table and field by its Airtable ID, not its name.

Who owns the result?

You do: the code, the hosting accounts, the database and the documentation. A retainer for changes and new screens is optional.

Start with a call

Tell us who needs in, and what they need to see.

We look at your base, the people who need access and what each of them does, and come back with a fixed-scope proposal. If Airtable Portals or a builder covers it, that's in the answer too.

Fixed price · Written scope · No obligation