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.
How it starts from your website, the work it performs, what you receive, an example, the input it needs, how to judge it, where its work goes, and what it depends on.
GT · GTM strategist
Turn the business behind your website into a focused plan for finding the first customers.
A clear offer and buyer profile give account research and outreach a useful direction, which is how this role helps reduce time spent on companies whose needs do not match what you can deliver. It creates no revenue on its own.
How it starts with your website
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.
What the role does for you
Read the website and draft the business brief: what you sell, who it is for, the problem, alternatives, voice and proof. AI Assist can propose any section from the current draft and web research; nothing is applied until you accept it.
Research the market and propose customer profiles, with the addressable-market estimate kept apart from the named companies, which are a research sample.
Keep the direction current: a scheduled morning briefing, a weekly operator review and a monthly investor update, each built from stored records and labelled where a figure is an assumption.
Prepare messaging, content and campaign material on request from the confirmed brief, and revise the profile as replies and objections arrive from the other roles.
On its own schedule: 11 scheduled tasks, 14 more on request
Tuesdays · 12:15 UTC ICP refinement: what the week’s replies and wins say about who to sell to, against the confirmed brief
Daily · 06:15 UTC Morning brief: the day’s top accounts and openings, ranked, with the angle for each, plus where the launch and daily prospecting stand
Wednesdays · 12:15 UTC Messaging: the positioning lines to test next, drafted from the brief and what has landed so far
Fridays · 12:15 UTC Messaging experiments: which angles got replies this week and which to retire
Mondays · 06:15 UTC Operator review: what moved last week across pipeline, content and outbound, and what did not
Daily · 17:15 UTC Signal prospecting: the accounts that showed a buying signal since yesterday, with the reason. Skipped while a founder plan does this
Thursdays · 12:15 UTC List chaser: the cold accounts that have gone quiet and the next touch for each. Skipped while a founder plan does this
Daily · 12:15 UTC Inbound triage: what arrived since the morning, sorted into answer now, route, and ignore
Mondays · 12:15 UTC Nurture: the contacts due a touch this week and a draft for each. Skipped while a founder plan does this
Monthly, day 1 · 06:15 UTC Investor update drafted from the month’s actual numbers and shipped work
Monthly, day 8 · 12:15 UTC Answer engines: whether they named and cited you for your buyers’ questions this month, what changed since last month, and the page fixes
Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console.
The work you receive
A confirmed business brief with sources and the questions still open, kept as the one version every role reads.
A market research result: the estimate or "not established", its method, assumptions, sources, and the customer profiles to choose from.
The morning briefing, the weekly operator review and the monthly investor update.
Messaging variants, content calendars and campaign briefs, prepared when you ask for them.
An example in practice
A founder pastes their URL. The brief comes back naming a service-team buyer and an operational problem the product addresses, with two claims marked as needing proof. After confirmation the market step returns two profiles, each with six candidate companies and the source that named them, and one profile is approved for research.
A scenario to show the shape of the work, not a customer result.
What it needs from you
Confirm what you sell, what is available today and who you want to help. Answer the focused questions the brief could not settle: geography, exclusions, pricing, proof. Approve a market profile. Material changes to the brief are proposals you accept or reject; once confirmed, the brief is reused everywhere and no role asks for it again.
The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup.
Expected outcomes and how to judge them
A reviewable market and offer hypothesis that can produce a first researched account batch. Over time the profile should get more specific as real replies replace assumptions.
Measures worth watching
Time from URL submission to a confirmed brief and an approved customer profile.
How much of the brief you corrected, how many sections carry a source, and the share of proposed companies you accepted.
Reply and opportunity results by profile, read with enough care not to attribute every change to positioning.
How the handoff works
Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next.
To Sales development
What moves: An approved customer profile and the confirmed brief.
What happens next: Research companies and contacts that match it.
To Account executive
What moves: The offer, the buyer problem and the claims you can support.
What happens next: Prepare replies and deal conversations from the same facts.
To Revenue leader
What moves: The commercial assumptions behind the plan.
What happens next: Compare them with what the pipeline and payments say.
When it is useful, and what it depends on
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.
Your website URL
A confirmed business brief for everything after the first scan
Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue.
Explore this role's capabilities
The name is literal.
gtmcron ships 11 scheduled tasks across its 5 roles. Here is a slice of the default week: research, content and launch prep each run on their own clock, and every one of them stops at a draft.
When
What runs
Tuesdays · 12:15 UTC
ICP refinement: what the week’s replies and wins say about who to sell to, against the confirmed brief
Daily · 06:15 UTC
Morning brief: the day’s top accounts and openings, ranked, with the angle for each, plus where the launch and daily prospecting stand
Wednesdays · 12:15 UTC
Messaging: the positioning lines to test next, drafted from the brief and what has landed so far
Fridays · 12:15 UTC
Messaging experiments: which angles got replies this week and which to retire
Mondays · 06:15 UTC
Operator review: what moved last week across pipeline, content and outbound, and what did not
Daily · 17:15 UTC
Signal prospecting: the accounts that showed a buying signal since yesterday, with the reason. Skipped while a founder plan does this
Thursdays · 12:15 UTC
List chaser: the cold accounts that have gone quiet and the next touch for each. Skipped while a founder plan does this
Daily · 12:15 UTC
Inbound triage: what arrived since the morning, sorted into answer now, route, and ignore
Mondays · 12:15 UTC
Nurture: the contacts due a touch this week and a draft for each. Skipped while a founder plan does this
Monthly, day 1 · 06:15 UTC
Investor update drafted from the month’s actual numbers and shipped work
Monthly, day 8 · 12:15 UTC
Answer engines: whether they named and cited you for your buyers’ questions this month, what changed since last month, and the page fixes
Times are UTC. The runtime dispatches three times a day, at 06:15, 12:15 and
17:15 UTC, and each task takes one of those windows. You can turn any of them
off in the console.
Five roles. One GTM team.
Operator, Closer, Writer, Researcher, and Event: the whole founder-GTM crew, licensed together as gtmcron.
Operator
Company OS Core
Stand up your Company OS: one canonical business context, four roles, a decision log, a weekly operating review. Required by every other plugin.
Closer
GTM Engine
An autonomous outbound demand engine: trigger-driven prospecting, a daily standup, a self-tuning funnel report, cold-list recovery, a deal closer.
Writer
Content Engine
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.
Operator
Founder Chief-of-Staff
A daily morning brief, meeting prep, and a monthly investor or board update, drawn from your calendar, inbox, and the business.
Operator
Launch Readiness Audit
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.
Closer
Inbound and Lifecycle
Triage every reply, route hot interest, and nurture signups through their lifecycle stages. Pairs with GTM Engine.
Researcher
Market Intelligence
A weekly competitive sweep and a daily community scan that surface threats, positioning shifts, and high-signal conversations worth a reply.
Event
Launch Kit
A full launch prep package and a launch-day operations plan with comment templates.
preview = built, but the vendor API path isn't verified with a live tenant yet · planned = on the roadmap, not built.
Scout watches the trends. Writer drafts in the voice it learned from your own material. Media cuts the video and thumbnail. A brand-safety agent checks every piece before anything posts. Publisher ships it, automatically where it's safe, and held for your approval where a wrong move would cost you. The orchestrator attributes the signups each piece drove and feeds the winners back to Scout.
Mode-per-channel is the point: it posts on its own where the platform allows it, and never auto-posts where automation would get your account banned. You stay in control of the channels that matter.
Anything that reaches a person waits for your yes. Auto-publish only where a channel welcomes it, after a brand-safety check.
Your tools, your data
Runs on our servers, on a schedule, on the CRM, inbox, and calendar you connect. We custody those tokens encrypted and isolated per tenant, never sell your data, never use it to train models, and let you revoke access anytime.
Compounding brain
Every run teaches it your voice, your accounts, and what worked. The value grows instead of resetting each session.
$99 per person per month, or $1,089 a year. That is the price of the whole platform: one seat licenses gtmcron and every other role, and adding a teammate adds a seat at the same price.
What does gtmcron include?
Five roles working together: Operator, Closer, Writer, Researcher and Event. They cover account research, outbound drafts, content, chief-of-staff briefs, market intelligence and launch prep.
Does gtmcron send anything without me?
No. Anything that reaches a person waits for your yes. Auto-publish only happens where a channel welcomes it, after a brand-safety check.
What does gtmcron run on?
Our servers, on a schedule, with nothing to install. You connect your CRM, inbox, and calendar in the product; we custody those tokens encrypted and isolated per tenant, read them only on your schedule, never sell your data, and never use it to train models. You can revoke access anytime.