The First 90 Days
What Actually Matters in a New PSM Role
I've started a few new customer-facing roles over the years, and the thing nobody tells you upfront is that how you spend the first thirty days determines a lot about the next two years. Not just whether you close a deal or hit a number — those matter too — but whether you end up operating from a real foundation or from a patchwork of assumptions you never had time to test.
The plan I use now has three phases. Not because thirty-day checkpoints are magic, but because the work genuinely changes character at each one. Month one is about building the map. Month two is about starting to drive. Month three is about connecting what you're seeing to where the client needs to be in three to five years. Those aren't interchangeable. Trying to skip ahead — treating an early win as a substitute for the intelligence-gathering you haven't done yet — tends to catch up with you somewhere between day 60 and renewal.
Month one is intelligence gathering, not orientation
Here's the reframe that changed how I approach new roles: the first 30 days aren't orientation. They're reconnaissance. Every conversation, every shadowed call, every product deep-dive — I'm building a picture I'll be drawing on for the next two years. The PSM who shows up to day one with a diagnosis is the one who ends up solving the wrong problems very confidently.
So I listen first. Not passively — I'm mapping the platform ecosystem, identifying where clients see ROI fastest, understanding where adoption stalls and why. I'm sitting on escalation calls alongside more experienced colleagues, not to observe, but to learn what the real conversations sound like versus the polished ones. I'm interviewing internal teams — implementation, support, sales engineering, product — specifically to understand what they wish the PSMs they hand accounts to already knew. That last question always produces something useful.
By weeks three and four, I'm into the client portfolio itself. Utilization audits. Volume and trend analysis. For payment and usage platforms especially, you need to understand seasonal patterns — when stress hits the system, what "normal" looks like for each client — before you can have an informed conversation about anything. Underutilization is almost always the first signal of either risk or a dormant opportunity, and you need to be able to tell the difference.
I want to come out of month one with a risk/opportunity matrix — at minimum three accounts flagged for immediate action. One that's at risk and needs attention now. One that's expansion-ready and just needs someone to start the conversation. And one quick win: something sitting unconfigured, some feature that would immediately reduce pain if the client knew it existed. That matrix is the foundation everything in month two gets built on.
I don't believe in showing up to day one with a diagnosis. I show up with a framework for listening. Clients can tell the difference between a PSM who's genuinely curious about their business and a PSM who's running through a checklist. And in regulated industries — utilities, energy, water — that distinction matters more than it does elsewhere. These clients deploy platforms they'll eventually need to explain to regulators and auditors. They're not looking for a vendor relationship. They're looking for someone who actually understands what they're trying to accomplish.
Month two: listening stops, leading starts
By day 31, I've mapped the portfolio. I know where the risks live. I know where the opportunities are. Month two is where I start acting on it — deliberately, not reactively, which is its own discipline.
The client-facing shift is significant. The meetings I'm scheduling now aren't status calls. They're strategy sessions. The agenda is their business goals first, platform performance second, roadmap alignment third. That order isn't incidental — it signals to the client that I'm thinking about their outcomes, not just product adoption metrics.
I also try to run one platform optimization workshop in month two. This is a working session built around the highest utilization gap I found in month one. The goal is to walk the client's team through how to get more value from what they already own — no new spend, no expansion pitch, just capability they've been leaving on the table. It's one of the fastest ways to establish credibility with a client who's been skeptical about whether their CS investment actually translates into anything.
The temptation in month two is to try to impress everyone at once. I've learned that the most impressive thing you can do is solve one real problem completely rather than half-solve five of them. An early win that actually sticks — a documented expansion opportunity, a churn prevention that you can point to specifically — is worth more than a month of visible effort that doesn't move anything.
The internal work in month two is just as important. I establish cross-functional syncs — product, support, sales, professional services — not to report, but to exchange intelligence. What are clients asking for that isn't on the roadmap? What implementation gaps are creating downstream PSM headaches? That intel loop is how you start getting ahead of issues instead of reacting to them. I also try to build the escalation reflex early: looping in delivery and support teams before situations become emergencies. The PSMs who earn a reputation for being genuinely easy to work with are the ones who over-communicate early and under-escalate late. That's a learnable habit, but it requires making it a priority in month two rather than something you get around to eventually.
Month three: from competent to strategic
By day 61, I should be able to run my portfolio without constant internal support. That's the baseline expectation for month three — not a goal, just the minimum. The actual work is shifting from competent to strategic, which means connecting what clients are doing today with where they need to be in three to five years and demonstrating that the platform is the vehicle that gets them there.
For at least one strategic account, I want to have a 12 to 24 month roadmap built out — something that ties platform capabilities to their stated infrastructure or business goals, that shows them what the product can do in year two that they aren't thinking about yet. This is where PSMs who've genuinely done the intelligence work in month one have a real advantage: you know enough about the account to make that roadmap feel specific and earned rather than like a template with their logo on it.
In regulated industries particularly, I've found it valuable to develop what I think of as a future-state framework — one that connects platform capabilities to the pressures that are actually bearing down on the client's sector. Grid modernization. AI adoption. Regulatory scrutiny of automated billing decisions. Affordability mandates in utility contexts. These aren't abstract forces; they show up in my clients' planning conversations all the time, and a PSM who can speak to them from both sides — vendor and former customer — creates a different kind of partnership than one who knows the product roadmap cold but doesn't understand the regulatory environment the client is navigating.
I try to build a QBR format that opens with the client's goals, demonstrates the platform's contribution toward those goals, surfaces at least one insight they didn't have before the meeting, and closes with a clear mutual action plan. Not a metrics deck. A strategic review. The difference is whether the client leaves thinking about their business or about your product.
The three things underneath all of it
The structure of a 30-60-90 is useful, but the structure isn't really the point. Three beliefs shape how I work in platform success roles, and they apply regardless of what phase I'm in.
The first is that I don't wait for health scores to turn red. In highly regulated industries, the gap between "things seem fine" and "this is now an emergency" is genuinely smaller than in other sectors. Procurement scrutiny happens faster, switching costs get weaponized in RFPs, and a client who felt fine six months ago can have a very different organizational reality by renewal. Tracking utilization patterns, support ticket trends, and stakeholder engagement isn't paranoia — it's the actual job.
The second is that I don't teach clients how to use features. I help them achieve business outcomes. A payment platform isn't a payment platform — it's a tool to reduce days sales outstanding, increase auto-pay adoption, eliminate the call center volume that comes from customers confused about whether their payment posted. When you lead with features, you get evaluated on features. When you lead with outcomes, you get evaluated on whether the client's business got better. That's a different conversation at renewal.
The third is trust through transparency. Clients in regulated industries deploy platforms they'll eventually need to explain to regulators, auditors, and boards. They need a PSM who understands that "defensible" matters just as much as "effective." I know what it's like to sit on the client side of that equation — which makes me a more useful partner when they're navigating it. That's not something you can fake. But it is something you can establish in the first 90 days, if you spend that time actually learning the client's world rather than performing expertise you haven't earned yet.
The first 90 days matter because the habits and relationships you build in that window are hard to undo. Show up curious. Build the map before you start driving. Solve one real problem completely. And get in front of the right stakeholders before you actually need them.
Everything else follows from that.
Questions? Want to compare notes on how this plays out in utility or fintech accounts? Reach me at sonya.freeney@gmail.com or LinkedIn.