Sales & CRM

How to log sales calls to your crm automatically as Small RevOps Teams

Sales & CRMFor Small RevOps Teams3 apps12 steps~24 min to set up

Your two-person team is the unofficial CRM police for 30 reps who treat HubSpot like a suggestion box. After every call cycle, you're chasing people down on Slack to log what happened — what stage the deal moved to, which contact was actually on the call, whether the next step got set. Half the time you're reverse-engineering the activity from Gmail threads or Apollo sequence data, manually matching them to open opportunities. The call happened, the deal moved, but none of it is in HubSpot until you or a rep manually types it in. That's Tuesday. Every week.

Build this on Starch → See the apps used

Sales & CRMFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated pipeline that pulls Gmail threads and HubSpot deal activity into a single view, so every call that touches a contact is logged against the right opportunity without rep intervention

A natural-language CRM layer on top of your HubSpot and Apollo data where you can ask 'which deals had a discovery call this week but no next step set?' and get a real answer

A weekly hygiene automation that flags stale deals, missing call logs, and contacts with no recent activity so you're not manually auditing pipeline before every forecast call

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 data on a schedule — contacts, companies, deals, and owners — and also syncs your Gmail messages on a schedule so email threads are matched to contacts automatically. Apollo is connected from Starch's integration catalog; the agent queries it live when an app or automation needs sequence or contact data. Salesforce and Pipedrive, if in your stack, are also reachable from Starch's integration catalog and queried live. Slack is connected from Starch's integration catalog so the agent can deliver digests and alerts to your team channel.

Prompts to copy

Connect HubSpot and Gmail. Every time a Gmail thread is matched to a HubSpot contact or company, log it as a call or email activity on that deal. If the deal stage hasn't changed in 14 days and there's been at least one call, flag the deal for review.

Build me a CRM view that shows every deal touched in the last 7 days, the last logged activity type (call, email, LinkedIn message), who from our team touched it, and whether a next step is set. Pull from HubSpot for deal stage and from Gmail for email activity.

Every Friday at 4pm, send me a Slack message listing every open opportunity where no call or email activity was logged in the past 10 days, the current deal stage, and the rep owner. Pull this from HubSpot and Gmail.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs deals, contacts, companies, and owner assignments on a schedule, so the agent always has a current picture of your pipeline without you running any exports.

2 Connect Gmail — Starch syncs messages on a schedule and matches threads to HubSpot contacts by email address, building an activity log that doesn't depend on reps manually logging calls.

3 If your team uses Apollo for outbound sequences, connect it from Starch's integration catalog — the agent queries sequence enrollment and contact-touch data live when building activity reports.

4 Start with the Sales Agent CRM app from the App Store as your foundation, then describe your actual pipeline stages and the fields your CRO actually cares about — Starch rebuilds the schema around your process, not the default.

5 Tell Starch: 'Log any Gmail thread matched to a HubSpot contact as an activity on the associated deal. Include the thread subject, date, participants, and a one-sentence summary.'

6 Build a deal hygiene view: 'Show me all open deals where the last logged activity is more than 10 days ago, grouped by rep, with the current stage and the next step field.' Save this as a persistent dashboard your whole team can pull up before the forecast call.

7 Set up the weekly stale-deal automation: every Friday at 4pm, the agent queries HubSpot deal data and Gmail activity, identifies deals with no logged touch in 10+ days, and posts a formatted list to a Slack channel — including deal name, rep owner, stage, and days since last activity.

8 Add an Apollo cross-check: 'If a deal has been in the same stage for 14 days and the contact is enrolled in an active Apollo sequence, note that in the hygiene report so we don't double-count the outreach as pipeline progress.'

9 For calls that happen outside of Gmail — Zoom calls, phone calls — prompt Starch to build a lightweight call-log form inside the CRM app: 'Add a one-click form to each deal record for reps to log a call in under 30 seconds: call date, outcome (interested, not now, moved to proposal, closed lost), and next step.'

10 Wire Meeting Notes to the workflow: after any Zoom or Google Meet call logged on a deal, Meeting Notes captures the transcript and summary, and the agent writes the key decisions and next steps back to the HubSpot deal record as a note.

11 Run the hygiene report manually before your Monday forecast prep — ask the CRM 'which deals moved stages this week?' and 'which opportunities had a call but still show the same stage?' — and use those answers to clean up before the CRO review.

12 Publish the hygiene automation and deal activity dashboard to your team so reps can self-serve their own pipeline view without pinging you on Slack for a list.

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 Pipeline Hygiene — Week of April 14, 2026

Sample numbers from a real run

Deals flagged stale (no activity 10+ days)	11
Deals with Gmail activity not yet logged in HubSpot	7
Deals in 'Proposal Sent' with no follow-up email in 7 days	4
Apollo sequences active on stale deals (double-counting risk)	3
Missing next-step field on deals touched this week	9

Going into the April 14th forecast call, the CRO asked why pipeline coverage looked thin at 2.8x. You ran the stale-deal automation in Starch and found 11 deals that hadn't been touched in over 10 days — 7 of those had Gmail threads that matched to HubSpot contacts but were never logged as activities by the reps. Starch had already matched the threads and surfaced them in the activity log, so you could see that three of those 'dark' deals were actually in active conversation; the reps just hadn't updated the stage. Four deals in 'Proposal Sent' had no follow-up email in 7 days and no next step set — those got flagged for rep follow-up before end of day. The Apollo cross-check caught 3 more deals where a sequence was running but the deal itself was marked 'Closed Lost' in HubSpot — sequence waste your team would have missed in a manual audit. The whole cleanup took 25 minutes instead of two hours of Slack messages and spreadsheet reconciliation.

Measurement

How you'll know it's working

Call log coverage rate — percentage of open deals with at least one logged activity in the last 7 days

Stage age — average days a deal sits in each pipeline stage before moving or being closed

Next-step hygiene — percentage of open deals with a next step set and a future date

Activity-to-pipeline match rate — percentage of Gmail threads matched to a HubSpot deal vs. threads with no deal association

Forecast call prep time — minutes spent manually cleaning pipeline before the weekly CRO review

Comparison

What this replaces

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

HubSpot native activity logging + rep discipline

Depends entirely on reps logging calls manually; when they don't — which is most of the time — your pipeline data is stale and you spend hours chasing it down before forecast calls.

Gong or Chorus call intelligence

Strong call recording and coaching features, but costs $100-150/seat and still requires deal stage and next-step updates to happen in HubSpot separately — it solves the recording problem, not the CRM hygiene problem.

Zapier HubSpot-Gmail zap

Can log Gmail activity to HubSpot contacts, but can't query deal context, flag stale pipeline, cross-reference Apollo data, or give you a natural-language answer to 'which deals are at risk this week' — it's a pipe, not a revenue ops layer.

Salesforce + Einstein Activity Capture

If your team is already on Salesforce, Activity Capture handles email logging natively, but you're still building hygiene reports and forecast dashboards manually — Starch can connect to Salesforce from its integration catalog and build those views on top without replacing your CRM.

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 replace HubSpot or Salesforce?

No. Starch syncs your HubSpot data on a schedule and can query Salesforce from its integration catalog. Your CRM stays the system of record — Starch is the layer on top where you build hygiene rules, activity views, and automations that HubSpot's native tooling doesn't give you without a developer or a $1,200/month operations hub subscription.

What if a call happens on Zoom or by phone and there's no Gmail thread to match?

Starch can add a lightweight call-log form directly in the CRM app for reps to fill in under 30 seconds. You can also connect Meeting Notes — it captures Zoom transcripts and the agent writes the summary and next steps back to the deal record automatically.

How current is the HubSpot data Starch is working from?

HubSpot is a scheduled-sync provider — Starch pulls deals, contacts, companies, and owner data on a regular schedule and stores it in Starch's database. It's not a live API call on every query, so there's a sync interval to be aware of. For most pipeline hygiene and weekly forecast use cases, that cadence is more than sufficient.

Can Starch log activities back to HubSpot directly, or does it just read?

The HubSpot scheduled sync is currently read-only for data that lives in Starch's database. Starch maintains its own activity log and deal view on top of HubSpot's data — a parallel source of truth your team can query. Two-way write-back to HubSpot is a fair question to ask the Starch team about current roadmap status.

We use Salesforce, not HubSpot. Does this still work?

Yes. Salesforce is reachable from Starch's integration catalog — the agent queries it live when your apps and automations need deal or contact data. The experience is slightly different from HubSpot (which has a dedicated scheduled sync), but the CRM hygiene views, stale-deal automations, and Gmail activity matching all work the same way.

Is Starch SOC 2 certified? We'll need to clear this with IT.

Not yet — Starch is not SOC 2 Type II certified as of today. That's an honest answer. If your org requires SOC 2 before connecting a CRM integration, that's a real blocker to flag upfront rather than discover later.

What happens when reps ask 'can you just pull me a list of...' instead of going to the dashboard themselves?

That's what the natural-language CRM is for. Instead of you building the query, you give reps access to the Starch app and they ask it directly — 'show me my deals that moved to Proposal Sent this week with no follow-up email' gets a real answer. The goal is to stop being the person who writes the list and start being the person who built the tool that answers the question.