Notes, page 2
Guides on GTM engineering, outbound and first customers for non-technical founders.
Essays
- GTM Engineer Salary in 2026: What Public Data SaysThe question is asked in the same words, over and over. Florin Tatulea posted it on X: "How much do GTM Engineers get paid?" In r/gtmengineering the threads have the same titles — GTM Engineer Salaries? and How much can I make? — because the title covers more than one job, and the public figures come from different kinds of samples.
- GTM Engineer vs Agency vs Fractional: How to ChooseThe question usually arrives as a staffing problem. On 7 November 2026 it was asked on X in one line: "Do I hire a GTM engineer full-time, go fractional, or just hand this to an agency?" A few days earlier, another founder hiring on X wrote, "I am hiring a GTM engineer. It's a remote role. Happy to also work with an agency."
- GTM Engineer vs Growth EngineerEvery few years a title absorbs a lot of hope. Someone on X put the current version bluntly: "GTM Engineer is going to be the next Growth Hacker." That might be a useful warning and a bad hiring plan at the same time. Over in r/sales, people are still asking whether there is any meaningful difference between traditional sales titles and "GTM." If you are a founder trying to open a role, those two threads are the fog you are walking through.
- GTM Engineer vs RevOps: Same Work, or Two Jobs?Nat Guy asked this directly, on X and again on LinkedIn: "Are GTM Engineers just RevOps folks with a new title? A made up role by a SaaS company trying to carve out a new category?" A widely circulated analysis of about 1,000 postings, discussed on r/gtmengineering, argued that "9 out of 10 responsibilities are identical," with GTM leaning outbound and RevOps leaning forecast accuracy. Mirjam Martin put the founder question underneath: if you can only hire one person for RevOps or GTM engineering, which should it be?
- GTM Engineer vs SDR: Which Hire Actually Builds PipelineI keep seeing the same hiring debate in seed and Series A rooms: should the next pipeline seat be an SDR, or a GTM engineer?
- What GTM Engineering Actually Costs a StartupWhen founders ask how much GTM engineers get paid, they are usually asking a wider question: what will this *work* cost us, all in, if we hire, go fractional, or buy a team? The salary article answers the offer letter. This article answers the budget line.
- GTM Engineering for Non-Technical FoundersTwo questions have been circulating on X this autumn, and they are really the same question. On 11 November 2026, Andrew Shin asked, "be honest: have you seen a non technical founder make money with a vibe coded product." A day earlier, another post put it as a poll: "Can a non-technical founder build a successful SaaS?" A third asked whether a non-technical founder can build a million-dollar tech company.
- A GTM Tech Stack for Non-Technical FoundersPeople like to post stacks. A widely bookmarked GTM engineering guide includes "the complete stack." Others say, "If I were learning GTM Engineering from scratch, this is the stack I'd start with." A stronger, and I think wrong, claim is that all a GTM team needs now is Clay and Claude Code.
- How to Build a B2B List Without Paying for Bad DataA lot of early GTM work gets stuck on "building the list," as if volume were the craft. I have sympathy for the opposite warning: new GTM engineers should not learn list building first. The first skill is knowing who belongs on a list at all. Data also decays — people change jobs, inboxes die — which is easy to forget if you bought a file last quarter and still treat it as fresh. And a point I want every founder to take seriously: give two "AI SDRs" the same messy CRM, and you will get the same wrong email. The software will not rescue bad rows. In consultants threads about automating outbound, validation keeps showing up as the unglamorous work people try to skip.
- How to Build an AI SDR Workflow a Founder Can Actually RunAfter sending a lot of cold email, Chris (coldemailchris) wrote on X: "I'm sure founders have AI backwards. Half of them bought an AI SDR to run outbound for them. The other half still won't let AI write a single email. Both groups are wrong, in opposite directions."
- How to Define an ICP Your Team Will Actually UseMost ICP documents are a slide. They get written for a fundraise or a website, then ignored the first time someone has a list to upload. The version I care about is operational: it decides who deserves a message today, and who the team is never allowed to contact.
- How to Handle Cold Email Replies Without a Bot Taking OverSending is the part vendors demo. Replies are the part that turns a motion into a company conversation, or into a mess. In a r/coldemail write-up of an AI lead-gen test, the useful lesson was about autopilot versus copilot: reply handling got better when a human stayed in the loop. Chris's split of the market still applies here. One camp wants the software to run. The other does not want it writing at all. On replies, I would be even stricter than on first touches: you just reply to the positive responses yourself, and you do not let a bot negotiate, promise, or improvise.
- How to Hire a GTM Engineer (and When Not To)On 7 November 2026, a post on X asked the question in the exact words founders use on calls: "Do I hire a GTM engineer full-time, go fractional, or just hand this to an agency?"
- Inbound Lead Routing for a Small TeamOutbound gets the airtime. Inbound, when it exists at all, often sits in a shared inbox or a CRM notification nobody owns. Fivos Aresti has listed "inbound orchestration" among core builds. Another operator frame, in an Era 1 systems list, treats automated inbound follow-up as a standard early system. And a fair challenge still circulates: why aren't B2B companies putting effort on inbounds?
- Instantly vs Smartlead for a Startup Sequencerr/coldemail has versions of this thread on a loop. One is simply titled "Instantly vs Smartlead?". Another asks, "Which of these 3 is best for cold email outreach," and puts Instantly, Smartlead, and Saleshandy on the same line. The comments, as comments do, contradict each other: inbox placement stories, pricing complaints, feature love, feature hate, a warning that the tool was not the real problem.
- Job-Change Outreach That Isn't CreepyJob changes are one of the few outbound signals that often have a real "why now" attached. Fivos Aresti has listed "job changes of champions" among favourite plays. thatGTMdude has written about hiring posts as a trigger. Both can work, and both can feel like you have been standing outside someone's new office with a brochure.
- Lead Response Time for B2B, When You Have No RevOps TeamInbound follow-up is one of the least glamorous GTM-engineering builds, and one of the first that should exist. It shows up in early-system lists as "automated inbound follow up". It is also the thing teams under-own, which is the complaint behind why aren't B2B companies putting effort on inbounds?
- Lead Scoring for Early-Stage SaaS: Fewer Fields, Clearer RulesEarly teams borrow scoring models from larger companies and then wonder why nobody uses them. Ten fields, a points engine, a "hot / warm / cold" badge that everyone ignores — that is not a system. It is a decoration. The version I would start with is closer to a sentence Adugbo Victory has used about the real work: who deserves a message today, and why. I would answer that with fit plus one signal, written as rules, not as a mysterious score.
- n8n GTM Workflows for Founders Who Are Not EngineersIn the Clay alternatives thread on r/gtmengineering, n8n shows up as a serious option, especially for technical teams: glue a data API, a verifier, and a CRM together without buying a full workbench. The labour market has noticed too. In Hlib S.'s November 2026 look at 161 GTM engineer postings, n8n appeared in 45% of that sample, ahead of Zapier at 30%. Those figures are his count, from that sample, not a law that you must learn n8n this quarter.
- Pipeline Reporting at Seed: A Report You Can TrustNat Guy's useful split still holds: GTM engineering leans toward tools that create pipeline; RevOps leans toward tools that manage and measure it. At seed, you often cannot hire the second person. Commenters on pay surveys have said, in so many words, that they are not sure the average company will be able to afford a specialist. You still need a report you can trust — one a founder can read on Friday without cleaning rows for an hour first.