A campaign brief for a single product launch takes a marketing team three days to write and two days to execute. That ratio is backwards, and it is the norm at most B2B companies still looking for AI agents for marketing teams that do more than generate copy faster. The brief bounces between the head of marketing rewriting the positioning, a content lead trying to translate that positioning into a landing page, and a growth marketer who finds out about the launch on day four with no time left to build the paid or lifecycle motion around it. Meanwhile the content calendar that felt sharp in January is publishing posts in April that nobody searches for anymore, chosen off a competitor's blog or a trending LinkedIn thread rather than actual demand. And when the quarterly review comes around, the paid team's attribution model says organic content drove 4% of pipeline, the content lead's own spreadsheet says 22%, and nobody in the room can reconcile the two because each channel owner built their own tracking in isolation. None of this is a tooling gap in the sense of needing another dashboard. It is a coordination gap: positioning, content, and growth are three disciplines that need to hand work to each other in sequence, and most generalist AI tools available to marketing teams treat them as one undifferentiated writing task.
Why ChatGPT and AI writing assistants don't fix a marketing team's actual bottleneck
Open ChatGPT or Claude.ai with that campaign brief and you will get serviceable copy in thirty seconds. It will not ask what your current positioning actually is, whether the launch collides with a claim the sales team is already using, or whether the content calendar covered this angle two months ago. A generalist chatbot answers the prompt in front of it. It has no memory of last quarter's positioning work, no visibility into what has already been published, no sense of which channel the growth motion is optimizing for this month. Ask it to write the launch page and it writes a launch page; ask it the next day to write three social posts about the same launch and you will get copy that quietly contradicts the page's core claim, because the chatbot re-derived the positioning from scratch instead of pulling from one source of truth. For a solo marketer testing an idea, that is tolerable. For a team of three or four people running parallel motions against the same launch, it produces exactly the inconsistency that shows up in the next QBR as 'why does our website say one thing and our LinkedIn ad say another.'
AI writing assistants embedded in marketing tools (Jasper, Copy.ai, the AI draft button inside HubSpot or Webflow) solve a narrower and different problem. They are fast, on-brand once fed a style guide, and genuinely useful for producing volume. But they are autocomplete, not strategy. They complete the sentence you started; they do not decide whether the sentence should exist. None of them will tell you that the blog post you are about to draft targets a keyword pulling 40 monthly searches when a five-minute rewrite of the outline would target one pulling 480. None of them coordinate a handoff, so the positioning that drafted your landing page headline is not the same positioning the growth team is running in paid ads, because there was never a shared document for either to read from. The gap is the same shape as the ChatGPT gap: strong at the sentence level, blind at the campaign level.
Meet Pitch, Ink, and Surge: AI agents for marketing teams that hand off work in sequence
Pitch is the product marketing engineer on tonone's team: positioning, messaging, value proposition, go-to-market sequencing, and launch copy. It does not work alone. Ink owns the content side, blog strategy, SEO, and the editorial calendar. Surge owns growth, acquisition channels, activation, and retention. The three read from the same positioning and hand work to each other in a defined sequence instead of each re-deriving the message independently, which is the actual failure mode generalist tools have no mechanism to prevent.
Pitch anchors every campaign in one positioning document that Ink and Surge both read from, so a launch page, a blog post, and a paid ad make the same claim in three different formats instead of three different claims.
Reading the current position before writing anything
Before Pitch drafts anything, pitch-recon reads what already exists: the current positioning doc if there is one, the last three launch pages, the messaging sales is actually using on calls, and any customer language pulled from support tickets or interviews. Most marketing teams skip this step under deadline pressure and end up rewriting the value proposition from a blank page every quarter, which is exactly how a company ends up with four slightly different descriptions of what it does living across the website, the deck, the outbound sequence, and the last blog post. The recon output is a short brief: what claim is currently live, where it is inconsistent, and what customer language is available to strengthen it. That brief becomes the input to every downstream piece of copy for the cycle, so the campaign brief that used to take three days to write starts from a grounded baseline instead of a blank document.
Locking positioning so every channel repeats the same claim
pitch-position takes the recon output and produces the single positioning statement for the cycle: who the product is for, what it replaces, the primary claim, and the two or three proof points that back it. This is the document that ends the argument between the content lead who wants to lead with 'automation' and the growth marketer who wants to lead with 'ROI.' Once positioning is locked, it becomes the shared reference for the blog post Ink writes, the landing page Pitch drafts with pitch-landing, and the ad copy Surge tests. Nobody re-derives the message independently, which is the difference between a coordinated campaign and three people writing the same launch from three different mental models of what the product does.
Turning positioning into channel-ready messaging
With positioning locked, pitch-message translates it into channel-specific messaging: the one-liner for the homepage, the subject line for the launch email, the three variants for paid social, the talking points for sales. This is where a generalist chatbot's speed advantage disappears, because the value of pitch-message is not that it writes fast, it is that every variant it produces is a restatement of the same locked claim rather than a fresh interpretation of it. When Ink later writes a cluster post referencing the launch, or Surge tests three ad variants for it, they are all pulling from messaging that was already channel-adapted and approved, not reinventing the phrasing under their own deadline.
This is where the handoff to Ink and Surge matters most. Positioning and messaging solve the brief-writing bottleneck; they do not solve a stale content calendar or unreconciled attribution on their own. Those two failures live downstream, in the calendar Ink builds and the funnel Surge instruments, and they only get fixed if both agents are working from the same locked claim instead of freelancing their own interpretation of what the product does.
Handing distribution to Surge before the launch ships, not after
The reason a growth marketer finds out about a launch on day four is that distribution planning gets treated as the last step instead of a parallel one. Surge's surge-activation skill takes the same locked positioning Pitch produced and maps it against the signup funnel before the launch page or the first blog post goes live: which step in onboarding the new message should reinforce, what the activation email sequence needs to say to match the claim a visitor just read on the landing page, and where a UTM-tagged CTA needs to sit so the click is attributable back to the specific piece of content that produced it. Pulling Surge in at this stage, rather than after content ships, is what turns 'we'll share it on social' from a vague afterthought into an actual funnel with a measurable step. It also means that when Ink's calendar goes live, every post already has a defined next step for the reader instead of ending on a paragraph with no path forward.
A worked example: rebuilding a calendar around real demand instead of a gut-feel topic list
Almanac Robotics sells warehouse automation software to 3PL operators. Its three-person marketing team, Dana (head of marketing), Priya (content lead), and Sam (growth), had a quarterly content calendar built the way most early-stage teams build one: six topics pulled from a competitor's blog and two from a trending LinkedIn thread about the future of logistics. Six posts had shipped over the previous two quarters. None ranked in the top 20 for any query. Priya could not say why, because nobody had checked whether the topics matched anything their actual ICP, warehouse operations managers evaluating automated guided vehicles, was typing into Google.
Dana handed the calendar to Ink with the locked positioning Pitch had just produced. Ink ran ink-seo against the ICP definition and the positioning claim, pulling real search volume and keyword difficulty for the topic space, then ran ink-calendar to rebuild the quarter's slate around what operations managers were actually searching for instead of what the team assumed they cared about. The difference between the old list and the rebuilt one was not subtle.
Old calendar (gut-feel, sourced from competitor blog + LinkedIn trend)
- "The Future of Warehouse Automation" 40 mo. searches, KD 61, informational, no CTA path
- "Why Robotics Matters in 2026" 20 mo. searches, KD 55, no ICP intent
- "5 Trends Reshaping Logistics" 90 mo. searches, KD 58, too broad, ranks nobody
Rebuilt calendar (ink-seo + ink-calendar, mapped to ICP demand)
- "warehouse pick error rate reduction checklist" 210 mo. searches, KD 18, commercial intent
- "AMR vs AGV cost comparison for 3PL warehouses" 480 mo. searches, KD 24, pillar post, cluster anchor
- "how to calculate warehouse robot ROI" 320 mo. searches, KD 21, commercial, links to pricing
- "pick to light vs voice picking accuracy" 260 mo. searches, KD 19, cluster post
- 8 more cluster posts linked back to the AMR vs AGV pillar
Projection: 12-post cluster reaches ~1,800 organic sessions/month by month 4,
vs. ~150/month projected from the old topic list at current rankings.
Distribution: surge-activation wires each post's CTA to the trial signup
funnel with UTM tags, so the attribution question stops being three
spreadsheets and becomes one number Dana can read.The gap was 12x in projected organic sessions, and it came entirely from targeting queries the ICP was already typing instead of topics the team found interesting. Every post in the rebuilt calendar also links to at least two others in the cluster and to the pillar comparison post, so the internal linking that makes a cluster compound over time was built in from the first post rather than retrofitted after the fact. Sam then used surge-activation to wire each post's call-to-action into the same signup funnel with consistent UTM parameters, which meant that by the time the next quarterly review happened, organic content's contribution to pipeline was one number everyone in the room agreed on, not two competing spreadsheets.
Ink does not pick topics from a trending list. It runs ink-seo against the ICP's actual search behavior first, then builds the calendar with ink-calendar around what that research surfaces.
Pitch, Ink, and Surge vs the alternatives
None of this replaces a marketing team's judgment. It replaces the redundant work of re-deriving the same positioning three times and the guesswork of building a calendar off instinct instead of demand data. The table below is specific to what a marketing team actually needs from an AI tool: not code generation, but a coordinated system that keeps a locked message intact across every channel and ties content to measurable demand.
| Capability | Tonone | Generalist chatbot | AI writing tools (Jasper, Copy.ai) |
|---|---|---|---|
| Locks one positioning claim across channels | Yes, pitch-position produces a single locked statement Ink and Surge both read from | No, re-derives the message on every new prompt | No, drafts per request with no shared source of truth |
| Builds content calendar from real search demand | Yes, ink-seo pulls search volume and difficulty before ink-calendar assigns topics | No, suggests topics with no keyword data behind them | No, drafts whatever topic you type in, no research step |
| Coordinates campaign, content, and growth handoffs | Yes, Pitch, Ink, and Surge hand off in sequence from one brief | No, one conversation thread with no cross-team memory | No, single-purpose drafting tool, no coordination layer |
| Ties content CTAs to a measurable signup funnel | Yes, surge-activation wires UTM-tagged CTAs into the activation funnel | No, no funnel or attribution awareness | No, produces copy, not instrumentation |
| Channel-adapted messaging from one source claim | Yes, pitch-message translates the locked claim per channel | Partial, will draft variants but each may drift from the last | Partial, drafts fast but with no locked reference to check against |
A marketing team's real bottleneck is not writing speed, it is that positioning, content, and growth each reinvent the message independently. Pitch, Ink, and Surge fix that by handing off from one locked source.
If your team's campaign brief takes longer to write than to execute, start with /pitch-position before touching a content calendar or an ad account. Lock the claim first, then hand it to Ink for /ink-seo and /ink-calendar, and to Surge for /surge-activation. Coordination, not more copy volume, is what closes the gap.
Tonone is free and MIT-licensed. Install it once and Pitch, Ink, Surge, and the rest of the marketing and product roster are available in your Claude Code session. You pay only for the Claude Code token usage during the work itself.
1. Add to marketplace
2. Install Pitch
Frequently asked questions
What does Tonone's Pitch do for a marketing team?+
Pitch is the product marketing engineer on tonone's team. It runs pitch-recon to audit existing positioning and messaging, pitch-position to lock one positioning statement per campaign cycle, and pitch-message to adapt that statement into channel-specific copy for the homepage, email, paid social, and sales talking points.
How do Ink and Surge work with Pitch?+
Ink and Surge both read from the positioning Pitch locks instead of re-deriving the message independently. Ink builds the content calendar around it with ink-seo and ink-calendar, mapping topics to real search demand. Surge ties content and campaign CTAs to the activation funnel with surge-activation, so growth and content share one attribution source.
How is this different from using ChatGPT for marketing content?+
ChatGPT answers each prompt independently with no memory of prior positioning decisions or what has already been published. Pitch locks a single positioning claim per cycle, and Ink and Surge build from that same claim, so a launch page, a blog post, and an ad all repeat the same message instead of drifting apart.
Can Tonone fix a content calendar that keeps going stale?+
Yes. Ink's ink-seo skill pulls actual search volume and keyword difficulty for a team's ICP terms before ink-calendar assigns the quarter's topics, replacing calendars sourced from competitor blogs or trending social topics with ones mapped to real demand.
How does Tonone help reconcile marketing attribution across channels?+
Surge's surge-activation skill wires each piece of content's call-to-action into the signup funnel with consistent UTM tagging, so organic content's contribution to pipeline is one number the whole team can read instead of separate, disagreeing spreadsheets per channel.
Do I need a separate keyword research tool alongside Tonone?+
No. Ink's ink-seo skill performs the keyword research (search volume and difficulty) directly, and hands the output straight into ink-calendar for topic assignment, without needing a separate SEO tool in the loop.
Is Tonone free to use for a marketing team?+
Yes. Tonone is MIT-licensed and free to install. Pitch, Ink, Surge, and the rest of the roster are available in the same Claude Code session. You only pay for the Claude Code token usage during the actual work.
What's a realistic result from mapping a content calendar to search demand instead of gut feel?+
In a worked example, rebuilding a 6-post gut-feel calendar into a 12-post cluster mapped to actual ICP search terms projected roughly 1,800 monthly organic sessions by month four, versus around 150 monthly sessions projected from the old topic list, a 12x difference driven entirely by targeting queries the audience was already searching.