HN user

ashed96

13 karma
Posts2
Comments25
View on HN

GTM Engine turns Claude Code into your sales team. Eight opinionated slash-command skills that run your entire go-to-market motion — pipeline tracking, daily rituals, call analysis, lead scoring, cold outreach — all from your terminal.

No specific structure - you'll need to experiment based on your project.

I treat it like briefing a senior engineer. Example:

"Currently we have X, Y, Z but it has ABC limitation. We need to support FOOBAR. What are our options?"

Agent suggests 3 approaches.

"Go with Approach 1 but remove the Z part. Implement it."

Try being specific about constraints and current state. The agent fills in the implementation details, but you drive the decisions.

I'm building a startup myself and we vibe code everything, except core/complex parts where AI struggles.

My workflow:

1. Give the agent detailed task + relevant file contexts (so it doesn't waste time searching)

2. Guide it with continuous feedback when it veers off

3. Jump in manually if it's going completely wrong direction

I use Claude Code for the agent work, Cursor for manual edits.

Key insight: AI coding works as well as your architecture does. I make all architecture decisions, file structure, organization -- AI just writes the implementation logic.

Clean architecture = better AI output.

I believe This is becoming the norm because it gives startups massive velocity advantage. That's probably why your CTO is pushing it.

Career impact? As a senior who understands what AI writes, you're gaining superpowers, not losing skills. You were previously bottlenecked by implementation speed and needed other engineers. Now you can be a 10x engineer - as long as you can envision the architecture, AI helps you build it faster.

The key is knowing when to guide vs when to take over. That judgment comes from experience.

What Is a "Why" 9 months ago

My WHY: I need money to pay rent. My company's WHY: Generate shareholder value.

There, saved everyone $97. You're welcome.

In theory, maybe to some extent yes - unique usernames could beat reused emails.

But let's be real - nobody actually does that.

As others mentioned, you can't stop them from doing this. It's a cutthroat game where companies will try to poach customers however they can.

Best defense is making your customers so happy they won't switch, but tactically:

- Create a private Slack/Discord for paying customers only (harder for them to infiltrate) - Move community to a platform with anonymous usernames (Something similar to Reddit-style forums or Discord with display names) - Add some soft vendor lock-in -- a bit evil but sometimes necessary - just maintain the balance between retention and not being user-hostile

On a positive side, if a VC funded startup is this desperate to poach your users, you're clearly doing something right.

- from fellow wannabe bootstrapper