Join the beta

Install guide

How an install works.

A fixed scope, installed in phases, with a sign-off at every gate. Here’s what happens week by week, what we need from you, and what you approve before anything moves on.

Join the beta What you sign off
3 wkFoundation
6 wkLibrary
4 moFull System

Week 0

It starts with ten terms.

A 30-minute call. We look at your site together and sketch the first ten terms of your vocabulary before we hang up.

Within a week you get a written plan: the scope, the phases and a beta price. Nothing is booked until you’ve read it and said yes.

10 terms so far. Each one you add becomes a new thread.

Week by week

Content leads. Structure follows.

  • Week 1
    A baseline, an audit and a strawman vocabulary

    Before anything changes, we record where you stand today: search clicks and impressions, top entry pages and enquiries. Then we read the whole site and draft 30 to 60 terms, in your words where we can find them.

  • Gate 1
    You sign off the vocabulary

    About half an hour: keep, cut or rename. Nothing is built before this.

  • Week 2
    Collections and tagging

    Topics, Insights and FAQs as native CMS collections; every project and service tied to your vocabulary.

  • Week 3
    Templates that build themselves

    Styled from your site’s own variables, with a walkthrough for your editors. Foundation is complete here.

  • Weeks 4–6
    The library

    You fill the Voice Kit and we draft 8 to 10 launch pieces. You keep your written voice profile.

  • Gate 2
    You approve every piece

    Nothing goes live until you approve it. Library is complete here.

  • Months 2–4
    Topic pages, the hub and the rest

    One topic page at a time, the hub last, with check-ins around day 60 and day 120.

What you sign off

Three gates. Every one is yours.

  1. The vocabulary

    Before anything is built. Every term is yours to keep, cut or rename.

  2. Every piece of writing

    Before it publishes. Drafts arrive in your voice; the final say is yours.

  3. Every topic definition

    Before its page ships. The definition is the page, so it has to sound like you.

What we need from you

Less than you’d think.

Access
Editor access to your CMS
Half an hour
To read the vocabulary and mark it up
About 15 minutes
For the Voice Kit, mostly talking, if your package has the library
Review time
For each draft and definition, on your schedule

We don’t need a brief, a content calendar or anything written in advance. If your voice already exists in proposals, talks or emails, we start there. Busy month? Tell us and we pause: the timeline moves with your reviews, and your written plan says how a pause works.

After the handoff

Everything stays.

It’s your content in your CMS, built with native collections and fields, with no plugin or subscription to cancel. Your editors publish the way they learned in the walkthrough: one entry, tagged once, and every related list and schema updates on publish.

With the Library, you also keep your written voice profile, to use with any writer or AI tool. If you want to keep growing it, add an optional monthly plan: reports by topic, capture from your phone and drafts in your voice that keep learning from your edits. If not, nothing changes. What we won’t promise is a ranking or a citation; nobody controls those.

Join the beta About the app