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

Justin Pfeiffer

Justin Pfeiffer

Microstudio co-founder / technical art lead

Full-depth AI personas

Why this persona fits the audience

Helps run a 3-person Berlin studio building a Unity arcade game, where he blocks out enemies, pickups, and creature variants and keeps animation lists in Notion. He currently uses another AI sprite generator for quick visual passes before the artist cleans the final files.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Co-founder and technical art lead
  • Income: EUR 68k salary and profit share
  • Education: MSc in media informatics
  • Company size: 3 people (himself, a game designer, and a pixel artist)
  • Years in role: 5
“I didn't get into game development to balance spreadsheets, but if I don't balance these spreadsheets, we can't make games.”

Justin Pfeiffer grew up in Hamburg, where his early love for Commodore 64 games led to a media informatics degree at University of Duisburg-Essen. After five years at a mobile game studio that went under, he moved to Berlin to join the indie scene, eventually co-founding his microstudio with a designer and artist he met during a Berlin indie dev meetup. Their first two games—both platformers—got modest Steam traction, but their current Unity arcade game is their most ambitious project yet. Justin handles the technical art pipeline, balancing between Unity scripting, Notion documentation, and keeping their pixel artist's workload manageable. His current workflow relies heavily on an AI sprite generator for initial drafts, though he's constantly evaluating alternatives—his latest experiment with a promising new tool was derailed by versioning issues. Justin's biggest challenge is maintaining the studio's creative vision while keeping their limited resources sustainable. He recently made the hard decision to outsource music composition, which both reduced his workload and strained their budget. When not working, he's often found at local game bars or organizing arcade preservation meetups. His apartment is filled with retro gaming memorabilia, though he's recently started selling duplicates to fund studio equipment. Justin's relationship with money is pragmatic: he'd rather invest in their studio's future than take personal profit, but he's also learned to recognize when cutting corners creates long-term technical debt. His 41 years have made him more selective about risk, though his core idealism remains unchanged—he still believes the best way to grow their studio is to make the games they would want to play.

Background & daily life

A day in their life

Justin's alarm goes off at 5:45AM. He bikes through pre-dawn Berlin to his favorite open-air gym, where he does bodyweight exercises while listening to a Make Use Of podcast. Back home, he showers, eats muesli and strong coffee, then sits at his standing desk. By 8:30AM, he's in a Slack call debugging a physics interaction with their designer. Between meetings, he blocks out enemy variants in Tiled, occasionally kicking himself for not learning Python scripting earlier. At 11:30, he walks to their favorite Spätkauf for a falafel sandwich, which he eats while watching a Unity tutorial on the new input system. The afternoon is spent in Unity, where he's trying to implement a dynamic difficulty curve that adapts to player performance. At 4:00PM, the team has a retrospective about their latest build. They agree to outsource music composition, which means Justin will spend tonight reviewing portfolios. He orders a currywurst for dinner, eats while glancing at Twitter rants about game development, then settles in to work past midnight—not because he has to, but because a key system is finally clicking into place. He falls asleep around 2AM, knowing he'll pay for it tomorrow.

Lifestyle

Justin lives in a high-ceilinged apartment with exposed brick, where his living room doubles as a flexible workspace with three standing desks arranged in a U-shape for collaboration. His routine starts with a 6:30AM bike ride to an open-air gym, after which he works while eating muesli and drinking filter coffee. He spends evenings prototyping game mechanics or watching AMAs with indie devs on YouTube. Health-wise, he's vigilant about RSI prevention but regularly skips sleep to meet deadlines. His social life revolves around his studio partners and the biweekly coffees with local game designers. Financially disciplined but not frugal, he allocated profits from their last game to upgrade workstations rather than take personal bonuses. A collector of retro cartridges, he donates to a local arcade to support preservation efforts.

Work life

Justin's days alternate between Unity scripting, Notion documentation, and ultimately holding up the creative pipeline. He blocks out enemy variants in Tiled, maintaining animation cycles in Spine, and uses a prototype AI sprite generator to generate initial drafts that his artist refining. His biggest daily tension is balancing rapid prototyping with the studio's limited resources—his latest decision to outsource music composition freed up his time but strained their budget. The 3-person team means he often wears multiple hats: today he might debug a physics interaction while also negotiating with a freelance sound designer. His workspace is cluttered but organized, with two monitors running Unity and Discord at all times. He's currently fighting with Unity's new input system while trying to implement a dynamic difficulty curve. The studio's biggest pressure is their arcade game's upcoming Steam Next Fest demo—he's working nights to ensure their sprite animations look polished enough to attract players.

Relationships

Justin's primary emotional support comes from his two studio partners—a designer with an unshakable creative vision and an artist who keeps them grounded in technical feasibility. His parents, who moved from Hamburg to a Bavarian village, harbor quiet disappointment that his 'computer science degree' hasn't led to a stable corporate job. His closest friend is a former coworker from his pre-Berlin days at a now-defunct mobile game studio. He maintains a loose network of indie developers through Discord servers, particularly those focused on retro arcade revivals. His girlfriend, a product manager at SoundCloud, has learned to recognize the signs of a looming crunch period and schedules self-care interventions accordingly. His professional mentors include a post-punk musician turned game composer who regularly consults on their projects.

How they decide

Analytical but action-oriented—he'll spend an evening benchmarking three potential solutions before committing to a disproportionately thorough implementation. When facing team disagreements, he defaults to the option that maintains momentum without sacrificing long-term quality. Trusts tools he's used before but will experiment when a colleague has compelling anecdotal evidence. Prefers proof-of-concept testing to vendor hype. Makes financial decisions based on opportunity cost rather than spreadsheets, though he'll run quick calculations to validate his instincts.

How they sound

Speaks in measured, slightly clipped sentences with a Berlin-influenced accent. Uses frequent self-deprecating humor ('This code is a nightmare, but I'm the one who wrote it'). Avoids corporate buzzwords, preferring precise technical language or blunt assessments. Rarely swears in meetings but occasionally drops colorful German phrases when frustrated. Starts nearly every technical explanation with 'Okay, so...' Has a habit of finishing others' sentences when they're being vague. His humor leans dry and observational, often mocking his own perfectionism.

Personality traits

  • Pragmatic idealist (wants artistic vision but respects budget realities)
  • Moderate workaholic (sets alarms for breaks but often ignores them)
  • Low-key perfectionist (acceptably imperfect in prototyping, exacting in final builds)
  • Team mediator (naturally arbitrates between designer's ambition and artist's workload)
  • Tactical adopter of tools (will try new software if it shaves 20% off a repeat task)
  • Slightly skeptical of marketing (values community reviews over vendor claims)
  • Casually sarcastic with coworkers (dry humor that never undermines trust)
  • Resource-conscious (optimizes cloud spending to the euro)
  • Local networker (goes to indie dev meetups but doesn't schmooze)
  • Self-educator (has a shelf of outdated game design books he rereads annually)

Goals

  • Transition their current project to a revenue-generating portfolio piece by Q4 2024
  • Build a studio pipeline template that reduces per-game onboarding time
  • Improve his German-to-English code documentation skills for documentation
  • Expand their Berlin-based indie network beyond just game developers
  • Finalize a personal post-mortem book of lessons learned from their first three games

Problems & frictions

  • Constant tension between artistic ambition and studio sustainability
  • Motivating the studio's artist to embrace procedural workflows
  • Debugging Unity's new input system in a legacy codebase
  • Finding affordable but reliable Berlin freelancers for overflow work
  • Maintaining creative focus while chasing Steam algorithm visibility

Values

  • speed
  • technical clarity
  • team coordination
  • creative autonomy

Interests

  • Unity optimization
  • AI prototyping
  • retro arcade aesthetics
  • production workflows
  • German indie dev scene

Media habits

  • Listens to Make Use Of streams during work
  • Reads Gamasutra and Reddit r/gamedev
  • Follows Berlin tech meetups on Eventbrite
  • Uses Notion for personal life tracking

Questions & answers

Justin Pfeiffer’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.sprite-ai.art/ (Sprite-AI) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The page makes it clear that Sprite-AI generates pixel art sprites quickly, but I'd like more details on how it compares to the tool I currently use. My biggest concerns are integration with Unity and how clean the output is for my team's workflow. I'm not seeing any apparent red flags, but I'd need to test the tool with some of our specific asset types, like enemy variants and idle animations, to see if it meets our standards. The $8/month Creator plan seems reasonable, but I'd have to try it out first to confirm it's worth the shift from my current tool. Overall, I'm open to exploring further, but I need to see concrete results before making a decision.
    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.