Skip to main content
Intempt
Coming soon

Lead to customer

Shows how many demo requests turn into booked meetings, completed demos, proposals and closed deals, and which lead sources actually convert.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Trace demo requests to closed deals

    Coming soon

    Blu builds a step

About this recipe

When to use it

Marketing and sales usually track leads in two different systems that never fully agree. This funnels real deal-stage and meeting events end to end, from lead to customer, with stage velocity and forecasted revenue built in.

What it delivers

Builds a lead-to-customer pipeline funnel from real deal_stage_changed and meeting events, with per-stage velocity and a forecasted revenue figure attached.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Shows how many demo requests turn into booked meetings, completed demos, proposals and closed deals, and which lead sources actually convert.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Trace demo requests to closed dealsCreate a Funnel report called "Lead to Customer". Steps: 1. Event "Form submitted" where form_id matches a demo-request form: "Requested Demo" (alternative: Deal created with stage matching "Discovery" or similar) 2. Event "Meeting scheduled" linked to the user (via primary_user_id or user_ids): "Scheduled Demo" 3. Event "Meeting scheduled" where canceled_at is null AND end_time < now (i.e. meeting actually happened, no subsequent meeting_canceled): "Completed Demo" 4. Event "Deal stage changed" where new_stage matches a "Proposal" pattern: "Proposal Sent" 5. Event "Deal won": "Deal Closed" Conversion window: 60 days Breakdown: By Users.UTM source attribute (first-touch lead source on the User record). Top 8 sources. Compare: Previous period (prior 60 days) For each step, also surface: - Median time-to-convert from previous step (stage velocity) - Per-source conversion rate at each stage - Forecast revenue: Sum of Deal created.amount (or current Deal stage changed.amount) for deals currently at this stage × historical conversion-to-won rate Annotations: - Flag the lead source with highest end-to-end win rate AND volume: invest more there. - Flag any stage where median velocity exceeded 14 days (deal-stalled signal). - Highlight any source with rising volume but falling win rate (lead-quality erosion). Surface the projected closed-won revenue for the period based on current pipeline volumes. Taxonomy notes: - "demo_requested", "demo_completed", "proposal_sent" as standalone events do not exist. They are derived from Form submitted, Meeting scheduled, and Deal stage changed.new_stage respectively. - Deal stage changed has previous_stage and new_stage properties; deal stages are project-configured (the Deals object has stage as a relation attribute). - Meeting scheduled has canceled_at, start_time, end_time: completion is derived from these. - Users.UTM source is the canonical lead-source User attribute.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /lead-customer-sales in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe