Workflow design · Internal prototype

Personalized Report Automation

Airtable + Zapier

I was trying to answer a practical question: could one intake score a law firm lead, shape a useful report, and point the follow-up in the right direction? This case study pairs live Airtable evidence with recreated reference visuals for the intake, automation, and report flow.

28 fieldsin the live Airtable table

5 score partscombined into Total Score

3 lead tiersHot, Warm, and Nurture

Softr linksgenerated per Airtable record

01 / The assignment

The brief started as a big idea with a lot of moving parts.

A law firm would answer questions about its practice, marketing spend, case value, team size, and current channels. Those answers would feed a score, shape a Market Intel Report, and help decide what should happen next.

The hard part was figuring out where automation was actually useful. Some steps fit the tools. Others needed a workaround or a person in the loop.

Important limitThe concept never launched, so there are no customer, revenue, conversion, or time-savings results to report.
02 / Live evidence

What the Airtable base proves

Live shared view

The live Airtable view is the piece I can still open and inspect. It has 14 rows and 28 fields. The screenshots below are real, with names, contact details, firm identities, and record-level report links cropped out.

Cropped live Airtable view showing Monthly Spend, Case Value, Firm Size, and component score columns
REAL AIRTABLE EVIDENCE Intake values are stored alongside formula score outputs. Captured September 3, 2026.
Contact and firm

Identity inputs

The table stores contact details, practice area, city, and firm size.

Commercial context

Qualification inputs

Monthly Spend and Case Value are single-select fields shown beside the score outputs.

Marketing context

Journey inputs

It also records marketing frustration, current channels, YouTube status, and video concerns.

Calculated layer

Derived outputs

Five component scores feed a total and tier. The base also creates a report link for each record.

03 / Scoring layer

Each lead gets five component scores.

The live table shows separate scores for Spend, Case, Size, Frustration, and YouTube. In every row I could inspect, those five numbers add up to the displayed Total Score.

Spend+
Case+
Size+
Frustration+
YouTube=
Total ScoreTier
Cropped live Airtable view showing component scores, Total Score, and Score Tier values
REAL AIRTABLE EVIDENCE Observed totals include Hot, Warm, and Nurture outputs. The report-link column is excluded.
Observed80, 83, 85

Hot

Observed65, 70, 75, 78

Warm

Observed35

Nurture

The visible rows suggest Hot starts at 80, Warm includes at least 65 through 78, and a score of 35 lands in Nurture. The rows do not reveal every cutoff, so this case study shows only the values present in the live view.

04 / Intake mapping

A recreated quiz shows how the intake mapped into Airtable.

Sanitized reconstruction

This reference visual maps representative questions to fields in the live Airtable base. It is a reconstruction from project records, not an original Typeform screenshot.

Open the recreated intake

Lead intake / representative fields01-07
01

What is your primary practice area?

Practice Area
02

Which city or metro do you serve?

City
03

What is your monthly marketing spend?

Monthly Spend
04

What is a typical case worth?

Case Value
05

How large is the firm?

Firm Size
06

What is your current YouTube status?

YouTube Status
07

Where should the report be sent?

Contact fields
05 / System architecture

The reference flow separates live evidence from recreated steps.

Verified live Recreated from project records Planned path
SANITIZED WORKFLOW RECONSTRUCTION
01 / Intake

Quiz submission

The Typeform intake gathered the firm, marketing, spend, case value, and channel inputs used downstream.

02 / Data

Airtable record

Live evidence. The fields, component scores, totals, tiers, and report-link formulas are visible in Airtable.

03 / Decision

Zapier layer

The Zapier layer represents the handoffs between intake, scoring, reporting, and follow-up.

Verified field

Softr report URL

Airtable creates a different Softr URL for each record. I did not test what those links open.

Recreated reference

Thank-you / booking

The mapped journey moves from submission into a thank-you page and booking path.

Planned path

Lead alert

The proposed high-value branch sends the team a lead alert for faster review.

Recreated reference

Follow-up

The follow-up branch uses the score, tier, summary, and next-action fields to guide outreach.

Open the recreated automation map

06 / Recreated page set

Five pages show how the full experience could have worked.

Concept recreations

Each page is built from the project’s documented fields, flow, and report outline. Sample Firm and its contact details are fictional.

07 / Report experience

I worked out the report before worrying about the layout.

The brief called for the five sections shown here. This is the planned outline, not a finished client report.

Recreated from project records

Open the recreated report

Market Intel ReportFirm snapshot / internal prototype
  1. 01
    Gap MapWhere marketing activity and opportunity diverge
  2. 02
    Competitive snapshotSignals from the firm’s market and content landscape
  3. 03
    ROI analysisScenario framing based on spend and case value inputs
  4. 04
    90-day content planA sequenced plan tied to the intake context
  5. 05
    Next stepsHuman review and a booking path
08 / Constraint and fallback

The report generator was the weak link.

Recreated from project records

Project records show that Canva Bulk Create could personalize the report, but someone still had to trigger the generation step. That fell short of the original goal: a report created and sent as soon as the intake arrived. This visual recreates the decision point and the fallback that followed.

Desired state

Instant personalized report

One submission creates the record, calculates the score, and starts the report and follow-up.

Constraint

Manual generation step

Bulk personalization still needed a person to generate the report.

Fallback

Separate data from presentation

Keep the scoring in Airtable, test other report tools, and leave room for a final human review.

09 / Built versus planned

What is live, recreated, planned, and out of scope.

Not launched
ComponentEvidence statusWhat can be said
Airtable data modelVerified liveTwenty-eight intake, formula, summary, and next-action fields exist.
Scoring and tiersVerified liveFive component scores sum to Total Score in observed rows; Hot, Warm, and Nurture appear.
Softr report linkVerified fieldA formula creates a Softr URL per record. The recreated report shows the intended page experience.
Typeform intakeReconstructedThe intake and its Airtable field mapping are shown as a reference visual based on project records.
Zapier flowsReconstructedThe report and follow-up handoffs are shown as a labeled reference flow.
Report modulesIntendedThe outline documents the plan. It does not prove a report was completed or delivered.
Launch and resultsDo not claimThe prototype never launched, so there are no client deliveries or business results to claim.
10 / Role attribution

What I will put my name on.

The live Airtable evidence supports the data model and scoring layer. The recreated visuals show the surrounding work without presenting them as original product screenshots.

Built

I designed the intake structure, Airtable data model, scoring logic, and Zapier handoffs for the report and follow-up paths.

Worked on

I also worked on the thank-you page, booking path, and report experience.

Tested

I compared report-delivery options and ran into the limits of bulk personalization.

Recommended

When full automation was not practical, I recommended keeping the data and presentation layers separate.

Not claimed

I am not claiming a production launch, client delivery, business results, or a confirmed final report platform.

11 / What this demonstrates

The useful part was the judgment.

I took a fuzzy funnel idea and made it concrete enough to test. The Airtable layer worked as a model for intake and scoring. Report generation exposed the real constraint, and the project stopped before launch. That is the honest version of the work.

Workflow Mapping Airtable Rule-Based Scoring Zapier No-Code Prototyping Process Design Tool Evaluation Human-in-the-Loop Planning
← All case studies