Chief of Staff
Meeting prep, inbox triage, post-call drafts, and spinning up the rest of the team.
GTM Engineering / how it works
GTM Engineering you can leave running overnight.
Figtech is not a prompt pack. It is demand generation from a fractional GTM Engineer: map the motion, stand up Instantly or Origami, run the engine in your stack, then wire a Grok Bot roster beside it. Humans approve sends.
What a GTM Engineer embeds to do
Typical start: a scoped embed. Rob sits with revenue leadership, RevOps, sales ops, and marketing ops, whoever owns Instantly, Origami, the CRM, and the funnel. We do not start by creating twelve bots. We start by standing up the engine, then naming the jobs the roster runs beside it.
01
GTM systems architecture
Map demand gen motion (outbound, inbound, content, SEO/AEO, creative, forecast) before anyone clicks Create. Jobs, source systems, output format, and standing approval boundaries, so the engine owns a pipeline outcome, not a pile of prompts.
02
GTM tooling and wiring
Instantly, Origami, CRM, Gmail, Calendar, Slack, Gong, LinkedIn, Notion, Sheets, warehouse. Hands-on config, not only agent logins. Sessions that persist. Computers that stay on after yours shuts.
03
Skills, routines, enablement
Onboard bots the way you onboard a teammate. Record the workflow once, save it as a skill, schedule the routine. Style profiles from sent mail. Anti-slop rules you actually keep. The roster sits beside the engine, not instead of it.
04
Operating cadence
Weekly iteration across engine and roster, with a human GTM Engineer in the loop next to RevOps. Parallelize research, clean dead routines, keep funnel writes behind approval. The system gets sharper; you stay on calls.
Sequence
How GTM Engineering lands in month one
- 01
Map the motion
ICP, demand gen channels, Instantly/Origami and stack, approval edges.
- 02
Stand the roster
CoS, outbound, prospecting, content, SEO/AEO, creative, forecast, reporting.
- 03
Wire and rehearse
Stand up the engine in their tools. One real outbound or content workflow. Wire agents. Save skills.
- 04
Put it on a clock
Nightly research, morning reviews, weekly SEO/AEO and forecast packs. Humans approve sends.
GTM systems the roster can own
The roster sits beside the engine. Chief of Staff, outbound, prospecting, content, SEO/AEO, creative, forecast, reporting. Agents research, draft, and watch. People send. We adapt the system to your stack. We do not clone someone else’s org chart.
Prospecting
Overnight account research, ICP scoring, contact picks, and review-ready outreach in your voice.
Account Expert
Covers your named accounts. Watches Slack, calls, and public signals. Weekly rundown, not noise.
Forecast
Gong, Granola, Slack, and email into Salesforce notes in the format your forecast call actually uses.
Account Health
Usage, support, renewal timing, and stakeholder activity as a ranked watch list with next steps.
Outbound
First-touch and follow-up drafts in your voice. Stops at a review queue. It does not hit send or enroll.
SEO
Keyword gaps, page briefs, and internal-link notes from the site and Search Console. Nothing publishes itself.
Content
Turns calls, webinars, and closed-won notes into posts and one-pagers. You approve before anything ships.
Product language follows the official Grok Bot for GTM guide and published use cases. Figtech implements; xAI ships the product.
Work with a GTM Engineer
Bring a demand gen stack. Leave with an engine.
A working session: map the motion, name the engine, decide what stays behind approval.