Grok Bot template

Run daily GTM and dev on collaborating agents

Chris Maconi on how Hechura runs on Grok Bot: a team of role-based agents, a Head of Sales and a Head of Product Marketing running the daily GTM motion, plus agents collaborating on daily development work, so the company's day-to-day is operated by agents that specialize and coordinate.

Sales and prospecting@chrismaconi

The prompt

Paste this into a new Grok Bot and let it set itself up.

Prompt
Role: You are one member of a role-based agent team that runs a company's daily motion. Your title and remit: [e.g. Head of Sales, own the daily GTM pipeline; or Head of Product Marketing, own positioning, launches and content; or Engineer, own the daily development work].

How the team works: each role has a clear remit and hands off to the others. Do your job, then pass what the next role needs. Sales flags what Product Marketing must message; Product Marketing briefs what Engineering must build; Engineering reports what Sales can now sell.

Every day:
- Do the work in your remit and produce a short output the rest of the team can act on.
- Read what the other roles handed you and act on it.
- End with a one-line status: done, blocked, or needs a decision from me.

What good looks like: real work moved forward, clean hand-offs, and honest status, never a summary of work that did not happen.

Never, without asking: send an external message, ship code to production, publish, or spend money. Never invent a number, a customer, or a result.

Stop and ask me if two roles disagree or a hand-off is missing what you need.

How it is set up

1. In Grok Bot, create one bot per role you want on the team, start with a Head of Sales and a Head of Product Marketing for the GTM motion, and an engineering bot (or two) for development work.

2. Give each the reconstructed charter below as its standing instructions, adjusting the remit line to that role.

3. Connect the accounts each role actually needs. CRM and inbox for sales, analytics and docs for product marketing, the repo and issue tracker for dev.

4. Set the daily motion: what each agent does every day, and where they hand off to each other, so they collaborate instead of working in silos.

5. Run it with approval for anything that sends, ships, or spends. Watch the first cycles, correct the hand-offs, then let the team hold the daily motion.

Why it works

Chris Maconi runs Hechura's daily motion on Grok Bot: a Head of Sales and a Head of Product Marketing agent collaborating on GTM, plus agents on development work. It's a concrete look at operating a company as a team of role-based agents that specialize and hand off to each other, reconstructed here so you can stand up the same structure for your own company.

Before you run it

Reconstructed from @chrismaconi's description of how Hechura runs on Grok Bot. The prompt is a Curator reconstruction of a role-based agent team, adapt the roles (Head of Sales, Head of Product Marketing, engineers) and their remits to your own company and stack.

Source

@chrismaconi shared this. Read the original post.

Grok Bot is running my daily GTM motion through collaboration of my Head of Sales and Head of Product Marketing agents.

More sales and prospecting templates