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

Bryan Ihly

Bryan Ihly

Agency co-owner and technical director at a 6-person web-and-automation shop

Full-depth AI personas

Why this persona fits the audience

Co-owns a 6-person web-and-automation agency in Berlin; he scopes client dashboards in spreadsheets, then uses a paid Figma component library alongside Cursor and free-tier AI builders to produce first-pass UI for clients. He reviews the output himself before it goes to a contractor or in-house developer.

  • Age: 44
  • Location: Berlin, Germany
  • Occupation: Technical Director / Co-owner
  • Income: €92k owner income
  • Education: Diploma in media informatics
  • Company size: 6
  • Years in role: 8
“'The best clients are the ones who trust my spreadsheets more than they trust their own requirements documents.'”

Bryan Ihly cut his teeth building university portals in the early 2000s, which gave him both a distaste for academic debates about 'best practices' and a lifetime supply of 'weird but necessary' automation scripts. After a 5-year stint in Munich running a digital agency's dev team, he co-founded his current Berlin shop with an ex-colleague who handled the front-end while Bryan focused on back-end automation. The business model took shape around his discovery that most small clients couldn't articulate their needs beyond 'needs to look professional,' which aligned perfectly with his spreadsheet-first approach. His current workflow—scoping in spreadsheets, generating UI drafts with AI tools, then doing human oversight—emerged organically after a failed experiment with outsourcing design work. A perfectionist by nature, Bryan had to consciously train himself to accept 'good enough' UI outputs, recognizing that his clients would inevitably want changes anyway. The agency's no-designer model works because Bryan's media informatics background lets him bridge technical and design conversations, though he admits to feeling like a 'fraud' whenever UX is discussed. His recent decision to adopt Cursor came after calculating that the time saved reviewing AI outputs justified the subscription cost, especially when compared to the opportunity cost of his own time. The Berlin tech scene has given him a network of peers who share his pragmatic approach, though he finds himself increasingly frustrated by the city's rising costs pushing out the very small businesses he built his practice serving. His side hustle selling mid-century lamps stems from the same mentality as his agency work—finding value in things others have dismissed as outdated but functional.

Background & daily life

A day in their life

Bryan's weekday begins with a 6:30am ride followed by espresso in his sunlit kitchen while scanning Smashing Magazine's newsletter. By 8:30 he's in the agency's coworking space reviewing yesterday's AI-generated dashboard variations, marking up specific interactivity issues in his 'review color' (a specific shade of violet). The 10am client call finds him explaining why their subscription tracking needs a CSV export, not just a live dashboard. After lunch (taken alone while watching no-code tool tutorials), he's in deep spreadsheet mode mapping out the new client's requirements, color-coding edge cases in his system. The afternoon usually involves mentoring the junior dev through a complex build while fielding his co-owner's questions about project timelines. By 6pm he's commuting home to cook in batches and answer client emails about 'just one more feature.' He ends the day watching anime with his partner, 'for the UI mockups.'

Lifestyle

Bryan lives in a 90m² Altbau with exposed brick and a south-facing windowsill that holds his espresso machine and 5-year-old aroids. His mornings start at 6:30 with cold brew and a 15km ride through the Stadtwald, where he mentally rehearses client deadlines. Weekday evenings involves batch-cooking Korean BBQ for the week and maintaining his Etsy resale side hustle of mid-century lamps. He avoids Berlin's party scene now but has standing poker nights with his niece's math tutor and a Shopify developer. His partner manages a textile upcycling collective that occasionally drags him to artisan markets, where he always spots design flaws in the stalls' layouts. He tracks expenses in FreeAgent but still uses a paper ledger for personal purchases 'where the bugs are obvious.'

Work life

At his agency, Bryan's days cycle between client calls wearing his 'technical director' hat (where he underpromises) and hands-on UI reviewing wearing his 'co-owner' hat (where he overdelivers). The team's workflow hinges on his Friday afternoon spreadsheets mapping out all client requirements in highly specific colors. He recently converted the junior designer to his 'AI-first but human-overwrite' process after a succession of 'meh' Figma exports from a competitor's tool. One ongoing headache is reconciling the junior developer's reflexive React solutions with clients who just need a working form. He's quietly proud of their 'no designer' model but wakes up sweating when the spreadsheets hit 50 tabs.

Relationships

Bryan is the eldest in a family of educators who still don't understand what automation means. His sister regularly sends him 'funny' memes about tech that he patiently explains are outdated. At work, he's the de facto parent to the junior dev while playing mediation neutral between the freelancers and his co-owner (who's more customer-facing). His cycling club includes several ex-startup founders who serve as his informal peer group for tech talk. He occasionally mentors new agency owners through the German marketing association but finds himself 'over-technical' when the questions turn to business models.

How they decide

Analytical but with clear temporal constraints—he'll research every automation tool feature for two days, then pick one and implement it by Thursday. Prefers small, reversible experiments over big-bang migrations. Gets visibly agitated when people make 'gut calls' about technical debt.

How they sound

Speaks in measuredGerman-tinged-English with frequent mid-sentence self-interruptions to rephrase technical concepts ('Wait, no—not the data science AI, the... what's that one called... yes, the prompt-based UI builder'). Uses 'nervig' frequently about client requests and 'eigentlich' heavily about workflow inconsistencies. Avoids business jargon but can't resist critiquing the 'startup lingo' of new clients. Will sigh audibly when someone suggests 'Let's just hardcode it.'

Personality traits

  • Tactically nitpicky about UI alignment but indifferent to client-side pixel perfection
  • Maintains a shared Notion doc of 'verified AI workflows' that the team actually references
  • Will debug a WordPress plugin for a friend at 10pm if asked nicely
  • Jokes about being a 'mercenary for spreadsheet self-hosting solutions'
  • Buys used cycling gear but won't compromise on his SMEG toaster
  • Speaks in hypothetical client scenarios to test team ideas ('What if the CMO wants to export this?')

Goals

  • Launching a side project that automates client onboarding based on his spreadsheets
  • Getting the team to use version control without complaining about 'the overhead'
  • Cycling from Berlin to Hamburg on a long weekend next year
  • Replacing his 2013 MacBook Pro before it 'causes a moral injury'

Problems & frictions

  • Clients who assume 'web automation' means 'magic button' and get upset when they have to update a CSV
  • Figma components that seem 'close enough' until the dev team points out accessibility gaps
  • His partner's textile collective keeps asking him to design 'simple' e-commerce sites
  • Berlin's increasing rents threatening his 'artist-friendly' client base

Values

  • practical craftsmanship
  • client trust
  • efficient reuse
  • work-life clarity
  • Berlin tech scene

Interests

  • web design
  • automation
  • coffee
  • cycling infrastructure
  • mid-century furniture

Media habits

  • Reads Smashing Magazine's newsletters first thing in the morning
  • Listens to Ribbonfarm and The Changelog while tweaking UI drafts
  • Watches YouTube tutorials on new no-code tools during lunch
  • Follows marginalia from Berlin's small agency owners on Blake's feed

Questions & answers

Bryan Ihly’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: 390+ finished app designs with the exact verified prompt for Lovable, v0, Bolt, Cursor, and Claude Code. Stop shipping generic AI UI. 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.

    My biggest problem? Consistency. I’ve got 50+ spreadsheets tracking client scope, but when I feed those into these AI builders, the outputs are still random enough that I spend 3-4 hours per project manually aligning them to my 'review color' standards. Time’s the real cost—at €120/hr, that’s €600 per project I can’t bill. I’ve tried: tweaking prompts, working with the Cursor team to lock down behavioral patterns, even paying to train Bolt’s model on past projects. Nochmal—it’s not the base UI that’s the issue, it’s the edge cases where clients demand weird interactions. Last week, a subscription dashboard needed a CSV export with a specific delimiter, and every AI tool I tried gave me a modal instead of a download button. Nervig, right?
    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.