Scan sales replies, founder updates, launch emails, support messages, and social drafts before they leave the workspace. One Authenticity Score across the team, sentence-level highlights for the AI passages, and a pricing path that starts at Pro and steps up to Business once you cross five people. Built for seed-stage startups, indie agencies, and founder-led shops shipping cross-function writing every week. Free to try. No card.
Seed and Series A startups, indie agencies, founder-led shops, and the first ten hires at any small B2B company. One workspace, two to five AI tools across the team, no content lead on payroll, and a writing surface that spans sales, marketing, support, and the exec layer.
The team is small enough that the founder is still in the writing. Cold replies to qualified inbound. Launch copy on the new feature page. The Notion doc that becomes a help article. The LinkedIn thread before the demo call. The same week, two operators draft a customer success email, a paid ad rotation, and three social posts. Every surface lands in front of a prospect or a customer, and every surface gets shaped by whichever AI assistant happened to be open at the time.
At this size, content is not a department. The founder writes the launch post; an operator writes the follow-up email; a designer writes the social caption. There is no editor on staff and no editorial policy doc that anyone has actually read. The scan replaces the policy because the score travels with the draft and reaches every teammate the same way.
A two-person product team writes sales sequences on a Monday and changelog entries on a Wednesday. A three-person agency partner team writes proposals on a Tuesday and pitch decks on a Thursday. Specialisation arrives at 15 or 20 people, not at five. Until then, the same scan covers every surface because the same person is writing across all of them.
Most lean teams have not locked the brand voice yet. The voice is whatever the founder wrote last week plus whatever the operators pattern-matched to. AI drift inside that situation is the most damaging because the team has no internal reference for what should sound right. The sentence-level highlights surface the templated passages every time, and the rewrites that follow are the artefact that locks the voice.
Five surfaces small teams ship every week. Each one is high-stakes per send because volume is low and every recipient is a real person the team will remember by name. A flat AI line on any of them costs a relationship rather than a percentage point.
At small scale the founder often sends the first ten of every campaign by hand. A templated reply to a warm inbound undoes the trust the inbound established. Target an Authenticity Score above 80 on every personal send and rewrite at the sentence level on anything flagged. The reply rate difference shows up inside the first week.
Monthly investor notes, customer announcements, hiring posts, the year-end summary. The founder voice is what carries these. A flat templated paragraph in the middle of an otherwise sharp update reads as a delegation tell, even when the founder wrote every word. Scan before send and rewrite the AI passages by hand to keep the voice intact.
Lean teams ship landing copy in an afternoon. Without a scan step, the hero ends up sounding like every other SaaS hero on Twitter that week. Scan the hero, the subhead, and the first two feature blocks. The conversion improvement on borderline pages is the metric most teams notice first.
The reply to an annoyed customer. The follow-up after a refund. Support is where AI templates do the most damage because the customer is already frustrated and a templated tone confirms whatever they suspected. Scan replies before send and rewrite anything below threshold by hand. The retention math pays for the plan inside a quarter.
The founder's LinkedIn presence is often the company's only top-of-funnel. An agency-written thread that reads templated within a sentence collapses engagement and the algorithm de-ranks the next post. The same applies to investor decks and conference talk drafts. Scan every piece that lands under the founder name.
Pro at $19.99 a month standard or $14.99 a month on yearly fits a 2 to 3 person workflow. Business at $39.99 a month standard or $29.99 a month on yearly is the team tier from five seats up, with shared scan history, audit log, REST API, and white-label PDFs. Full breakdown on the pricing page.
Billed $89.88/year — Save $30
Billed $179.88/year — Save $60
Billed $359.88/year — Save $120
Yearly billing saves 25%. View full pricing →
The honest pricing math for a small team. Pro covers the solo or duo workflow cleanly. Business is the inflection at five seats where the shared workspace, audit log, and API replace three separate subscriptions plus a Slack thread about who scanned what.
A founder and one operator share a workflow on Pro at $14.99 yearly each. Total cost: $29.98 a month. Each person gets unlimited scans, 50,000 AI rewriter words, 90-day scan history, the Chrome extension, and the WordPress plugin. Shared visibility happens informally because the team is small enough to mention scores in Slack rather than pull a dashboard.
Business at $29.99 yearly covers five seats under one workspace. Compare against five Pro seats at $14.99 each, which lands at $74.95 a month with no shared history, no audit log, no API. Business saves money the moment the headcount math turns, and the consolidated workspace pays back the saving twice over because the team gets one bill, one admin, and one place to see who scanned what.
The first time a founder opens the workspace and sees the last 30 days of scans across every teammate is the moment the workflow stops being individual. Per-seat averages, deliverable types, and trend lines come out of one view. A teammate drifting lower gets a one-line nudge in Slack rather than a quarterly review. The visibility itself is the coaching mechanism.
The Business audit log records who scanned which deliverable with timestamps. Useful the first time a customer or a board member asks how the team guarantees AI quality across published content. The REST API matters when the team grows into a CMS and wants scans wired into draft creation, publish gates, or a custom workflow. Most small teams do not need the API at five people, but every team that grows past ten is glad it is already on the plan.
Brand voice fragments fastest in the first five hires. The founder is no longer the only writer, the new hires lean on different AI tools, and the brand voice averages out toward a neutral templated register inside a quarter. The scan is the diagnostic that catches the drift early.
Reading individual drafts catches individual sentences. It rarely catches the aggregate drift across thirty pieces of writing in a month, which is why founders read a launch email in week 12 and feel something is off without being able to point at it. The scan surfaces the structural drift by showing sentence-level highlights across the whole calendar, not just inside one piece.
Small teams move on shared context, not policy. A policy doc that nobody reads is worse than no policy. The rule that actually works at this size is one sentence: scan before send for anything external. The founder picks a target, usually 80, and everyone hits it. Three months in, the rule is invisible because it has become muscle memory.
The Authenticity Score is the diagnostic, not the goal. Rewriting purely to lift the number flattens the voice. Use the sentence highlights to find the specific lines that drift into stock phrasing, rewrite those in the team's own words, and let the headline score land where it lands. The voice that emerges is the team's, not the classifier's.
Once on Business, the team gets one workspace with shared scan history across teammates and deliverables. The founder pulls a rolling thirty-day view per surface and sees averages instead of anecdotes. A surface drifting toward lower scores gets attention before a published asset does, and the founder reclaims the hour a week that used to go to spot-checking drafts.
Under thirty seconds added per short piece. Under two minutes per long one. The flow disappears into drafting rather than adding a review phase to the team calendar. Chrome extension covers the inline cases; the web app handles the long ones.
Gmail for sales replies. Google Docs for the founder update. Notion for the launch email. Slack draft for the support reply. Whichever AI tool is open is fine. The scan is the standard, not the prohibition. ChatGPT, Claude, Gemini, or a mix all work the same way under the workflow.
The Chrome extension scans inside Gmail, Google Docs, Notion, and most rich-text editors with one click. The score returns in about six seconds. Above the team threshold, the piece ships. Below, the highlighted sentences show exactly which lines need a rewrite. No tab-switching, no copy-paste into a separate tool.
Rewrite by hand if the piece is short and the voice matters. Use the AI rewriter if the piece is long, the deadline is tight, and the team needs the draft to ship today. Either way, rescan and confirm before send. Most short pieces clear the threshold on the first rewrite once teammates learn what the model flags.
There is no editor handoff, no CMS gate, no policy doc that someone has to remember to consult. The score sits in the workspace, the highlights live on the draft, and the teammate ships when both look right. The whole loop is invisible inside the drafting tools the team already uses.
The detector that worked at five people keeps working at fifteen, twenty-five, and beyond. No migration, no re-onboarding, no data loss. Scan history, per-seat averages, and the audit log are already in place by the time the company hires its first content lead.
Business includes five seats. Additional seats bill from the same workspace at the standard per-seat rate. The founder adds a seat the day a new hire starts and the new teammate is scanning the same afternoon. No separate procurement cycle for the eleventh hire, no IT ticket to file.
Team Management ships with an owner role and a member role at small scale. As the team grows past ten, additional roles unlock for senior operators, content leads, and external collaborators. Contractors brought on for a launch can be added with scoped permissions and removed when the engagement ends, without losing the scan history on their work.
At five people the audit log is a nice-to-have. At fifteen it becomes the artefact a marketing lead points at during quarterly reviews to demonstrate consistent AI quality control across the writing team. The same log is already populated from day one on Business, so there is no retrospective backfill exercise when the company decides to use it.
The REST API on Business lets a growing team wire scans into Sanity, Contentful, Webflow, HubSpot, or any custom CMS via webhook on draft creation or status change. We do not ship native plugins for those platforms yet, so integration is API-first with a few lines of glue in your CMS. Most teams add the API the quarter they hire the first dedicated marketing lead.
More for small teams.
The next step up once the team formalises a content function past 15 people.
For marketing →The sequence-and-proposal counterpart for when outbound becomes its own function.
For sales →The per-writer drafting workflow once the team hires its first dedicated writer.
For writers →Free, Starter, Pro, Business. Yearly billing saves 25%. Per-seat math on every tier.
See pricing →Free to try. No card. Pro from $14.99 a month on yearly for the founder plus one or two; Business at $29.99 a month on yearly from five seats up.