57 Days Ago, I Had No Idea What I Was Doing.
I'm currently a product manager. Not an engineer. Not a marketer. Not a content strategist or a data analyst or a sales ops person. I'm one person at a 10-person startup trying to figure out how to go-to-market from scratch.
So I just started.
The On-Ramp: The Foundation You Can't Skip
Before day one, there were a few hours where I set up the foundation. I want to be honest about this because I've watched too many people try to skip it — and I've watched them end up frustrated, stuck, or building in the wrong direction entirely.
Here's what actually needs to exist before any of this works:
Claude CLI: Not the browser chat. The command-line tool that runs inside your terminal, beside your actual files, with your actual work. This is the thing that lets Claude not just answer questions but do things — read files, write files, version control, run automations. If you're talking to Claude in a browser window and copy-pasting results into Notion, you're not building a system. You're doing more work.
GitHub and the gh CLI: Everything lives in a GitHub repository. Not in Obsidian. Not in Notion. Not in a folder on your desktop. A git repo. This sounds scary if you've never used one, but here's all you need to know: it's a folder where everything has a history, everything is searchable, and both you and Claude can read it, write to it, and automate against it. Obsidian is great for notes. It's the wrong foundation for a team system that does things.
Structured Claude.md's plus a few hooks and rules: Small configuration files that tell Claude how to behave in your specific context. What to always do. What to never do. Where things live. How to format output. This is what makes Claude feel like your assistant rather than a generic one — and it's what makes the system get smarter over time instead of starting from scratch every session.
That's it. Three things. It takes two hours max if you're on a clean machine.
I know it sounds like setup cost. It is. But it's the only setup cost there is — after this, everything compounds.
A quick note: For anyone who's heard me say "just call me if you need help getting started" — I mean it. I've gotten dozens of people through this on-ramp in the last few months and every single one of them was off and running within two hours. The first session is the hardest. After that, you'll wonder what took you so long.
Days 1 & 2: The Power of the First Question
Day 1: I asked Claude to research our competitors.
That's it. Nothing fancy. I had a doc, Claude had the internet, and we filled it in together — who they were, what they offered, how they positioned themselves, what they charged.
One thing jumped out immediately: a capability gap. Something our product did that none of theirs did. That single finding — confirmed in about two hours on the first day — became the foundation of everything. Every piece of content. Every sales pitch. Every product decision. I didn't plan for that. I just started, and the problem revealed itself.
Day 2: I had a new problem.
Now that I knew what we had, I needed to make sure we could find out when that changed. What if a competitor closed that gap next month? I'd want to know immediately.
So Claude and I built a small automation. Every month, it checks competitor websites, reads their docs, and flags anything new. It opens a pull request with what changed. I review it. Done. That took maybe three hours.
Then I thought: what else changes in our market that I should be tracking? So we built another automation to monitor that too — pulling from sources I'd never have time to check manually, surfacing only what was relevant.
I didn't know I needed either of those things when I woke up that morning. The day before's work revealed them.
How It Actually Goes (The Compound Effect)
You don't start with a plan for an 18-workflow automated system. You start with one question. The answer to that question reveals the next question. And slowly, almost without noticing, you've built something real.
By Day 5: We had automated competitor monitoring, a content gap tracker, a market intelligence feed, and a CRM integration that turned sales call recordings into engineering tickets.
By Day 14: We had a brand system, a pitch deck framework, a 12-cohort customer research map, and account dossiers for our most important customer relationships.
By Day 41: We had a weekly intelligence digest that landed in Slack every Friday — competitive signals, regulatory news, market updates, conference opportunities — synthesized from eight different data sources, automatically.
By Day 57: We had 18 scheduled automations, a full outbound sales sequence for every customer segment, a blog content pipeline, and an automated image generator.
I did not know on day one that any of that was possible. I just knew what question I needed to answer that day.
What This Is (And Isn't)
What this is NOT:
A story about being technical: I did not write the code. I did not set up a server. The automations are workflows — Claude wrote them. I described what I wanted in plain English and we figured it out together.
A story about having a strategy: I didn't have a strategy on day one. I had a competitor doc and a question.
A story about scale: We're 10 people. My Claude Teams plan and I are the entire GTM function. There is no agency, no budget for a full marketing stack, no RevOps team.
What it IS a story about:
It's about the fact that the gap between "I have no idea what I'm doing" and "I have a system that compounds" is smaller than you think — and the bridge is just starting.
If you're an engineer who's never thought about marketing: you already know how to break a problem into smaller pieces. That's the whole skill.
If you're a marketer who's never touched code: you don't need to touch code. You need to describe what you want. Claude handles the rest.
If you're early in your career and wondering how people build these things: they build them one day at a time, surprised by the next problem, and then solve that one too.
If you're later in your career and wondering if you have the chops for this new world: the new world rewards people who can identify problems and communicate clearly. You've been doing that for years.
The Real Secret: Don't Stop
The system I have now has taken 57 days to build.
Not 57 full days. 57 calendar days, where most of the time I was doing my actual job — running sprints, talking to customers, writing specs, sitting in meetings. The GTM system got built in the margins. An hour here, an afternoon there.
The thing that made it compound wasn't intelligence or experience or a plan.
It was just not stopping.
Every day I'd look at what we'd built the day before, notice one thing that was missing or broken, and fix it. Claude and I would solve it together. Then I'd stop and do my job. The next day, same thing.
By day 57, I looked back and couldn't believe what we'd built.
Your First Step
If you want to start, start with the on-ramp. Two hours. Claude CLI, a GitHub repo, a few configuration files. If you're not sure how, reach out — I'll walk you through it. I've done it enough times now that I can get anyone set up in a single call.
Then ask your first question. Not a big strategic question. Just: What's one thing I need to know right now?
See what the answer reveals. Come back tomorrow.
That's the whole playbook.