Back to database

Joe McCormick, Babylist's AI use case

Principal Engineer at Babylist

Built custom AI helpers that turn images, links, spelling issues, and visual information into more useful text-based workflows across Slack, the browser, and everyday family life.

The problem

What was broken before AI

Many workplace tools assume people can quickly scan images, links, interfaces, and visual cues. Small gaps add up: an image in Slack may have no useful description, a link may be unclear, a misspelled word may be hard to catch quickly, or a visual page may take extra effort to interpret. Each issue is small on its own, but together they create ongoing friction.

What changed

What the use case made possible

Joe uses AI to build lightweight helpers that convert visual or unclear information into clearer text. A Slack image describer turns shared images into descriptions. A link summarizer gives context before opening a page. A spelling helper gives quick feedback without switching apps. He also uses vision models in family life, including reading books aloud with his kids.

Why this matters

Why this use case is worth studying

Joe’s workflow is valuable because it shows AI filling the small gaps that traditional software often misses. Better access is not only about one big assistive device; it is also about dozens of little moments where software should explain itself better. AI makes it possible to build personal bridges over those gaps, even when the original app was not designed for that exact need.

Use this when

When this pattern applies

Use this pattern when useful information is stuck in a format that slows someone down: an image without a clear description, a link without context, dense page content, a spelling issue, or visual material that would be easier as text or audio.

Exponential Builder analysis

01

Build for the tiny barriers that repeat.

AI value often shows up in moments too small for a roadmap: an undescribed Slack image, an unclear link, a typo check, a visual page that needs explanation. When those moments happen every day, a small helper can change the whole feel of a workflow.

02

Format-shifting is a practical accessibility pattern.

Joe’s tools work because they translate information from a less usable form into a more usable one: image to text, link to summary, page to explanation, book page to spoken reading. The builder move is to ask, “What format would make this easier right now?”

03

Put the helper where the friction happens.

A great AI accessibility tool loses power if it requires a separate app, copy-paste ritual, or extra cognitive load. Slack, the browser, VS Code, keyboard shortcuts, and screen-reader-friendly outputs matter because proximity is part of the product.

Who this is for

Best fit

Accessibility-minded engineers

Product teams improving inclusive workflows

People building personal helpers for daily software friction

Workplace teams using image-heavy or link-heavy communication

Parents or caregivers adapting visual content for audio

Anyone trying to make an existing app easier to use without waiting for the app itself to change

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

AI descriptions can miss details, so review important outputs.

Keep each helper close to the place where the task happens.

Test the tool in the real routine, not only in a quick demo.

Review privacy settings before connecting workplace or personal content.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Start with one repeated friction point

Joe looks for moments where visual or unclear information slows work down, like images, links, or spelling.

02

Turn the friction into a small helper

Instead of building a full product, he uses Claude Code to create focused tools for one job.

03

Convert visual information into text

Vision models describe images, pages, or books so the information becomes easier to use through text or audio.

04

Keep the helper close to the workflow

The best tools live where the problem happens, such as Slack, the browser, or a keyboard shortcut.

05

Reuse the pattern in daily life

The same idea works at work and at home, from Slack image descriptions to reading books aloud with his kids.

Copy the pattern

The reusable idea

Pattern in one sentence

Use AI to translate everyday software friction into a clearer format at the exact moment someone needs it.

Reusable idea

Joe’s use case is a reminder to look for small places where information is trapped in the wrong format. The best starting point is one repeated moment where an image, link, page, or interface needs to become text, audio, or a clearer summary. AI can often become the bridge between the app and the person trying to use it.

Steal this workflow

Use the “one input, one output, one location” accessibility helper recipe:

1

Pick one repeated friction point: Slack image, browser link, selected text, screenshot, visible page, or document.

2

Name the trapped format: visual, unclear, misspelled, too dense, or hard to scan.

3

Choose the helpful output: clear description, short summary, typo-only correction, plain-language explanation, or audio-friendly reading.

4

Write 3 examples of what a good answer should include and 3 mistakes to avoid.

5

Build the smallest version with Claude Code or a similar coding assistant.

6

Place it where the task already happens: Slack action, Chrome extension, VS Code command, keyboard shortcut, or screen-reader-friendly output.

7

Test it during the real routine for a week.

8

Refine only the failures that actually show up.

9

Add a privacy rule before connecting workplace or personal content.

10

Reuse the same pattern for the next trapped-format problem.

Suggested prompt

“I want to build a small AI helper for one recurring accessibility or usability friction. The friction is: [describe the moment]. The input will be: [Slack image / browser link / selected text / screenshot / visible page / document]. The output should be: [clear description / short summary / spelling correction / plain-language explanation / audio-friendly reading]. Design the smallest useful version of this helper. Include: where it should live in the workflow, what the model should be asked to do, what the output format should look like, privacy boundaries to consider, and a short test plan using real examples. Keep the helper narrow: one input, one output, one place where it runs.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all