Not a workflow.
An operator.
A Scribe runs the recurring work behind your company. Campaigns, code, exceptions, reports, research.
A Scribe runs the recurring work behind your company. Campaigns, code, exceptions, reports, research.
Last 28 days, Actual Production Scribes
0
tasks shipped
Spanning ads, code, reports, research, and admin. Delivered to queues, not chat windows.
0
hours active work
Billed only while the Scribe was actually working. No seats, no idle time, no token math.
A Scribe's Week
Active Task List
Owns paid-growth execution, engineering triage, and weekly reporting end to end.
Research top waitlist prospects
Pull company signals, recent hires, funding, and product changes. Write a personalized first-touch draft per account.
Analyze pricing-tier impact on LTV
Query the product database, segment cohorts by tier, plot retention curves, and write a recommendation memo.
Build out Google Search and Meta campaign
Creative, audiences, budgets, pixel events. Pushed live across both networks with safezone QA before launch.
3 Instagram story ad variations, review before push
Scribe generated the creative, ran the safezone box, fixed headline position, and attached transparent-logo PNGs. Paused for approval.
Fix error-monitor sampling and broken frontend config
Diagnosed via CLI, patched backend sampling, corrected the public-layout config, opened a PR, merged after checks passed.
Daily dependency upgrade audit
Reviewed 6 open bump PRs, merged 4 after test runs, escalated 1 with a breaking change for your review.
Weekly ads deep-analysis report
Pulled 7 days of spend data across Meta, Google, and Reddit, joined to product activation, summarized by campaign, emailed the report.
Pulled main branches for both repos, checked overnight deploys, logged two warnings to review later.
Opened ad accounts across three networks, captured yesterday's spend and conversions, drafted the daily status email.
Generated a safezone preview for the new creative variants, flagged one for manual review, attached it to the approval task.
Triaged overnight exceptions, auto-resolved three, escalated one with enough context to decide in under a minute.
Surface
Structured plugins where an API earns its keep. A browser for everything else.
Examples from the Field
A snapshot of real standing orders Scribes are carrying today. Each queue is written to fit its operator, these are just a few patterns we see.
Yesterday's ad spend, conversions, and pacing across Meta, Google, and Reddit. In your inbox before coffee, formatted for a phone.
Revenue, churn, pipeline, and the top three blockers. Rolled up from the tools you already use, written in prose, not a dashboard link.
Clusters new exceptions, auto-resolves the noise, escalates the real ones to Slack with enough context to decide quickly.
Scrapes the pricing pages you care about, captures changes, writes a one-page summary if anything moved. Otherwise stays quiet.
Reviews open bump PRs, runs the tests, merges the safe ones, escalates anything with a breaking change.
"Book travel Thursday." "Research this market." "Draft the positioning memo." Drops into the queue, worked in priority.
Priced Like Talent
Active work time only. Reasoning, browsing, writing, calling APIs. No seats, no token math, no idle fees. A transparent invoice every month, with a trail of what your Scribe actually did.
The Obelisk Model
Start narrow, keep humans on approvals, and expand only after the queue proves itself.
Start with one queue.
Keep humans on approvals.
Expand after trust is earned.
Your Scribe's Inbox
Email it from your phone, a meeting, the back of a cab. It picks up the work, does it, and writes back with the result — not a status update, the actual thing you asked for.
Push campaigns, adjust bids, generate creative with safezone QA, report outcomes mapped to real activation, not just clicks.
Read the monitor, cluster the noise, auto-resolve what's trivial, escalate what's real, ship small fixes via code-agent CLIs on the VM.
Inboxes, reconciliations, vendor requests, follow-ups that go cold. The work that sits between teams and never gets owned.
Query the product database, pull from the ad platforms, synthesize a memo. Not a chatbot answer, a written artifact you can forward.
Latest