Opinions Verdicts Guides Google Ads Paid Social Programmatic B2B Performance Marketing The Agency About Tools Contact Subscribe
Behind The Scenes

The Stack We actually
Run On.

Six tools do most of the work at Market Correct. This isn't a sponsor list. It's the actual setup, plus a founder's read on what each one earns its keep doing.

Disclosure. This page contains affiliate links. If you buy or sign up through one, Market Correct may earn a commission at no extra cost to you. As an Amazon Associate, Market Correct earns from qualifying purchases.

See The Stack Build Your Own
6 Tools 3 Affiliate Zero Fluff
A Founder's Note

Most "tools we use" pages are sponsored grids. This isn't one.

Six tools hold the agency together. Wipe the laptop tomorrow and these go back on first, before any client work gets done. Everything else in the stack is swap-out. These six are load-bearing.

Tool 01 Build Environment

Claude Code Ships The work.

Claude Code is the agentic coding environment where everything actually gets built. Terminal-native, MCP-connected, and the reason ideas land in production instead of dying in a Notion doc.

mrktcorrect.com was built and is maintained through Claude Code. So are the custom MCP servers, the GSC integrations, the Cloudflare Workers, the automation scripts that keep the agency running while I sleep. If it requires code, it ships from here.

It's the bridge between "Claude had a good idea" and "that idea is live." Most agencies still email Word docs around. We commit and push.

Open Claude Code No affiliate. The most useful tool we run.
Tool 02 Foundation Model

Claude Is The brain.

If Claude Code is the hands, Claude is the head. Every page on this site, every blog post, every campaign brief, every SEO audit, every Google Ads optimization runs through Claude before it ships.

This isn't AI-assisted work. It's AI as the system. Claude replaced a content team, a strategy consultant, and a research assistant on retainer, all at once.

The site you're reading was architected here. The blog posts ranking in Google were drafted here. The ads we run for clients pass through here on the way out.

Try Claude No affiliate. Just a real recommendation.
Tool 03 Voice Input

Wispr Flow Catches The thinking.

Wispr is voice-to-text the way you actually think. Fast, messy, mid-thought, switching subjects in the same breath. It cleans up the noise without flattening the voice.

I use it for first-draft copy, briefs, prompts, and ideas I'd lose between meetings. In a solo agency, getting words out fast without breaking the thread saves hours a week.

It runs system-wide, not locked to one app. That matters when you bounce between Claude Code, a doc, an email, and a Slack thread inside a 30-minute window.

Try Wispr Flow Affiliate link. We use Wispr daily.
Tool 04 Meeting Capture

Pocket Catches everything.

Pocket is the meeting layer. Every client call, every strategy session, every internal conversation gets captured, transcribed, and organized without manual effort.

What makes Pocket different from a generic transcription tool, it has an MCP server. Claude can query Pocket transcripts and action items mid-session. "What did we decide about the Q2 budget" stops being a memory problem and starts being a lookup.

We pair it with Granola. Pocket captures the raw signal, Granola structures the output. Both run at the same time.

Get Pocket Affiliate link. Worth it for the MCP alone.
Tool 05 Meeting Structure

Granola Does The cleanup.

Granola is the other half of the meeting stack. Where Pocket captures, Granola structures. The summaries actually feel useful after the call, organized by meeting, with action items that read like a person wrote them.

Both run at once. The combination means nothing falls through the cracks between strategy calls and execution. By the time a meeting ends, the notes are already structured.

Like Pocket, Granola has an MCP server. It hooks straight into Claude Code, so meeting context is one query away when we're building campaigns or writing briefs.

Try Granola Affiliate link. Picked it before joining the program.
Tool 06 Version Control

GitHub Ships The site.

The site lives in a GitHub repo. Every page update, every new blog post, every code change gets pushed to main. Cloudflare Pages auto-deploys from there.

No build step, no CMS, no pipeline. The repo is the deployment mechanism. It also stores MCP server code, automation scripts, and anything else that needs to persist and be versioned.

View On GitHub
Build Your Stack

Check Out Our favorite
Tools.

Pick the ones that fit. Skip the ones that don't. The stack matters less than what you ship with it.

01 / Build Claude Code Terminal-native agent. The site, the MCP servers, and the automation all ship from here. Visit 02 / Foundation Claude The model behind every page, post, brief, and audit. The brain on top of the build. Visit 03 / Voice Wispr Flow System-wide voice-to-text fast enough to keep up with the thinking. Visit 04 / Capture Pocket Meeting transcripts Claude can query. The capture layer. Visit 05 / Structure Granola AI-structured meeting notes that read like a person wrote them. Visit 06 / Deploy GitHub Push to main, Cloudflare Pages handles the rest. No CMS, no pipeline. Visit

Want to see how we run paid media on top of this stack? Get a free audit.