Mika Janssen

Why this persona fits the audience

He runs a 3-person startup in Amsterdam and checks app marketplace trends weekly using a paid competitor tool, then cross-verifies key findings in spreadsheets before making decisions. The team watches review trends, category pricing, and feature gaps across several app ecosystems.

• Age: 39
• Location: Amsterdam, Netherlands
• Occupation: Technical founder
• Income: €115,000
• Education: Master's degree in Computer Science from TU Delft
• Company size: 3
• Years in role: 4

“The real value isn't just seeing the data; it's understanding what the data *means* after you've rigorously tested its integrity.”

Mika Janssen, 39, is a Dutch technical founder deeply embedded in the world of app market intelligence. Raised in a modest family in Utrecht, his early fascination with how systems worked led him to pursue a Master's degree in Computer Science at TU Delft. Upon graduation, he spent several years at a prominent Dutch tech firm, honing his skills in backend development and data architecture. However, the allure of building something of his own, coupled with a keen observation of inefficiencies in how app developers identified market opportunities, spurred him to co-found his current venture four years ago. He lives in Amsterdam's Oud-West district with his partner and young daughter, a life he meticulously balances with the demands of his startup. His income, while comfortable, is secondary to the company's progress and his personal drive for technical excellence. Mika is inherently skeptical of surface-level information, a trait that heavily influences his professional approach. He believes that true insights lie beneath the obvious, requiring diligent investigation and validation. This manifests in his rigorous weekly process: he subscribes to a paid app intelligence platform, but never takes its output at face value. Instead, he dedicates significant time to cross-referencing its findings with custom-built spreadsheets, analyzing review sentiment trends, category pricing fluctuations, and feature gaps across multiple app ecosystems. This methodical approach is driven by his core values of accuracy and speed – he wants to move fast, but only on a foundation of solid, verified data. He sees ownership not just of his company, but of the integrity of his decision-making process, as paramount. His technical background provides him with the confidence to build and refine the tools he needs, even if it means spending extra hours ensuring data pipelines are robust and analyses are sound. He is driven by the challenge of finding genuine product-market fit and optimizing the developer experience through data, viewing his work as a continuous problem-solving exercise rather than a means to rapid personal wealth.

Background & daily life

A day in their life

Mika's typical weekday begins around 7:00 AM with coffee and a quick scan of Hacker News and overnight metrics. After getting his daughter ready and cycling her to daycare, he arrives at his co-working space by 9:00 AM. The morning is dedicated to coding, debugging, or architectural planning, often involving deep focus sessions. Lunch is usually a quick, healthy meal at his desk or a brief walk. The afternoon involves a weekly market trend analysis session using their paid competitor tool, followed by cross-referencing findings in custom spreadsheets and discussing potential product implications with his co-founders. He aims to leave by 6:00 PM to be home for dinner, but often returns for another hour or two of focused work after his daughter is asleep, typically around 9:30 PM.

Lifestyle

Mika lives in a characteristic Amsterdam canal house in Oud-West with his partner and young daughter. His days are structured around his startup, but he prioritizes family time, often cycling his daughter to daycare before heading to the co-working space. Evenings are for focused work or quiet family dinners. He's a creature of habit, starting his day with a meticulously prepared espresso and reviewing key metrics. Weekends involve exploring the city by bike, visiting local markets, or working on personal coding projects. He’s financially prudent, preferring to reinvest profits rather than take on external funding, and views his income as a measure of his company's progress, not personal luxury.

Work life

As CTO and co-founder, Mika lives and breathes his startup, a small SaaS company focused on app market intelligence. His workday is a blend of deep technical work, strategic planning, and team management. He spends significant time analyzing competitor data, market trends, and user feedback, often using a paid app intelligence tool but always cross-referencing with custom-built spreadsheets for validation. He feels the pressure to constantly find the next product-market fit and optimize their offering. His two co-founders handle marketing and operations, allowing him to focus on product development and technical strategy. The small team dynamic fosters intense collaboration but also means everyone wears multiple hats.

Relationships

Mika's primary relationships are with his partner, who understands the demands of startup life, and his young daughter. He maintains a close circle of university friends, a few of whom are also in tech, providing a sounding board for technical challenges. Within the startup, he has a collaborative but direct relationship with his co-founders, built on mutual respect for each other's expertise.

How they decide

Mika is a research-heavy, data-driven decision-maker. He meticulously gathers information from multiple sources, including paid tools, public data, and team input. He prioritizes accuracy and validation, often building custom analyses to confirm findings before committing to a course of action. While he values speed, he is not impulsive and will delay a decision if he feels the data is insufficient or potentially misleading. He trusts his own analysis above all else.

How they sound

Speaks with a calm, measured tone, often pausing to formulate precise language. His Dutch accent is subtle but present. He avoids hyperbole and buzzwords, preferring direct, factual statements. When discussing technical topics, he can become quite animated, but his overall demeanor remains composed. He uses 'we' when referring to the company's decisions and 'I' when discussing personal technical insights.