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

Zeyd Dekker

Zeyd Dekker

Technical cofounder already paying for newsletter infrastructure

Full-depth AI personas

Why this persona fits the audience

He and one cofounder are validating a developer tool, publishing a landing page, collecting email interest in Beehiiv, and keeping a shared spreadsheet of signup source, role, and use case; he checks the list daily from his laptop and phone.

  • Age: 30
  • Location: Amsterdam, Netherlands
  • Occupation: cofounder
  • Income: EUR 55k from contracting
  • Education: Bachelor's in Software Engineering
  • Company size: 2 (cofounder + himself)
  • Years in role: 0.5
“The elegance isn't in the feature set; it's in how seamlessly the pieces fit together to solve a real problem.”

Zeyd Dekker, 30, is a cofounder based in Amsterdam, Netherlands, currently bootstrapping a developer tool startup. Holding a Bachelor's in Software Engineering, he spent his early career in various contracting roles, honing his skills in backend systems and cloud infrastructure, which currently provide his EUR 55k income. This financial independence allows him the freedom to pursue his entrepreneurial ambitions without immediate pressure for external funding. His technical expertise is the bedrock of the startup, where he focuses on building the core product while his cofounder handles much of the go-to-market strategy. Zeyd is driven by a deep appreciation for technical elegance and efficiency, often spending hours optimizing code for performance and maintainability. He views time as a critical resource, meticulously managing his schedule to maximize productive output, a trait reflected in his minimalist lifestyle and disciplined routines. His decision-making is heavily influenced by data and logical analysis, preferring to iterate based on concrete evidence rather than abstract theories. He is currently paying for newsletter infrastructure (Beehiiv) and actively managing a spreadsheet detailing signup sources, user roles, and use cases for their new developer tool, a process he monitors daily from both his laptop and phone. This hands-on approach to validation underscores his commitment to building a product that resonates deeply with its target audience, prioritizing speed and technical soundness above all else. He views status through the lens of technical achievement and problem-solving capability, not necessarily through financial wealth or public recognition.

Background & daily life

A day in their life

Zeyd's day begins at 5:30 AM with a strong espresso and a 45-minute cycling session, returning home just as the city stirs. After a quick shower, he's at his standing desk by 7:00 AM, immediately checking Hacker News and then diving into the shared signup spreadsheet, analyzing new entries for patterns and potential user segments. The morning is dedicated to coding, tackling complex features or refactoring existing modules. Lunch is a quick, pre-prepared meal eaten while reviewing product analytics or documentation. The afternoon might involve a focused async discussion with his cofounder or more coding, interspersed with checking email and monitoring the landing page's performance. He aims to wrap up core work by 6:00 PM, often followed by an hour of reading technical blogs or exploring new developer tools before winding down.

Lifestyle

Zeyd lives alone in a small but efficient loft in De Pijp, where his primary furniture is a standing desk, a high-end mechanical keyboard, and a fold-out bike he assembles before dawn to avoid morning crowds. He runs on black coffee and disciplined routines, often skipping lunch to maximize coding time. His income from freelance contracting funds his startup's lean operations and his modest lifestyle, prioritizing experiences and tools over material possessions. Social life is minimal, usually limited to occasional, intense discussions with his cofounder or a quick beer with a former colleague.

Work life

As cofounder of a nascent developer tool startup, Zeyd's work life is a blur of intense focus and constant iteration. He splits his time between coding the core product, managing the landing page and newsletter infrastructure (currently Beehiiv, which he pays for out-of-pocket), and meticulously tracking signup data in a shared spreadsheet. His cofounder handles more of the outward-facing sales and marketing copy, while Zeyd dives deep into the technical validation. He works primarily from his home office, occasionally using co-working spaces for a change of scenery, but always with his trusty laptop and phone within reach. The pressure is immense, fueled by a desire to prove the concept and build something technically sound.

Relationships

His primary professional relationship is with his cofounder, a dynamic contrast to his own analytical approach. They communicate constantly via Slack and bi-weekly syncs, with Zeyd often deferring to his cofounder on messaging while rigorously defending technical architecture. His family is supportive but distant, living in another province. Friendships are few but deep, often with fellow engineers who understand his intense focus.

How they decide

Zeyd is a data-driven decision-maker, heavily influenced by empirical evidence and logical deduction. He researches thoroughly when a technical problem arises, often exploring multiple solutions before committing. For strategic decisions, he relies on his cofounder's market intuition and their shared spreadsheet data, preferring to iterate quickly based on feedback rather than prolonged deliberation.

How they sound

Speaks with a precise, measured cadence, often using technical analogies. Avoids hyperbole and emotional language, preferring factual statements. His Dutch accent is subtle but present. He tends to use 'we' when discussing the company, but 'I' when referring to his technical contributions. Can be terse when focused, but opens up when discussing elegant code or system design. Avoids jargon unless speaking to other developers.

Personality traits

  • Tactically impatient, strategically patient
  • Designs systems first, asks questions later
  • Prefers whiskey and cycling over parties
  • Talks in tight, technical metaphors
  • Hates meetings, loves async communication
  • Will rewrite a 100-line script if it's 'dirty'
  • Writes extensive READMEs for his own code
  • Distrusts hype, trusts data
  • Deletes unused apps weekly like they're clutter
  • Always has 3 backup plans for critical processes

Goals

  • Achieve product-market fit for their developer tool within 18 months.
  • Build a sustainable, profitable SaaS business without external funding.
  • Automate 90% of their current validation and onboarding processes.
  • Maintain full technical and strategic autonomy over the product's direction.
  • Eventually scale the team to a small, highly-skilled engineering unit.

Problems & frictions

  • Limited runway for product development due to self-funding.
  • Balancing deep technical work with the necessity of user acquisition.
  • The inherent uncertainty of validating a new developer tool.
  • Finding time for strategic planning amidst daily operational demands.
  • The constant need to optimize and refine the validation funnel.

Values

  • speed
  • technical elegance
  • freedom
  • autonomy
  • minimalism

Interests

  • developer tooling
  • newsletters
  • product analytics
  • functional programming
  • cycling

Media habits

  • Hacker News
  • Y Combinator podcasts
  • Lobsters
  • Indie Hackers
  • Twitter (for tech news)

Questions & answers

Zeyd Dekker’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Lighthouse (https://lighthouse.build/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, my cofounder and I are using Beehiiv for our newsletter infrastructure and a shared spreadsheet to track signups, roles, and use cases. Lighthouse seems to consolidate many of these functions. What specifically stops me from trying it is understanding how seamlessly the data from my current Beehiiv setup would migrate, and whether the AI insights are truly unique or just a repackaging of basic analytics. The MCP server integration for AI querying is interesting, though. If it integrates smoothly and the AI analysis proves valuable beyond what I can glean from manual review and basic analytics, I might consider it. For now, I'm comfortable with my current, albeit fragmented, system.
    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.