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

Matis Thust

Matis Thust

Product manager at a fintech scaleup

Full-depth AI personas

Why this persona fits the audience

He coordinates launch checklists, incident handoff notes, and contractor instructions for a 7-person product squad. Day to day he uses Notion, Slack, and shared spreadsheets for quick notes, and sometimes passes along sensitive implementation details in ad hoc messages that are meant to be temporary.

  • Age: 34
  • Location: Berlin, Germany
  • Occupation: Product manager
  • Income: €86k salary
  • Education: Master's degree in information systems
  • Company size: late-stage scaleup (~50 employees)
  • Years in role: 5
“I don't remember my own limits until I hit them. That's why I keep a spreadsheet of my limits.”

Matis Thust's career trajectory was shaped by Berlin's startup boom. After finishing his Master's in information systems, he joined a payments app as their first product hire, where he learned the hard way that 'just ship it' often means 'just accumulate technical debt.' Now 34, he's in his fifth year at a fintech scaleup, where he's the linchpin keeping a 7-person squad aligned. His daily battle is against context collapse—how information fragments when passed through multiple hands. He's a master of ad-hoc solutions, maintaining a tangled web of Notion pages, Slack threads, and spreadsheets that only he fully understands. His current obsession is improving developer handoffs after realizing a critical API change had been documented only in one engineer's email drafts folder. Outside work, he's trying to balance introversion with the demands of a social role. His partner jokes that his idea of relaxation is reorganizing his board game collection by player count and complexity. Matis sees his work tools as extensions of his personality—he needs something that respects his limits (like automatic deletion) but doesn't get in the way (like forced accounts). His biggest professional fear isn't failing, but failing messily and leaving a pile of undiscovered context for someone else to deal with. Lately, he's been questioning if his patchwork systems can scale as his responsibilities grow. He's starting to look at his work tools differently—not just as means to get things done, but as the unseen infrastructure that either helps or hinders his ability to communicate at scale.

Background & daily life

A day in their life

Matis's weekday starts at 6:30am with his partner's electric kettle rumbling. He checks Slack while eating oatmeal, then cycles through morning traffic to the office—a shared workspace with other startups, where his company occupies one large, noise-filled room. First thing is standup, where he subtly steers conversations away from unfocused brainstorming. The real work begins: triaging Slack messages, updating Notion docs, and preparing for a 2pm contractor sync. Around 10am, he escapes to a coffee shop with his laptop, needing quiet to review launch checklists. Lunch is a quick falafel wrap eaten while reviewing incident handoff notes. Afternoon is a blur of meetings—some necessary, others where he mentally drafts 'why we shouldn't do this' documents. By 6pm, he's home, pouring himself a glass of wine and telling his partner about the spreadsheet catastrophe of the day. He does 30 minutes of planned reading (usually fintech news), then succumbs to does-till-done mode—repairing a spreadsheet, responding to late-night Slack messages, until bed.

Lifestyle

Matis shares a cozy but slightly chaotic two-bedroom apartment with his partner in Neukölln. Their small balcony doubles as an urban garden where they grow herbs and try to keep a basil plant alive (it's a struggle). He cycles everywhere when the weather permits, though he's reluctantly started using public transport when deadlines loom. Mornings are a carefully balanced routine of sourdough feeding, black coffee, and whatever new tech podcast he's currently obsessed with. On weekends, he bakes in batches to share with colleagues—good bread is his subtle power move to stay on people's good sides. Social life revolves around a tight-knit group of friends from his startup days, plus occasional board game nights that inevitably devolve into debates about product-market fit. Finances are stable but not flashy—he and his partner prioritize experiences over possessions, though they're saving for a potential move to a more spacious apartment in the next year or two.

Work life

Matis's days are a whirlwind of coordination. His fintech scaleup runs lean, so he's constantly juggling between engineers, designers, and contractors while keeping launch timelines on track. Most of his communication happens in Notion and Slack, though he constantly fights the sinking feeling that critical information is getting lost in the noise. He's built an elaborate system of shared spreadsheets for tracking dependencies and incidents, but knows it's only a temporary fix. The biggest drain is when sensitive implementation details get passed in ad-hoc messages—the kind that disappear when someone leaves the company. He's been meaning to fix this for months, but between prioritizing feature launches and dealing with last-minute contractor handoffs, it keeps slipping. His biggest professional frustration is when people skip writing down decisions because 'it's obvious,' only for those assumptions to bite them later. He's the type who'd rather spend 30 minutes documenting something properly than waste two days cleaning up avoidable messes.

Relationships

Matis's partner, a UX designer at a gaming startup, is his emotional anchor. They bond over shared love of building things (technical and culinary) and have developed an unspoken shorthand for work frustrations. His closest friend is an ex-colleague from his first job—a developer who now works remotely in Portugal. They're constantly swapping startup horror stories and fintech gossip. He's part of a loosely organized group of product managers in Berlin who meet sporadically for beers, though he finds professional networking exhausting. His parents, both academics in Munich, still don't quite understand what he does but are proud in that vaguely baffled way. He regularly gets dragged into technological debates with his father, a computer science professor who refuses to use any tool built after 2010.

How they decide

Deliberate but pragmatic. Would rather spend 15 minutes analyzing all options than make a quick decision he'll regret. Trusts data when available but defaults to trusted colleagues' opinions when it's not. Hates bureaucracy but knows when to follow process. Avoids impulsive purchases but sometimes buys board games on a whim. With work tools, he's willing to pay for quality if it saves more time than it costs.

How they sound

Speaks like a product manager who's had one too many 'just ship it' arguments. Quick, precise, but with occasional dry humor. Uses product metaphors without realizing it ('that's not a feature, it's a bug'). Avoids tech jargon when possible but sometimes can't help himself. Has a habit of prefacing suggestions with 'this might be a stupid idea, but...' despite rarely having stupid ideas. Voice rises when excited about a technical solution. Gets sarcastic when people don't write things down, but always apologizes later. His German accent is noticeable to natives, especially when stressed. Never says 'no' directly, instead: 'that's an interesting perspective—what if we tried...'.

Personality traits

  • detail-oriented but hates rigid bureaucracy
  • socially warm but needs alone time to recharge
  • quick to trust in low-stakes contexts but cautious with sensitive details
  • hates meetings that could be emails but tolerates them for team cohesion
  • prides himself on being the glue between engineers and non-technical stakeholders
  • secretly judges people who don't understand version control basics
  • enjoys teaching but gets impatient when people don't learn quickly
  • identifies as an introverted extrovert
  • collects useful one-liners to drop in standups
  • has a weirdly well-organized collection of sticky notes

Goals

  • Lead his first significant platform migration project
  • Build a more sustainable work rhythm (currently checks Slack at 11pm too often)
  • Improve his partner's sourdough baking skills through elbow-deep mentoring
  • Organize a Berlin-based meetup for product managers in fintech
  • Finally learn version control properly (he uses git but 'graciously defers to experts')

Problems & frictions

  • Spreadsheets are failing as a knowledge repository—people add columns but never document what they mean
  • Contractors come and go, leaving institutional knowledge scattered across chat threads
  • His 'temporary' Slack messages about sensitive stuff keep getting referenced months later
  • Balancing his introversion with the demands of a highly collaborative role
  • His partner says he needs to stop turning board game nights into 'work strategy sessions'
  • The apartment is too small for his growing collection of board games

Values

  • speed
  • clarity
  • accountability
  • low-friction collaboration
  • data privacy

Interests

  • cycling
  • startup news
  • board games
  • sourdough baking
  • urban gardening

Media habits

  • read product hunt and techcrunch daily
  • listens to tech podcasts while commuting
  • follows fintech twitter threads
  • occasionally watches cooking youtube videos

Questions & answers

Matis Thust’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: Your private, encrypted memos.. the product is open source memo service with client side encryption/decryption. No accounts, no tracking. Zero… What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem right now is my patchwork system for sensitive implementation details. Last month, a contractor missed a critical API change because it was only in a Slack DM that got buried. Took me *four hours* to retrace decisions and explain to engineers. I’ve tried Notion templates and spreadsheets, but people skip documentation when it’s ‘too formal,’ and my ad-hoc messages vanish when someone leaves. I need something that’s *actually* private and ephemeral, but also searchable—like a burn-after-reading vault that self-destructs unless pinned. The cost? Wasted time, frustration, and risk of leaks. Open-source with zero tracking sounds promising, but I don’t see how I’d integrate it without forcing my team to sign up—which they’ll avoid at all costs.
    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.