Back to BlogView the featured project — Client Intake Agent
AI & Tech

Building the Client Intake Agent: A Notion Pipeline for the First 72 Hours

A Notion custom agent that automates the highest-friction part of freelance client ops.

Summer Chang

Summer Chang

April 1, 2026 · 8 min read

Client

Self (freelance practice)

Role

AI Product Designer & Builder

Tools

Notion Custom Agents, Gmail, Google Calendar, Notion Calendar, Figma

Timeline

Notion Agent Hackathon 2026

tl;dr

Running a solo design practice, the first 72 hours after a new inquiry are the highest-friction window — follow-up emails, portfolio examples, booking confirmations, proposal drafts. I built a Notion custom agent with a 9-step pipeline: auto-send where timing matters, Gmail drafts where relationships matter, and portfolio matching pulled from a STAR-format case study database. Submitted to the Notion Agent Hackathon 2026 as a free Marketplace template.

9

Automated pipeline steps

0 min

Manual onboarding per client

Free

Notion Marketplace template

the problem

The first 72 hours are where leads go cold

Running a freelance design practice means wearing every hat. The first three days after a new inquiry are the most time-sensitive — and the most manual.

Every new lead meant writing a personalized follow-up, attaching relevant portfolio examples, sending a booking confirmation, drafting a day-before reminder, following up if they went quiet, then drafting a proposal after the call. One dropped ball and the lead goes cold.

The work isn't hard. It's just repetitive enough to create a bottleneck when business picks up — and every manual step is a place where things get dropped.

I needed a front desk for client ops, not another checklist app.
the pipeline

Nine steps — one form submission

The entire system fires from a single trigger: a client submitting the intake form. No manual steps between form and a fully set-up project workspace.

StepActionSend rule
1 — IntakeLead submits formTrigger
2 — Follow-upBranded Gmail draft with portfolio examplesDraft — you review
3 — Book a callLead self-schedules via booking linkLead action
4 — ConfirmationBranded confirmation with meet linkAuto-sends instantly
5 — Day-before reminderReminder with join + reschedule optionsAuto-sends at 7am
6 — Write proposalAgent drafts scope + portfolio matchDraft — you review
7 — Send proposalFinalized proposal to clientDraft — you review
8 — ContractDocuSign contract for signingDraft — you send
9 — DepositQuickBooks invoice for 50% upfrontDraft — you send
architecture

Auto-send vs. human in the loop

The hardest part of the build was trigger logic — deciding what should fire automatically and what should land as a Gmail draft. The rule I landed on: auto-send only when the content never changes and timing matters. Everything else gets a draft, because client relationships deserve a human touch before anything goes out.

decisions

Three design decisions that made it work

Portfolio matching by service type

The agent searches a Portfolio Database and pulls 1–3 case studies matched to what the client asked about. Each project has a Best For Questions field — plain language describing which client ask that project answers. If a project has no live URL, the agent skips it automatically.

Branded HTML email templates

All emails use a centralized HTML layout — colors, fonts, logo, CTA button style defined once so every draft looks consistent regardless of which step triggered it.

Notion as single source of truth

Clients, projects, tasks, and portfolio entries all live in linked Notion databases. One place to check, one place to update — the agent reads and writes against the same structure you work in daily.

The pipeline in motion

Confirmations and reminders fire on their own. Follow-ups and proposals land as Gmail drafts. Portfolio examples attach automatically based on what the client asked for.

Built for the Notion Agent Hackathon 2026

results

What shipped

OutputDetail
Marketplace templateFree — duplicate and run in under an hour
Pipeline steps9 automated stages from intake to deposit
Portfolio matchingService-type-aware case study selection
Email systemBranded HTML templates with draft vs. auto-send rules
Known gapsDocuSign + QuickBooks are placeholder links in v1 — documented in the template

Key Takeaways

  • 1Systems design is design — map the pipeline before you automate it.
  • 2Auto-send only when content is fixed and timing is the variable — everything relational stays a draft.
  • 3Portfolio matching beats generic follow-ups — attach proof that matches the ask.
  • 4A free Marketplace template is a distribution strategy, not a compromise.
  • 5Document the manual gaps honestly — DocuSign and QuickBooks placeholders set the right expectations.

Scheduling: Notion Calendar works for booking but doesn't support reschedule/cancel links inside reminder emails — exploring Calendly with a branded wrapper for v2.

Newsletter Agent: spin the email infrastructure from this build into a standalone Notion-native newsletter engine — write, send, and manage subscribers entirely inside Notion.

what's next

Scheduling: Notion Calendar works for booking but doesn't support reschedule/cancel links inside reminder emails — exploring Calendly with a branded wrapper for v2. Newsletter Agent: spin the email infrastructure from this build into a standalone Notion-native newsletter engine — write, send, and manage subscribers entirely inside Notion.

Share this post