Airtable Omni, HubSpot, and GA4 Can Make Growth Planning Less Political

Quarterly planning breaks when evidence arrives late

I have watched too many QBRs turn into theater by slide 17. The paid lead has a polished case for a LinkedIn test. The content lead has 42 keywords and a competitor screenshot. The founder wants a webinar because one enterprise prospect mentioned procurement education on a call last Tuesday. Everyone is partly right, which is why the room gets stuck.

The fix is not another scoring rubric copied from a product roadmap template. Growth planning needs live campaign records, named owners, GA4 key-event evidence, and a revenue-stage check that updates before the next meeting. Airtable’s Omni release on June 24, 2025 gives operators a better shell for that job because Omni can build and edit Airtable apps through conversation, update records, analyze data, and work inside the base rather than sitting in a separate chat window. Airtable says Omni is part of its AI-native app platform and that Airtable is used by 450,000-plus organizations. Useful scale. Still, the business value comes from the operating model you put around it, not the novelty of asking an AI assistant to make a table.

I would start with one base: quarterly growth priorities. Keep it boring.

The three systems have different jobs

Airtable should hold the prioritization logic. HubSpot should hold campaign ownership, assets, budgets, and CRM-stage evidence. GA4 should hold behavior that happened before a person was ready to talk to sales. When those jobs blur, reporting gets muddy by week 3.

Airtable Omni is useful because it can draft the workflow you would otherwise sketch in a Google Doc. Ask it to create tables for campaign ideas, HubSpot campaign records, GA4 key events, revenue checkpoints, experiments, and planning decisions. Then ask it to add fields for owner, target segment, expected pipeline, confidence, channel, offer, launch date, source evidence, and review status. That takes minutes. The operator work begins after the skeleton exists.

HubSpot’s current Campaigns API uses endpoints under /marketing/campaigns/2026-03, returns a campaign id as a UUID-style campaignGuid, and supports properties like hs_name, hs_start_date, hs_end_date, hs_campaign_status, hs_utm, hs_owner, budget totals, and spend totals. HubSpot also notes that the old hs_goal property was sunsetted on July 9, 2025, so I would avoid building any planning logic around it. Use campaign status, owner, budget, spend, UTM, and downstream deal data instead.

GA4 changed the language in March 2024. What used to be Analytics conversions are now key events inside GA4, while Google Ads still uses conversions. That naming split matters in planning. A demo_request_submit event in GA4 might be a strong buying signal. A pricing_page_view key event might be a useful mid-funnel marker. A scroll_90 key event is usually too soft for pipeline scoring unless you sell something with a long education cycle, like compliance software or industrial equipment.

Build the Airtable base around decisions, not tasks

The first table is Campaign Ideas. Each record is one bet: “Q4 2026 founder-led webinar for RevOps teams,” “LinkedIn document ad for SOC 2 checklist,” “SEO refresh for comparison pages,” or “partner email with fractional CFO newsletter.” I make the title plain because clever internal names rot fast. Six months later, nobody remembers what “Project Lighthouse” meant.

Fields should include channel, audience, offer, target month, estimated cost, expected SQLs, expected pipeline, confidence, and effort. Add one field called Why now. Force a human sentence there. “G2 comparison page dropped from position 4 to 9 between May and August 2026” is useful. “Increase awareness” is a fog machine.

The second table is HubSpot Campaigns. Sync or import the HubSpot campaignGuid, hs_name, hs_campaign_status, hs_owner, hs_utm, budget total, spend total, start date, and end date. If you do not want to wire the API on day 1, export a CSV from HubSpot Campaigns every Friday at 9 a.m. Eastern and upload it. Fancy sync can wait. Bad fields cannot.

The third table is GA4 Evidence. Pull key events by campaign UTM, landing page, source, medium, and date range. For most B2B teams I care about five GA4 events: generate_lead, sign_up, demo_request_submit, pricing_page_view, and contact_sales_click. Your property may use different event names. Keep the list short enough that people can explain why each event matters.

Then add Revenue Checks. This table links campaigns to HubSpot deals, lifecycle stages, or a warehouse table if the company has one. I like four checkpoints: MQL created, SQL accepted, opportunity created, and closed-won revenue. A campaign that drives 900 GA4 key events and 2 SQLs should lose to a campaign that drives 90 key events and 14 SQLs. That is the point.

Let Omni draft the workflow, then tighten it by hand

Here is the prompt I would give Omni inside the Airtable base:

“Create a quarterly growth prioritization app for a B2B SaaS company running paid search, LinkedIn ads, SEO, webinars, and lifecycle email. Add tables for campaign ideas, HubSpot campaigns, GA4 key-event evidence, revenue checks, and planning decisions. Link campaign ideas to HubSpot campaigns and GA4 evidence. Create a priority score using expected pipeline, confidence, effort, owner capacity, and revenue-stage proof. Add views for Q4 2026 planning, owner review, ready for launch, and evidence missing.”

That prompt will get you a decent first draft. I would immediately inspect the scoring formula. AI-built workflow logic tends to overweight completeness because complete records look trustworthy. A weak idea with every field filled out can beat a messy idea with real buying evidence if you let the formula reward tidy admin work.

My default score is simple: expected pipeline times confidence, divided by effort, then multiplied by a revenue-stage factor. Confidence is 0.25, 0.5, 0.75, or 1.0. Effort is 1, 2, 3, 5, or 8. Revenue-stage factor is 0.7 for GA4-only evidence, 1.0 for MQL evidence, 1.3 for SQL evidence, and 1.6 for opportunity evidence. If a $40,000 pipeline idea has 0.75 confidence, effort 3, and SQL proof, it scores 13,000. If another idea claims $100,000 in pipeline with 0.25 confidence, effort 8, and GA4-only evidence, it scores 2,187.5.

Crude math beats a polished argument.

The weekly update loop is where the system earns its keep

A quarterly plan made on October 1, 2026 starts dying by October 8. Spend changes. Sales rejects leads. Google Search Console surfaces a query nobody expected. HubSpot owners go on leave. GA4 starts showing that the webinar registration page gets traffic from paid social but the thank-you event fails on Safari 18.6. Planning has to move with that mess.

I use a weekly Friday review with three Omni-assisted updates. First, ask Omni to summarize which campaign ideas gained or lost evidence since the previous Friday. Second, ask it to flag records where HubSpot status, owner, or spend changed. Third, ask it to list ideas where GA4 key events increased but revenue checks stayed flat. That last one catches the campaigns that look healthy in marketing reports and dead in the CRM.

Do not let Omni auto-promote work into the launch queue without a human owner. HubSpot’s campaign owner field exists for a reason. If nobody in HubSpot owns the campaign, nobody owns the cleanup when UTMs break, the landing page ships late, or sales asks where the leads came from.

For a small team, I would cap active growth bets at 7 per quarter. That might be 2 paid tests, 2 SEO bets, 1 partner campaign, 1 webinar, and 1 lifecycle email sequence. A founder-led team with one marketer and a contractor cannot run 19 serious experiments in 90 days. Airtable can hold 19 records. The business cannot absorb them.

What this changes in the planning meeting

The meeting gets shorter because the argument moves from opinion to exception handling. Instead of asking “Which ideas do we like?” the team opens the Airtable interface and looks at four filtered views.

The first view shows high expected pipeline and missing evidence. These are speculative bets. They need sharper proof or a smaller test budget. The second view shows low pipeline and high effort. Kill these unless a founder has a strategic reason and is willing to name it. The third view shows GA4 key-event lift without HubSpot stage movement. Fix tracking, lead quality, sales routing, or the offer. The fourth view shows HubSpot opportunity proof with low spend. Those are the campaigns I want to fund first.

A real example helps. Say a cybersecurity startup has three Q4 campaign ideas. One is a $12,000 LinkedIn document-ad test aimed at CISOs, tied to a SOC 2 readiness checklist. GA4 shows 184 generate_lead key events from a similar Q2 checklist, but HubSpot shows only 6 SQLs and 1 opportunity worth $18,000. The second is an SEO refresh of “Vanta alternatives” and “Drata alternatives” pages. GA4 shows 71 pricing-page key events in August 2026, and HubSpot has 9 SQLs from organic comparison traffic with $140,000 in open pipeline. The third is a founder webinar on AI governance with no past key-event trail, but 3 open enterprise deals mention governance in HubSpot notes.

I would rank the SEO refresh first, the webinar second as a contained sales-support play, and the LinkedIn checklist third unless the team changes the offer or audience. That is not a philosophical call. It follows the evidence.

Keep the data model small enough to survive

The trap with Airtable is that operators keep adding fields until the base becomes a second CRM. Resist it. HubSpot already has contacts, companies, deals, owners, campaigns, ads, emails, forms, and landing pages. GA4 already has events, sessions, traffic source fields, landing pages, and audiences. Airtable should carry the decision layer.

I would keep fewer than 25 fields on Campaign Ideas and fewer than 15 fields on GA4 Evidence. Add linked records instead of copying every metric into every table. Use rollups for SQL count, opportunity count, spend, and pipeline. Store a plain-text Evidence summary because people still read sentences faster than formulas when they are deciding what to cut.

One rule has saved me hours: every planning score must be explainable in under 30 seconds. If a founder asks why a campaign ranked number 2, the answer should fit in one breath. “It has $140,000 in open HubSpot pipeline from 9 SQLs, GA4 pricing-page key events rose 38 percent in August, and the effort is a 2 because the pages already exist.” Done.

Airtable Omni can make the workflow easier to build and easier to maintain. HubSpot campaign records keep ownership and revenue close to the work. GA4 key events show whether the market is giving you any signal before sales gets involved. Tie those three together and quarterly planning stops rewarding the sharpest brief. It starts rewarding the bets with the clearest path to pipeline.