Show notes: AI sales workflows
Video Gist Guides Chapters Links
Shoreline / Episodes / Ep. 2
EP 002 Season 01 · Field operations

Sales work, agents, and the friction gap.

Episode 2 starts with Rick Rubin and creative resistance, then turns into a field guide for AI-assisted sales travel, Telegram voice capture, Notion/CRM structure, company-brain reporting, and post-call follow-through.

43:44 18 chapters Transcript-derived Sales ops
The gist

The episode connects two kinds of resistance: the creative resistance Rick Rubin talks about and the operational resistance that shows up after a promising AI demo. AI makes it easier to start projects, trips, sales motions, and creative assets. The hard part is still turning the first spark into reviewed work that lives in the right system.

The practical center is Will's field-sales workflow. AI helps choose the right accounts in Pennsylvania and Ohio, prep the right people, capture notes over Telegram from plane Wi-Fi, write the result back into Notion or a CRM, and convert messy conversations into follow-ups, proposals, product requests, calendar moves, and task queues.

Key takeaways

Six things to steal from this episode.

01

AI lowers friction, not responsibility.

The first artifact is easier than ever. Shipping still needs taste, review, timing, and the willingness to push through the boring middle.

02

Sales trips are data-routing problems.

The trip planner should rank territories, companies, people, outreach angles, meeting notes, and next steps before the rep lands.

03

Voice notes can be the CRM interface.

A short Telegram memo after a meeting can become a contact update, a follow-up date, a task, and a cleaner shared record.

04

The company brain is an ops layer.

Agents become more useful when they can read the business: Notion, Vercel, GitHub, Sentry, analytics, search data, and customer notes.

05

Customer time is the scarce work.

Use AI to reduce admin drag so more of the week goes toward real buyer conversations, better preparation, and sharper follow-up.

06

Creative AI gets better with context.

Image generation, thumbnails, copy, and strategy improve when the model already knows the brand, audience, and exact job to be done.

Tactical guidesWhat to try next
Guide 01

Build the AI field-sales trip planner.

Use AI before the trip to turn a broad region into a ranked, realistic plan for who to meet and why.

  1. Define the territory, dates, ICP, product fit signals, and hard constraints.
  2. Ask AI for candidate companies by geography, vertical, size, trigger event, and buying likelihood.
  3. Rank accounts with a simple score: fit, urgency, proximity, relationship path, and deal size.
  4. Identify the people to meet, then write one useful reason to talk to each person.
  5. Turn the ranked list into a travel map, outreach queue, meeting-prep brief, and CRM view.
Guide 02

Run a Telegram-to-CRM capture loop.

The episode's best unlock is simple: talk to your agent while the meeting is still fresh.

  1. Create a private Telegram bot or agent chat that can receive text and voice messages.
  2. Connect the agent to a safe Notion or CRM workspace with scoped read and draft permissions.
  3. After each meeting, record a short memo: who, what happened, objections, next step, and date.
  4. Have the agent draft contact notes, task records, follow-up reminders, and missing-field questions.
  5. Review the draft before the agent writes to the source of truth or sends anything externally.
Guide 03

Create a daily company-brain digest.

For operators, the agent should not just wait for prompts. It should surface what changed overnight.

  1. Connect only the systems that matter: deploys, code, crashes, analytics, search, customer data, and tasks.
  2. Schedule a morning digest with sections for wins, risks, anomalies, pending decisions, and owner-ready tasks.
  3. Require evidence links for every claim, especially traffic spikes, broken pages, bug reports, or campaign movement.
  4. Rank items by urgency and business impact instead of presenting every metric with equal weight.
  5. End with a small action queue: what to inspect, what to fix, what to double down on, and what to ignore.
Guide 04

Turn calls into post-call automations.

The sales rep should not lose the day to cleanup after every good conversation.

  1. Import the transcript, meeting notes, and CRM context into one reviewable workspace.
  2. Ask AI to extract needs, objections, promised follow-ups, stakeholders, timing, and deal risk.
  3. Draft the follow-up email, proposal outline, calendar invite, quote request, and internal handoff.
  4. Create tasks for sales, product, engineering, or support only when the transcript supports them.
  5. Save personal details carefully so future outreach feels attentive, not creepy or over-automated.
Guide 05

Capture inspiration without project sprawl.

The episode treats inspiration as perishable, but also admits that too many AI-started projects can become chaos.

  1. Make the capture step one gesture: voice memo, quick note, Telegram message, or action button.
  2. Ask the agent to produce a tiny artifact: sketch, brief, outline, landing page draft, or task card.
  3. Store the artifact in Notion with tags for customer value, timing, effort, risk, and owner.
  4. Let the agent compare new ideas against existing commitments, bugs, deadlines, and revenue work.
  5. Promote only the ideas that survive review; archive the rest without shame.
Guide 06

Make creative assets with real brand context.

The thumbnail discussion becomes a broader creative rule: generation works best when the model sees the lane.

  1. Collect the brand kit: colors, type, image rules, prior thumbnails, tone, and audience.
  2. Start from the episode theme or transcript, then generate a few precise visual directions.
  3. Use image generation for backgrounds, objects, art styles, mood, and variations that used to require stock-photo hunting.
  4. Review for taste: composition, brand fit, readability, and whether the idea matches the episode.
  5. Save prompts and final assets so the next creative run starts grooved into the same system.
ChaptersTimestamp map
00:00

Rick Rubin, The Creative Act, and resistance

The episode opens on Rick Rubin's creative philosophy and the surprising resistance that appears before meaningful work.

01:27

Grind mode, flow mode, and multiple paths to output

The hosts compare artists, athletes, engineers, and founders who arrive at good work through different rhythms.

03:25

Find your workflow by using the tools

AI advice becomes real only after you try it against your own business, customers, schedule, and personal style.

06:31

Creative work still has a hard middle

Training, coding, school, design, and content creation all include days where getting started is the hardest part.

08:20

Vibe-coded demos versus production systems

AI can spin up a concept fast, but production requires testing, polish, data, permissions, and boring completion work.

10:57

Planning a real sales trip with AI

Will explains how AI helped narrow Pennsylvania and Ohio into companies, people, and outreach angles worth pursuing.

13:01

Plane Wi-Fi, Telegram, and a laptop at home

Free text-only Wi-Fi becomes a work surface because OpenClaw is reachable from Telegram and connected to the real workspace.

15:48

Unstructured meeting notes become structured tasks

Voice notes after meetings turn into contact updates, follow-up dates, task records, and CRM-ready data.

17:15

OpenClaw, Hermes, Codex, Claude Code, and the agent layer

The hosts compare agent frameworks and coding harnesses as the layer between frontier models and real business systems.

19:31

OpenClaw as COO and CTO

Enzo describes using agents to watch deploys, GitHub, Sentry, analytics, search data, Hotjar, and daily business signals.

23:00

Reducing operator friction

Agents shrink the lag between idea and action, especially when they already have the right harness, tools, and context.

26:57

Inspiration is perishable

The conversation returns to capturing ideas immediately while still respecting the toil needed to finish anything valuable.

29:24

Notion as the prioritization layer

Meeting transcripts, email, deadlines, and project ideas feed a company brain that can rank what matters next.

31:00

Friction design: action buttons and EV charging

Small interface choices matter because every extra step makes capture, follow-up, and priority review less likely to happen.

33:48

Sales reps, admin drag, and customer time

The hosts focus on the gap between high-value customer work and the CRM updates, proposals, quotes, and coordination around it.

36:08

The pre-call personalized podcast

AI can brief a rep on the buyer, company, context, competitor movement, and next conversation while the rep is on the move.

39:26

Thumbnails, image generation, and brand fit

Creative production shifts from hunting for approximate assets to generating the right image in the right style.

42:00

Every function should ask where AI fits

The closing argument is broad: sales, content, coding, finance, strategy, and operations all have daily workflows worth rebuilding.

The stackTools & concepts

OpenClaw + Telegram + Notion

Field sales · company brain

The core workflow is a mobile command surface: send a text or voice note to an agent, let it read the company brain, draft structured updates, then review before it writes to the CRM or task database.

Creative source

The Creative Act

Rick Rubin's book frames the opening discussion about resistance, flow, taste, and creative work.

Open publisher page
Podcast source

Tetragrammaton

Rick Rubin's interview show is referenced as part of the creative and technology conversation around the episode.

Open Tetragrammaton
Personal agent

OpenClaw

The episode uses OpenClaw as the example of a persistent assistant that can connect messaging, tools, memory, and workflow actions.

Open OpenClaw
Agent framework

Hermes Agent

A related self-hosted agent framework mentioned in the agent-layer discussion.

Open Hermes Agent
Protocol

Model Context Protocol

A good follow-up for understanding how AI apps can connect to tools, data sources, prompts, and workflow resources.

Open MCP docs
Workspace

Notion API

Useful for the episode's CRM-like pattern: pages, databases, task fields, permissions, and shared company memory.

Open Notion developers
Messaging

Telegram Bot API

The official API path for building a Telegram bot that can receive messages and route them into an agent workflow.

Open Telegram API
Product ops

Sentry Cron Monitoring

A reference for the heartbeat and scheduled monitoring idea in the company-brain digest section.

Open Sentry crons
Analytics

Google Analytics

A source for site and campaign signals that can feed daily reports, trend checks, and operator prioritization.

Open Analytics docs
Search

Search Console API

Useful for the search-performance part of an AI-generated weekly or daily website health report.

Open Search Console API
Behavior

Hotjar

A behavior analytics reference for understanding where real users struggle, click, scroll, and abandon.

Open Hotjar
Sales research

Salesforce State of Sales

The episode cites the low-customer-time problem; Salesforce's public write-up reports reps spend just 28% of their week selling.

Open Salesforce research
Coding agent

Codex

A reference for the coding-harness idea: agentic software work needs repo context, tools, tests, and review evidence.

Open Codex docs
Coding agent

Claude Code

A related command-line coding agent in the conversation about harnesses, repo work, and agentic development.

Open Claude Code docs
Creative AI

OpenAI image generation

A follow-up for the thumbnail workflow: generating or editing visual assets instead of hunting for approximate source images.

Open image docs

The practical AI sales workflow is not one magic prompt. It is capture, context, structure, review, and a next action that lands in the right system while the conversation is still fresh.

Shoreline Ep. 2 · distilled operating principle
Listener checklist
Day 1

Pick one field workflow.

Choose trip planning, meeting prep, post-call notes, follow-up drafting, or daily ops reporting. Keep the first workflow narrow.

Day 2

Choose the source of truth.

Decide where contacts, tasks, transcripts, follow-ups, and account notes should live before connecting any agent.

Day 3

Add one mobile capture surface.

Use Telegram, voice memos, or a private form so real-world notes can enter the system immediately.

Day 4

Draft, then review.

Let AI create structured updates, but keep the first few weeks behind a human approval gate.

Day 5

Schedule a digest.

Ask the agent for a daily report with wins, risks, changed records, missing context, and suggested next actions.

Day 6-7

Promote only what saves real time.

Keep workflows that reduce admin drag or improve customer conversations. Archive impressive demos that add review burden.