When Someone Leaves, the Answer Shouldn’t Leave With Them.
Your team already wrote down how this company works. It is just scattered across a Slack thread, a doc nobody has opened since, and a Notion page three people disagree about. Scri8e reads all of it, answers in plain language, and tells you the moment a source has gone out of date.
Ask it something.
Six Days to Find Something Three Documents Already Said.
One ordinary question at a thirty person company, with a wiki, a documentation culture and a Notion nobody hates. A composite of what teams described to us on our discovery calls, hour by hour.
“What’s our refund window now?” goes into #ops.
Two people answer. They give different numbers.
Someone digs up a Notion page that says 30 days. It was last edited 14 months ago, and nobody can tell whether that matters.
DM to the one person who would actually know. She is on leave until Monday.
The customer is still waiting. Support picks the more generous number, because guessing generously is the safer way to guess.
She is back. She answers in eleven seconds.
Nobody was disorganised and nothing was missing. The answer was written down in three places the whole time. What took six days was working out which of the three was still true.
“Someone left and the product didn’t move forward.”
“Last time someone was on leave and I needed info only they had, I ended up just having to wait.”
“There was always one person everyone went to for info.”
Three different companies, three different interviews, the same sentence.
No Single Tool Has the Whole Answer. It Never Does.
Slack AI can only read Slack. Notion AI can only read Notion. But almost nothing important lives in one place: the decision gets made in a thread, the wording ends up in a contract, and the consequence gets written into a runbook. Here is one real question, split across all three.
“What response time did we promise on the enterprise contract?”
“We agreed four hours for a P1. Eight was the old number, before the Acme contract.”
“Supplier shall respond to Priority 1 incidents within four (4) business hours.”
“A P1 unacknowledged after 15 minutes escalates to the secondary, 30 to the lead.”
Four business hours for a P1, next business day for everything else. It went from eight hours to four when the first enterprise contract was signed in June, and the on-call rota was rewritten to match: unacknowledged after 15 minutes goes to the secondary, 30 to the engineering lead.
Nobody on that team had the whole answer in their head either. It has to be assembled, and assembling it is the work that quietly gets redone every time somebody new asks.
Every Answer Arrives With Its Age Attached.
A search box hands you a document and walks away. It cannot tell you the page is eighteen months old, that the process changed twice since, or that the person who wrote it has left. That gap is why wikis rot, and closing it is the whole product.
- A process or an SOP
- A decision
- Reference material
- Day-to-day chatter
Every source gets sorted into one of these, then measured against its own clock rather than one blanket cutoff. A two month old SOP is perfectly fine. A two month old decision might already be wrong, and Scri8e will say so.
What do we promise on response time in the enterprise contract?
Four business hours for a P1, next business day for everything else. It was raised from eight hours when the first enterprise account was signed in June.
A contract term is reference material. Nine days is nothing, so Scri8e says nothing.
What it will not do yet: referee a flat contradiction between two tools and declare a winner. That one is still being built. Today, when it is not confident, it tells you so instead of sounding sure.
Connect It Once, Then Genuinely Forget About It.
Every wiki fails for the same reason: keeping it current is nobody’s actual job. So we took that job out of the product. There is nothing to tag, nothing to migrate, and no new page for anyone to maintain.
Sign in to the tools you already use
One OAuth click each for Slack, Google Drive and Notion. Then choose exactly which channels, folders and pages Scri8e may read. Nothing is indexed until you pick, so an unscoped account can never quietly hoover up everything.
It reads in the background, and keeps reading
Messages, threads, docs, spreadsheets and wiki pages, along with the date each one was genuinely last touched. It re-reads on a schedule, so what it knows keeps pace with what your team writes. Nothing to tag, nobody to chase.
Ask it in the words you would use with a colleague
Plain language in, plain language out, with every source listed underneath and a clear flag the moment one of them starts getting old. No query syntax, no filters, no guessing which tool it lives in.
- 0 items
- Every hour
- None, ever
Nobody Sees Anything They Could Not Already See.
Scri8e never grants access to anything. It mirrors the permissions that already exist in Slack, Drive and Notion, document by document, and it checks them at the moment somebody asks rather than at the moment it indexed. Same question, two people, two different answers.
What is the salary band for a Band 4 engineer?
Band 4 is $118k to $142k base, plus a 10% target bonus. The range was widened in April after the market review.
What is the salary band for a Band 4 engineer?
The bands themselves aren’t something you can open. What is public: reviews run twice a year, and any change to a band needs sign-off from the people lead.
Checked when you ask, not when it indexed
Permissions are resolved at query time against the live membership of every channel, folder and file. Someone loses access on Monday, they lose it here on Monday.
Read-only, on purpose
Scri8e has no ability to post, edit, move or delete anything in Slack, Drive or Notion. The worst it can do is quote something back to someone who could already read it.
Your content stays yours
Each workspace is stored and queried separately. Your messages and documents are never pooled with another company’s, and they are never used to train a model, ours or anyone else’s.
What we don’t have: a SOC 2 report. We’re early, and we’d rather tell you that than imply otherwise. If you need one before you can sign, say so on the waitlist form and we’ll tell you honestly where it stands.
Four Ways to Look Something Up. None of Them Tell You What Is Current.
All of them are fine at finding a document, and most teams have two or three of them running already. The gap is identical every time, and it is the row you would never think to ask a vendor about.
| A wiki you maintain | The AI inside one tool | Enterprise search | A general chatbot | Scri8e | |
|---|---|---|---|---|---|
| Reads across Slack, Drive and Notion | Only what someone pasted in | Only its own tool | Yes | No | Yes, all three, in one answer |
| Tells you when an answer has gone stale | No | No | No | No | Yes, inside the answer itself |
| Respects the permissions you already have | Yes | Yes | Yes | No idea who you are | Yes, per document, at query time |
| Someone has to keep it up to date | Constantly, and nobody does | No | No | Not applicable | No, it re-reads on its own |
| What it takes to get value | Months of writing | Minutes | A procurement cycle | Pasting context every single time | Connect three tools, then ask |
| What it costs | Cheap, plus the upkeep nobody counts | Bundled into a per-seat plan | Tens of thousands a year, with a sales call | Per seat, per person | $99 a month, the whole team |
What Teams Actually Ask It.
Not trivia, and not search. These are the questions that quietly stop work for a day or two, because the only person who knows the answer is asleep, on leave, or gone.
Who can approve a refund over $500 while Dana is on leave?
What’s the escalation path if a P1 isn’t picked up?
Why did we move off the old billing provider?
What did we actually promise this customer in their contract?
How does a release actually get out the door here?
Who owns pricing changes, and who has to be told?
One Price, However Many People Ask.
Not per seat. A ten person team and a fifty person team pay the same, because charging per head to ask a question is a strange way to encourage asking.
- Everyone in the workspace, no seat counting and no per-person maths
- Slack, Google Drive and Notion, scoped to the folders and channels you choose
- Unlimited questions, with sources on every single answer
- Permission checks per document, at the moment each question is asked
- Freshness checks on every answer, and a warning when a source is old
- Read-only. Scri8e answers, it doesn’t act on your behalf
- Asking from inside Slack, and an endpoint your own AI tools can query, are next
- No SOC 2 report yet, and no self-hosted option yet
We would rather list this here than have you find it out in week two.
The Questions People Ask Us on the First Call.
Including the three where the honest answer is still “not yet”. We would rather you find those out here than in week two.
Your content is stored and queried per workspace, never pooled with another company’s, and never used to train a model. Scri8e connects with read-only scopes, so it can index and quote but cannot write. We don’t have a SOC 2 report yet and we say so plainly rather than dressing it up.
Next Time Someone Is Out, the Work Keeps Moving.
We’re taking on a small number of teams at a time so we can set each one up properly. Leave your work email and we’ll write when it’s your turn.
$99 a month
Flat, for the whole team
About ten minutes
To connect and start asking
Read-only
It can’t change anything you have