Outbound GTM Engineer

AI-First Outbound / GTM Engineer — Freelance
Company: Flowace Technologies (flowace.ai)
Engagement: Freelance, 4 hours/day × 5 days/week
Experience: 3+ years hands-on in outbound / GTM engineering
Location: Remote (India timezone overlap required)
Reports to: Head of Growth
Individual freelancers only. Agencies will not be considered.
Why this role exists
Flowace is a bootstrapped, profitable workforce productivity and time-tracking platform. 650+ enterprise clients, 80,000+ users, eight years in the market. Almost all of that came from inbound and referral.
Outbound, at Flowace, is currently at 0-1 stage. There is limited infrastructure, signal layer, scoring, no routing, and no attribution.
We are not looking for someone to send more emails. We are looking for one person to build the outbound system from the base — infrastructure, data, signals, plays, routing, dashboards — and then run it.
If you have done this end to end before, at least once, you already know what the first two weeks look like. That is who this is for.
The mandate
You own eight things.
1. Encode the target market. Validate and sharpen our existing ICP and persona work. Map and prioritise TAM. Build the account scoring model that decides who gets worked and who does not.
2. Sending infrastructure. Secondary domains, mailbox provisioning, SPF/DKIM/DMARC, warmup schedules, inbox rotation, volume caps, bounce and spam monitoring. Our primary domain reputation is never at risk. Volume increases only when infrastructure is healthy.
3. Data and enrichment layer. A centralised, maintained target list. Waterfall enrichment, deduplication, verification. You are accountable for data quality and for cost per enriched record.
4. Signal layer. This is where the leverage is, and it is the part most people skip. You build the triggers that tell us when to reach out, not just who. Named signals we already know exist are listed below.
5. Multi-channel plays. Email, LinkedIn, WhatsApp, and call tasks. Each play is tied to a specific signal and segment, with a stated success criterion before it launches.
6. CRM, routing, alerts. Everything pushes to HubSpot. Leads route to an owner. Replies get handled inside an SLA. Nothing sits unclaimed.
7. Dashboards and attribution. Sends, deliverability, reply rate, positive reply rate, meetings booked, pipeline sourced — split by play and by segment. If we cannot see which play produced a meeting, the play does not count.
8. Operate the loop. Daily reply triage, list refresh, message iteration, and honest kill-or-scale decisions based on the data rather than on how much work went into building the play.
Experience we're looking for
At least 3 years hands-on in outbound, growth or GTM engineering.
More important than the experience year number: you should have built at ONE outbound system from zero - domains, warmup, data layer and signals included, not inherited from a predecessor and not operated inside someone else's setup.
Years matter less to us than the number of systems you've stood up and the number of plays you've killed. If you're at the lower end of that range but have one genuine zero-to-one build behind you, apply.
If you're above it and still hands-on daily, also apply — just be clear you're not planning to subcontract this.
What "AI-first" means here
Everyone says AI-first. Here is the specific bar.
The system should continuously detect qualified triggers, enrich the account and the buyer, select the correct play, and create the next action — with human judgment kept in the loop for approvals and for actual conversations.
Concretely, we expect fluency in:
Enrichment and orchestration: Clay or equivalent, built as real tables with waterfalls and conditional logic
Sending: Instantly, Smartlead, or similar, plus HeyReach/Expandi of similar for LinkedIn (we own a seat)
Data waterfall: Apollo, FullEnrich, Findymail, LeadMagic, PredictLeads, BuiltWith, or your own preferred stack
Automation: n8n, Make, or equivalent — including webhook and API work
LLM tooling: prompt chaining, agentic workflows, Claude Code / MCP or similar. Using ChatGPT to write subject lines is not what we mean.
CRM: HubSpot
We care about what you have built, not which logos you have used.
Non-negotiables
Ownership. There is no team behind you and no one to escalate to. You scope it, you build it, you fix it.
Response speed. Replies from prospects get handled the same day. Outbound dies on latency.
Discipline over hours. Four focused hours daily, consistently, beats ten sporadic ones.
Positioning. Flowace is productivity, not surveillance. Any copy that reads like spying on employees is disqualifying, regardless of how well it converts.
Individual, not agency. If you plan to subcontract the work, this is not the right fit.
What this role is not
Not closing deals. Not running demos. Not managing SDRs. Not content marketing or paid ads. You build and run the machine that fills the calendar; the sales team works the calendar.
Success metrics
Bounce rate under 2%, spam complaint rate under 0.1%, sustained at ramped volume
Positive reply rate benchmarked and improving month over month
Qualified meetings booked per month (target to be agreed at kickoff)
Pipeline sourced and attributable by play

Work arrangement
No