Client project / Sales automation

A sales engine.
Built around
your team.

Agentic sales workflow. Inbound and outbound pipeline generation, without a large internal team.

SALES SYSTEM Two pipelines. One operating logic.
↘INBOUNDSomeone raises a hand.Demo request · Content form
↙OUTBOUNDA relevant signal appears.Account profile · Role change
CONTEXT + QUALIFICATION RULES
✳
CONNECTED WORKFLOWResearch. Qualify. Prepare.

Claude + n8n + HubSpot

→
High fitPersonalized draft
Needs judgmentHuman review
Not yetRelevant nurture
Respond sooner

Less time between interest and a useful next step.

Focus the team

Clear qualification and sensible human review.

Keep context

Research, replies and next actions in the CRM.

Follow a fictional account

From signal to conversation.

Choose a route, then move through the workflow.
Explore the platforms, checks and handoffs using sample rules and records.

Sample data · No live connections
THE WORKFLOW, MADE VISIBLE

Follow the signal.

Platform-aware walkthrough
Identity & duplicate checksSending policy & opt-outsSource evidence & CRM historyExceptions → operator
One request. A traceable route to the right next step.Click a stage to inspect it ↓
STEP 01 / 05Incoming signal

The original client implementation used Claude, n8n and HubSpot. Names, scores, messages and interface screens here are illustrative; this is not the client's live system.

The operating problem

The work between
“new lead” and “good conversation”.

A form fill is only the beginning. Someone still has to research the company, judge the fit, find a useful angle and keep the record current.

Every lead starts
another round of admin.

Read the formResearch the companyJudge the fitWrite the first messageUpdate the CRMRemember to follow up

With a small sales team, research and sorting compete with the work that actually needs a person: understanding the buyer and moving the conversation forward.

The next person gets
a decision-ready handoff.

  • 01
    Why this account matters

    Company context, relevant signals and the original inquiry.

  • 02
    Why it took this route

    Qualification against the rules agreed with the client.

  • 03
    What to do next

    A useful draft, a clear owner and the follow-up attached.

MY CONTRIBUTION

Business process
through to working system.

I translated the client's sales process into qualification and routing rules, connected the tools, and shaped how the system used context to prepare drafts. The objective was a workflow the team could actually operate: fewer manual decisions about where a lead belongs, and better preparation for the decisions that remain human.

Two complementary motions

Different starting points.
The same attention to context.

01 INBOUND

Turn interest into a useful response.

A demo request or content form supplies the initial context. Enrichment adds company size, industry, role and relevant company signals, helping the team distinguish an urgent opportunity from early research.

High-fit records get a short personalized email draft, a CRM update and a meeting link when calendar availability permits. Ambiguous cases go to Slack for a quick decision. Lower-priority interest can enter a relevant nurture path.

The useful changeThe rep opens a prepared opportunity, with the original context still attached.
02 OUTBOUND

Build relevance before asking for time.

The outbound motion starts from the ideal customer profile, identified company interest or a signal such as a role change. Accounts are enriched in batches, tiered and given a practical outreach angle.

The engine prepares an email sequence and a LinkedIn note. Emails run through the reps' actual mailboxes, with replies monitored and activity logged in HubSpot. Positive responses surface quickly with a proposed next step for the rep.

The useful changeResearch, first drafts and follow-up tracking no longer depend on starting from scratch.

Inside the system

One engine. Two ways in.

The same operating logic connects inbound interest with outbound research.

INBOUND + OUTBOUND / SYSTEM FLOWCHARTFrom a raw signal to an owned conversation
ENTRY A / INBOUND

A person raises a hand

Demo or content form → n8n webhook. Preserve the original message, source and timestamp.

HubSpot formsTypeform / website · options
ENTRY B / OUTBOUND

An account matches the brief

Ideal customer profile + company-level website interest or role-change signals → research queue.

Role / company signalsDealfront / research · options
↓ Agreed source access · Traceable event ID ↓
n8n orchestrationOne shared qualification engine
01 / NORMALIZE

Match & deduplicate

Normalize fields, match HubSpot records and preserve the existing owner.

HubSpot
02 / ENRICH

Build the context

Company size, industry, role, recent news and funding signals; keep sources attached.

Apollo / Clay · options
03 / QUALIFY

Score & tier

Apply the agreed profile and intent rules. Missing evidence stays visible.

Rules + confidence
04 / ROUTE

Choose a next step

Separate clear fit, unresolved questions and lower-priority interest.

Decision + owner
FIT + EVIDENCE + CONFIDENCE
A clear
next step?
HIGH FIT

Prepare useful outreach

Claude drafts from source context. Check claims, contact details and the sending policy before release.

ClaudeGmail / Outlook · options
NEEDS JUDGMENT

Put the question with a person

Send a concise qualification brief to a reviewer. Approve outreach, request more context or choose nurture.

Slack reviewCRM task
NOT YET

Keep a proportionate nurture path

Log the reason, use relevant content and revisit when the account or buying signal changes.

HubSpot nurture
APPROVED OUTREACH

The rep takes over

Email from the connected mailbox, a LinkedIn draft and a meeting link when the calendar allows. Stop follow-ups on reply.

Rep mailboxCalendly / Calendar · options
REVIEW DECISION

Resolve the open question

A person can approve outreach, request more research or choose nurture. Record the decision and retain the source context.

Slack / team reviewDecision + owner
NURTURE + RECHECK

Revisit on new evidence

Keep the lighter content path. Rescore when account context or buying intent changes; avoid a premature sales handoff.

Nurture historyNew-signal trigger
Reply loop

Positive → rep alert & suggested next step
Unclear → review · Not now → revisit
Opt-out → stop & suppression record

HubSpot remains the shared record

Original signal, evidence, qualification, draft history, replies, ownership and follow-up return to the contact or company record.

Exceptions have an operator

Failed enrichment, stale credentials or delivery errors → retry policy, evidence and an actionable alert. Avoid duplicate sends.

Client stack: Claude, n8n and HubSpot. Other named services are potential integration choices. This public flowchart uses sample records and makes no live connections.

Inbound, with judgment built in.

Form submissions are enriched with company size, industry, role and recent company signals. High-fit leads receive a personalized draft and a customer relationship management (CRM) update, with a meeting link ready when the calendar allows. Borderline leads go to human review; lower-priority leads enter nurture.

Outbound, with the context attached.

The engine researches and tiers accounts, then prepares practical email sequences and LinkedIn notes. Email runs through the reps' actual mailboxes. Positive replies surface with suggested next steps; the activity and follow-up are logged back to HubSpot.

My role, from rules to delivery.

I worked with the client to define the qualification rules and build the connected workflow. That meant translating sales decisions into routing logic, integrating the tools, shaping the prompts and making the handoff useful to the people doing the selling.

Project-reported outcome

Next-day response → under an hour

Sales development reps spent less time manually sorting form fills. Reported for the client project. The fictional records and scores in this walkthrough illustrate the workflow; they are not the source of this result.

Design decisions illustrated in the demo

Automation with
an understandable decision trail.

Useful automation should leave the team better informed and in control of the next step.

01 / CONTEXT

Keep the source attached.

The form message, research context and company signals travel with the record. A rep can understand what prompted the draft instead of inheriting a black-box score.

02 / JUDGMENT

Make uncertainty visible.

Clear rules handle straightforward cases. Borderline records have a review path, with the open question made explicit. A lead should not become high priority just because a model can write a confident email.

03 / RELATIONSHIPS

Make the human handoff useful.

The output is a next action with context: review the draft, clarify the use case, confirm a meeting or respond to a positive reply. The system supports the rep's judgment and ownership.

04 / OPERATIONS

Work through existing tools.

The CRM remains the team record. The reps use their own mailboxes. Review arrives where the team works. A connected process is easier to adopt when it fits the operating environment.

For teams with more pipeline work than capacity

Give your team
more time for the conversation.

A similar workflow can be adapted to your qualification rules, CRM and sales process.

Discuss a sales workflow ↗Explore Plug & Play operations →