Design partner program · now open

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.

You're on the list.

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.

30+ practitioner conversations 150+ capability records on real enterprise product data
Search Acme GTMSlack
# deal-acme-renewal14 members
✓
ATTEST APP 2:03 PM
Only visible to you
PM-approved · Dev Rao · 28 Oct 2026Contradicted

Not unlimited. Agentic Content caps AI generations at 30 a month for the whole org. Raising it needs a plan change, not a setting.

Record Allocations and LimitsConfidence HighSource Salesforce Help
View record⚑ Flag for owner
Message #deal-acme-renewal
Sample conversation in Slack, illustrative. Verdicts come from approved records, not from a model's guess.
The gap

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.

24–72hrs

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.

Solution engineers and Services, 2026
~70%

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.

Account executives, in ATTEST discovery interviews
100%

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.

Same Services team lead
2 minvs2–3 daysThe same customer question, answered by Services with full context, then by Customer Success after the handover. The customer pays the same fee for slower answers.

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.

How it works

From scattered docs to one approved answer.

No one maintains a spreadsheet. The agent drafts, one named human approves, and everyone else just asks.

Day one: the agent does the heavy lifting6 sources → 1 draft record
PRDsWhat was meant to ship, and for whom
Figma prototypesHow the feature actually behaves
Jira historyWhat shipped, when, and what slipped
Eng design docsLimits, constraints and edge cases
Slack threadsDecisions and workarounds nobody wrote down
Meeting notesCommitments made along the way
Draft capability record with status, limits, editions, how to enable it and the evidence for each line. Then it goes to the owning PM.
01 · Ingestagent

Reads everything. Drafts every record.

Status, limits, editions and how to enable it, each with its evidence attached.

02 · Approve~2 min per record

The owning PM signs off. Nothing goes live without it.

AI generations (Agentic Content)
Limit30 / month / org
Evidence2 sources
✓ ApproveEditReject

A named owner, a source and a date on every record. That is the trust signal.

03 · Answerin Slack

Anyone asks. The verdict comes first.

/attest does MPI support Google Ads?✓ PM-approvedConfirmed. Owner, source and date attached.

Not in the record? One click flags it to the owner. Their answer is saved as evidence.

It gets smarter every time someone is unsure. When a question has no answer, the owner replies once. That reply is saved as dated evidence, and the next person who asks gets it instantly.

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.

Field research

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.

30+conversations with PMs, solution engineers, sellers and Services leads
5enterprise software vendors: Salesforce, Microsoft, SAP, Oracle, ServiceNow
150+capability records drafted on real enterprise product data
2handoffs mapped: Sales to Services, and Services to Customer Success
Documentation readiness from product is a big problem.
Professional Services team leadEnterprise software vendor
A feature-wise documentation repository — what it is, how to implement it, what the limitations are.
Professional Services team leadAsked what would fix it, unprompted
A taxing job no one wants to do.
Professional Services team leadOn refreshing a roughly 250-page implementation guide every few months
Solution engineers ask the Slackbot first. It is good enough to be the default, but it does not know who owns what.
What we heard, paraphrasedSeveral solution engineers
The PM channel works, but every answer takes one to three days and nobody tracks it against a deadline.
What we heard, paraphrasedSolution engineers and Services
Owners move teams and the owner list goes stale, so the question lands on whoever is nearest.
What we heard, paraphrasedCustomer Success and Services
Pre-seed, pre-revenue. That is why we are opening a small design partner program: to prove this on your real product.
Why not search

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 GleanKnowledge layerVerified wikis and cards, such as Guru and ConfluenceATTESTProduct capability truth layer
What it storesDocuments and messages, indexed as they areKnowledge cards on any topic, written by anyoneOne structured record per capability: status, limits, editions, how to enable
Who vouches for itRelevance ranking, no owner sign-offA named verifier, or an AI agent verifying on their behalfThe owning PM approves each record, by name, with a date
When it goes out of dateNot tracked. It reads whatever is indexedWhen a re-check timer runs out, whether or not anyone needed the answerFlagged for review when a real question or claim relies on aging evidence
When it does not knowAnswers from the closest text it findsShows the card, or nothingSays so, and flags the owner in one click
Catches an oversellNot its jobNot its jobContradicts the claim against known limits, by edition, before the proposal goes out
Who is accountableNo capability-level ownershipWhoever last verified it, not necessarily the feature ownerA named owner and backup on every capability, with a deadline on each escalation
Where people use itSearch bar, chat and SlackApp and SlackSlack-native with /attest, plus a web app for owners
Owner answers improve itNot by designEdits stay on the pageEvery 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.

Inside the product

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.

Needs my answer 1Questions routed to you
Contradicted claimsWhere the record disagreed
Record healthWhat needs re-verifying
What people askQuestions on your products
Ask a question, e.g. “Can Agentic Content generate unlimited emails?”
What are the Blocker limitations for Agentic Content?Which MPI capabilities are Marketing Intelligence-only?What is the monthly generation limit in Agentic Content?
Recent activity
Asked in Slack 31 Oct 2026, 13:03 UTC · AI Image Generation and Editing
/attest Can Agentic content generate unlimited no of images
Priya Nair · Product Manager · #ask-attest
Showed: AI Image Generation and Editing, Allocations and Limits · Blocker limitation surfaced
Product truth
All capabilitiesRecord healthHandoff guides
Every capability record in your repository. Open one to see its limitations, evidence and full activity timeline.
Marketing Cloud Next › Marketing Performance Intelligence
Cross-Channel Marketing Analytics DashboardsCAP-0001 · Marketing Performance Intelligence
GA Blocker 3 limitations
Goal TrackingCAP-0002 · Marketing Performance Intelligence
GA 0 limitations
Journey PathingCAP-0003 · Marketing Performance Intelligence
GA 0 limitations
Email & SMS Attribution (First- and Last-Touch)CAP-0004 · Marketing Performance Intelligence
GA Blocker
All activity
Every claim, question, lookup and Slack thread across the capabilities you can see, newest first.
39Claims and questions
10Claims contradicted
4Open escalations
13Questions asked in Slack
Where claims get contradicted
Email & SMS Attribution2 contradicted
AI Content Generation and Refinement2 contradicted
Cross-Channel Analytics Dashboards2 contradicted
Data Management Tab1 contradicted
Open escalations
Workspace CollaborationEscalated to Sam Patel · open 11 days
Data Management TabEscalated to Priya Nair · open 13 days
Allocations and LimitsEscalated to Dev Rao · open 2 days
My work
What needs you, and what you're waiting on.
Routed to you 1
Asked in ATTEST 31 Oct 2026, 11:01 UTC · Allocations and Limits
what is the allocation limit for MCG & MCA on no of flows that can be created
Priya Nair · Product Manager · Home
Asker replied Marketing Objects storage for Advanced is 50 GB on one page but 40 GB on another. The two pages disagree.
Escalated to Dev Rao · open 2 days · SLA breached (24h)
Priya Nair Asker 31 Oct 2026, 11:05 UTC
Marketing Objects storage for Advanced is 50 GB
Respond to the person who asked. They get it in ATTEST and in a Slack message.

FAQ

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.

Design partner program

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.

You're on the list.

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.

What you get
  • 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
What we ask
  • One product area to start with
  • One PM to approve records
  • Honest feedback every week
Prefer to talk first? Book a 20-minute call →

Pick the exact date and time that suits you, in your own time zone. We'll confirm by email.

We use your details only to arrange the call.

Thanks. We'll be in touch.

We'll reply to the email you gave to find a time.