Operational Discovery Report
“The CEO is functionally running customer success and doesn't know it.”
Northwind — B2B SaaS, Series A
22 people mapped · 19 workflows · 8 cross-team patterns · 3 agents scoped · Interviews conducted March 17–20, 2026
The map, in one paragraph.
Northwind is a 30-person B2B SaaS company in the phase every growing startup gets stuck in: the founders are still doing the work that shouldn't require a founder, and the team has gotten used to it. We interviewed every person on the team — 22 people across 7 hours and 41 minutes of conversation — and built a map of 19 workflows, 8 cross-team patterns, and 11 pieces of knowledge dependent on individual people. The single most revealing pattern: every person on the team, in separate interviews, said some version of ‘I wish we had more process’ — and every founder said some version of ‘I don't want to slow us down with too much process.’ That gap is the whole map. This document is a snapshot as of March 20, 2026.
The three patterns the map revealed first.
Your CEO is functionally your head of customer success and doesn't know it.
The map revealed that your CEO is spending between 12 and 15 hours per week on customer issues that aren't CEO issues. Support tickets escalated by customers who know his email, intros to new prospects that should be handled by the two AEs, implementation questions that should be answered by the CS lead, and a weekly cadence of ‘just checking in’ calls with customers who were onboarded more than six months ago. We mapped this by asking him to walk us through his calendar for two weeks and by cross-referencing what the rest of the team described him doing.
Nobody on the team thinks this is a good use of his time. Multiple people described it as ‘the CEO thing’ — a pattern they've observed, privately disagreed with, but never raised because they assumed he wanted it this way. When we told him what we found, his first reaction was that it couldn't possibly be 15 hours a week. His second reaction, after looking at the calendar cross-reference, was that it was probably more like 18.
He is also, in the same time period, trying to close the Series B. These two things are not compatible.
Estimated time recovered: 12–18 CEO hours per week, which at his current priority of fundraising and strategic partnerships is the most valuable time in the company. Cost to address: low. The fix is mostly about the CS lead having explicit permission to take over, and the CEO not responding when customers email him directly. Both of these are behavioral changes, not tool changes.
Your engineering lead is running hiring and it's eating her week.
The map revealed that your head of engineering is spending an estimated 14 hours a week on hiring activities: reviewing applications, doing first-round screens, coordinating with the recruiter, running technical interviews, debriefing with the team after each interview, writing offer emails, and responding to candidate questions after offers go out.
This is happening because you don't have a head of talent, because the engineering lead is the person who best understands what you're hiring for, and because the founders (reasonably) don't want a bad hire. But the knock-on effect is that she is producing roughly 30% less engineering output than she was six months ago, and her team has noticed. Two engineers mentioned, in separate interviews, that they ‘don't really have a technical lead anymore.’
You're hiring her replacement as a technical lead without realizing she's become a full-time recruiter wearing a technical lead's title.
Estimated time recovered: 10–14 engineering lead hours per week if hiring ops are moved to a contractor or part-time recruiter. Cost: one contractor, probably $4–6K/month, recouped immediately in engineering output.
Three different people are maintaining three different views of the pipeline.
The map revealed that your CEO has a spreadsheet. Your head of sales has a different spreadsheet. Your head of CS has a Notion page. All three contain information about the same set of customers and prospects. None of the three are the source of truth, though each person refers to their version as ‘the’ pipeline in conversation.
When we laid them side by side, the three views disagreed about the status of 8 of the 24 accounts they all tracked. In one case, a customer was listed as ‘churning’ in one view and ‘expanding’ in another. Nobody on the team had noticed because nobody on the team looks at more than one of the three views.
This isn't a tools problem — you have a real CRM and everybody has access. It's a trust problem. Each of the three people doesn't trust the CRM enough to rely on it, so each has built a shadow version they can trust, and now you have four sources of truth including the CRM. The fix is not ‘use the CRM more’ — the fix is figuring out why nobody trusts it and fixing that first.
Estimated time recovered: modest — maybe 4 hours a week across the three people. But the strategic value is much higher than the hours saved, because right now you can't actually answer the question ‘what's happening with our customers’ with any single source.
The five mid-tier patterns.
These are presented more briefly. Each was mentioned by multiple interviewees or surfaced as a pattern across teams.
Your on-call rotation is two people.
Everyone else on the engineering team knows this and nobody has volunteered to be the third, because the on-call experience is described by those two people as 'brutal.' Worth fixing the on-call experience before trying to expand the rotation.
Cultural fix, not a tools fix.
Your weekly all-hands is 45 minutes long and has the same agenda every week.
Three people described it as 'the meeting where I catch up on Slack.' The founders described it as 'important for alignment.' Both are right, which means the meeting is doing a job that could be done better in writing.
Probably worth switching to an async written update with a 15-minute sync for questions.
Your head of CS is the only person who knows how two of your biggest customers actually use the product.
If she leaves, that knowledge leaves with her. Neither of the two customers has good internal documentation on their own usage, and nobody else at Northwind has spent real time with them.
Succession risk worth addressing even if she has no plans to leave.
Your junior AE is outperforming expectations and nobody has told him.
His close rate is 40% higher than the senior AE's. The senior AE has noticed and is frustrated. The junior AE doesn't know he's outperforming. Leadership hasn't acknowledged it. This is a retention risk on the person you most want to keep.
Not an automation finding. A management finding.
You have no single place where new hires can find out how things work.
Onboarding is done by 'shadow someone for your first week,' which is working by accident. Two of the three most recent hires said the first two weeks were 'confusing but figurable.' That's a runway-burning way to onboard when you're growing.
A simple internal wiki would solve 80% of this for about two days of work.
The agent blueprint.
For each high-value pattern, a specific AI agent to build — in the order we'd build them, with estimated hours recovered and the reason it sits in that slot.
CEO-to-CS handoff agent
Hiring operations agent
Pipeline truth agent
A note on what the map didn't reveal.
A few things worth saying, because documents like this tend to oversell.
We didn't find evidence that your team is underperforming. The opposite, actually — the people we interviewed are working hard on the right things and the product is clearly good. The findings in this report are about the scaffolding around the team, not the team itself.
We didn't find a reason to believe you have a culture problem. A few of the things in this report (the on-call burnout, the junior AE who hasn't been recognized) could become culture problems if left alone for six more months, but they aren't yet.
We didn't find that you need more tools. You already have most of the tools you need. The problem is that the tools you have aren't being trusted, and the fix for that is not buying more tools. It's having a hard conversation about why nobody trusts the CRM and then either fixing the CRM or picking a different source of truth and committing to it. That conversation is worth more than any automation we could build for you.
This is a snapshot. The real map is live.
This document captures the Plainsight map for Northwind as of March 20, 2026. The live map is hosted at a private URL for the leadership team and continues to update as new interviews happen and patterns shift. If you are the leader who commissioned this map, your URL is in your email. If you are evaluating Plainsight, the closest thing to a live map view is in the three sample companies on our homepage.
This is what your company's map could look like.
Add your team and we'll start the interviews this week. You'll watch your map build in real time.