Sales & CRM

How to set up your first crm as Small Marketing Teams

Sales & CRMFor Small Marketing Teams2 apps11 steps~22 min to set up

Your team runs HubSpot for deals, GA4 and Amplitude for behavior, Meta and Google Ads for spend, and Customer.io or Klaviyo for nurture — and none of it talks to each other. Every Monday you rebuild the pipeline-contribution report by hand: exporting HubSpot deals to a spreadsheet, joining it against GA4 session data, pulling Meta Ads cost from a separate CSV, then formatting it before the 9am CEO sync. That's 90 minutes of copy-paste before anyone has had coffee. Meanwhile your CRM contact records are stale because nobody has time to update them, and LinkedIn profiles for key prospects haven't been touched since Q3. You need a CRM layer that's wired to the rest of your stack — not a $1,200/month HubSpot upgrade with a six-week admin project to configure it.

Build this on Starch → See the apps used

Sales & CRMFor Small Marketing Teams2 apps11 steps~22 min to set up

Outcome

What you'll set up

A CRM tailored to your marketing team's language — MQL stage, campaign source, content touchpoints, deal influence — not a generic sales pipeline someone else designed

Automated HubSpot deal sync and LinkedIn profile enrichment so contact records stay current without anyone doing data entry

A weekly pipeline-contribution report that pulls HubSpot deals, Gmail thread history, and live ad platform data in one place — built from a natural-language description, not a BI tool

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

CRM Sales Agent CRM

Data sources & config

Starch syncs your HubSpot contacts, companies, and deals on a schedule as a scheduled-sync provider — this powers the CRM's deal view and activity history. Gmail is also a scheduled-sync provider, so email thread context appears on every contact record automatically. LinkedIn enrichment runs through browser automation — no LinkedIn API needed. GA4, Meta Ads, and Google Ads connect from Starch's integration catalog and are queried live when your pipeline-contribution report runs. Slack is also connected from Starch's integration catalog to deliver your Monday morning report.

Prompts to copy

Build me a CRM for a 3-person marketing team. Contacts should have fields for: company, title, MQL date, original lead source (paid search / paid social / content / event / outbound), current lifecycle stage (MQL / SQL / Opportunity / Closed Won / Churned), assigned SDR or AE, and last meaningful touchpoint date. Deals should be linked to contacts and show pipeline stage, associated campaign, and estimated influenced revenue. I want to be able to ask 'which contacts came from our Q1 content push and haven't moved to SQL in 30 days?' and get a real answer.

Connect HubSpot and sync contacts, companies, and deals on a schedule. For each contact, also enrich their LinkedIn profile through browser automation so I always have their current title and company. Flag any contact whose last activity in Gmail is older than 21 days and surface them in a 'needs follow-up' view.

Build me a weekly pipeline-contribution report. Pull open and newly closed deals from HubSpot, join them to their original lead source field, and pull live session and conversion data from GA4 from Starch's integration catalog. Show me MQLs created this week, SQLs created this week, pipeline influenced by marketing this month, and which campaigns are generating the highest close rates. Send it to me as a Slack message every Monday at 8am.

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

Walkthrough

Step-by-step

1 Connect HubSpot in Starch — it syncs contacts, companies, deals, and owners on a schedule. This is your source of truth for pipeline data; you don't need to change anything about how your sales team uses HubSpot today.

2 Connect Gmail as a scheduled-sync provider. Starch pulls message history so every contact record in your CRM shows recent email threads without you copying anything manually.

3 Start from the CRM starter app in the Starch App Store, then describe your actual schema: MQL date, lead source, lifecycle stage, campaign attribution fields, and any custom deal fields your team actually uses.

4 Tell Starch to run LinkedIn enrichment for your contact list through browser automation — it visits each profile and updates title, company, and connection status on a schedule. No LinkedIn API credentials required.

5 Connect GA4, Meta Ads, and Google Ads from Starch's integration catalog. These are queried live, so your reports always reflect current data without a manual export.

6 Build your pipeline-contribution view: describe to Starch what you want — deals by original lead source, MQL-to-SQL conversion rate by channel, influenced revenue this quarter — and Starch assembles the app.

7 Set up the 'needs follow-up' filter: tell Starch to surface contacts whose last Gmail activity is older than 21 days and whose lifecycle stage is still MQL or SQL. This replaces the spreadsheet you currently rebuild by hand each week.

8 Connect Slack from Starch's integration catalog and set up the weekly pipeline-contribution automation: every Monday at 8am, Starch pulls HubSpot deals, GA4 sessions, and ad spend, assembles the report, and posts it to your #marketing-ops channel.

9 For contacts sourced from LinkedIn outbound campaigns, wire the LinkedIn Automation starter app so Starch can track connection requests, message replies, and profile views through browser automation and write those touchpoints back to the contact record.

10 Run your first 'stale MQL' query — ask Starch in plain language: 'Which contacts came from our Q1 LinkedIn campaign, are still in MQL stage, and haven't had a Gmail touchpoint in the last 30 days?' Review the list and assign follow-up tasks directly from the CRM.

11 Share the pipeline-contribution dashboard with your CEO as a read-only link before your next Monday sync. You've replaced the 90-minute spreadsheet rebuild with a live view that updates automatically.

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

April 2026 Pipeline Contribution Review

Sample numbers from a real run

MQLs created (April)	47
SQLs created (April)	18
Pipeline influenced by marketing ($)	214,000
Paid social spend attributed to influenced pipeline ($)	11,400
Contacts enriched via LinkedIn automation	312
Stale MQLs surfaced for follow-up	23

In April, your team ran a content-led campaign targeting mid-market operations personas on LinkedIn and Google. The Starch CRM pulled 47 new MQLs from HubSpot, tagged each one with original lead source (22 from paid LinkedIn, 14 from organic content, 11 from paid search), and showed their journey through lifecycle stages. The pipeline-contribution report — built once in Starch, running automatically every Monday — showed $214,000 in influenced pipeline for the month against $11,400 in paid social spend, a 18.8x influenced-pipeline ROI you'd never had visibility into before because joining HubSpot deals to Meta Ads cost data required a manual spreadsheet. The 'stale MQL' query surfaced 23 contacts from the Q1 campaign still stuck at MQL stage with no Gmail activity in 21+ days. Your SDR team worked the list and converted 6 to SQL that week. LinkedIn enrichment updated 312 contact records automatically — meaning when you briefed the CEO on the MQL dip in week two, you already knew it was a paid search CPL spike, not a content volume issue, because the data was current.

Measurement

How you'll know it's working

MQL volume by channel and week (paid social, paid search, organic content, events)

MQL-to-SQL conversion rate broken down by original lead source

Marketing-influenced pipeline ($) as a share of total open pipeline

Contact record freshness — percentage of active contacts with a LinkedIn-enriched profile updated in the last 30 days

Time-to-follow-up on stale MQLs (days between MQL creation and next logged touchpoint)

Comparison

What this replaces

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

HubSpot Marketing Hub (Pro or Enterprise)

Gives you native deal-to-campaign attribution, but starts at $800–$3,200/month and requires significant admin time to configure custom properties, lifecycle stages, and reporting views — overhead a 3-person team usually can't absorb.

Salesforce + Marketing Cloud

Best-in-class attribution and segmentation at scale, but the implementation cost and admin burden are realistically a 6-month project with a dedicated RevOps hire — not a realistic option without dedicated ops headcount.

Google Sheets + manual exports

Free and flexible, but the weekly pipeline report rebuild takes 60–90 minutes of manual joins every single Monday, and contact records go stale within weeks because nobody has time to update them.

Looker Studio (free BI layer)

Good for visualizing data from a single source, but joining HubSpot deals against GA4 sessions and Meta Ads spend still requires manual data connectors and a working knowledge of Looker's schema — it doesn't build the report for you.

On Starch RECOMMENDED

One platform — crm, sales agent crm 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

We already use HubSpot — does Starch replace it or sit on top of it?

Starch sits on top of HubSpot. It syncs your HubSpot contacts, companies, and deals on a schedule and lets you build custom views, reports, and automations on top of that data. Your sales team keeps working in HubSpot exactly as they do today. Starch gives you the attribution layer and the custom CRM surface you'd normally need a BI tool or a RevOps hire to build.

Can Starch actually pull data from GA4, Meta Ads, and Google Ads together in one report?

Yes. GA4, Meta Ads, and Google Ads connect from Starch's integration catalog and are queried live when your report runs. You describe the report in plain language — 'show me MQLs by channel, pipeline influenced this month, and cost-per-MQL by platform' — and Starch builds it. The data isn't stored in Starch; it's pulled live from each platform when the report runs, so it reflects current numbers without a manual export.

How does LinkedIn enrichment work — do I need a LinkedIn API key or Sales Navigator?

No API key needed. Starch runs LinkedIn enrichment through browser automation — it navigates LinkedIn the way a human would and pulls current profile data. You do need to connect your LinkedIn account in Starch. Sales Navigator is not required, though if you have it, Starch can access that data too.

Is Starch SOC 2 certified? We'd need to clear this with our security team.

Not yet — Starch is not currently SOC 2 Type II certified. That's worth knowing before you route sensitive customer data through it. If your security team has a hard requirement for SOC 2, that's a real constraint today.

The report I need joins HubSpot deals to GA4 sessions by campaign. Can Starch actually do that join, or does it just display data from each source separately?

Starch can join data across sources in a single app. When you describe the report — 'pull HubSpot deals with their original lead source field, join to GA4 sessions by UTM campaign parameter, and show me conversion rate by campaign' — the Starch agent queries both sources and assembles the combined view. The fidelity of the join depends on how consistently your UTM parameters are set up between HubSpot and GA4, but the join itself is a supported pattern, not a workaround.

We use Customer.io for nurture, not Mailchimp or HubSpot sequences. Can Starch connect to it?

Yes. Customer.io connects from Starch's integration catalog and the agent queries it live. You can surface Customer.io email engagement data — opens, clicks, sequence enrollment — alongside HubSpot deal stage and GA4 behavior in your CRM views or pipeline reports.

What happens to the CRM if we eventually migrate from HubSpot to a different CRM?

The Starch CRM is its own surface — your schema, your views, and your automations live in Starch. If you switch from HubSpot to Salesforce or Pipedrive, you'd re-point the data connection to the new source. Your Starch-built views and automations don't disappear; you'd update the underlying connection they pull from. Salesforce, Pipedrive, and several other CRMs connect from Starch's integration catalog.