Stop selling features that don't exist.
ATTEST is the PM-approved source of truth for what your product can actually do. An agent drafts each feature record from your product docs, the owning PM approves it in two minutes, and Sales, Services and Customer Success get the verified answer in Slack with /attest.
A founder will email you personally to set up your first product area.
Or skip the wait: book a 20-minute setup call with a founder.
For product and GTM teams at enterprise software companies. A founder replies personally.
Not unlimited. Agentic Content caps AI generations at 30 a month for the whole org. Raising it needs a plan change, not a setting.
Sales oversells. Services absorbs it. Nobody owns the truth.
Product knowledge lives in release notes, wikis and a few people's heads. By the time a customer asks, nobody can say what is real, and nobody knows who to ask.
To reach the PM who owns the answer.
Questions wait in a shared Slack channel. Nothing tracks the delay, so it is felt, not measured. Past a point it becomes a Jira ticket.
Of account executives know they are overselling.
Another ~30% sell features that do not exist at all. The demo typically runs 3 to 6 months ahead of what is generally available.
Of customers hit implementation friction after signing.
Services spends one to two months just learning what a newly signed deal actually needs. The documentation says if a feature exists, not how to turn it on.
It is not bad faith. Documentation decays because nobody is paid to maintain it, and every handoff makes the picture worse.
From 30+ ATTEST discovery interviews. These are interview accounts, not a measured study.
From scattered docs to one approved answer.
No one maintains a spreadsheet. The agent drafts, one named human approves, and everyone else just asks.
Reads everything. Drafts every record.
Status, limits, editions and how to enable it, each with its evidence attached.
The owning PM signs off. Nothing goes live without it.
A named owner, a source and a date on every record. That is the trust signal.
Anyone asks. The verdict comes first.
Not in the record? One click flags it to the owner. Their answer is saved as evidence.
Live today: product docs, release notes, the web app and /attest in Slack. Connected with design partners: PRDs, Jira, Figma, design docs, Slack threads and meeting notes.
30+ conversations. The same gap every time.
We spoke with product managers, solution engineers, sellers and Services leads before writing a line of product. Here is what they told us.
Documentation readiness from product is a big problem.
A feature-wise documentation repository — what it is, how to implement it, what the limitations are.
A taxing job no one wants to do.
Solution engineers ask the Slackbot first. It is good enough to be the default, but it does not know who owns what.
The PM channel works, but every answer takes one to three days and nobody tracks it against a deadline.
Owners move teams and the owner list goes stale, so the question lands on whoever is nearest.
Search tools find text. ATTEST governs the truth.
Glean retrieves and summarises what is already written down. Guru adds verified cards, with a named verifier and a re-check timer. ATTEST keeps one record per product capability that its owner stands behind, and re-checks it when someone actually relies on it.
| Horizontal searchEnterprise search and agents, such as Glean | Knowledge layerVerified wikis and cards, such as Guru and Confluence | ATTESTProduct capability truth layer | |
|---|---|---|---|
| What it stores | Documents and messages, indexed as they are | Knowledge cards on any topic, written by anyone | One structured record per capability: status, limits, editions, how to enable |
| Who vouches for it | Relevance ranking, no owner sign-off | A named verifier, or an AI agent verifying on their behalf | The owning PM approves each record, by name, with a date |
| When it goes out of date | Not tracked. It reads whatever is indexed | When a re-check timer runs out, whether or not anyone needed the answer | Flagged for review when a real question or claim relies on aging evidence |
| When it does not know | Answers from the closest text it finds | Shows the card, or nothing | Says so, and flags the owner in one click |
| Catches an oversell | Not its job | Not its job | Contradicts the claim against known limits, by edition, before the proposal goes out |
| Who is accountable | No capability-level ownership | Whoever last verified it, not necessarily the feature owner | A named owner and backup on every capability, with a deadline on each escalation |
| Where people use it | Search bar, chat and Slack | App and Slack | Slack-native with /attest, plus a web app for owners |
| Owner answers improve it | Not by design | Edits stay on the page | Every owner reply is saved as dated evidence and reused on the next ask |
Based on public product descriptions as of November 2026. Capabilities vary by plan and configuration. ✓ built for it, ~ partly, – not designed for it.
Limits, contradictions and open questions in one place.
Every capability shows its status and known limitations. Contradicted claims and questions waiting on an owner are one click away.
Questions teams ask before they start.
What is ATTEST?
ATTEST is a PM-approved record of what your product can actually do. Each feature has one record with its status, known limits, editions, how to enable it, and a named owner, source and date. Sales, Services and Customer Success get answers from those records in Slack or the web app.
Who is ATTEST for?
Enterprise software companies whose Sales, Solutions, Professional Services and Customer Success teams keep asking, “Can the product really do this, and who confirms it?” The people who keep it true are the product managers who own the features.
How does ATTEST work?
An agent drafts a capability record from your product sources. The owning PM reviews and approves it, which takes about two minutes. After that, anyone can ask in Slack with /attest, or in the web app, and get a verdict with the owner, source and date attached.
Which sources does ATTEST read?
It is designed to draft from six: PRDs, Figma prototypes, Jira history, engineering design docs, Slack threads and meeting notes. Today it drafts from product documentation and release notes. The other sources are connected with design partners.
What does ATTEST say when it doesn’t know?
It says so. Verdicts come from approved records by fixed rules, not from a model’s guess. If the records are silent or conflict, the answer is “Needs verification”. One click sends the question to the owner. The owner’s reply is saved as dated evidence, and the next person who asks gets it.
How is ATTEST different from Glean, Guru or Confluence?
Glean searches and summarises what is already written down. Guru keeps verified cards, with a named verifier and a re-check timer. ATTEST keeps one structured record per product capability, approved by its owning PM by name. It checks sales claims against known limits by edition, routes unanswered questions to the owner, and saves each owner reply as evidence for the next ask. Records are flagged for review when a real question relies on them, not just when a timer runs out.
Does ATTEST replace our product documentation?
No. It sits on top of it. ATTEST reads your documentation and turns it into approved, queryable records. When something changes, the owner updates the record once and every team sees the same answer.
Does it work in Slack?
Yes. Type /attest followed by a question in any channel. The answer shows the verdict, limits, owner and source. If you’re unsure, you can flag it for the owner without leaving Slack.
What does a design partner get?
Founder-led onboarding on your own product, capability records drafted from your docs and ready for your PMs to approve, /attest live in your Slack, and a direct say in what we build next. We ask for one product area, one PM to approve records, and honest feedback every week.
Is ATTEST available today, and what does it cost?
ATTEST is pre-seed and working with design partners now. There is no self-serve sign-up. Request access and a founder will reply personally. Pricing hasn’t been set.
Put ATTEST on your real product.
We are working with a small group of product and GTM teams at enterprise software companies. Start with one product area. Within weeks, your Sales, Services and Customer Success teams are asking /attest instead of guessing.
A founder will email you personally to set up your first product area.
Or skip the wait: book a 20-minute setup call with a founder.
A founder replies personally. We use your email only to reach you about the program.
- Founder-led onboarding on your own product
- Capability records drafted from your docs, ready for your PMs to approve
- /attest live in your Slack for Sales, Services and Customer Success
- A direct line into what we build next
- One product area to start with
- One PM to approve records
- Honest feedback every week
Prefer to talk first? Book a 20-minute call →
Thanks. We'll be in touch.
We'll reply to the email you gave to find a time.