Stop Writing Blog Posts. Ship Instruments.

Your blog post is worthless. Not because it's badly written. Because it's a blog post, and any AI can write a competent one in nine seconds. The thing you paid a copywriter $400 for, or spent your Sunday afternoon drafting, is now a commodity with a marginal cost of zero.

I spent 20 years as a software engineer before I got into functional medicine marketing. My last app went from nothing to a $500M business in four years. I know what happens to a market when the cost of production collapses. Prices go to zero and volume goes to infinity. That is exactly what's happening to content right now. Every practice in your city will soon have a blog full of competent, generic words about gut health and hormone balance. Competent and generic is not a moat. It's wallpaper.

Why Words Stopped Being Proof

For fifteen years I've been a functional medicine patient myself, sitting across from practitioners, reading their sites, trying to figure out who actually knew what they were talking about. Here's the thing nobody in marketing wants to say out loud: a well-written article was never really proof of expertise. It was a proxy for it. Writing clearly used to correlate with thinking clearly, so we used one as a stand-in for the other.

AI broke that correlation. Now anyone can produce clear, well-structured, seemingly authoritative writing about SIBO or Hashimoto's without understanding either condition. The proxy failed. So the market needs a new proxy, something that can't be faked by a language model typing fast.

That thing is an instrument. A tool the reader operates, not a page they read. A symptom calculator that asks them questions and gives them a number. A lab-prep tool that tells them exactly what to stop eating three days before a test. An assessment that scores their actual situation and hands back a real answer, specific to them.

An instrument can't be generated in nine seconds because it requires you to have already done the thinking: what are the actual decision rules, what are the actual thresholds, what happens in each branch. You have to know your clinical logic well enough to encode it. A blog post can gesture at expertise. An instrument has to contain it.

The Content Marketing Consensus Is Selling You the Wrong Asset

Every agency, including plenty of ones I compete with, will tell you to publish more. Post three times a week. Build topical authority. Stack keywords. That advice made sense in 2019. It makes much less sense in a world where your competitor can produce the same volume of content for free, this afternoon, with a prompt.

Volume was never the moat. Thinking was the moat. The blog post was just the container we used to ship thinking, because it was the cheapest container available. Now the container is free and the thinking inside it is diluted to nothing, because everyone's container looks the same.

An instrument flips the economics. One good calculator on your site does more for your authority and your conversion rate than a hundred more articles, because it's the one thing on your site a competitor cannot copy by hitting generate. They'd have to actually understand your clinical framework to rebuild it. Most won't bother. Almost no practice in functional medicine has even one real instrument live on their site today. That's not a gap. That's an open field.

I've built these myself for a real client. Dr. Piper Gibson's practice was hard to find online. I built her interactive calculators and supported the build-out of a genetics program tool, something patients could actually run their own numbers through. Her practice went from invisible to ranking. Not because we wrote more words about her genetics program. Because we shipped something that did work for the patient before they ever booked a call.

The Instrument Playbook

Here is the whole thing, no gate, no email opt-in required to read it.

Step 1: Find the question patients already compute in their heads. Every practice has a handful of these. Patients sit at their kitchen table doing rough mental math: "Is my fatigue bad enough to be Hashimoto's or am I just tired?" "How many of these nine symptoms do I actually have?" "What do I need to stop eating before this stool test so I don't wreck the results?" You already answer these questions verbatim in intake calls. That repetition is your signal. If you've explained the same decision rule to your third patient this month, that's your first instrument.

Step 2: Write the decision rule down before you build anything. Don't open a no-code tool yet. Write the actual clinical logic on paper first. If symptom count is above X and duration is above Y, flag for further testing. If prep window is under 72 hours, use the short protocol, otherwise use the long one. This is the part that requires you, the practitioner, not a developer and not an AI. The logic is your IP. Everything after this is just presentation.

Step 3: Build the simplest version that could ship this week. Your first instrument should not be an app. It should be a scored quiz or a simple calculator, five to twelve inputs, one clear output, one clear next step. Tools like Typeform, Outgrow, or a basic embedded calculator built by a freelance developer can get a working version live in days, not months. Resist the urge to make version one do everything. Trying to cover every case is what kills these projects before they ship.

Step 4: Make the output specific enough to feel like it was built for them. The difference between an instrument that ranks and converts, and one that gets ignored, is specificity of output. "You may have some hormone imbalance" is a blog post pretending to be a tool. "Your score of 14 out of 20 places you in the moderate-risk range for subclinical hypothyroidism; here are the three lab markers to ask your doctor for" is an instrument. Vague output kills the format. Specific output is the entire point of the format.

Step 5: Put the instrument at the center, not the edge. Link to it from your homepage. Build the article that explains the condition around the tool, not the other way around. The tool is the asset. The article is now just the doorway to it.

Where to Start

You don't need an engineering team for step one. Pick the single question your patients ask most often in the first five minutes of an intake call. Write down the actual scoring logic on paper this week. Then either hand that logic to a freelance developer for a week-long build, or wire it up yourself in a no-code form tool as a scored quiz. Ship the ugly version. Refine it once real patients have used it.

This is the same move I made in software for twenty years before I ever touched functional medicine marketing: find the repeated manual calculation, build the thing that does it automatically, ship it before it's perfect. That principle scales from a $500M app down to a single practice's website. It works the same way at both ends. See Authority Leverage for how this compounds into a defensible position, and Visibility Leverage for why tools like this tend to outrank pure content over time.

If you want a second set of eyes before you scope your first one, that's what work with me is for.