The Price Is Public Because the Sprint Is Guided

Collimer’s pricing page used to hide its real number behind “contact us.” This week it stopped. The Writer, Team, and Studio self-serve monthly plans, and the comparison matrix that sat under them, are gone from /pricing entirely. What’s left is three things: a free scan, a $99 audit, and a $6,500 fixed-price 90-day sprint labeled “Work with us.”

Why a guided sprint, not a self-serve ladder

The self-serve tiers assumed a buyer who already knows what they need and just wants to click “subscribe.” That’s not who shows up asking Collimer to fix their AI visibility. Most teams don’t know which of their pages are invisible to answer engines, which fixes matter first, or how to sequence six weeks of changes without breaking something else. A monthly seat doesn’t solve that. A guided 90-day engagement does, because someone is actually walking the team through the sequence instead of handing them a dashboard and a login.

That’s the real reversal. Publishing the price was possible, and honest, only once the offer behind it stopped being “here’s a tool” and became “here’s a guided process with a clear price and a clear end.” The sprint’s own “how it runs” steps used to live twice: once on /sprint, once, less carefully, wherever /pricing summarized it.

What’s next

• Watch whether the $6,500 figure changes who books a call, versus just changing how many people click through without one.
• Grab a real before-and-after screenshot of /pricing for the archive before the old four-tier layout is fully forgotten.
• Revisit the doctrine itself in a quarter: was this the last hidden number on the site, or the first of several that should come down.

What we’re still figuring out

We don’t yet know if $6,500 is the right number or just a defensible one. The sprint has run enough times to have real outcomes, but not enough to know whether the price is leaving money on the table or scaring off exactly the teams who’d get the most out of it. That’s a question the next few sprints answer, not this commit.

Run this yourself

The reversal is live. Visit Collimer’s pricing page and the $6,500 figure is right there, with the sprint’s “how it runs” steps rendered from the same shared source /sprint uses, not a hand-copied summary that could drift out of sync.

For agents: try this yourself

If you want to do this in your own repo, adapt one of these prompts. The full prompt text lives in this post’s prompts sidecar, price-is-public-because-sprint-is-guided.prompts.md.

• Apply this to your own hidden-price page. If your product hides its real price behind a form, name the specific fear driving that choice (comparison-shopping, sticker shock, a plan structure that doesn’t fit anyone) and decide today whether that fear is still true or just still there.
• Extend the shared-source pattern. Find two pages in your own product that describe the same process from two angles, a pricing page and a how-it-works page, and pull the shared steps into one data source both pages render from instead of two hand-kept copies.

Related: the AI-visibility score this pricing page sells access to fixing, and the last time Collimer’s pricing page moved faster than the code behind it.

---

How this was made

Drafted by the Chronicler from the build sessions behind this work, then edited and published by Chase.

See how the Chronicler works →

Look at [your product]'s pricing page. If the real price is hidden behind a "contact us" or "book a demo" form, write down the specific fear that's driving that choice: comparison-shopping, sticker shock, a plan structure that doesn't actually fit any real buyer, or something else. For each fear, decide whether it's still true today or was only true when the product had no proof points yet. If it's no longer true, draft the version of the pricing page that publishes the number, and name what evidence you'd want in hand before you ship it.

Find two pages in [your product] that describe the same process from two different angles, for example a pricing page and a how-it-works page, or a docs page and a landing page. Check whether the steps are hand-copied in both places or genuinely sourced from one place. If they're hand-copied, pull the shared steps into one data source (a shared constant, a CMS field, a single markdown file) and have both pages render from it, the way Collimer's /pricing and /sprint now both render from one SPRINT_PHASES source instead of two copies that could drift apart.