Sales & CRM

How to build an outbound email sequence as Professional Services Founders

Sales & CRMFor Professional Services Founders3 apps12 steps~24 min to set up

You bill on relationships, not volume, so every new engagement starts with a targeted outreach push that you mostly do by hand. Your process: export a contact list from HubSpot or a Google Sheet, write five slightly-different versions of the same email in Gmail, manually track who replied in a Notion table, and follow up three weeks later when you remember. A senior consultant burns two hours building the list; you spend another hour editing copy. By the time the sequence is running, two prospects have already signed with someone else. You don't need a mass-email blaster — you need a sequence that sounds like it came from you, tracks replies against HubSpot deal stage, and surfaces follow-ups before the window closes.

Build this on Starch → See the apps used

Sales & CRMFor Professional Services Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A multi-step outbound email sequence that pulls target contacts from HubSpot, drafts personalized messages in your voice, and queues follow-ups automatically when someone doesn't reply within your chosen window

A live dashboard that shows sequence performance by contact, deal stage, and service line — so you know which message is converting retainer conversations, not just who opened what

An automated handoff: when a prospect replies, Starch flags the thread in your CRM, logs it against the deal, and drafts your first response so you're not starting from a blank screen

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Sales Agent CRM CRM Email Agent

Data sources & config

Starch syncs your HubSpot contacts, companies, and deals on a schedule and syncs your Gmail threads on a schedule — both feed the sequence logic directly. Google Calendar is also synced so Starch knows your live availability when drafting meeting-ask emails. For contacts that exist on LinkedIn but aren't yet in HubSpot, Starch's LinkedIn Automation app handles outbound connection requests and profile enrichment through browser automation — no LinkedIn API needed.

Prompts to copy

Build me an outbound email sequence for my consultancy. Pull contacts from HubSpot who are tagged 'target account' and have no activity in the last 60 days. Draft a 3-touch sequence: first email introduces our strategy work for mid-market SaaS companies, second email sends a short case study PDF link, third email is a low-friction ask for a 20-minute call. Space them 5 business days apart. Log every send and reply against the HubSpot deal record.

When a contact replies to any email in this sequence, triage their message by intent — interested, not now, or unsubscribe. If interested, draft a reply in my tone offering two specific calendar slots from my Google Calendar availability. If not now, snooze the contact for 45 days and re-add to sequence. If unsubscribe, remove from all sequences and tag in HubSpot.

Every Monday at 8am, show me a sequence performance report: total contacts in sequence by stage, reply rate per touch, deals created this week from sequence replies, and which service line is getting the most traction.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot: Starch syncs your contacts, companies, deals, and owners on a schedule. Your existing pipeline stages, custom properties, and contact tags carry over — you don't rebuild anything.

2 Connect Gmail: Starch syncs your message threads on a schedule so it can read prior conversation context before drafting any outbound email. It also uses this to detect if a contact has already replied to a different thread before enrolling them in a sequence.

3 Connect Google Calendar: Starch syncs your calendar events so when it drafts meeting-request emails at step 3 of your sequence, it pulls two real available slots — not a generic 'let me know when works.'

4 Install the Sales Agent CRM starter app from the App Store, then describe your specific service lines, deal stages, and the criteria that make a contact 'ready for outreach' in plain English. Starch adjusts the schema to match your pipeline.

5 Define your target segment: tell Starch which HubSpot contact properties, tags, or deal stages should qualify someone for this sequence. Example: 'contacts at companies with 50-500 employees, tagged strategy-target, no open deal, last activity over 60 days ago.'

6 Write your sequence brief in plain English: tell Starch the goal of each touch, the tone you want, any reference materials (past proposals, case study links, service descriptions from Notion), and the send cadence. Starch drafts all three emails and shows them to you for review before anything goes out.

7 Set your reply-handling rules: tell Starch what to do when a contact replies (draft a response, create a HubSpot deal, assign to you, snooze, or unsubscribe). This is a natural-language instruction, not a flowchart builder.

8 Run a test batch of five contacts and review the drafted emails. Edit the tone brief if anything sounds off — most founders tweak it once and then leave it alone.

9 Activate the sequence. Starch sends on the schedule you set, monitors replies via Gmail sync, and handles branching automatically based on your rules.

10 Each morning, check the Email Agent's triage view: it surfaces any sequence replies by priority, shows you the drafted response, and lets you send with one click or edit inline.

11 Each Monday, review the sequence performance report: reply rate by touch, deals opened from sequence conversations, and which service line message is resonating. Adjust your copy brief directly in Starch if a touch is underperforming.

12 For prospects who haven't replied after all three touches, tell Starch to try a LinkedIn touchpoint: the LinkedIn Automation app sends a connection request with a short note through browser automation, keeping your account activity looking human-paced.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q2 2026 retainer pipeline push — 40 target accounts

Sample numbers from a real run

Contacts enrolled (HubSpot 'strategy-target' tag, no open deal, 60+ days cold)	40
Touch 1 emails sent (intro + service line hook)	40
Touch 2 emails sent (case study link, 5 business days later)	31
Touch 3 emails sent (20-minute call ask)	22
Replies received across all touches	9
Deals opened in HubSpot from sequence replies	4
LinkedIn follow-up requests sent to non-responders (browser automation)	18
Estimated pipeline value from 4 new deals (avg retainer $18k/quarter)	72,000

In the first week of April 2026, you tell Starch to pull every HubSpot contact tagged 'strategy-target' with no open deal and no activity since January. It surfaces 40. You paste in your best-performing case study URL, give Starch a one-paragraph description of your firm's positioning for mid-market SaaS ops work, and approve the three drafted emails after one round of edits — total time: 45 minutes. Over the next three weeks the sequence runs automatically. Nine contacts reply. Starch triages each reply by intent, drafts your response using two real calendar slots from your Google Calendar, and logs everything against the HubSpot deal record without you touching the CRM. Four deals open with a combined value of roughly $72,000 in quarterly retainers. The 18 contacts who never replied get a LinkedIn connection request from your account through browser automation — three accept and one sends a message the following week.

Measurement

How you'll know it's working

Reply rate by sequence touch (which email is actually starting conversations)

Deals opened per sequence run (how many pipeline entries trace back to outbound)

Days from first email to first meeting booked (is your cadence too slow or too fast for your buyers)

Retainer pipeline value created per outreach campaign (revenue weight, not just activity)

Senior consultant hours reclaimed from manual list-building and follow-up tracking

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

HubSpot Sequences (Sales Hub Professional)

Solid if your whole team lives in HubSpot and you can justify the $450+/month seat cost, but it doesn't read prior Gmail thread context before drafting, can't branch based on reply intent without workflow rules you have to build yourself, and won't do a LinkedIn follow-up step without a separate tool.

Outreach or Salesloft

Built for 20+ rep sales teams with a full-time rev ops person to configure them; pricing, onboarding complexity, and required seat minimums make them wrong-sized for a 12-person consultancy where one person owns pipeline.

Mailshake or Lemlist

Fast to set up a basic drip sequence, but they don't read your HubSpot deal stage, don't sync reply context back to your CRM automatically, and the 'personalization' is mail-merge variables rather than AI-drafted copy that knows your firm's positioning.

Manual Gmail + Notion tracking table

Free and you already know how it works, but a senior consultant is doing the scheduling, copy, and follow-up tracking — that's $150-200/hour work that doesn't bill.

On Starch RECOMMENDED

One platform — sales agent crm, crm, email agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually send email from my Gmail account, or does it spoof a from-address?

Starch sends through your connected Gmail account — replies land in your inbox, your sent folder shows the messages, and prospects see your real address. One honest note: the Gmail OAuth consent screen currently shows the name of Starch's underlying verified client rather than 'Starch' — that's on the roadmap to fix, but it won't affect deliverability or how recipients see your emails.

We already have HubSpot. Do we need to migrate everything into Starch's CRM?

No. You can keep HubSpot as your system of record. Starch syncs your HubSpot contacts, companies, deals, and owners on a schedule and uses that data to power the sequence — you don't duplicate your pipeline. The Sales Agent CRM app is there if you ever want to run a leaner setup inside Starch, but it's not required.

What happens if a contact is already mid-conversation in Gmail — will Starch accidentally send them a cold intro email?

Because Starch syncs your Gmail threads on a schedule, it reads prior conversation context before enrolling anyone in a sequence. You can set a rule like 'skip any contact with a Gmail thread in the last 90 days' and Starch will filter them out before the first send.

Is there a risk the LinkedIn automation step gets my account flagged?

The LinkedIn Automation app runs through browser automation — it mimics normal human-paced activity rather than making API calls, which is what typically triggers LinkedIn's rate limits and flags. You set the daily invite volume and Starch stays within it. That said, LinkedIn's terms are what they are: keep volumes conservative (under 20 new invites per day is a reasonable ceiling) and you're operating in the same range as someone doing outreach manually.

Can Starch write emails that sound like me, or will they obviously be AI-written?

The quality of the output depends on the brief you give it. If you paste in two examples of emails you've sent that performed well, describe your firm's tone in a sentence or two, and name the specific pain point you solve for this segment, the drafts will be close enough that you'll edit punctuation, not substance. Most founders do one review round when they first set it up and then run it unedited after that.

Does Starch store all my email and contact data permanently?

Starch is a live data platform, not a long-horizon data warehouse. Your HubSpot and Gmail data is synced on a schedule and available for your apps and automations to act on — it's not designed as a permanent archive of your full email history. If you need years of historical data for compliance or analytics, keep that in HubSpot or your email provider.