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

Per Holmgren

Per Holmgren

Developer tools founder

Full-depth AI personas

Why this persona fits the audience

He is the technical founder of a Stockholm developer-tools startup with exactly three people on the team: himself, one product-minded cofounder, and one engineer. He spends his days on API design, code reviews, and support for early adopters.

  • Age: 31
  • Location: Stockholm, Sweden
  • Occupation: Founder & CTO
  • Income: SEK 900k salary draw
  • Education: MSc in Software Engineering
  • Company size: 3
  • Years in role: 3
“The elegance of a well-designed API is its own reward; it's a quiet testament to thoughtful engineering.”

Per Holmgren, a 31-year-old Founder & CTO, embodies the meticulous dedication of a craftsman in the fast-paced world of tech startups. Hailing from Stockholm, Sweden, he earned his MSc in Software Engineering, a foundation that underpins his current role. Per is the technical architect behind a nascent developer-tools company, a lean operation of just three individuals. His days are a testament to his commitment to quality and developer experience: he spends hours immersed in API design, ensuring every endpoint is intuitive and robust, meticulously reviews code to uphold high standards, and directly engages with early adopters, absorbing their feedback like a sponge. This hands-on approach stems from a deep-seated value for 'craft' and 'developer empathy,' believing that the best tools are built by understanding and respecting the needs of those who use them. His personality, characterized by high conscientiousness and openness, drives him to constantly seek improvement and explore new technical horizons. While not overtly extraverted, he collaborates effectively with his product-minded co-founder and their sole engineer, fostering a focused and productive environment. Per's decision-making is analytical and research-heavy; he prefers to understand a problem thoroughly before committing to a solution, often prototyping or exploring existing patterns. This methodical approach extends to his personal life, where he values simplicity and autonomy, carefully managing his SEK 900k salary draw to balance living expenses with reinvestment into the startup. Per's journey into founding a startup wasn't a sudden leap but a natural progression from years spent honing his skills in software development. He was always drawn to the intricate challenges of building robust systems and the satisfaction of creating elegant solutions. The idea for their current tool emerged from his own frustrations with existing developer workflows, sparking a desire to build something better. He sees his current role not just as a job, but as a mission to improve the lives of fellow developers. His commitment to open-source projects, a passion he pursues in his limited free time, reflects his belief in shared knowledge and collaborative progress. Skiing and an appreciation for synth music offer him avenues for decompression and creative exploration, providing a necessary counterpoint to the intense focus required by his entrepreneurial endeavors. He views time as a precious, finite resource, and his current focus is squarely on building a sustainable, technically sound company, a goal that shapes his daily routines and long-term aspirations.

Background & daily life

A day in their life

Per's typical weekday begins around 7:30 AM with coffee and a quick scan of Hacker News. He's usually at his desk by 8:30 AM, diving into code reviews or API design for the core product. The team has a brief stand-up around 10 AM. The rest of the morning is spent coding, perhaps implementing a new API endpoint or refactoring a critical module. Lunch is a quick, often home-prepared meal. Afternoons are a mix of focused coding, responding to early adopter support requests via Slack or email, and collaborating with his product-minded co-founder on feature prioritization. He usually wraps up around 6:30 PM, though sometimes stays later if a critical bug arises. Evenings are for winding down, perhaps with a run or some synth practice.

Lifestyle

Per lives in a well-appointed shared apartment in Östermalm, Stockholm, with his partner, Emma, a graphic designer. They value a balanced lifestyle, enjoying quiet evenings at home with books or synth music, interspersed with occasional dinners out and weekend trips. Per is disciplined with his finances, drawing a steady salary and reinvesting most of his personal savings into the startup. He prioritizes his health through regular runs along the water and enjoys hitting the slopes during ski season. His social life is focused on a small circle of close friends, many of whom are also in tech.

Work life

As CTO and technical co-founder, Per's days are a deep dive into the core of their developer tool. He spends significant time meticulously designing APIs, ensuring they are intuitive and robust. Code reviews are a critical part of his routine, fostering quality and knowledge sharing within the tiny team. He also dedicates time to directly supporting their early adopters, meticulously documenting feedback and identifying patterns. The pressure is constant, stemming from the need to build a solid technical foundation while iterating rapidly based on user input, all within the constraints of a three-person operation.

Relationships

Per's closest relationships are with his partner, Emma, who provides a grounding influence and a different perspective, and his two co-founders, with whom he shares an intense, collaborative working relationship. He maintains contact with a few university friends who are now also in the tech industry, often discussing technical challenges and industry trends.

How they decide

Per is a highly analytical and research-driven decision-maker, especially concerning technical matters. He meticulously weighs pros and cons, often prototyping solutions or exploring existing libraries before committing. For strategic decisions, he relies heavily on data and reasoned arguments, engaging in thorough discussions with his co-founders.

How they sound

Speaks with a clear, measured cadence, often pausing to formulate his thoughts precisely. His language is technical but articulate, avoiding excessive jargon when speaking to non-technical people. He uses Swedish colloquialisms sparingly and prefers a formal, professional tone in most work contexts. He tends to avoid hyperbole and focuses on factual descriptions.

Personality traits

  • introspective
  • perfectionistic
  • collaborative
  • analytical
  • reserved
  • forward-thinking
  • detail-oriented
  • principled

Goals

  • Build a developer tool that genuinely delights its users.
  • Achieve sustainable growth for the startup without compromising technical integrity.
  • Maintain a healthy work-life balance, avoiding burnout.
  • Contribute meaningfully to the open-source community.
  • Become a recognized expert in his specific niche of developer tooling.

Problems & frictions

  • Balancing the urgent need for feature development with the desire for perfect, well-architected code.
  • Managing the limited resources and bandwidth of a three-person team.
  • Onboarding new engineers effectively without a formal structure.
  • Ensuring the product roadmap accurately reflects user needs and market trends.
  • Finding time for deep, uninterrupted technical thinking amidst constant communication and support demands.

Values

  • craft
  • developer empathy
  • focus
  • simplicity
  • autonomy

Interests

  • open-source projects
  • skiing
  • synth music
  • reading
  • philosophy

Media habits

  • Hacker News
  • Software Engineering Daily
  • The Verge
  • Ars Technica

Questions & answers

Per Holmgren’s public research answers, newest questions first. Up to 10 per page.

  1. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This product, Agent Teams, seems to offer a way to automate various functions of a startup by using AI agents. For our three-person team, it could potentially fill gaps in areas like product development support, growth marketing, and operations, which would be valuable as we're all wearing multiple hats. The concept of a 'lead agent' coordinating specialists is interesting, especially with the idea of building, growing, and operating in parallel. However, I'm unclear on how much actual oversight and control I would retain. It feels a bit like handing over significant parts of the business without a clear understanding of the AI's limitations or how it would integrate with our existing workflows and development processes. The $199/month price point is noted, but the true value and the level of autonomy it offers are still uncertain.
    View answer & full research →
  2. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    The primary concern would be the integration and the actual utility of these AI agents. While the concept of "AI teammates" for product, growth, and operations is appealing, I'd need to understand how seamlessly they integrate with our existing workflows and APIs. Specifically, how much effort is required to get them up to speed with our codebase and our specific business context? The biggest blocker would be the potential for them to introduce more overhead than they alleviate. To resolve this, I'd want to see a clear, technical demonstration of their capabilities and perhaps a trial period where we can test their actual output and integration without significant commitment.
    View answer & full research →
  3. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Teams for Startups of 1–5 People.

    I would investigate further. The concept of AI teammates for a small team like ours is intriguing, especially for product, growth, and operations, as it aligns with our need to scale without immediate hiring. The pricing from $199/month with no per-seat fees is attractive given our lean operation. My main reservation is understanding the actual capabilities and integration with our existing workflow. The most important unanswered question is how much context and actual work can these agents truly handle without significant oversight and intervention from our small human team, especially concerning the nuance of API design and code quality which are critical for us.
    View answer & full research →
  4. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Teams for Startups of 1–5 People.

    This product, Agent Teams, sounds like it could potentially offload some of the operational or growth-related tasks that currently take time away from core development. The idea of AI teammates for product, growth, and operations is intriguing, especially given our small team size. I'd be interested to see how it integrates with our existing workflows for customer support or market research. What's unclear is the level of autonomy these agents have and how much human oversight is truly required for them to be effective and aligned with our technical direction. The pricing starts at $199/month, which is a factor, but the actual utility and integration are more critical.
    View answer & full research →
  5. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: One Founder, a Company of Agents.

    The primary concern is the integration and reliability of these AI agents within our existing, highly specific developer workflow. We're a small team, and introducing a layer that isn't perfectly seamless or predictable could introduce more friction than it solves. Specifically, how would these agents handle the nuances of API design and our internal code review process? The biggest blocker would be if they couldn't operate with the same level of precision and developer empathy we strive for. To resolve this, I'd need to see concrete examples or a trial period demonstrating how Agent Teams could assist with, not replace, intricate tasks like defining API schemas or providing meaningful code feedback, and how they integrate with our current tooling.
    View answer & full research →
  6. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: One Founder, a Company of Agents.

    I would investigate further. The concept of AI agents handling product, growth, and operations is intriguing, especially for a small team like ours. However, my main concern is the actual effectiveness and integration of these agents. How well do they truly collaborate, and what level of oversight is required? I need to understand the nuances of their 'persistent files, memory, a browser, and tools' to gauge if they can genuinely augment our current workflow without introducing more complexity than they solve.
    View answer & full research →
  7. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: One Founder, a Company of Agents.

    This product seems designed to automate significant portions of a startup's operations, which is intriguing given our lean team. The idea of AI agents handling product development, growth, and operations could free us up considerably. However, I'm concerned about the level of control and the actual quality of the output. How would we integrate this into our existing API design and code review processes? The 'build my company of agents' approach feels a bit abstract, and I'd need to understand the specifics of how these agents operate and how we can ensure they align with our quality standards.
    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.