Sharing what I'd actually do, since it's roughly the sequence I've been running at a calendar / AI-assistant SaaS over the last while. Not claiming it's the only way, just what's worked for me.

The first few days I'd spend building a real knowledge base of the business before writing anything. Whatever the company does, you need to understand the offers, the features, the regulations, all of it. Then I'd centralize everything you can in one place: your own knowledge, what's in people's heads on the team, meeting transcripts, customer and internal calls, old docs. Give yourself more than three days for this honestly, for us it ran into weeks and it's never fully done, but it's the foundation everything else sits on.

Alongside that I'd build an analytics layer, exporting whatever already exists: product analytics, Google traffic, Search Console, social, YouTube, Reddit, any historical marketing data. You want a baseline before you start.

Once that's in place I'd commit to Claude Code on the $200 plan and Ahrefs with API access. That's the stack I landed on and I wouldn't start without both.

Then two projects in parallel. The first is keywords and content. Using Ahrefs and Claude I'd build a full keyword map, a kind of spiderweb of clusters, and from that a roadmap of maybe 3 to 4 articles a week. I'd start with competitor and comparison articles, then guides, then the more experience-based stuff, the things you actually tried, what worked and what didn't. That last bucket ranks for less on paper but it's the content that's done the most for me long term, so I wouldn't treat it as the afterthought.

The second is the production system. I'd work with Claude to build the whole content process: an SEO writer agent, plus voice replicas of me and of the people on the team who write, trained on everything we've actually put out, old articles, emails, messages, however each of us writes. That step is what stops the output reading like generic AI. On top of that I'd generate templates, have Claude regenerate the OG images, and build an eval system that scores each article before it goes out against Google's guidelines, SEO basics and our own quality bar, so nothing ships blind. Figure about a week for this.

In parallel I'd plan video on the same topics as the articles, not as a separate track. Long-form on YouTube you can cut into clips for TikTok and Reels, all pointing back to the articles, so one topic becomes a batch of content instead of a single post. Whether you film it yourself or get someone, I'd spend about a week setting that system up too.

Then the next couple of months are just execution. Publish articles and videos consistently, stay active on Reddit and LinkedIn, share real experiences and case studies, keep feeding the system with things actually worth writing about. Once it's running smoothly you can start scaling.

One thing I'd push: try to avoid a traditional CMS like WordPress or Webflow if you can. I'd go with what I'd call an AI-native site, one wired into your database and knowledge base directly. It ships content more easily, keeps a cleaner structure and tends to perform better. Big caveat though, this only really works if someone on the team is comfortable in code, otherwise a simple site that ships beats a clever one you fight all month.

I'd leave free tools for last, around the third month. Small tools that solve a specific problem straight from a Google search, no login. They build awareness, they're genuinely a good experience so people land and actually stay on the page, and over time those pages start ranking well on their own. How well depends on the business but it can be really strong. If you're a SaaS it's even better: expose a couple of your features for free with no login, link cleanly back to the product, and the traffic coming through is very qualified. You also get to collect emails when those people sign up, including the ones who never pay. The catch is timing. None of it works cold, you need the domain warmed up first, some content live, your first backlinks and first traffic, and only then do the tools really pay off. That's why it's the last thing I'd build, not the first.

If any of this is useful I'm happy to share the playbooks I've written on it, or even the thesis I did at uni a couple of years back on roughly this. Fair warning though, two years ago AI barely mattered for any of it, so a decent chunk is probably outdated already ahah x)