How to start a marketing engineer practice: keep the first version painfully simple
If you were starting tomorrow morning, the approach should be almost painfully simple. Build a Growth OS folder with five files: customer truth, founder voice, experiments, agent jobs, and one more for context. Paste in 20 real customer notes or call summaries. Then ask the agent to do exactly one job: tell me what's changed, show me the receipts, and suggest one marketing test that could create pipeline this week — not next week, not a month from now. Build one thing from that output. For the HVAC example, that might be a lost-replacement-revenue calculator. The first goal is simply to prove the system can turn messy market data into one useful action. Complexity can come later; proof that it works comes first.
Go deeper with Greg Isenberg
Ask anything about this, and Greg Isenberg answers from everything they've shared.
More to learn
See everything in Learn
Small businesses are deploying AI agents faster than 50,000-person companies ever could
In Hyper Agent's early adoption base, small shops have become surprisingly sophisticated very quickly and are running their operations in genuinely game-changing ways. The reason is simple: a 50,000-person company can't pivot on a dime — th
Hyper Agent targets both power users and casual users with the same product
The design philosophy behind Hyper Agent is to serve the full range of users — from power users who want granular control over how the agent is set up, so they can squeeze out maximum bleeding-edge performance, all the way to people who jus
Choosing an agent platform means choosing an ecosystem — pick deliberately
Greg Isenberg frames platform selection as an investment decision: when you pick a platform — whether it's OpenClaw, Hyper Agent, Codex, or something else — you are investing in an ecosystem. That framing matters because the switching costs