gtmcron

Overview

gtmcron is the founding role of the team. It runs a founder's or early GTM team's day as scheduled agents on our servers: account research, drafted outbound, a self-tuning funnel, inbound triage, weekly content, a chief-of-staff brief, a pre-launch audit, and launch-day ops. Everything is draft-first; nothing reaches a person, a CRM, or a channel without your yes. There is nothing to install.

gtmcron brings five roles together for founder GTM work. Each role below links to its reference material.

What this role does for a founder

Pick who to sell to first, before you hire anyone to find them. Turn the business behind your website into a focused plan for finding the first customers.

Starts with your URL. The first launch reads your website, proposes a business brief in eight sections with the source behind each, and asks only for what it could not read. If your site describes a concept rather than a launched product, the brief keeps the hypothesis separate from what you can sell today. Once you confirm the brief, market research runs on web search and returns a market estimate with its method, assumptions and sources, or says the estimate is not established, plus up to three customer profiles.

Before it has work

• Your website URL
• A confirmed business brief for everything after the first scan

Where its work goes

• To Sales development: An approved customer profile and the confirmed brief. Research companies and contacts that match it.
• To Account executive: The offer, the buyer problem and the claims you can support. Prepare replies and deal conversations from the same facts.
• To Revenue leader: The commercial assumptions behind the plan. Compare them with what the pipeline and payments say.

Useful from the first minute, because it needs only your website. Market recommendations stay hypotheses until evidence supports them. It cannot validate demand, product readiness or willingness to pay from a website, and a research call runs within a per-launch ceiling of AI calls and web searches. The full overview, with the work, outputs, an example and the measures to watch, is on the GTM strategist page.

Its five roles

Company context is shared across the team, so every role reads the same company, offer, ICP, and voice.

• Company OS Core (Operator): Stand up your Company OS: one canonical business context, four roles, a decision log, a weekly operating review. Required by every other plugin.
• GTM Engine (Closer): An autonomous outbound demand engine: trigger-driven prospecting, a daily standup, a self-tuning funnel report, cold-list recovery, a deal closer.
• Content Engine (Writer): Turn real product activity into top-of-funnel content, timed to what your audience is talking about: a weekly content calendar with drafts, build-in-public posts, release-to-content.
• Founder Chief-of-Staff (Operator): A daily morning brief, meeting prep, and a monthly investor or board update, drawn from your calendar, inbox, and the business.
• Launch Readiness Audit (Operator): A complete pre-launch audit of your repo and website, codebase health, homepage, payments, security (authz + XSS), SEO/GEO/AEO, and launch ops, as a prioritized findings report, a manual operator checklist, and a ready-to-run remediation prompt. Read-only: it never touches your code.
• Inbound and Lifecycle (Closer): Triage every reply, route hot interest, and nurture signups through their lifecycle stages. Pairs with GTM Engine.
• Market Intelligence (Researcher): A weekly competitive sweep and a daily community scan that surface threats, positioning shifts, and high-signal conversations worth a reply.
• Launch Kit (Event): A full launch prep package and a launch-day operations plan with comment templates.

These are licensed by your seat rather than bought one at a time. See /pricing.

Built-in founder / GTM craft library

gtmcron ships with a deep, cited founder craft library so your drafts read like a seasoned operator from day one, before you have uploaded a thing. It covers defining the ICP by the problem (not the firmographic), founder-led selling, the "why now" narrative, positioning against the alternative the buyer actually considers, pricing to a value metric, running investor updates like a sales cadence, distribution and building in public, and hiring the first rep only once the motion repeats. On your first scheduled run these notes seed your knowledge library, so every AI draft grounds on real founder method instead of generic prose. Add your own proof points on top in the console Library tab.

Get started

1. Buy a seat at /pricing ($99 per person per month, which licenses this role and every other one, see Licensing & renewal), then set up at /onboarding.
2. Open your console and connect your tools (CRM, inbox, calendar) in Settings. We custody each token encrypted and read it on the schedule; there is nothing to install.
3. In the console, run "set up my Company OS" first (the sanctioned exception to the "run <product> setup" phrase, kept for installed-base compatibility). It interviews you for company, offer, ICP, and voice, then run each other plugin's own setup.
4. Choose where drafts land in Settings: an in-app draft queue, or your Google Drive. Nothing is sent without your approval.

Licensing & the control plane

Your licence is checked before a run, never during one. The scheduler enumerates only the tenants whose gtmcron subscription is current, so a lapse means the next run is not scheduled, and a run already under way is never cut off. Every run reports its telemetry to your Rollup either way. Details: Licensing & renewal.

One of the 9 roles, and the one a founder's first launch starts with. See Concepts, the unit is a job for how gtmcron relates to the others, such as salescron, leadercron, and secronjob.

Your console (runs on our servers, nothing to install)

By the numbers (live). gtmcron ships 25 hosted skills, 11 of them on an auto-run schedule (daily driver: morning-gtm-briefing). Tier: leadership. These counts are read from the live registry, not hand-typed.

gtmcron has a control surface in your browser at /gtmcron/console. It drives the hosted runtime that runs gtmcron's agents on our servers on a schedule, so nothing depends on you keeping an app open. Scheduled AI work runs on your own provider key (Claude, OpenAI or OpenRouter; every tier is bring-your-own-key), after any platform-funded first-run allowance the deployment turns on. The free deterministic checks need no key. A key turns drafting on; nothing is sent until you turn the send layer on. Bedrock is built but not accepting keys yet; Settings shows it as coming soon until the transport is validated.

Today and Activity link to the original work in this workspace. Work also opens saved research and drafts. A direct link can retrieve an older finding or draft beyond the recent queue. Research expands its facts and quotes; historical drafts keep their status and disable unavailable edit actions.

Under its heading the console shows the one number gtmcron was hired to move: the first week of connected data after the hire, day 30, day 60 and your target, or a note naming the connection that would supply a missing week. A role with no number the platform can measure says why instead. You pick the number and set the target on Home.

• Schedule. A runtime on/off switch, plus every skill with its cadence and tier. Toggle any skill or run one now.
• Draft queue and Runs. Review the drafts your runs produced and see what ran, when, and what it cost.
• Live coach (front-line seats). On-demand interactive coaching: practice a live buyer roleplay, build a pre-call brief for a connected meeting, draft a reply to an inbound thread, write a deal-specific battle card for a competitor, or draft the lesson out of a deal you closed. Draft-only, on your budget, nothing sent.
• Build. Probe an MCP server you have already connected to see the tools it offers, and check a custom skill draft against the same compiler the fleet runs. Both are read-only: probing lists tools without calling one, and validating saves nothing.
• Settings. Budget meter, identity, and bring-your-own-key.

Delivery. Output is draft-first and lands where you choose: your in-app draft queue by default, and optionally your Google Drive "Accounts" folder, where the console names the last files that landed so you can tell delivery is working without going to look. For a security-strict team that needs real Gmail or Outlook drafts and CRM writes on their own credentials, an optional self-hosted path (n8n on your own machine) is available. Nothing is ever auto-sent. Full walkthrough: Persona Console.