The founder instinct is a slicker application tracker. The actual fear looks different. What building ScholarPilot revealed about the gap between assumption and signal.
Building ScholarPilot for a while surfaces a specific pattern: what I assumed international students needed and what the actual early signal pointed to were not the same thing. None of this is proven — ScholarPilot has zero paying customers, same as everything else in the portfolio — but the gap between assumption and signal was consistent enough to be worth writing down.
The assumption: a slicker application tracker
The obvious founder instinct is "make the process feel less chaotic" — a clean dashboard, deadline reminders, a visual sense of progress. That's a UI problem, and UI problems are satisfying to solve because they're visible and easy to demo.
What the actual fear looks like
The thing that seems to actually keep a student up at night isn't disorganization. It's a specific, concrete failure: submitting the wrong document, or a document with a small formatting error, and having an application rejected on a technicality that has nothing to do with whether they're qualified. That's not a UI problem. It's a correctness problem, and no amount of visual polish addresses it. A document-rejection prevention feature matters more to that fear than a nicer dashboard does, even though the dashboard is what a founder instinctively wants to build first.
The assumption: the student is the buyer
Individual students researching and applying directly, one at a time, paying for their own account — that's the default mental model. It's wrong often enough to matter. A real slice of this market goes through coaching centers and consultants who handle the application process on behalf of many students at once, and who are the ones actually making a purchasing decision. That's the entire reason a coaching-center-priced tier exists in ScholarPilot's pricing, separate from the individual plans — because the buyer, in a meaningful share of cases, isn't the student navigating the tool. It's the institution paying for many of them to use it.
The assumption: this is a regional product
Building from Bangladesh, the easy default is to build for students like the ones nearby. ScholarPilot deliberately doesn't target Bangladesh specifically — the underlying fear (getting something technically wrong on a document that matters enormously) doesn't belong to one country. It's a function of the process being unforgiving and the stakes being high, which is true wherever the student is applying from.
The honest caveat
This is informed by early signal, not proof. A handful of signups and a few real conversations shaped these assumptions-versus-reality contrasts, not a large sample or any paying customer confirming them at scale. The pattern worth taking from this isn't "these three specific insights are correct." It's that the gap between what a founder assumes a user needs and what the user is actually afraid of is often wide, and the only way to find that gap is by getting close enough to real users to hear what they're actually worried about, rather than designing from your own guess at their experience.