10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Jort Lubbers

Jort Lubbers

CTO at a bootstrapped SaaS

Full-depth AI personas

Why this persona fits the audience

He is CTO of a 3-person bootstrapped SaaS team in Amsterdam and is kicking off a new internal tool in Next.js alongside the main product. The team already has a homegrown boilerplate with shared UI, auth, and deployment scripts reused across repos.

  • Age: 41
  • Location: Amsterdam, Netherlands
  • Occupation: CTO
  • Income: €110k
  • Education: MSc Computer Science
  • Company size: 3 (Founder/CEO, Designer/Frontend, himself)
  • Years in role: 4 years as CTO, 12 years total in tech leadership
“I don't build things to impress investors; I build them so they don't break when I'm asleep.”

Jort Lubbers, 41, is the backbone of a lean, bootstrapped SaaS operation in Amsterdam. With an MSc in Computer Science from Delft University of Technology, he spent the early part of his career in large-scale enterprise environments, where he grew disillusioned with bureaucratic inertia and the disconnect between architectural ideals and business reality. This led him to join a small startup as a founding engineer four years ago, eventually taking the title of CTO as the team remained stubbornly small to preserve equity and autonomy. He is a staunch advocate of the 'build it yourself' philosophy, particularly regarding developer tooling. His team currently relies on a bespoke Next.js boilerplate that Jort wrote from scratch, containing custom hooks for internationalization, role-based access control, and a unified deployment pipeline that scrapes AWS costs daily. Recently, he faced a critical decision regarding the migration of their legacy monolith; while competitors suggested a costly SaaS platform, Jort opted to incrementally refactor the database schema and introduce a GraphQL gateway, a move that required six weeks of intense coding but saved the company €40,000 annually in licensing fees. He is a man of discipline, treating his body and his codebase with equal reverence. He runs marathons not for glory, but for the mental clarity it provides during late-night debugging sessions. Despite his technical prowess, he remains acutely aware of the fragility of their position; one major bug could bankrupt the venture. Consequently, his days are a delicate dance between pushing innovation forward and fortifying the walls against inevitable failure. He does not seek fame or venture capital; he seeks a sustainable, self-sufficient existence where his code solves real problems efficiently.

Background & daily life

A day in their life

The alarm rings at 5:30 AM. Jort rises immediately, bypassing snooze, and prepares black coffee while checking global server status dashboards. By 6:15, he is lacing up his running shoes for a 7km run along the Amstel river, listening to a podcast on distributed systems. Back home by 7:30, he showers and eats a protein-rich breakfast before logging into his dual-monitor setup at 8:15. The first hour is dedicated to deep work: refactoring the authentication module for the new internal tool. At 10:00, he joins a brief stand-up with his CEO and designer, discussing the progress of the main product's billing integration. Lunch is a quick, pre-prepared meal eaten at his desk while reading documentation on Next.js 14 features. Afternoon meetings are minimized, allowing him to focus on code reviews and deploying the latest staging build. By 5:00 PM, he disconnects, heading out for a second workout or cycling commute home. Evenings are reserved for family, cooking, and occasionally tinkering with open-source contributions on GitHub before bed, usually around 10:30 PM.

Lifestyle

Jort lives in a meticulously organized apartment in Amsterdam's Oud-West district, where every cable is managed and every book is categorized by subject. His mornings are non-negotiable: a 5:30 AM wake-up, followed by an hour of high-intensity interval running or long-distance cycling before work. He treats his health with the same rigor he applies to code refactoring, tracking macros and sleep cycles religiously. Financially, he is conservative despite his income; he maximizes tax-efficient investments in the Dutch system and avoids consumer debt, viewing cash flow as a critical survival metric for his company. Socially, he is selective, preferring deep one-on-one conversations over crowded networking events, often found cycling through the Vondelpark with a close friend or hosting small dinner parties where the conversation inevitably turns to engineering challenges.

Work life

As the sole technical decision-maker for a three-person bootstrapped entity, Jort operates without a safety net. His day is split between writing core backend logic for their flagship SaaS and architecting a new internal admin dashboard using Next.js. He maintains a custom, internal boilerplate that serves as the single source of truth for UI components, authentication flows, and CI/CD pipelines. Recently, he rejected a popular third-party CMS integration because it introduced unnecessary latency and vendor lock-in, opting instead to build a lightweight headless solution tailored to their specific data needs. He spends hours reviewing pull requests from his remote frontend designer, ensuring type safety and architectural consistency. The pressure is constant but self-imposed; there are no investors to please, only the need to keep revenue positive and the system stable while manually managing server costs.

Relationships

Jort is married to a graphic designer who runs her own freelance studio; they share a quiet, supportive dynamic where professional boundaries are respected. He has two close friends from university, both in tech, with whom he shares a monthly 'code review' dinner. He is not deeply embedded in the broader Amsterdam tech scene, avoiding large conferences, but participates actively in a small, private Slack group of bootstrapped founders. His primary influence comes from his own past failures and the practical feedback of his two colleagues, rather than industry thought leaders.

How they decide

Jort employs a highly analytical, evidence-based decision style. He rarely acts on hype or peer pressure. Before adopting any new technology, he conducts a thorough cost-benefit analysis, often building a small proof-of-concept (PoC) to verify performance claims against his existing stack. He values data over intuition and prefers incremental changes that can be easily rolled back. His decisions are slow but deliberate, prioritizing long-term maintainability and system stability over short-term velocity, though this sometimes frustrates faster-moving stakeholders.

How they sound

His speech is direct, precise, and devoid of filler words. He speaks in complete, structured sentences, often using analogies related to physical mechanics or structural integrity. He avoids marketing jargon like 'synergy' or 'disruptive,' preferring terms like 'latency,' 'coupling,' and 'maintenance burden.' His tone is calm and measured, rarely raising his voice even under pressure. He tends to pause slightly before answering complex questions, processing the logic internally before speaking. There is a distinct Dutch pragmatism in his phrasing—straight to the point, factual, and slightly formal, yet approachable among peers.

Personality traits

  • meticulous
  • stoic
  • efficiency-obsessed
  • methodical
  • quietly confident
  • risk-averse regarding stability
  • direct communicator
  • process-oriented
  • physically disciplined
  • independent thinker

Goals

  • Achieve full passive income coverage within 3 years to reduce operational stress
  • Refactor the legacy monolith into a micro-frontend architecture without downtime
  • Complete a 100km endurance bike ride unassisted within six months
  • Establish a mentorship program for junior developers in the Amsterdam region
  • Reduce technical debt ratio by 40% in the next fiscal year
  • Automate 90% of manual deployment tasks to free up development time

Problems & frictions

  • Time scarcity prevents deep work on architectural improvements due to immediate feature demands
  • Maintaining consistency across multiple repositories with their custom boilerplate is becoming brittle
  • Balancing the need for rapid iteration with the desire for rigorous code quality
  • Limited budget restricts access to premium enterprise-grade developer tools
  • Isolation in decision-making leads to occasional blind spots in security auditing
  • Scaling the team from three to five people without introducing bureaucratic overhead

Values

  • pragmatism
  • autonomy
  • technical depth
  • sustainability
  • craftsmanship
  • self-reliance

Interests

  • system architecture
  • developer tooling
  • endurance sports
  • mechanical keyboards
  • Dutch cycling infrastructure
  • open-source governance

Media habits

  • Lobsters community discussions
  • The Pragmatic Engineer newsletter
  • Local Dutch tech meetups (low key)
  • Podcasts on system design (e.g., Software Engineering Daily)
  • Strava for training data analysis
  • GitHub trending repos

Questions & answers

Jort Lubbers’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Staarter (https://staarter.dev): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    A lifetime license for $299, using code LAUNCH100, sounds reasonable for a comprehensive boilerplate. The features listed – auth, billing, localization, admin dashboard, dark mode, type-safe API, and integrations for payments, database, and cloud storage – align with what we've built ourselves, though ours is highly customized. The key differentiator for me is the 'last update 11 months ago' – that's a significant red flag for a rapidly evolving stack like Next.js. If updates are infrequent, the value diminishes rapidly. I'd stop considering it if the price went significantly above $300 for what appears to be a static codebase. My maximum acceptable price would be $299 per item for lifetime access, provided there's a clear, active update and support strategy.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.