For teams without a research seat

The work nobody
on the team owns.

A team of six has no analyst, no researcher and nobody whose job is the write-up, so it lands on whoever has the evening free. Else takes that work as an explicit hand-off, does it against sources and files you give it, and returns a document plus a receipt — and it cannot send, post or publish anything without a person saying yes.

Where the week goes

Four jobs with
no owner between them.

Not one of them justifies a hire. Together they take an evening a week off somebody who was hired to do something else.

The 11pm competitor check
Done by whoever cares most, which is usually the founder, which is why it happens at 11pm or not at all.
The write-up nobody owns
Everyone has the context in their head and nobody has the two hours to put it into a document other people can read.
“Can someone pull the numbers?”
A five-minute ask that costs forty, and interrupts the one person who knows where the numbers live.
The same question, asked twice
Two people research the same thing a month apart because the first answer was never written down anywhere findable.
The hand-off, word for word

One person hands it over.
Everyone reads the result.

Written like a brief to a contractor who is competent, literal, and not allowed to touch your accounts without permission.

Copy this, change the brackets

“Look into [question] using current public sources. Write it up as a two-page brief: what we know, what we don’t, and every claim linked to where you found it. Save it as a file. Don’t send, post or publish anything — I’ll share it with the team myself.”

When it finishes you can turn on a read-only link so a colleague sees the run and its answer without an account of their own. The produced files stay with you and are not included in what the link shows, so sending the document round is still a deliberate act by a person.

What it does, what you get

It works where you work,
with the brakes on.

The three things a team actually needs from a stand-in: it can reach your tools, it asks before it acts, and it accounts for the money.

01 — CONNECTS
Six apps, then the long tail
Gmail, Google Drive, Slack, Notion, GitHub and Airtable connect first-class. Most other apps connect by pasting a key — and your details are encrypted and never shown to the AI.
02 — ASKS FIRST
Three settings, one default
Before anything leaves this app is the default, covering sending, publishing, buying and changing things. The looser settings are yours to pick; sending an email asks regardless.
03 — ACCOUNTS FOR ITSELF
A receipt per run
Total, the run’s spend limit and how much of it was used, and itemized lines — including each action a connected app performed. Nothing is rounded to look tidier.
Cost and control

Per run, per person,
on the record.

There are no seats to buy and nothing to cancel. Money is spent a run at a time and shown a run at a time.

Which tier it runs on
Auto · Fast · Smart · Max
Price depends on the tier — Auto, Fast, Smart, or Max. Auto picks per request; Fast is the cheapest acceptable answer; Smart is balanced quality with long context; Max is the deepest reasoning.
Each run’s own limit
$0.15 by default · up to $5
Every run carries a spend limit — $0.15 by default, and you can set it as high as $5. Reach it and the run pauses and asks you before going on. Settings also carries a threshold above which a task should always check with you: $0.10, $0.50, $1.00 or $5.00.
The receipt
Itemized, unrounded
One receipt per finished run, with the total, the limit, the percentage used and the line items. A run that consumed nothing shows no charge at all.

No per-seat price appears here because there are no seats, and no “$X per brief” figure appears because a tier carries no fixed price. The number that is real is the one on the run’s receipt.

Where it falls short

What it will not do
for your team.

If you are choosing between this and a part-time hire, these are the parts a hire would still cover.

It is not a shared seat
There is no team account, no shared queue and no view of a colleague’s work. Everyone runs from their own account and their own balance; the only thing that crosses between you is a read-only link somebody chooses to send.
The shared link excludes the files
A colleague with the link sees the run and the written answer. The produced documents stay with the owner of the run, so distributing the deliverable is still manual work.
It has no view on your business
It will tell you what it found and what it could not confirm. It has no opinion about your pricing, your customers or your roadmap, and it should not be treated as though it does.
Approvals mean it can stall
Because the default is to ask before anything leaves the app, a run can sit parked for as long as nobody answers. That is the safe failure mode, but it is still a failure mode on a deadline.
It sometimes returns “I couldn’t confirm this”
When a turn has no ability to browse or open files, it says so rather than improvising an answer, and it will not invent an account or a credential it does not have. Honest, and occasionally less useful than you wanted.
The spend limit is a brake, not a wall
The spend limit is a brake, not a wall. It is checked between steps, so one long step can finish a little above the number you set before the run pauses. Read it as “stop soon after this”, not “never exceed this”.
Fair questions

Asked and answered.

Is there a team account or a shared workspace?
No. Each person hands work off from their own account, with their own balance, their own spend limit and their own receipts. What you can share is a read-only link to a finished run.
Can a colleague see the files it produced?
Not through the link. A shared run is read-only and the deliverable files stay with the person who ran it — they are removed from what the link shows. If a colleague needs the document, you download it and send it.
Which of our tools can it work inside?
Gmail reads, drafts and sends with approval. Google Drive finds files and saves deliverables. Slack reads threads and publishes updates. Notion searches notes and creates pages. GitHub reads repositories and opens pull requests. Airtable reads and updates connected records. Most other apps connect by pasting a key, and your details are encrypted and never shown to the AI.
Can we stop it acting on its own?
That is the default. Before anything leaves this app is selected out of the box, covering sending, publishing, buying and changing things. The stricter and looser settings are yours to choose, but sending an email asks either way, and Plan before doing — which shows you the steps first — is on by default too.
How do we know what it cost us?
Price depends on the tier — Auto, Fast, Smart, or Max. Each run sets its own limit before it starts, $0.15 by default and up to $5, and finishes with a receipt showing the total, the limit, how much of it was used, and itemized lines. Every action a connected app takes appears there too.
Other kinds of work

Not quite your job?

Scattered files into one document
DocumentsRead on →
Work that comes back every week
Standing workRead on →

Hand over the job
nobody was hired for.

Free to start · no card needed · Price depends on the tier — Auto, Fast, Smart, or Max.

Try Else
Try Else