CEO @ Kinetyca | GTM Systems that turn sales teams into revenue engines | Official Partners: Clay, Hubspot, Heyreach, S… · 2w ago
What used to take 10 SDRs now runs on 2 people.
One is a GTM Engineer, and the other is a Content Engineer.
The two roles feed each other. The Content Engineer warms the accounts the GTM Engineer converts, so every outbound touch lands on a name the prospect already knows.
That is what changes the math.
Here is how the work splits.
1. GTM Engineer:
Owns signal to pipeline.
→ Ingests from RB2B, Bombora, Trigify.io, G2, Apollo.io and HubSpot
→ Enriches through Clay, ZoomInfo, Ocean.io and n8n
→ Scores fit and intent with Clay and Claude, stores the output in Notion, and lets n8n fire the next play
→ Runs sequences through Smartlead, HeyReach and Instantly.ai
→ Captures outcomes weekly in HubSpot, Slack, Notion and Gong
2. Content Engineer:
Owns the engine that warms every account before outbound starts.
→ Creates assets in Figma and manages the calendar in Notion
→ Distributes content through n8n
→ Engages the audience daily through Leadshark
→ Routes post engagers back to the GTM Engineer as warm signals
Every account the GTM Engineer contacts has already seen the brand. That is why reply rates go up, and meeting rates follow.
We have built this across $18M+ in client revenue.
Follow for more systems like this.
David Turewicz
CEO @ Kinetyca | GTM Systems that turn sales teams into revenue engines | Official Partners: Clay, Hubspot, Heyreach, S… · 7d ago
The companies scaling fastest in 2026 run 3 engines with one GTM engineer at the center.
They wire growth, ops and sales into one system, and one person owns the wiring.
That role did not exist 5 years ago.
Revenue teams used to be siloed. Sales over here. Ops over there. Growth somewhere in between.
Someone had to connect all three. That became the GTM engineer.
Here's how the three engines map.
GROWTH ENGINE
Demand generation and campaign automation.
→ Bombora: detect topic-based intent surges
→ RB2B: identify website visitors down to the person
→ Apify: scrape and extract custom signal data
→ Common Room by Zoom: aggregate signals across every channel
OPS ENGINE
CRM automation and pipeline management.
→ Attio: manage pipeline and track relationships
→ n8n: automate plays across the full stack
→ Notion: document systems and plan operations
→ Clay: enrich and route data to every downstream layer
→ Supabase: hold the record so nothing is lost when a campaign ends
SALES ENGINE
AI prospecting and personalized outbound.
→ Apollo.io: build ICP contact lists at scale
→ Prospeo: verify emails before sequences launch
→ HeyReach: run LinkedIn outreach across multiple accounts
→ SalesNav: target and track prospects on LinkedIn
→ Smartlead: manage email sequences and inbox health
WHERE THE ENGINES OVERLAP
→ Signal Routing (growth + ops): intent and visitor signals get enriched in Clay and land with the right owner in Attio
→ Warm Outreach (growth + sales): ac…
David Turewicz
CEO @ Kinetyca | GTM Systems that turn sales teams into revenue engines | Official Partners: Clay, Hubspot, Heyreach, S… · 9d ago
The first 3 GTM hires for founders building outbound from scratch, in the order that actually works.
Get it wrong and you lose 6 months, a good SDR and every sequence you started.
The usual first hire is an SDR, before any system exists. They spend their first months building infrastructure instead of selling. Then they leave, and the sequence resets.
We've rebuilt this motion from scratch across $18M+ in client revenue.
Build the system first. Then the SDR has something to sell into.
Here's the order.
HIRE 1: GTM ENGINEER (OUTBOUND)
The founder is already the best salesperson in the company. What's missing is the system behind them.
The GTM Engineer builds the ICP model, the sequences and the enrichment infrastructure the whole motion runs on. That system fills the founder's calendar while they're still the only salesperson.
→ ICP model + TAM mapping
→ Signal tracking + lead scoring
→ AI account research
→ Copywriting + campaign launching
→ Automated outreach sequences
→ AE call coaching
Tools: Claude, Clay, Supabase, BlitzAPI, Exa, Findymail, LeadMagic, DeBounce, BounceBan (Verify risky emails without sending messages), Smartlead, Slack
HIRE 2: SDR
The SDR steps into a proven system. Sequences built, lists live, tools configured.
Their job is to turn what that infrastructure produces into booked meetings, from the day they start.
That's the difference between an SDR who ramps in 30 days and one who churns in 90.
→ Cold calling
→ Discovery + qu…
David Turewicz
CEO @ Kinetyca | GTM Systems that turn sales teams into revenue engines | Official Partners: Clay, Hubspot, Heyreach, S… · 13d ago
There are 3 levels of GTM Engineer (but most hiring briefs almost always describe the third)
We have placed and worked alongside GTM engineers at every level.
Someone who struggles in one setup performs like an architect in another, and it usually has little to do with talent.
The role shifts with where the person is in their development.
If you put a Level 1 or 2 into a Level 3 brief and it gets called a bad hire, even though the brief was the problem.
Here is how the levels break down.
1. Workflow Builder:
"How do I automate this one task?"
→ Builds single, isolated workflows from a clear brief
→ Works inside one tool at a time
→ Executes well, building toward system design with more reps
Tools: Clay, Apollo.io, LinkedIn Sales Navigator, Smartlead, HeyReach, Make, Zapier
2. Systems Integrator:
"How does data move from signal to sequence?"
→ Connects workflows into a working funnel
→ Thinks in data flow across tools
→ A strong executor whose architecture thinking grows with reps
Tools: Clay (advanced), n8n, Supabase, Findymail, LeadMagic Attio, RB2B, Trigify.io
3. Revenue Architect:
"How do I build something that keeps working as conditions change?"
→ Designs the full revenue engine with AI in the decision layer
→ Builds systems that score, route, research and adapt
→ Earned through reps, never through a job description
Tools: Claude, n8n, Supabase, Exa, BlitzAPI, Smartlead, HeyReach, Kixie, HubSpot
The hire rarely fails because of the person. It fails…
David Turewicz
CEO @ Kinetyca | GTM Systems that turn sales teams into revenue engines | Official Partners: Clay, Hubspot, Heyreach, S… · 3d ago
GTM engineering has shifted a lot in 2026
And we see it in our own work at Kinetyca.
For a long time, that meant stitching tools together through APIs and MCPs.
Now we build custom setups for most of our clients. Each one fits their own offer, value proposition and market.
The video shows the Growth Radar, the setup we run our own growth on. The data on screen is demo data.
It has 2 parts:
1. Content:
→ we scrape the posts in our market three times a day, plus the news and our own results
→ it all lands in Supabase and turns into ideas for next week's posts
→ newsletter and SEO performance sit in the same view
2. Sales:
→ every LinkedIn and email inbox in one place, with AI drafting the replies
→ it learns from our posts, our sales calls and everything we have done before
→ a nurturing engine finds who to reach out to again each day, from hot follow-ups to closed-lost deals
→ the live version covers 30,000 people from our connections, past emails and CRM
→ we approve in bulk, and our comments teach the AI
We already had tools for most of this. Each one showed things its own way, and we wanted to see our growth in a specific way. So we connected it all here.
The usual worry with custom builds is maintenance. 2 years ago, something like this would have needed a lot of it. With how fast AI has improved, maintenance on our custom builds is now very low.
What makes the difference now is the creativity of the builder, and the knowledge from every build before.
We are no…
