Product · Docs

Knowledge that stays close to the work.

Internal wikis, runbooks, customer-specific playbooks. Linked to the records they describe, searchable from anywhere, and built to be opened, not buried in a Notion workspace that nobody touched since onboarding.

Docs that don't get forgotten

Because the best wiki is the one your team actually reads.

Strkr's Docs sit inside the same workspace as your CRM. A runbook for handling escalations links to the contact. A customer playbook links to the account. Search hits records and docs together, so knowledge surfaces where the work is, not three tools away.

Spaces

Team workspaces, with permissions.

Engineering's docs. Sales' playbooks. Onboarding for new hires. Each space has its own membership and write permissions. Public spaces, private spaces, and the customer-shared spaces for the deliverable docs your customers can read.

Record links

A doc per customer. Or per kind.

Pin a doc to an account, a deal, a contact, a project, or a custom record. The record's sidebar surfaces it. Updates flow both ways. The doc and the record stay in lockstep.

Search

Cmd-K across records and docs.

One bar finds every piece of knowledge your team has. No more 'I think it's in the Slack channel from last quarter.' No more switching between five tools to find the playbook you wrote.

Markdown

A real editor. Tables, code blocks, images.

Built on the same primitives developers expect. Paste from a Google Doc and it survives. Export when you need to. Mermaid diagrams, embedded videos, callouts, all the building blocks of a modern doc.

Versioning

Roll back a bad edit.

Every change is recorded. Compare versions side-by-side, restore in one click. The audit log shows who changed what, surfaced to space admins on demand.

Templates

A doc shape, ready to clone.

Customer onboarding template, escalation playbook template, incident retro template, weekly status template. Pick one, fill it in. Less staring at a blank page, more capturing what you already know.

Stop paying Notion + Confluence + Slack snippets.

Docs is a $39/mo add-on that fits inside the CRM your team already opens every day. Save the knowledge close to the work. Search both at once.

Why a CRM should have docs

Three problems the standalone wikis can't solve.

The escalation playbook

Should live on the customer.

Standalone wikis force a copy-paste link into a CRM note. Strkr Docs pin to the account directly. The playbook surfaces when the customer surfaces. Right tool, right time.

The renewal one-pager

Should reference the deal.

Quarterly renewal docs reference real numbers: deal size, contact count, last NPS. In Strkr, those references live as merge fields against the record. The doc stays current as the record changes.

The onboarding handbook

Should know the role.

New AE reads the AE-specific onboarding doc. New SDR reads the SDR one. Strkr Docs spaces have role-based visibility built in, no manual link-sharing required.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.