MMarketing Against The Grain
← All episodes
07 January 2025

The Ultimate Guide to Using Claude AI for Work

4Frameworks
7Insights

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 1

Hot Take17:00

AI Will Turn Job Functions Into Overlapping Venn Diagrams

Scott expects AI to expand what employees can execute beyond their traditional roles. Designers can write code, salespeople can contribute to marketing and product synthesis, and engineers can build low-fidelity visual artifacts, reducing the coordination gaps between functions.

  • AI lowers the cost of working outside one's original specialty
  • Designers can move ideas closer to production through code
  • Salespeople can synthesize field knowledge for marketing and product teams
  • Engineers can communicate product ideas through visual artifacts
  • Organizational functions may overlap rather than remain rigidly separated

it's also people expanding their scope at the same time into like other job functions and like the lines becoming blur

Scott White · 17:00

how these job functions will sort of overlap in vend diagram circles

Scott White · 18:00
#future of work#job design#cross-functional work#enterprise ai

Explainer· 3

Explainer07:00

Why Claude's Personality Can Matter More Than Benchmarks

Kieran says benchmarks do not explain why he repeatedly gravitates toward Claude. Scott argues that people use a model more deeply when it feels collaborative and pleasant to spend time with, which encourages them to share more information and pursue more meaningful work.

  • Product preference is not reducible to benchmark performance
  • Claude's collaborative character affects repeated usage
  • A model users like receives more context and engagement
  • The lived relationship with an assistant can create product stickiness

I don't think about the benchmarks I just think about my experience with Claude

Kieran Flanagan · 07:00

being a model that you like spending time with means that you will give it more information

Scott White · 12:00
#claude#collaboration#product experience#ai adoption
Explainer14:30

How Claude Multiplies Marketing and Sales Output

Scott describes enterprise applications that accelerate work already performed by marketing and sales teams. Centralized style guides, personas, product documentation, and account information can support higher-quality content and a dramatic increase in strategic account planning.

  • Marketing teams can centralize style, persona, audience, and product context
  • The same content can be adapted across channels and countries
  • Claude can increase the volume of strategic sales planning
  • The goal is faster work without sacrificing strategic quality

you now can do way faster with way higher quality with centralized information

Scott White · 15:00

he's now like I do 20 20 with clot like I've 20x the output of like actual strategic account plans

Scott White · 16:00
#enterprise ai#marketing#sales#content generation#account planning
Explainer37:30

How Claude Computer Use Navigates a Screen

Scott describes the early computer-use capability available through the API. Claude can inspect screenshots, identify coordinates, and click those locations to complete browser-based tasks, pointing toward assistants that operate beyond a standalone chat interface.

  • The model receives screenshots from a computer environment
  • It identifies coordinates corresponding to interface elements
  • It can click those coordinates in pursuit of a task
  • The capability remains in an early preview stage
  • Computer control may change where users encounter AI assistants

computer use is this interesting model capability that's available in an early sort of preview via our API

Scott White · 37:30

which allows Claude to take screenshots uh on your computer ident ify coordinates and then click on those coordinates based on the task that you're…

Scott White · 37:30
#computer use#automation#claude api#browser agents

Story· 1

Story42:30

A Three-Minute Claude Artifact Converted an AI Skeptic

Kieran recounts sharing a published Claude artifact that analyzed a clean-energy fund with charts, forecasts, and models. A friend who had not understood AI's value saw the finished artifact, learned it took about three minutes to create, and immediately decided to sign up.

  • Published artifacts make AI output accessible to non-users
  • Concrete work products communicate value better than abstract explanations
  • Claude created charts, forecasts, and predictive models
  • Shareable outputs can produce product virality

Claude Built Me charts forecasted things predict models it's like it took me I'm literally watching TV and this took me 3 minutes

Kieran Flanagan · 42:30

he's like okay signing up for an account

Kieran Flanagan · 43:00
#artifacts#virality#data analysis#ai adoption

Q&A· 1

Q&A31:00

When to Use Claude, Its API, or a Domain-Specific Product

Scott explains that Claude should complement rather than replace deep systems of record. Companies can choose the direct product for broad knowledge work, the API for custom security or compliance requirements, and point solutions for highly specialized workflows.

  • Claude aims to improve work with existing systems rather than replace every system
  • The API supports custom deployment and compliance choices
  • Broad knowledge work may fit Claude directly
  • Deep domain workflows may belong in specialized products
  • Cost, security, administration, and maturity influence deployment choices

it's not about competing or replacing the systems that exist today and uh where people are working it's about complementing and making you work better…

Scott White · 31:30

if you have a very deep domain specific thing that you're trying to get done it might make sense to build into a point solution

Scott White · 33:00
#api#enterprise architecture#compliance#systems of record#build vs buy

Takeaway· 1

Takeaway39:30

The Killer B2B Use Case: Prioritize Every Unread Message

Kieran proposes that an assistant should combine email, Slack, and other communication channels, structure the backlog, and tell knowledge workers what requires attention. Scott agrees that this depends on broad information access combined with personal preferences.

  • Knowledge workers lose substantial time clearing communication backlogs
  • An assistant could collate messages across communication channels
  • Parsing and structuring must precede prioritization
  • Personal preferences are necessary for tailored recommendations
  • Access to the underlying information is the critical prerequisite

the most impactful thing you can do for B2B knowledge workers is collate all of the comps parse it and structure it and then prioritize…

Kieran Flanagan · 40:00

you can really only prioritize the information for someone if you have access to the information

Scott White · 40:30
#productivity#slack#email#prioritization#knowledge work