Your how-to guides, checked and fixed every week.
For RevOps and enablement teams on HubSpot or Salesforce. Guidekeep replays every guide in a test account each week, updates the steps when a screen changes, and flags broken ones to their owner.
Most know-how never gets written down, and what does goes stale.
People ask the same questions, and senior staff give the same answers again and again. Scribe’s own survey claims 71% of company know-how is undocumented.
The guides that do exist break without warning. An app changes a screen, an admin renames a field, and nothing tells you which guide is now wrong. The usual fix is manual: Scribe suggests a yearly review, and Guidde’s answer is to record the guide again.
So new hires follow the wrong steps, nobody trusts the docs, and everyone goes back to asking a colleague.
Your guides stay current, and you approve each fix.
We bring your guides in during week one. From then on an agent replays each one in a test account every week, and again on the day a change shows up.
Captured
Guides imported from Scribe and Confluence
The processes nobody wrote down are recorded from real screen work. We do that part for you.
Open libraryAdd a source
One report each week, so you know which guides to trust.
Every guide gets a status from its latest replay: current, fixed and waiting for your approval, or broken and sent to its owner.
Current38
Fixed, waiting for approval3
Broken, sent to the owner1
| Guide | App | What the replay found | Status |
|---|---|---|---|
| Create a deal | HubSpot | Every step matched the app | Current |
| Convert a lead | Salesforce | Every step matched the app | Current |
| Log a call | HubSpot | Log button moved, new screenshot for step 4 | Fixed |
| Assign a territory | Salesforce | Lead Source field renamed, step 2 updated | Fixed |
| Request a discount | Salesforce | The approval step no longer exists | Broken |
| Hand off a demo | HubSpot | Every step matched the app | Current |
Replayed, not reminded
Each status comes from running the guide in a test account, not from a review date on a calendar.
You approve every change
Updated steps and screenshots wait for one click before your team sees them.
Owners hear about breaks
A process that no longer works goes to the person who owns it, with the step that failed.
Your guides and change logs in, current guides out.
Guidekeep reads the guides you already have and watches the places where app changes are announced.
What it reads
- Scribe and Tango
- Notion and Confluence
- Salesforce admin change log
- Vendor release notes
Every week and on change
- Replay agenttest account
What your team gets
Guides people can trust
- UGUpdated guidesApproved in one click
- OWOwner alertsWhen a process breaks
- WRWeekly reportCurrent, fixed, broken
Replays run in a test account, not your live one
Tools that record guides, and one that keeps them current.
Recording tools make guides fast. Mintlify and Ferndesk keep docs in step with your own code, and Tettra turns Slack answers into wiki pages. None we found replays your guides to check they still work.
| What you need | Scribe, Tango, Guidde, TrupeerRecord guides | GuruKnowledge base | WhatfixIn-app guidance | GuidekeepKeeps guides current |
|---|---|---|---|---|
| Captures how-to guides | Screen recordings | Written cards | In-app walkthroughs | Imports yours, records the rest |
| Checks that a guide still works | Yearly review, or record it again | Reminds owners on a schedule | Auto-heal for its own overlays | Replays every guide each week |
| Reacts to an app change | For its own overlays | Same-day replay of the affected guides | ||
| Fixes the guide itself | You record it again | The owner edits it | For its own overlays | New screenshot and step, you approve |
| Built for | Anyone writing guides | Company wikis | Large companies | RevOps and enablement on HubSpot or Salesforce |
Start with a list of your stale guides.
We’re opening early access for RevOps and enablement teams at B2B SaaS companies. We aim to send a stale-guide report within 48 hours of bringing in your guides.
Who it’s for
- RevOps, enablement or ops leads
- B2B SaaS companies of 50 to 1,000 people
- On HubSpot or Salesforce, with guides in Scribe, Tango, Notion or Confluence
Common questions
It keeps your how-to guides current. It brings in the guides you already have, records the processes nobody wrote down, replays every guide in a test account each week, and fixes or flags the ones that changed.
An agent follows each guide’s steps in a test account. When a screen or field no longer matches, the guide gets a new screenshot and step for your approval. When the process no longer works at all, it’s flagged to the guide’s owner.
No. When a change shows up in Salesforce’s admin change log or in a vendor’s release notes, the guides it affects are replayed the same day.
We’re starting with HubSpot and Salesforce. Your guides can come from Scribe, Tango, Notion or Confluence.
No. Your existing guides are imported as they are. The processes nobody wrote down are recorded from real screen work, and we do that for you in week one.
No. A new screenshot or step waits for your one-click approval. A process that no longer works goes to its owner to decide what happens next.
No. Replays run in a test account, which we set up with you during week one.
We aim to send a stale-guide report within 48 hours of bringing in your guides: which ones still match the app and which ones don’t.
We’re setting the price with our early-access teams. Join the waitlist and you’ll see it before you commit to anything.