Back to examples
Sales and RevOpsInternal workflow example

Inbound lead intake and CRM relay

Capture an inquiry, validate it, add useful context and route it to CRM or human review.

This example explains a workflow design and its controls. It does not represent verified client results. Tooling and benefits must be validated in each project's context.

Inbound lead intake and CRM relay editorial cover

Solution example

Inbound lead intake and CRM relay

Capture an inquiry, validate it, add useful context and route it to CRM or human review.

The design connects these steps: Website form → Supabase → Research → Sales summary → HubSpot → Resend → Digest. Rules, exceptions and approvals are defined before external actions are connected.

Workflow map

Lead intake from form to CRM

The view keeps the production logic and omits only internal status logs so it is easy to read.

Main pathInternal reviewSalesNoYesYesYesBack to CRMStart1. Check and score leadValidate | priority | offer | next action2. Read form + websiteSubmitted fields + website pagesPython3. Research public webCompany | contact | sourcesTavily4. Build sales summaryNeed | questions | reply draftOpenRouter5. Prepare sales briefPriority | context | source trailSpam risk?6a. Create/update CRMContact | company | deal | task | noteHubSpot7a. Alert salesPriority | likely need | next actionResendEnd6b. Hold out of CRMNo sales record yet7b. Ask for spam reviewFlags | context | lead IDResendReplyreceived?EndNo replyReceive replyReviewer responseResend webhookReply saysNOT SPAM?EndMark not spamReady to enter CRM

Main database: Supabase

The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.

Tool icons

SupabasePythonTavilyOpenRouterHubSpotResend

The scenario

Design scenario: Capture an inquiry, validate it, add useful context and route it to CRM or human review. The starting point is a workflow with scattered information, manual steps and responsibilities that need to be made explicit.

Before implementation, we review available data, responsible owners and decisions that need approval. Understand the workflow first.

The approach

The design connects these steps: Website form → Supabase → Research → Sales summary → HubSpot → Resend → Digest. Rules, exceptions and approvals are defined before external actions are connected.

AI can help classify, extract or draft; sensitive actions retain human review. Clear controls at each step.

What was used

Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.

In practice, the build combined Website form, Supabase, Python/FastAPI, OpenRouter, Tavily, HubSpot, Resend. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.

Website formSupabasePython/FastAPIOpenRouterTavilyHubSpotResend

Workflow design

Manual approach and proposed workflow

Manual approach

1Lead arrives from website or campaign
2Someone checks the inbox
3Company context is researched manually
4Fields are copied into HubSpot
5Spam is cleaned after entering CRM
6Owner gets an ad hoc alert

Proposed workflow

1Website form writes one lead record
2Rules validate priority and spam risk
3Public research enriches company/contact context
4LLM creates a consistent sales brief
5Spam-risk leads go to review before CRM
6Qualified leads sync to HubSpot and sales email

Visible artifacts

  • Lead event run log
  • HubSpot timeline note template
  • Resend sales-notification example
  • Spam-review email with NOT SPAM recovery
  • Weekly lead digest

Controls

  • Clear validation rules before AI summary
  • Spam branch skips HubSpot until reviewed
  • NOT SPAM reply resumes the same CRM path
  • Every major step writes an event
  • Manual retry endpoint for one lead

What this aims to improve

The aim is to reduce manual coordination and make records, exceptions and the next action visible. Any improvement must be validated against the project's own data and operating conditions.

Project scoping establishes a baseline and success criteria so proposed improvements can be tested. Validate the benefit in context.

The workflow in one line

01Website form02Supabase03Research04Sales summary05HubSpot06Resend07Digest

Tooling and boundaries

The design shows how Website form, Supabase, Python/FastAPI, OpenRouter, Tavily, HubSpot, Resend can work together. Final tooling, scope and controls are agreed for each project.

Integrations need appropriate permissions, run logs and a way to review exceptions. The team should be able to understand and operate the workflow.

What this example demonstrates

Design components
  • Form intake
  • Lead event log
  • CRM sync
  • Fit scoring
  • Spam review
  • Sales digest
Intended controls
  • Clear validation rules before AI summary
  • Spam branch skips HubSpot until reviewed
  • NOT SPAM reply resumes the same CRM path
  • Every major step writes an event
  • Manual retry endpoint for one lead

Discuss a similar workflow.

Discuss your workflow

Free initial conversation. No obligation.

Ductio newsletter

Practical ideas for better work.

Get ideas on automation, connected systems and more reliable processes.

Ductio
DuctioSYSTEMS
Custom automation, connected systems and support for teams that need reliable, documented workflows.
Operating focus

CRM operations, reporting workflows, approvals, document handling, and AI-assisted internal tools.

Copyright © 2026 Ductio. All rights reserved.

Discuss your workflow

Free initial conversation. No obligation. We will work through the details together.

Add more details (optional)

We use these details to respond to your inquiry. Please do not include passwords or confidential business data. Privacy notice

You can also email contact@ductiosystems.com.