Carlos EscasainCommercial Systems & Process Architect
ENES

Process case / 06 · Entry point vs. process

Designing an inbound lead process beyond form submission

A fictional case showing why “web-to-lead” is a technical entry point, not a process architecture.

Fictional scenario7 min readUpdated 28 Sep 2026
Fictional scenario

Independently created. Contains no employer or client implementation detail, internal names or figures.

01The outcome

Every valid submission reaches the right owner in the right subsidiary, is answered on a clock and ends in a recorded decision—converted, nurtured or disqualified with a reason.

The reality

Every web form creates a CRM lead—and nobody owns what happens next.

Key dimension

Entry point vs. process

Key decision

Treat the form as one entry point into a lead lifecycle with rules for validity, duplicates, territory, ownership and closure.

ContextA B2B company generates inbound leads from its website across several countries and subsidiaries. The integration works: every form creates a CRM lead. The process around it does not exist.

Disciplines involvedProcess ArchitectureRevenue OperationsSystems & CRM Architecture
Systems and partiesWebsiteCRMMarketing automation

02The reality · current state

What actually happens today.

  • Every submission becomes a lead—including job applications and support requests
  • Existing customers re-enter as new leads
  • Leads from some countries have no owner
  • Nobody knows how quickly leads are answered
  • Unqualified leads stay open indefinitely
  • Sales and Marketing disagree on what a good lead is

03Target process

8 stages, 3 roles, 2 systems.

Each stage sits in the lane that owns it and shows what happens in each system at that moment. Select a stage for its anatomy; read the model through controls, exceptions or automation fit.

Operating model / swimlaneInbound leadWebsite form submitted → Converted, nurtured or disqualified with a reason

Stages, owners, system touches and handoffs.

Marketing opsValidity & routing rules
Inside salesResponse & qualification
SalesAcceptance & conversion
WebsiteForm & consent
CRMLead lifecycle & matching
Lane / stage
Marketing → Inside sales
Inside sales → Sales
Submission recordValidation resultSubsidiaryOwner + response clockCriteriaCadenceAccount + opportunity
Human actionSystem actionDecisionApproval gateLifecycle stateSystem touchHandoffAuthority transferException return
Stage anatomy · 03 / 08

Deduplication

System actionAssist — person confirms
  1. Trigger

    Valid lead

  2. Decision

    Is this person or company already known—as a lead, a contact or a customer?

  3. Owner

    Marketing operations (rules) · Sales operations (merge decisions)

  4. System action

    The CRM matches against leads, contacts and accounts, including customers

  5. Data state

    Lead · Matched

  6. Next stage

    04 Subsidiary resolution

Information required
  • Email and domain
  • Company name and country
  • Existing records
Controls
  • A lead from an existing customer never starts a new acquisition journey
Exceptions
  • Existing customer — Becomes an activity on the account, routed to its ownerDetected: Account match · Owner: Account owner · Routed to the account team
  • Probable duplicate lead — Merged into the open lead; history keptDetected: Match rule · Owner: Marketing ops · Merged by rule, or reviewed
Automation suitability

Assist — person confirms. Matching is automated; uncertain merges are reviewed.

    1. Trigger

      Valid lead

    2. Decision

      Is this person or company already known—as a lead, a contact or a customer?

    3. Owner

      Marketing operations (rules) · Sales operations (merge decisions)

    4. System action

      The CRM matches against leads, contacts and accounts, including customers

    5. Data state

      Lead · Matched

    6. Next stage

      04 Subsidiary resolution

    Information required
    • Email and domain
    • Company name and country
    • Existing records
    Controls
    • A lead from an existing customer never starts a new acquisition journey
    Exceptions
    • Existing customer — Becomes an activity on the account, routed to its ownerDetected: Account match · Owner: Account owner · Routed to the account team
    • Probable duplicate lead — Merged into the open lead; history keptDetected: Match rule · Owner: Marketing ops · Merged by rule, or reviewed
    Automation suitability

    Assist — person confirms. Matching is automated; uncertain merges are reviewed.

04Key dimension · Entry point vs. process

“Web-to-lead” is an entry point, not a process

The naive design stops where the technical integration stops. The designed process starts there.

The naive design
  1. Form
  2. CRM lead
The designed process
  1. 01Form submission
  2. 02Validation
  3. 03Deduplication
  4. 04Subsidiary resolution
  5. 05Ownership
  6. 06Qualification
  7. 07Follow-up
  8. 08Conversion or disqualification

Everything after the arrow is where leads are lost: duplicates of existing customers, unowned countries, unanswered forms and leads that age for months without a decision.

05Ownership & decision rights

One accountable role per decision.

Decision rights for Inbound lead
DecisionMarketing opsInside salesTeam leadSalesChannel mgr
02Define a valid leadA AccountableC ConsultedNot involvedC ConsultedNot involved
03Merge a probable duplicateA AccountableNot involvedNot involvedI InformedNot involved
04Own the territory rulesR ResponsibleNot involvedNot involvedA AccountableC Consulted
05Reassign after an SLA breachNot involvedI InformedA AccountableNot involvedNot involved
06Qualify or nurtureNot involvedA AccountableNot involvedC ConsultedNot involved
08Accept and convertI InformedR ResponsibleNot involvedA AccountableNot involved
  1. 02Define a valid lead
    AAccountable
    Marketing ops
    CConsulted
    Inside sales · Sales
  2. 03Merge a probable duplicate
    AAccountable
    Marketing ops
    IInformed
    Sales
  3. 04Own the territory rules
    AAccountable
    Sales
    RResponsible
    Marketing ops
    CConsulted
    Channel mgr
  4. 05Reassign after an SLA breach
    AAccountable
    Team lead
    IInformed
    Inside sales
  5. 06Qualify or nurture
    AAccountable
    Inside sales
    CConsulted
    Sales
  6. 08Accept and convert
    AAccountable
    Sales
    RResponsible
    Inside sales
    IInformed
    Marketing ops
AAccountableRResponsibleCConsultedIInformedExactly one A per decision

06Exceptions & failure paths

9 exception paths, each with an owner and a destination.

01 Form submissionSpam or bot

Discarded and counted—never routed

Detected by
Form protection
Owner
Marketing ops
Route
Discarded and counted
02 ValidationNot a sales request

Routed to the right team, with a receipt to the sender

Detected by
Request type
Owner
Marketing ops
Route
Routed to support, HR or procurement
03 DeduplicationExisting customer

Becomes an activity on the account, routed to its owner

Detected by
Account match
Owner
Account owner
Route
Routed to the account team
03 DeduplicationProbable duplicate lead

Merged into the open lead; history kept

Detected by
Match rule
Owner
Marketing ops
Route
Merged by rule, or reviewed
04 Subsidiary resolutionCountry served by a distributor

Handed to the partner; the outcome is tracked

Detected by
Territory rule
Owner
Channel manager
Route
Passed to the partner, with consent
05 OwnershipNo response within SLA

Reassigned and counted as a breach

Detected by
SLA clock
Owner
Team lead
Route
Reassigned to another owner
06 QualificationNot ready yet

Nurtured with a revisit date—not an open lead forever

Detected by
Inside sales
Owner
Marketing ops
Route
Nurture with a revisit date
07 Follow-upNo reply after the attempt cadence

Closed with a reason code, then nurtured

Detected by
Inactivity rule
Owner
Inside sales
Route
Closed as unresponsive; nurtured
08 Conversion or disqualificationSales rejects the lead

Returned with a reason; criteria reviewed on a fixed cadence

Detected by
Sales
Owner
Marketing ops
Route
Returns to 06 Qualification

07Process ↔ system

The process question first. Then the system question has an answer.

StageAccountableSystem actionData stateAutomation
01Form submissionMarketing (form) · Legal (consent wording)The form posts to the CRM with source, consent and page contextSubmission · ReceivedAutomate
02ValidationMarketing operationsRules check completeness and request type; non-sales requests are routed outLead · ValidAutomate
03DeduplicationMarketing operations (rules) · Sales operations (merge decisions)The CRM matches against leads, contacts and accounts, including customersLead · MatchedAssist — person confirms
04Subsidiary resolutionMarketing operationsTerritory rules map country, region and segment to a subsidiaryLead · Subsidiary assignedAutomate
Accountability transfers — Marketing → Inside sales
05OwnershipInside sales team leadThe CRM assigns by queue and capacity and starts the response clockLead · OwnedAutomate
06QualificationInside salesQualification criteria are recorded as observable factsLead · Qualified or notKeep human
07Follow-upInside salesThe attempt cadence is tracked; inactivity closes the lead with a reasonLead · WorkingAssist — person confirms
Accountability transfers — Inside sales → Sales
08Conversion or disqualificationSalesConversion creates or links the account, contact and opportunity; disqualification records a reasonOpportunity · Open, or Lead · DisqualifiedKeep human
Process question: P1What counts as a valid lead?
System question: S1Which rules run on submission, and where do non-sales requests go?
Process question: P2Which subsidiary owns it?
System question: S2Which territory rules assign it, and who maintains them?
Process question: P3How quickly must someone respond?
System question: S3When does the clock start, and what happens at a breach?
Process question: P4When should a lead become an account?
System question: S4Does conversion create or link—and what prevents a duplicate account?

08The second layer

Questions that change the design.

Validity

  1. What counts as a valid lead?
  2. What happens with submissions from existing customers?
  3. Which requests are not leads at all?

Ownership

  1. Which subsidiary owns it?
  2. How quickly must someone respond—and who owns that clock?
  3. Who owns unqualified leads?

Lifecycle

  1. When should a lead become an account?
  2. What happens after inactivity?
  3. Who may disqualify, and with which reasons?

09Measurement

Process health, defined by owner and action.

No values are shown: in a design, the definition is the deliverable.

LeadingStages 05 → 06
Speed to first response

Assignment to first contact, by subsidiary

Owner
Team leads
Triggers
Adjust queues and capacity
ControlStage 03
Duplicate rate

Submissions matched to existing leads, contacts or customers

Owner
Marketing operations
Triggers
Route existing customers earlier; fix the forms
ControlStages 04 → 05
Unowned lead age

Leads without an owner, by age

Owner
Marketing operations
Triggers
Close the gaps in the territory rules
ControlStage 08
Sales acceptance rate

Qualified leads accepted by Sales, with rejection reasons

Owner
Sales management
Triggers
Revise the qualification criteria with Sales
LaggingStages 02 → 08
Lead-to-opportunity conversion

Valid leads that became opportunities, by source

Owner
Marketing
Triggers
Invest by source on outcomes, not on volume

10What the work produces

Outputs and connections.

  1. 01Lead lifecycle & states
  2. 02Validity & deduplication rules
  3. 03Territory & ownership model
  4. 04Response SLA
  5. 05Qualification criteria
  6. 06Funnel KPIs by source
Disciplines involvedProcess ArchitectureRevenue OperationsSystems & CRM Architecture