Expert Airtable Builder for Sales & Marketing Dashboards

Job ID: 40176525

Budget: $250 – $750 USD

Description:
I need an experienced Airtable builder to design and implement two executive dashboards in Airtable Interfaces:

Sales Dashboard

Marketing Dashboard

These dashboards must support robust filtering, clean UI (tiles/rows), and accurate funnel math across Bookings, Closed Deals, and Capacity (Available Slots).

Tables (already exist)

Contacts

Bookings

Closed Deals

Reps

Closer EOD (Available Slots lives here)

Marketing tables for Leads / Applications / MQLs (or equivalent)

Core Requirement (critical)

Interfaces must not incorrectly source everything from one table.
Metrics must be accurately calculated and filterable.

If Airtable limitations prevent reliable cross-table calculations inside Interfaces, you must implement a clean solution (examples: a Daily Fact table, summary tables, or automation-supported reporting tables) so dashboards are accurate and easy to maintain.

Sales Dashboard Requirements
Filters (multi-select where relevant)

Date range (based on Booking Date/Time on calendar, not created time)

Marketing Source(s)

Meeting Type(s)

Appointment Status (Show / No Show / Cancel / Reschedule etc.)

Confirmation Status

Booking Outcome

Deal Outcome

Closer

Setter

Ability for viewer to hide/collapse filters if possible

Sales KPIs

Available Slots

Bookings

Confirmations

Shows

Cancels

No Shows

SQLs

WSQLs

Offers

Closed Deals

Cash Collected

Revenue Generated

Sales Rates / Derived Metrics

Filled Slot Rate = Bookings / Available Slots

Confirmation Rate = Confirmations / Bookings (and also Shows/Confirmations if you prefer that definition—confirm with me)

Show Rate = Shows / Bookings

Confirmed Show Rate = Shows / Confirmations

Cancellation Rate = Cancels / Bookings

No Show Rate = No Shows / Bookings

SQL Rate = SQLs / Shows

WSQL Rate = WSQLs / Shows

Offer Rate = Offers / Shows

Win Rate = Closed / Bookings

Close Rate (Show) = Closed / Shows

Close Rate (SQLs) = Closed / SQLs

Close Rate (WSQLs) = Closed / WSQLs

AOV = Cash Collected / Deals

Collection Rate = Cash Collected / Revenue Generated

Cash Per Booking = Cash Collected / Bookings

Marketing Dashboard Requirements
Filters

Date range (Booking Date/Time on calendar, not created time)

Marketing Source(s)

Meeting Type(s)

Type of meeting (setter call / new / follow up / reschedule etc.)

Appointment Status (Show/No Show/Cancel/Reschedule)

Confirmation Status

Booking Outcome

Deal Outcome

Closer

Setter

Ability to hide/collapse filters if possible

Marketing KPIs

Ad Spend (daily input or pulled if available)

Leads

Applications

A/B/C/Disqualified breakdown

MQLs

Available Slots

Bookings

Shows

Offers

Cancels

No Shows

SQLs

WSQLs

Closed Deals

Cash Collected

Revenue Generated

Marketing Unit Economics

CPL = Cost / Leads

Cost per Application

Cost per MQL

Cost per Booking

Cost per SQL

Cost per WSQL

Cost per Closed Deal

Cash per Lead / App / MQL / Booking / SQL / WSQL / Closed Deal

Lead → Application %

Application → MQL %

MQL → Booking %

Application → Booking %

MQL → SQL %

Filled Slot / Show / Confirmed Show / Cancel / No Show / SQL / WSQL / Offer / Win / Close Rates

ROAS (Paid Media Cash / Ad Spend)

Blended ROAS (All Cash / Ad Spend)

Deliverables

Two Interface pages: Sales Dashboard + Marketing Dashboard

Correct filter behavior across tables (no “everything under bookings” mistakes)

Clear documentation:

what each metric uses as source fields

definitions for each rate

how to maintain / update

Short Loom walkthrough (5–10 min)

QA checklist: confirm a handful of known days match expected counts

Screening Questions (must answer)

Share 1–3 examples of Airtable dashboards/interfaces you built (screenshots or Loom).

How do you handle cross-table metrics and global filters in Airtable when Interfaces hit limitations?

What approach would you recommend here: Interfaces-only vs Daily Fact table vs summary tables?

Estimate timeline + cost.

Budget: Open to fixed price or hourly. I care more about correctness and maintainability than speed, although speed IS important