A GTM engineer 30 60 90 day plan for outbound should fit on one page, and the first 30 days should end with something that runs. If the CEO said “I want an outbound engine by day 30”, this is the plan by week: audit in week 1, first campaign live by the end of week 2, measurement in week 3, a handover routine in week 4. On day 30 you show four artifacts. None of them is a promise about meetings.
This article is for a newly hired first GTM engineer at a startup with a small sales team or none. It covers the first 30 days in detail and days 31 to 90 in outline. The examples use GTM Bud through an AI chat or a coding agent, because a new hire has no time to learn a large sending product in week 1.
What does “an outbound engine” mean on day 30?
An outbound engine on day 30 is a campaign that sends without you starting it each morning, a record of what it produced, and a routine that another person can follow. It is defined by what can be inspected, not by a pipeline number.
Get that definition agreed in your first meeting with the CEO, in writing. The reason is arithmetic. A campaign that launches on day 12 has 18 days of data on day 30. Connection requests take days to be accepted, and replies come after that. The numbers on day 30 will be early.
The sentence to send the CEO in week 1: “By day 30 you will see one live campaign, what it sent and what came back, and a routine that runs without me for a week. By day 60 you will see which of three audiences deserves more.”
The plan on one page
| Week | Theme | Main work | Artifact at the end of the week |
|---|---|---|---|
| 1 | Audit | Inventory, five interviews, one audience picked | Audit page, agreed day 30 definition |
| 2 | First build | Draft, preview, offer, messages, review, launch | One active campaign, one signed review |
| 3 | Measurement | Results log, reply handling, first playbook rules | Log with dated readings, reply rules |
| 4 | Handover | Routine written down, one week run by someone else, day 30 page | Routine document, day 30 page |
Week 1: What do you audit?
Audit four things: accounts, past outbound, the buyer and the rules. Write one page. Launch nothing.
Day 1 and 2: inventory.
- Which LinkedIn accounts could send, and whose are they. If the company already has a GTM Bud account, ask its owner to add the connector and run
list_sending_accounts. It returns each connected account with its connection status, its pause state and its Sales Navigator access. - Which campaigns exist anywhere, in any tool, and who started them.
- Which replies sit unanswered. This is often the fastest win of the month. An interested lead from August who never got an answer costs nothing to find.
Day 3 and 4: five interviews of 20 minutes. Both founders, the best seller, the newest customer and one lost deal if someone will take the call. Ask each the same three questions: who bought fastest, what did they say on the first call, what would make you embarrassed to see in a message with your name on it.
Day 5: pick one audience and write the day 30 definition. One audience, not three. If the founders cannot agree on one, do not pick for them. Run five ICP hypotheses in one week as your week 2 and move everything else by a week. Tell the CEO on day 5 that the plan moved and why.
The audit page has five lines: accounts we can send from, what was tried before, the one audience and the reason, the rules for messages, and what day 30 will show.
Week 2: How do you get the first campaign live?
Build on Monday and Tuesday, review on Wednesday and Thursday, launch on Friday. The build is fast. The review and the things that depend on other people are slow, so start those first.
Monday morning, before any build: the dependencies. Three steps happen on gtmbud.com and need the account owner: connecting the LinkedIn account, choosing the sending account for the campaign, and setting the sending schedule. The 14-day free trial starts when you launch your first campaign. Book 20 minutes with the person whose LinkedIn account will send. If you wait until Thursday, you launch in week 3.
Monday and Tuesday: the build. In order:
- Give the AI the audience sentence. It writes the criteria, and GTM Bud checks them and saves a draft. Rewrite each flagged criterion.
- Start a prospect preview and look at the people yourself first.
- Set the seller profile of the draft: the company website and the sender’s personal LinkedIn profile.
- Have the AI write the value offers from GTM Bud’s brief. A value offer is something free and useful for each lead. Check with the person who must deliver it that they can.
- Have the AI write the message sequence from the sequence brief. GTM Bud checks the messages and saves them only if they pass.
Wednesday: the founder marks prospects. Fifteen minutes, one person at a time, Good fit or Not a fit, with a reason. This is the step that makes the campaign theirs and not yours.
Thursday: the review. One page, signed by the sender: targeting read, every message read, readiness checklist empty. The launch preview shows the first message of each channel, so print the full sequence for the review.
Friday: launch. The launch takes two calls. The first returns the preview. The second happens after the sender agrees in the session.
you Is "Oct: ops leaders, 3PL" ready?
ai get_launch_readiness
All checks met.
you Launch it.
ai launch_campaign
Preview: first message of each channel shown.
Waiting for your agreement.
you Dana has read it and agrees. Go.
ai launch_campaign
Launched. Status: active.If you already keep notes and scripts in a repository, build this week with the Claude Code outbound workflow, so the brief and the review are files from day one.
Week 3: What do you measure, and how often?
Measure the same few numbers on the same two days each week, and write each reading down with its time. In week 3 the goal is a habit and a clean record, not a conclusion.
The numbers. Connection requests sent and accepted, replies, Interested replies, and the count of replies with no label yet. Results come per campaign. They refresh when someone asks and can be up to about 15 minutes old, and each reading carries an as-of time. For definitions that the sales team will accept, use outbound KPIs and benchmarks as the shared vocabulary.
The days. Tuesday and Friday. More often than that and you will react to noise. GTM Bud does not send a report on a schedule, so the reading is a question that you ask.
The reply habit. Every working day, ask which replies need an answer. The AI writes each answer from the reply playbook and shows it. The sender, or the person they named, approves the exact text before it goes. In week 3 you sit in on this, because it is where you learn the buyer.
The first rules. By Friday you will have seen the same two or three questions more than once. Write a rule for each in the campaign reply playbook. The AI shows the exact new text and saves it after approval in the chat, and the earlier text stays in the version history.
What you must not do in week 3: change the audience and the messages because of four days of data. Write the idea in a decisions file and wait for week 4.
Week 4: What is the handover routine?
The handover routine is a one-page document that lets a named person run outbound for a week while you only watch. If nobody else can run it, you have built a dependency on yourself, not an engine.
The routine has three rhythms.
| Rhythm | Who | What | Time |
|---|---|---|---|
| Daily | The sender or a named reviewer | Replies that need an answer: read, edit, approve | 15 minutes |
| Twice a week | The GTM engineer | Results reading into the log, labels checked | 10 minutes |
| Weekly | GTM engineer and sales lead | One decision: keep, change one thing, or clone for a new audience | 30 minutes |
The times are planning estimates for one campaign.
The test week. From day 22 to day 28, the named reviewer does the daily step alone. You read the log. Each thing they had to ask you goes into the routine document as a new line.
The stop rule. Write down who may stop sending and how. A change that stops sending applies at once, in one sentence to the AI. A change that starts sending again needs a preview and a confirmation. Everyone on the routine should know the first half.
The honest limit. The person who can approve and launch is the person signed in to the GTM Bud account. GTM Bud has no roles and no approval chain in this setup. “The sender approves replies” is a rule in your document, kept by people.
What do you show on day 30?
Show four artifacts and one page that summarizes them. Bring them to a 30 minute meeting with the CEO and the sales lead.
- The audit page from week 1, unchanged, so the starting point is on the table.
- The live campaign: the audience sentence, the full sequence, the signed review.
- The results log: every Tuesday and Friday reading since launch, each with its as-of time. Then three replies, word for word, with the answers that went out.
- The routine document, with the name of the person who ran it during the test week.
The summary page has four headings: what runs, what came back, what we changed and why, what we do in days 31 to 60. Under “what came back”, write counts and dates. Do not turn 18 days of data into a forecast.
Days 31 to 90 in outline
Days 31 to 60: breadth. Duplicate the first campaign for a second and a third audience. A copy keeps the targeting, the sequence, the message settings, the reply playbook, the sending accounts and the daily targets, and you change the audience. Now the weekly decision has a comparison in it.
Days 61 to 90: ownership. The daily routine moves to sales fully. You keep the log, the weekly decision and the next audience. On day 90 the question is which audiences keep running, answered with two months of readings.
Five prompts for the first month
- “List the sending accounts connected to this GTM Bud account and tell me which are disconnected or paused. I am doing an audit and will change nothing.”
- “Across all campaigns, find replies that need an answer and are older than seven days. Give me the lead, the date and the last line. Write no answers yet.”
- “Print the full sequence of the October campaign as a numbered list, with the days between steps, so the sender can sign the review.”
- “Today is a reading day. Give me the five numbers for the October campaign and the as-of time, in one row that I can add to my log.”
- “Draft the day 30 summary under four headings from my audit page, my log and my decisions file. Use counts and dates only, and make no forecast.”
Three things that break a 30 day plan
The LinkedIn account is not yours. The whole plan waits on a person connecting their own account and agreeing to messages under their name. Ask on day 1, not day 8.
The CEO hears “engine” and expects a number. Settle the day 30 definition in week 1. This article gives no reply rate and no meeting count, and your plan should not either.
You change three things at once. One change per week, with a line in the decisions file. Otherwise the log cannot tell you what worked.
Frequently asked questions about a GTM engineer 30 60 90 day plan
What should a GTM engineer deliver in the first 30 days?
For outbound, four things: a written audit of what exists, one live campaign that a person reviewed before launch, a results log with dated readings, and a routine that someone else can run for a week. That is an engine in the sense that it runs and can be inspected. It is not yet a pipeline number.
What do days 31 to 90 look like for a GTM engineer?
Days 31 to 60 are for the second and third audience and for changing the first campaign from what replies say. Days 61 to 90 are for handing the daily routine to sales and for deciding, with numbers from at least two months, which audiences keep their budget.
How soon can a first outbound campaign launch?
In this plan, at the end of week 2. The build itself fits in a day. The time goes to the audit, to getting a founder to mark real prospects, and to the steps outside your control, such as connecting a LinkedIn account that belongs to someone else.
Whose LinkedIn account should the first campaign send from?
A person the buyer would want to hear from, who agrees to it: often a founder or the head of sales. The seller profile of a campaign takes a personal LinkedIn profile, not a company page. That person signs in to LinkedIn themselves on gtmbud.com in the company account. Once the account has one connected LinkedIn account, the account owner can also send the next person a connection link.
What if the CEO expects booked meetings by day 30?
Say in week 1 what day 30 will and will not show. A campaign launched on day 12 has under three weeks of data by day 30. You can show what was sent, what came back and what you changed. Do not promise a count of meetings that you cannot control.
Day 30 is a running system, not a result
A GTM engineer 30 60 90 day plan works when each period ends with something a skeptical person can open and read. In the first 30 days that is an audit, a live campaign, a log and a routine. If the sender is a founder with no sales team, the page on LinkedIn outreach for SaaS founders describes their daily part. To start the build in week 2, add the connector with the steps on GTM Bud for Claude, and keep AI LinkedIn outreach for GTM engineers open for the list of steps that happen outside the chat.