Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

AI lead qualification

A detailed enquiry can contain useful buying signals that never reach the CRM: the requested service, a delivery constraint, or an unanswered question about scope. Norml builds AI lead qualification around your written fit criteria. The workflow reads an eligible enquiry, checks the approved CRM context, and prepares a qualification record with evidence for each criterion. Your team can see why a lead was flagged and correct the assessment before it affects follow-up.

Qualification built around your sales process

The scope covers interpreting an enquiry and preparing a reviewable CRM update. Your team defines what counts as a suitable opportunity.

Solution
Automations
Tools
HubSpot, n8n, Claude
Trigger
A new enquiry enters the agreed intake source with a stable enquiry ID and enough text to assess.
Outcome
A criterion-by-criterion assessment, missing-information list and suggested next action reach a review queue. Approved fields can then be written to the matching HubSpot record.

Fit criteria with supporting evidence

We turn your qualification rules into named criteria, such as service fit, location or required capability. Each assessment carries the relevant enquiry text or approved CRM fact. A missing answer stays unknown; an enthusiastic tone does not become evidence of budget or buying authority.

HubSpot matching and protected fields

The workflow looks up the contact using agreed identifiers and checks whether the enquiry has already been processed. We map approved assessment fields and preserve human-owned lifecycle stages, deal stages and notes. A repeated enquiry from the same person remains a separate event where your process requires it.

Review and exception handling

Ambiguous requests, conflicting facts and failed CRM updates go to an owner. The model cannot invent new qualification rules or follow instructions embedded in an enquiry. We keep a processing record so an interrupted run can be reconciled without silently overwriting a salesperson’s correction.

What we need from your sales team

A written qualification rubric

Supply examples of suitable, unsuitable and unclear enquiries, with the reasons your team would record. Include which criteria are mandatory and which merely inform a conversation.

An approved intake and CRM map

We need the enquiry source, record identifiers, HubSpot property definitions and permitted access. Decide which existing context may be sent to the model and which data must remain outside the workflow.

A named decision owner

Choose who reviews ambiguous assessments, approves CRM changes and maintains the criteria. Define whether a completed review creates a follow-up task, updates fields or only records a recommendation.

Review each enquiry against your criteria

  1. Compare assessments with your team

    We test representative enquiries against decisions made by your sales team. Disagreements reveal unclear criteria, missing inputs or cases that should remain manual.

  2. Connect the reviewed handoff

    We build intake, contact matching, assessment storage and the agreed HubSpot update. Failure handling covers missing contacts, duplicate events, denied access and an update interrupted after submission.

  3. Test changes before releasing them

    Your team checks evidence, field protection and uncertain cases. We document how to change a criterion, pause processing and review failed runs without submitting duplicate updates.

Lead qualification questions

Is this the same as routing a website lead?
Routing moves an enquiry to an owner using known rules. Qualification interprets the enquiry against your fit criteria and records what is known or missing. A routing workflow can supply the input, while qualification remains a separate reviewable step.
Will it automatically reject leads?
Automatic rejection is excluded from this starting scope. An unclear or apparently unsuitable enquiry receives a review status and reasons. Your team decides whether to request more information, continue the conversation or close it.
Can it produce a lead score?
We can implement a score based on your explicit rubric. That score is a summary of the selected criteria, not a predicted conversion probability or HubSpot’s native predictive scoring. We agree its meaning before anyone uses it to prioritize work.
Can it enrich leads from the web?
Public-web enrichment needs a separate source and data-use scope. This workflow starts with the submitted enquiry and approved CRM information. It does not assume access to paid databases or treat an unverified company claim as a fact.
Share your intake source, HubSpot fields and a few anonymized examples with your team’s decisions. We’ll identify the assessment and review steps worth building.

Show us how you qualify an enquiry

Discuss your automation