Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 37 ยท Projects and Practice

Project: From Form Submission to Closed Deal

Design and simulate an end-to-end HubSpot setup: a form, lead scoring, lifecycle stages, owner rotation, a deal pipeline and a revenue report, with a runnable Python simulation of the whole flow.

In this project you plan the lifecycle of a lead from a website form to a closed-won deal, then reproduce the logic as a simulation so you can test your rules before touching a real account. Along the way you will use almost everything from the earlier chapters: forms, lifecycle stages, scoring, workflows, rotation, deals and reports.

HubSpot cannot run on this site, so the build steps below are written for you to follow in your own (free or trial) portal, and the Python code is a stand-in that verifies the design. Menu names can shift slightly between releases.

The scenario

Northwind Cloud sells project software. Visitors fill in a "Request a demo" form with name, email, company, team size and country. Marketing wants only well-fitting leads handed to sales; sales wants fair distribution; the manager wants a weekly report of pipeline by stage.

Step 1: Design on paper

Piece Decision
Form Request a demo: email, first name, company, team size (select), country
Score +20 team size 50 or more, +10 target country, +40 demo form, -10 free email domain
Qualify Score 50 or higher moves a Lead to MQL
Owners Round-robin Ana, Ben, Chi (available only)
Deal pipeline Qualified (20%), Demo done (40%), Proposal (60%), Contract (80%), Closed won, Closed lost
Report Open pipeline amount by stage, and weighted forecast

The flow

Form Contact created, lead
Score Fit plus engagement
Workflow MQL, owner, task
Deal Pipeline to closed won

Each step is testable

1 / 2

Step 2: Build in HubSpot

  1. Marketing > Lead Capture > Forms: create the form and publish it, embedding it on a page (or share the hosted link). Map fields to contact properties; set lifecycle stage to Lead through the form's options.
  2. Settings > Properties: create team_size_band (enumeration) if it does not exist.
  3. Scoring: create a score with the points above, or a number property updated by a workflow.
  4. Automation > Workflows (contact-based): trigger on score at least 50 and lifecycle Lead; set lifecycle to MQL; rotate owner; create a task "Call within 4 hours"; send internal notification.
  5. Settings > Objects > Deals > Pipelines: edit the stages and probabilities.
  6. Reporting: a bar report of deal amount by stage with filter "pipeline is Northwind Sales", and add it to a dashboard.

Step 3: Simulate the design

Python Form to MQL to owner (stand-in simulation)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Eli scores 30 and stays a lead (nurtured by marketing), the others become MQLs, and owners rotate in order. If your real portal disagrees, compare the workflow's enrollment history with this table.

Step 4: Move deals through the pipeline

Python Deals, probabilities and the weekly report

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Step 5: Test and harden

  • Submit the form yourself with three test emails; confirm the contact, score, owner and task.
  • Check what happens when the form is submitted twice by the same email (HubSpot updates the existing contact).
  • Add a suppression list for internal addresses.
  • Look at the workflow History and fix any failed actions.
  • Add a goal: exit when a meeting is booked.

Stretch goals

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. In the simulation, why did Eli not become an MQL?

    Demo form +40, free email -10 gives 30, below the cutoff.
  2. 2. Which workflow action hands the new MQL to sales fairly?

    Rotation assigns owners in turn.
  3. 3. What does the weighted pipeline report?

    Weighting by probability gives an expected-value forecast.

Summary

  • A good HubSpot setup starts with a written design: form, score, qualification, owners, pipeline, report.
  • Workflows connect the pieces; test with sample records and read the history.
  • Simulating the rules first catches logic errors cheaply.

Next: Project: A Support SLA Monitor