How to Build a Product Marketing Function from Scratch at a SaaS Startup

You're the First. That's a Feature, Not a Bug.

Congratulations  you've just joined a SaaS startup as their first Product Marketer. The product is live, some customers are paying, and the sales team is shipping decks that look like they were made in 2015.

There's no positioning doc.

No personas.

No launch process.

Just a lot of Slack messages that say 'can you write something for this?'

This moment  terrifying as it feels  is actually an extraordinary opportunity. You get to build the function from scratch. No inherited bad habits. No outdated playbooks. Just a blank page and the chance to create something that will compound in value for years.

But where do you start? Here's a structured 30/60/90 day framework for the first PMM hire at a SaaS startup.

Days 1–30: Listen, Learn, and Don't Touch the Keyboard Yet

Your first instinct will be to build things. Resist it. The single most valuable thing you can do in your first 30 days is develop a deep, unfiltered understanding of the business.

What to prioritize:

• Conduct 10–15 customer interviews. Ask about their jobs-to-be-done, why they chose you, what they almost chose instead, and what they'd miss if you disappeared. These conversations are gold.

• Shadow 5+ sales calls. Listen for the objections, the competitor mentions, and the moments where the rep improvises because they don't have the right answer.

• Interview every function: product, sales, CS, leadership. Understand what they think the product does, who it's for, and what 'winning' looks like.

• Audit existing materials: website copy, pitch decks, one-pagers, onboarding emails. What story is being told? Is it consistent?

Early PMMs reportedly spend significant time with customer success teams to understand why enterprise customers were choosing their competitors over them. That intelligence directly shape their go-to-market positioning.

Your output by Day 30: A findings doc. What you heard, what's consistent, what's contradictory, and where the biggest gaps are.

Days 31–60: Build the Foundation

With research in hand, you're now ready to build the assets that have the highest leverage  starting with what impacts sales and retention most immediately.

Priority 1: Positioning Document

Use April Dunford's framework (competitive alternatives, unique attributes, value, customers, market category) to synthesize your research into a positioning doc. Present it to leadership and the sales team. Expect debate. That debate is healthy  it means you've surfaced assumptions that were never made explicit.

Priority 2: ICP and Persona Profiles

Define your Ideal Customer Profile (ICP) with firmographic precision: company size, industry, tech stack, buying trigger. Then build 2–3 persona profiles for the key buying roles. Keep them short  a good persona fits on one page.

Priority 3: One Competitive Battlecard

Pick the competitor that comes up most in lost deals. Build one thorough battlecard. Share it with the sales team. Get feedback. This immediately earns you credibility with the revenue team.

Your output by Day 60: Positioning doc, ICP + 2-3 personas, first battlecard, preliminary messaging framework.

Days 61–90: Go-to-Market Infrastructure and Credibility

By now you have a foundation. The next 30 days are about embedding yourself in the revenue motion and building the systems that scale.

Build a launch process

Create a simple launch template that defines: launch tiers (internal vs. limited vs. GA), required assets per tier, approval workflow, and post-launch review. This doesn't need to be perfect  it needs to exist. Every company that ships features without a process is leaving revenue on the table.

Create a sales enablement kit

Package your positioning, personas, and battlecard into a sales kit. Record a Loom walkthrough. Do an enablement session with the sales team. Make it easy for reps to use your assets without having to ask you.

Establish a win/loss review rhythm

Set up a monthly call with sales leadership to review win and loss patterns. This keeps your positioning sharp and gives you the data to prioritize future PMM work.

Postman, which built much of its early growth through developer community and product-led motion, eventually needed a more structured PMM function as it moved upmarket. That transition required clear ICP documentation, enterprise-specific messaging, and a sales enablement layer that hadn't existed before.

The Meta-Skill: Earning Cross-Functional Trust

Technical skills aside, the most important thing you'll do in your first 90 days is earn trust. Sales needs to believe your assets will help them win. Product needs to believe you understand the technology. Leadership needs to believe you're driving outcomes, not just outputs.

Three things that build trust fast: show your work (share drafts early, ask for feedback), be present in revenue meetings (not just marketing syncs), and deliver something fast that makes someone's job easier  even if it's imperfect.

Chargebee's early PMM team reportedly operated with a strong bias toward sales partnership. The mindset wasn't 'what content should we produce'  it was 'what does the sales team need to close the next deal?'

Conclusion: Build for the Business, Not the PMM Playbook

There's no universal template for the first PMM role at a startup. Every company is different. But the 30/60/90 framework works because it sequences your work in order of leverage: understand first, build the foundation second, systematize third.

The product marketer who spends their first week writing website copy before talking to a single customer is building on sand. The one who listens first, synthesizes what they heard, and then builds assets rooted in real customer language? They're building something that compounds.

Start there. Everything else follows.

KEY TAKEAWAYS

• Days 1–30 should be spent entirely on research: customer interviews, sales call shadows, and a full audit of existing messaging.

• The positioning document is the highest-leverage first asset  it aligns the entire organization around a single narrative.

• Building one great battlecard early earns immediate credibility with the sales team.

• A launch process and sales enablement kit by Day 90 creates the systems that make PMM scalable.

• Cross-functional trust is built by showing up in revenue meetings and delivering things that make other people's jobs easier.

Follow Deepak Ruchandani for more such insights