3-Question Qualifier

The form a lead fills out after they comment NUMBERS and receive the auto-DM with the link. Submit fires a webhook to the DM tool (ManyChat or GHL) which delivers the Daily Numbers Tracker plus a Telegram invite, with one personalized line based on their Q2 answer.

Hosted on Tally (default — free tier supports webhooks; mobile-first form rendering matches the IG audience). Form URL stored in frontmatter as tally_url: once impl creates the form.

Question 1 — sub-persona

Copy: Where are you in your e-commerce journey right now?

Type: single-select.

Options: 1. Pre-first-sale. I have a product idea or a half-built store. 2. $10K to $100K per month. I have sales but I am drowning in ad spend or operations. 3. Past $1M per year. I have hit a ceiling and I am looking for the structural unlock. 4. Something else.

Scoring: - Option 1 → tag sub_persona: Validator - Option 2 → tag sub_persona: Operator - Option 3 → tag sub_persona: Scaler - Option 4 → tag sub_persona: Other and route to a manual review DM

The sub-persona tag drives which Telegram nurture sequence the lead enters. It also bias-corrects the LEARN pass — if Operators are under-indexing in carousel reach but over-indexing in funnel conversion, the agent shifts hook mix toward Operator.

Question 2 — bottleneck

Copy: What is the one bottleneck most slowing you down right now?

Type: single-select.

Options: 1. Cashflow. I am running out of money before the sales catch up. 2. ROAS. My ads are not paying back. 3. Team. I am the bottleneck and I cannot hire fast enough. 4. Product. I do not know if I am selling the right thing. 5. Mindset. I know what to do, I am not doing it. 6. Something else.

Scoring: - Each option maps to a bottleneck: tag of the same name. - The tag is echoed back in the tracker delivery DM verbatim: "Got it — your bottleneck looks like {bottleneck}. Here's the row in the tracker that matters most for you: {row}." - The {row} mapping is a fixed lookup: - cashflow → "Revenue minus all spend, weekly running balance" - roas → "ROAS column, day over day" - team → "(no row — Telegram invite for the team thread)" - product → "Cost per ATC vs ROAS — if both are bad it is the product" - mindset → "(no row — Telegram invite for the discipline thread)" - other → "(manual review)"

Question 3 — email

Copy: What is the best email to send the tracker to?

Type: email field, required, validated.

Scoring: - Captured to wiki/content/leads.md row. - Used for the 7-day nurture sequence (Phase 2).

Webhook payload (what Tally sends downstream)

{
  "submission_id": "...",
  "submitted_at": "2026-05-05T14:22:00Z",
  "answers": {
    "q1_journey": "10k_to_100k",
    "q2_bottleneck": "roas",
    "q3_email": "lead@example.com"
  },
  "source_post_id": "<from URL parameter set by ManyChat/GHL>"
}

The DM tool receives this, does the row-lookup for q2, fires the tracker DM, and writes a row to wiki/content/leads.md:

| 2026-05-05T14:22 | lead@example.com | Operator | roas | <post_id> | pending |

The pending in the last column is the telegram_join flag — flips to joined if/when the lead clicks the Telegram invite (tracked via the unique invite link the DM ships).

Form configuration notes

• No required fields except Q3. Letting people skip Q1/Q2 surfaces more leads but tagged as Other — design the manual-review DM for this case.
• No "thank you" page after submit. Redirect to t.me/gustavsgotauts directly. The lead is on their phone, in IG flow; sending them to a generic thank-you wastes the moment.
• Mobile-only validation. The audience is overwhelmingly on mobile IG. Test the form on iPhone Safari + Android Chrome before launch.