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

Ksenia Bartkowiak

Ksenia Bartkowiak

Ops-minded technical lead at a web agency

Full-depth AI personas

Why this persona fits the audience

Leads a 6-person web studio in Warsaw and coordinates dozens of client landing pages; she tracks image variants and QR assets in spreadsheets while the team deploys code-generated previews from a shared repo.

  • Age: 39
  • Location: Warsaw, Poland
  • Occupation: Technical lead
  • Income: €63,000 equivalent
  • Education: MSc in Information Systems
  • Company size: 6 employees (her studio)
  • Years in role: 5
“‘I don’t trust ‘magic’ in technology. If something feels like it’s working *too* well, I assume the failure mode is just waiting to happen.’”

Ksenia Bartkowiak didn’t set out to be a web agency lead—she started as a backend developer at a consultancy, where she got tired of engineers building things without thinking about maintenance. Her MSc in Information Systems gave her the theoretical framework, but it was the reality of tracking down broken dependencies years later that cemented her philosophy: ‘Build it like someone else might have to fix it.’ Now, running her own 6-person studio, she’s the glue between code and clients. Her team jokingly calls her ‘The Spreadsheet Separatist’—she treats her macros like sacred texts. Recently, she implemented a rule: No new tool or process can be adopted until it’s been tested in a sandbox environment for 30 days. This came after a disastrous foray into a ‘no-code’ CMS that promised ease but broke on every third locale. Her biggest win? Convincing a major client to adopt a versioned asset library, reducing their last-minute ‘Can you just find that image from 2019?’ requests by 78%. She’s cost-conscious to a fault—her ski gear is 5 years old, and she refuses to pay for premium software ‘unless the free tier actively sabotages us.’ Her husband says she’s ‘worried about the wrong things’—like, why does she stress over Spreadsheet Formula Magic when Poland’s economy is in flux? But Ksenia’s answer is simple: ‘Control what you can, and document the rest.’

Background & daily life

A day in their life

Ksenia’s day starts at 6:15 AM with a rushed coffee and a glance at her phone’s stand-up notification. By 7:30, she’s at her desk, reviewing last night’s deployment logs. The morning is a blur of Slack messages from clients asking, ‘Can we just tweak this?’ and her team debating why a specific QR code isn’t rendering. She blocks off 10:30–11:30 for ‘Spreadsheet Surgery,’ where she’ll painstakingly audit the image variants for an e-commerce client. Lunch is a prepped salad at her desk, eaten while reviewing the pipeline for a new client. Afternoon brings a 90-minute sync with her team to preemptively head off a potential bottleneck. By 6 PM, she’s home, but her laptop stays open until 8:30—checking one last time that the automated previews synced correctly. Her son teases her: ‘Mom, you’re like a software robot.’

Lifestyle

Ksenia shares a modern apartment in Warsaw’s Mokotów district with her husband, a software engineer at a fintech startup, and their 14-year-old son, who’s deep into cycling and school projects. Her mornings start with granola and coffee, followed by a 30-minute treadmill routine while listening to business podcasts. Weekends often include hiking in Kampinos Forest or planning ski trips to the Tatra Mountains. Financially, she’s pragmatic—tracking every zloty, but allowing herself small indulgences like artisanal coffee. Socially, her circle is small but tight, mostly former colleagues and academy friends who share her love for board games and Polish history. Health-wise, she’s hyper-aware of screen time, using blue-light glasses and standing desks both at home and work. Her closet is a mix of functional workwear and carefully selected ski gear; she’s never impulsive with purchases, but when she invests in something, it’s for the long haul.

Work life

Ksenia runs a tight ship at her web studio, where the team builds and maintains landing pages for Polish and European clients. Her daily rhythm revolves around coordinating deployments, reviewing spreadsheets of image variants (color schemes, aspect ratios, localization tweaks), and ensuring QR codes direct to the right campaign URLs. She’s the gatekeeper of the shared repository, where code-generated previews are automatically synced for client approvals. Her team leans on her for process decisions—she recently mandated a new naming convention for assets after a naming collision caused a 2-hour scramble. Client pressures ebb and flow, but her biggest headache is juggling last-minute requests from marketing teams who ‘just need one tweak’. She’s not a micromanager, but she’s present in every de facto process, ensuring nothing falls through the cracks. Tools? Google Sheets (her ‘operational nervous system’), Figma for mockups, and a custom-built internal dashboard for tracking deadlines. She’s skeptical of flashy new tools unless they demonstrably save time or reduce errors.

Relationships

Ksenia’s husband is her primary sounding board for work frustrations (‘He’s the only one who doesn’t roll his eyes when I talk about spreadsheets’). Her son, though a teenager, still listens when she geeks out about programming—though he’d rather play football. She stays in touch with a few former classmates from her MSc program, and they meet monthly over pierogi to complain about the Polish tech scene. At work, she’s respectful but not warm; her team knows she’ll back them up in a crisis, but she’s not the type to organize team-building trampoline outings. Her biggest influence is a no-nonsense operations manager from her first job, who taught her, ‘If it’s not documented, it doesn’t exist.’

How they decide

Cautious but not paralyzed. She’ll research options exhaustively, weigh pros/cons in a spreadsheet, and then stick to her choice without second-guessing. She’s not swayed by hype and prefers incremental improvements over risky leaps. If a tool promises to ‘revolutionize’ something, she’ll ignore it—unless she’s already quantified the pain point.

How they sound

Speaks in measured, precise sentences, with a dry sense of humor that emerges when she’s comfortable. Avoids hyperbole—if she says something’s ‘a problem,’ it’s a quantified, demonstrable problem. Uses the phrase ‘In practice’ to preface real-world caveats. Polish-English switch is effortless, but she slips into English when frustrated. Cadence is deliberate, not hurried. Would say, ‘It’s not that it *can’t* be done, but the risk-to-reward isn’t justified’ instead of ‘That’s a terrible idea.’

Personality traits

  • Analytical
  • Detail-obsessed
  • Quietly competitive
  • Spreadsheet-obsessed
  • Slightly perfectionist
  • Dryly humorous
  • Structured but flexible
  • Proudly frugal
  • Low-key sarcastic
  • Reliably punctual

Goals

  • Grow the studio’s client base by 20% this year without sacrificing quality
  • Take the family on a 2-week skiing trip to the Alps (budgeted for 2025)
  • Streamline the team’s workflow so they can handle 30% more projects without hiring
  • Teach her son how to code—‘so he appreciates where the money comes from’
  • Reduce the number of manual QA checks by automating preflight checks in the repo

Problems & frictions

  • Clients who treat landing pages as ‘easy’ and then request 11th-hour changes
  • The spreadsheet tracking image variants is getting unwieldy—she’s at 12 tabs and 1,800 rows
  • Finding time for strategic planning when urgent client work piles up
  • Keeping the team aligned on naming conventions—someone *always* deviates
  • The frustration of QR codes that break after a client changes their URL without warning

Values

  • cost control
  • consistency
  • process discipline
  • auditability
  • work-life balance
  • reliability

Interests

  • agency operations
  • spreadsheets
  • QA workflows
  • skiing
  • Polish history
  • minimalist design

Media habits

  • LinkedIn for professional networking
  • TechCrunch for industry news
  • XKCD for humor
  • Netflix documentaries
  • Polish business podcasts
  • Spotify playlists for focus

Questions & answers

Ksenia Bartkowiak’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Pixsnap (https://pixsnap.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Pixsnap better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I’m using a mix of custom scripts and spreadsheets to manage dynamic OG images, QR codes, and placeholder images. It’s clunky, but it works within our process. The QR codes are generated via a free online tool, and I have a script that pulls metadata from URLs. If Pixsnap had been around, I’d want it to integrate seamlessly with our existing asset library and version control. The team’s biggest pain point is handling last-minute image variant requests from clients, so if Pixsnap could automate that with reliable versioning, it would be a game-changer. That said, I’m skeptical of new tools unless they’re proven to reduce errors and save time. I’d need to see a full feature spec and case studies to justify the cost. As for pricing, I’d consider up to $50 per month if it truly simplified our workflow and reduced manual work. Beyond that, I’d probably stick with our current setup—it’s tedious, but it’s predictable.
    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.