Your help articles, tested in your live product.

Gamut follows every article in your product, shows you the exact step that stopped being true, and drafts a fix it’s already tested.

Illustrative example: Plotwell is a made-up product, shown in Gamut’s dashboard.

How it works

What it does

  1. Reads your help center like a customer would.

    Every article, the same ones you send your clients.

    Plotwell’s help center as Gamut read it: 49 articles in seven collections, from Getting started to Sharing & embedding, with “Select all 46 with steps.” Nothing has been checked yet.
  2. Then runs them.

    Give it a test login. Watch it sign into your live product and follow each article, step by step. Nothing to install. No access to your code.

    A check in progress, 30 of 46 articles done. Gamut’s browser is on Plotwell’s New alert form, typing 50,000 into the threshold field. Beside it, “Setting up a threshold alert”: steps 1 to 3 ticked, step 4 in progress, step 5 still to come.
  3. When something’s off, it shows you.

    The article on the left. A screenshot of what the product actually does on the right. Breakages, and the small touch-ups that keep articles honest.

    Gamut’s report on “Exporting a report to CSV or PDF”: needs attention, step 4 couldn’t be followed. On the left, the article’s step 4, “In the report toolbar, click Export,” with Export circled in its picture. On the right, the live product: the toolbar has no Export any more; downloading a report has moved into Share.
  4. Drafts the fix. Then tests the fix.

    It rewrites the article from what’s really on screen, then follows its own rewrite to make sure it holds. Nothing posts until you say so.

    Gamut’s fix, marked “Verified in the product”: “In the report toolbar, click Export” becomes “click Share, then Download.” Beside it, the download options Gamut reached by following the new step, with Approve fix, Edit and Dismiss.
  5. Gamut doesn’t quit.

    Your product keeps changing. Gamut keeps rerunning, and tells you what broke this time.

    Plotwell’s checks: a weekly schedule, Fridays at 10 AM, and five runs of all 46 articles. Three hold, then one finds 1 broken, then, with the fix in, all 46 hold again.

Access and approval

You stay in control.

  • One test user, nothing more. Gamut signs in as an ordinary user you create, through your product’s own sign-in page. No API keys, no SSO, never your own account.

  • The password stays sealed. It’s stored encrypted and used only to sign in. It’s never logged or shown again, and you can remove it any time.

  • No shortcuts past your guards. Two-factor prompts and CAPTCHAs are reported, never worked around. Articles about billing, invites or deleting things are left out unless you pick them.

  • Nothing changes without you. Gamut never edits your help center. Approved fixes wait in a queue for you to paste in or export.

The test login: who, and when it last signed in. Never the password.
Gamut’s test login for app.plotwell.io: it signs in as gamut-qa@plotwell.io through the product’s /login page; the password shows only as dots; stored encrypted and used only to sign in.
An approved fix, waiting for you to paste it in.
Ready for the help center: the approved fix for “Exporting a report to CSV or PDF,” step 4, verified in the product, with Copy and Export all.

Want this for your help center?

Gamut is in private beta. Leave yours and I’ll write to you myself.