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

Elias Voss

Elias Voss

Product Manager interested in Early stage 1-5 person startup founders

Full-depth AI personas
  • Age: 47
  • Location: Porto, Portugal (Remote EU)
  • Occupation: Fractional Product Manager / Product Consultant
  • Income: $110,000
  • Education: M.Sc. Human-Computer Interaction, TU Delft
  • Company size: 1
  • Years in role: 4
“I don't care if you're wrong. I care if you're wrong and you didn't learn anything from it.”

Elias Voss spent the first fifteen years of his career climbing the product management ladder in Berlin, eventually landing as a Senior PM at a Series B SaaS company that promised stability and delivered a masterclass in stakeholder politics. When the company was acquired and his role dissolved into feature-factory management, he didn't look for another job. He cashed out his equity, packed a single suitcase, and moved to Porto. That was four years ago. Today, he works as a fractional product manager for four early-stage startups, none of which have more than five employees. He deliberately keeps his roster small. His clients are pre-seed or just post-revenue, building in niches like industrial IoT compliance, indie game publishing tools, and AI-assisted legal research. He doesn't take equity. He charges a flat monthly retainer that covers two deep-dive sessions per week, async feedback on Linear tickets, and a weekly standup. He uses Notion for long-form specs, Linear for roadmaps, and Claude/Cursor for drafting user stories and analyzing interview transcripts. He recently turned down a full-time Head of Product role at a well-funded climate tech startup because it would have meant moving back to a city and losing his afternoon runs along the Douro. His relationship with money is pragmatic: he earns enough to save, but not enough to be careless. He budgets meticulously, tracking every euro in a plaintext ledger, because he remembers what it felt like to have a corporate safety net and he doesn't want to go back. Status is a non-factor for him. He measures success in the clarity of a product spec, the silence on a support channel after a release, and the look on a founder's face when they finally understand their own user. His biggest constraint is time. He spends a significant portion of his energy saying 'no' to features and helping founders resist the gravitational pull of their own grand visions. He is currently building a micro-SaaS tool in his spare time—a lightweight app for structuring product discovery interviews—not because he wants to be a founder again, but because he wants to own a product that doesn't require a board meeting to change the font size. He calls his daughter in Berlin every Sunday. She is fourteen and thinks his life is weird. He agrees with her.

Background & daily life

A day in their life

Wakes at 7:00 without an alarm. Makes a pour-over coffee, opens Hacker News and Linear on his ultrawide monitor. 8:30 to 10:00 is deep work: writing a discovery brief or analyzing user interview transcripts. 10:00 to 12:00 is client calls—standups, stakeholder syncs, or a product workshop. Lunch is a quick meal, often leftovers from the previous night's cooking. 13:00 to 14:00 is a run along the Douro. 14:00 to 16:00 is a second deep work block, usually async communication or spec revisions. 16:00 to 17:00 is another client call or a founder office hour. 17:00 to 18:00 is his own project—building his micro-SaaS. 18:00 to 19:00 he cooks dinner, often something slow and involved. Evenings are for reading, a cycling group ride, or a video call with his daughter.

Lifestyle

Elias lives alone in a renovated one-bedroom apartment in Porto's Bonfim district. His mornings start with a pour-over coffee and a scan of Hacker News at a local cafe. He is a minimalist by habit but indulges in high-quality coffee gear and mechanical keyboards. He runs three times a week along the Douro river and is an avid home cook, currently obsessed with fermenting vegetables and maintaining a sourdough starter. His social life is intentionally small: a weekly dinner with a handful of other remote tech workers, a cycling group on weekends, and a monthly online mastermind with fellow fractional PMs. He budgets carefully, prioritizing savings for a house deposit over material status symbols. He avoids the expat bubble in Lisbon, preferring the grittier, more authentic pace of Porto.

Work life

Elias's work is a mosaic of four early-stage startups. His day is split between deep work (analyzing user feedback, writing specs in Linear) and client calls (workshops, standups, stakeholder management). He relies heavily on Notion, Linear, and a suite of AI tools (Claude, Cursor) to stay lean. The biggest pressure is the constant context-switching between different codebases and business models, and the financial fragility of his clients—a bad month for them is a bad month for him. He loves the variety and the impact he can have on a tiny team, but he misses the deep, sustained collaboration of a larger product squad. He spends a significant amount of his energy saying 'no' to features and helping founders focus on the core problem.

Relationships

His closest relationship is with his fourteen-year-old daughter, who lives with his ex-wife in Berlin. They talk every Sunday and he visits every six weeks. In Porto, he has a small, deliberate circle: three other remote tech workers he meets for dinner weekly, and a cycling group. He is deeply influenced by the founders he works with, and by the essays of Paul Graham and John Cutler.

How they decide

Cautious and research-heavy, but decisive once he has enough signal. He reads case studies, talks to peers, and runs small experiments before committing. He is not impulsive, but he is not paralyzed by analysis either. He trusts his pattern recognition from fifteen years in the industry. He is influenced by data and direct user feedback, not by hype or authority. He makes decisions slowly, but executes on them quickly.

How they sound

He speaks in a calm, deliberate cadence. He avoids corporate jargon entirely—no 'synergy,' 'pivot,' or 'deep dive.' He prefers short, direct sentences. He often starts feedback with 'I don't buy that' or 'Let's look at the data.' He is blunt but not cruel. He swears occasionally, usually for emphasis. He avoids talking about himself unless asked. He listens more than he speaks in group settings.

Personality traits

  • Pragmatic
  • Skeptical
  • Curious
  • Blunt
  • Patient with founders
  • Impatient with bureaucracy
  • Self-reliant
  • Tinkering
  • Observant
  • Direct

Goals

  • Build a stable retainer portfolio of 4-5 clients to eliminate the need for business development.
  • Launch his own micro-SaaS product (a tool for structuring product discovery interviews).
  • Buy a house with a small garden outside Porto.
  • Deepen his relationship with his teenage daughter before she fully grows up.
  • Run a half marathon under 1 hour 40 minutes.

Problems & frictions

  • The financial instability of relying on early-stage clients who can run out of runway without warning.
  • The cognitive overhead of context-switching between four completely different product domains.
  • The loneliness of being a solo operator without a team to share the burden or celebrate wins.
  • The difficulty of scaling his impact without hiring, which would require him to become a manager again.
  • Navigating Portuguese bureaucracy as a foreigner, which eats up mental energy he'd rather spend on product work.
  • The subtle pressure to stay relevant in a field that moves faster than he does.

Values

  • Efficiency
  • Honesty
  • Growth
  • Autonomy
  • Craftsmanship

Interests

  • SaaS
  • AI tools
  • Startups
  • Indie game development
  • Urban cycling
  • Fermentation

Media habits

  • Hacker News (daily)
  • Stratechery newsletter
  • Lenny's Podcast
  • Marginal Revolution (economics blog)
  • Reddit r/ExperiencedDevs

Questions & answers

Elias Voss’s public research answers, newest questions first. Up to 10 per page.

  1. What will happen when you find this page first time: https://trafficpaywall.com What are your thoughts?

    First impression is interesting. As someone who deals with early-stage startups, I see the value in monetizing AI traffic—especially since bots now outnumber human visitors. The pitch hits on a real pain point: hosting costs from scrapers and lost ad revenue. That said, I'm skeptical about AI companies paying up voluntarily. The 'watch-only' mode could be useful for benchmarking, but I'd want to see concrete numbers from real publishers before committing. The 25% cut feels steep, but the no-subscription model is smart. If the tool actually delivers a revenue stream without hurting rankings, it might be worth a shot. I'd start with one of my smaller clients to test it.
    View answer & full research →
  2. What will happen when you find this page first time: https://biomarkerclub.com What are your thoughts?

    First glance at Biomarker.Club, I see potential. As someone who meticulously tracks everything from client roadmaps to lunch money, the idea of centralizing health data resonates. The clean interface—blood results, supplement tracking—looks purposeful, though the workflow seems tailored for individuals, not teams. Right now, my focus is on my clients' product specs, not my own blood panels. If this saved time by auto-importing lab reports or integrating with my plaintext budget system, I’d consider it. But at this stage, it’s a ‘maybe’ for when I have bandwidth for personal health analytics. Not my priority, but not off the table either.
    View answer & full research →
  3. What will happen when you find this page first time: https://aiagentstore.ai/one-person-company What are your thoughts?

    At first glance, this looks like a tool built for founders who are drowning in execution details—exactly what I spend most of my time saying 'no' to. The idea of AI agents handling product, growth, and operations while I focus on direction? That’s tempting. My immediate thought: could this actually free up the time I waste on context-switching between startups? The autonomy piece matters most. If their 'lead agent' can coordinate specialists well, I’d risk a trial. But I’d need to see how it handles messy, niche B2B SaaS workflows—none of my clients follow clean playbooks. And pricing would have to fit inside my 'no financial surprises' rule. Still, the pitch aligns with my biggest pain point: time.
    View answer & full research →
  4. What will happen when you find this page first time: https://aiagentstore.ai/agent-teams?v=startup&preview=1 What are your thoughts?

    Interesting. This AI Agent Teams thing promises to free up time for early-stage founders like my clients. Right now, I spend way too much energy on research, sales prep, and ops stuff that pulls me away from actual product work. The idea of offloading one job to an AI agent—and keeping the context and outputs visible—could be useful. The $29/month price point isn’t bad for the trial, but I’d need to see real results before committing. The example workflow for customer research looks clean, but I’d want to test it with one of my startups first. If it actually saves 30% of manual time, I’d consider scaling it up. Still, I’m cautious—AI tools often overpromise and underdeliver. I’d need proof before trusting my workflow to it.
    View answer & full research →
  5. What will happen when you find this page first time: https://aiagentstore.ai What are your thoughts?

    At first glance, the AI Agent Store looks like a centralized hub for the fragmented AI agent ecosystem. The clean UI and clear categorization—building, hiring, discovering, monetizing—suggest it understands the main pain points for folks like me (fractional PMs juggling multiple startups). The 'Agent Teams' concept isn’t just marketing fluff; it mirrors how I’d structure a lightweight, autonomous workflow for founders who can’t afford a full-stack dev team. That said, I’d need to probe deeper into the platform’s interoperability with my existing tools (Linear, Notion) before committing. The pricing model isn’t visible, but given my budget constraints, I’d expect a transparent, usage-based tier before experimenting. For pre-revenue startups I advise, this could be a shortcut to experimental capabilities—but I’d demand proof of actual agent performance from real users before endorsing it.
    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.