Technical handover / 02 of 06 · Funnel Intake System

Replit Forms replit · 2 apps

The two forms the client actually fills in. The link they open decides which questions they see.

Watch Full walkthrough (9 min) Map Full system breakdown For AI Point Claude here
System
Funnel Intake
Unit
2 of 6
Platform
Replit + Make
Built by
Icarus Growth

▸ The 9-minute walkthrough — both forms, live on screen

What this does

This is the part the client actually sees. Two forms built in Replit: the full New Funnel Brief and a shorter Express version. The link they open already carries the funnel type, their name, and their company — so the form loads the right fields and pre-fills what it can. They answer, hit a review page, and submit. On submit, everything they typed gets posted over to Make.

The one thing to remember: the form only knows what the link told it. The Kickoff Form packs the funnel type and the client details into the URL. Open the form without that URL and it has nothing to go on.

Where it sits

Both forms live here: the full New Funnel Brief and its one-page Express twin. Same wiring — the Express just carries fewer funnel types.

How it works

The Kickoff Form hands over a link. Everything below runs off that link.

  1. The client opens the link. Its query params — client_name, company_name, funnel_name, funnel_type, target_date, evergreen — tell the form who they are and which funnel this is. The right fields load and the known answers are already filled in.
  2. The funnel type in the link picks the dropdown — call booking, quiz, webinar, and so on. That single value sets the shape of the form.
  3. The client fills the page(s):
    1. New Funnel Brief — two pages: the Brief, then the Funnel Details.
    2. Express Funnel — one page.
  4. Finishing a page posts it to Make straight away. Page 1 files the funnel; page 2 tops up the same record. Go back a page and re-submit and it simply overwrites — no duplicates.
  5. They land on a review page — a plain summary of what they entered. It's cosmetic; the data is already saved by this point.
  6. Which automation catches it depends on the form: New Funnel Brief posts to New Funnel Brief » Push to Airtable, Express posts to Express Funnel » Push to Airtable.

The moving parts

No Make blueprint here — these are web apps. Two of them, doing the same job for different tracks.

The two apps
funnel-brief-portal.replit.app — New Funnel Brief, 2 pages · express-funnel.replit.app — Express, 1 page
Reads
The link's query params — to pre-fill fields and pick the funnel type
Sends
A webhook POST to Make — on each submit
Runs on
Replit — hosted and versioned there; source isn't in this repo
Posts to
Two different Make webhooks — one per form
Good to know
• The forms are built and hosted on Replit — the source isn't in this repo. You edit them by chatting to Replit's coding agent, then hitting republish. Right now only Anissa has republish rights.
Webhook and payload changes are the exception — those go live without a republish. That's developer-side.
• The two forms post to two different Make webhooks. Don't cross the wires.
• Any files the client attaches ride along inside the payload as source material.

What you can safely change

Straight answer: this is a hosted Replit app, so nearly everything here is developer territory. Green = go. Amber = fine, but it needs Replit access. Red = leave it, call us.

GreenNothing, really — there's no safe knob to turn from outside Replit. If it lives in the form, it lives in Replit.
AmberForm copy, labels, and which fields are required — all editable, but inside Replit, and someone with republish rights has to push it live.
AmberAdding or reordering questions — same deal: do it in Replit, test a dummy submission, then republish.
RedThe URL parameter names (client_name, funnel_type, …) — rename one and the Kickoff Form's links stop pre-filling.
RedThe funnel-type keys — they pair a link to a funnel build. Change one here and you must change it in the Kickoff Form and the Make automations too, or the wrong build fires.
RedThe webhook URLs the forms post to — repoint these and submissions stop reaching Make. Airtable goes quiet.

What connects to this

This sits in the middle of the chain. Here's what feeds it and where it sends things next.

◀ Comes in from

  • Kickoff Form
    Hands over the link. The query params in it pre-fill the form and set the funnel type.

Goes out to ▶

Not covered here: the form's Replit source code (it lives in Replit, not this repo) and what happens to the payload once Make has it — that's the Push to Airtable breakdowns.

If something looks wrong

The form opens blank, or with the wrong fields.
The link is wrong. Both the pre-fill and the funnel type come straight from the URL — check the Kickoff Form that generated it.
Client submitted, but nothing appeared in Airtable.
The form did its part — the break is downstream at the webhook or the Make automation. See New Funnel Brief / Express Funnel.
A field label or question reads wrong on the live form.
That's a Replit edit — fix it in Replit and republish (Anissa has the rights).
Where this lives. These forms are hosted on Replit and every change is versioned there. There's no copy in this repo to restore from — edits, fixes, and rollbacks all happen inside Replit.

Call us if: submissions stop reaching Make even though the link looks right, or a change in Replit won't go live.
Jargon buster
Replit
A web-app builder. You make changes by chatting to a coding agent — the same way you'd talk to a coding tool — then republish to push them live.
Republish
The button that makes your Replit edits go live. Only someone with republish rights can press it.
Query params
The bits after the ? in a link, like funnel_type=call_booking. They tell the form what to show and what to pre-fill.
Pre-fill
The form filling itself in from the link, so the client isn't retyping their name and company.
Funnel-type key
The short code (e.g. webinar) that maps a link to one specific funnel build.
Webhook
The address the form posts to. It's what carries the answers over to Make.
Payload
The bundle of answers — and any uploaded files — the form sends.