What Working at a Pre-PMF SaaS Startup Actually Feels Like

Before I understood what pre-PMF actually meant experientially, I understood it intellectually. I had read the frameworks, knew the metrics, could explain the concept in an interview. None of that prepared me for what it actually feels like to work inside a company that does not yet know if it has a sustainable business.

The gap between knowing a concept and experiencing it is nowhere wider than in the pre-PMF startup phase. What follows is an honest account of what that experience actually contains, written for the person who is about to join one or who is currently inside one wondering if what they are experiencing is normal.

The Absence of Feedback Loops

In a post-PMF company, you have enough users that data tells you something. Activation rates, retention cohorts, feature adoption, support volume, these numbers reflect reality and you can act on them. In a pre-PMF company, you often have twenty or fifty users, and the data tells you almost nothing because the sample size is too small and the users are too similar to each other to generalize from.

This creates a specific disorientation that nobody warns you about: you are making high-stakes product decisions without the feedback loops you were trained to rely on. The analytics dashboard is nearly empty. The customer conversations are the only signal. And the customers you have are early adopters who are often too generous in their feedback because they believe in the mission rather than because the product is working.

In my experience, the adjustment that helped most was treating every week as a research sprint rather than a delivery sprint. The goal was not to ship features. The goal was to answer the single most important question about the business. What is that question this week? Answering it was the work. Features were how you tested the answer.

The Constant Pivot Temptation

Pre-PMF companies live in a permanent tension between staying the course and changing direction. Every new customer conversation surfaces a slightly different version of the problem. Every failed sales call suggests a different ICP. Every week without meaningful growth triggers a discussion about whether the current approach is right.

The psychological experience is exhausting. You are simultaneously trying to execute with conviction and remain genuinely open to being wrong. Those two things are in direct tension. Executing with conviction requires committing to a direction. Remaining open to being wrong requires holding that direction loosely.

The teams that navigate this well have a clear definition of what would have to be true for them to change direction, agreed on in advance. Not "we'll know when to pivot when it feels right." But: if we have not reached X threshold with Y type of customer by Z date, we will revisit the ICP. The definition creates permission to stay the course without that permission requiring ignoring contradictory evidence.

What You Learn That Cannot Be Learned Any Other Way

Working in a pre-PMF startup builds a specific set of intuitions that are genuinely difficult to develop in any other context.

You learn to function under uncertainty without defaulting to the decision that reduces anxiety rather than the decision that reduces the most important unknown. The most anxiety-reducing move in a pre-PMF company is usually to build more features. The highest-leverage move is usually to talk to more customers. These are different things and the feeling that you should be building something is a trap.

You learn that most product problems are sales and positioning problems in disguise. When a feature is not being used, the first question is usually not "is the feature bad?" but "did we explain what problem it solves and for whom?" A lot of pre-PMF product work is really product marketing work: making the value proposition legible to the right people.

You learn to tell the difference between a customer who likes your product and a customer who has no good alternative. These look the same in the short term. In the long term, the first type renews and refers. The second type churns the moment a better alternative appears. Pre-PMF companies often accidentally build their early user base out of the second type, which makes the retention numbers look fine until they do not.

The Part Nobody Talks About

The hardest part of working in a pre-PMF startup is the loneliness of not knowing. Not the workload, not the ambiguity, not the lack of resources. The not-knowing-if-this-will-work part.

Every week you do your best work and the results are inconclusive. You cannot yet tell from the data whether the product is on a path to something. The honest answer is that nobody can. The only response available is to keep reducing the most important unknowns as fast as possible and trust that clarity will come from contact with reality.

The founders and PMs who come out of pre-PMF with the most intact sense of what they learned are almost always the ones who focused on the quality of their questions rather than the quality of their answers. The right question, asked of the right person, produces more value in pre-PMF than almost anything you can build.

For the signals that tell you whether you are approaching PMF, the PMF signals piece covers what actually changes when fit is developing. The idea validation framework covers the structured approach to reducing uncertainty at the earliest stage. The resources page has the external reading that is most useful during this specific phase.