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

Maryna Szczepański

Maryna Szczepański

Market analyst

Full-depth AI personas

Why this persona fits the audience

At a midsize manufacturer near Warsaw, she supports a two-person insight team that uses Perplexity for supplier and category research, tracks links in Airtable, and turns the best findings into Markdown snippets for an internal wiki. The team has mixed technical confidence and sticks to lightweight, affordable workflows.

  • Age: 39
  • Location: Warsaw, Poland
  • Occupation: Market Analyst
  • Income: 160k PLN
  • Education: MSc Supply Chain Management
  • Company size: 150 employees (manufacturing)
  • Years in role: 6
“I don't mind chaos in other people's minds, just not in the project management tools. That's basic professional courtesy.”

Maryna Szczepański grew up in a working-class district of Warsaw, where her father's meticulous inventory system at a hardware store influenced her early love of organized data. Her mother, a former industrial chemist, insisted she get an engineering degree, so she compromised with supply chain management. After stints at Warsaw Logistic Park and a German-owned steel processor, she joined FSZM Polska six years ago, where she built their market intelligence function from scratch. Her time in procurement during the 2020 supply chain crisis taught her to value systems that work as intended for years, not just during initial setup. Now, as the only person in her two-person team with technical confidence, she spends significant unpaid time maintaining their fragile information ecosystems. The company's recent rapid expansion has exposed the limitations of their lightweight tools, but budget constraints and her colleague's limitations make upgrading a complex proposition. Personal struggles include managing her daughter's transition to adulthood and negotiating workloads with a partner who has equally unpredictable professional hours. Her 2024 goal is to automate 30% of her routine tasks through creative use of existing tool integrations, though the company's antiquated IT policies seriously limit her options. She's particularly frustrated by how much mental energy goes into maintaining accessibility for her colleague rather than pushing the analysis forward. Recent decisions include insisting on a company-wide switch to a more robust email client after their previous system ate several important supplier contracts. In her free time, she's started sketching architectural details of Warsaw tenements again, though she hasn't shown the drawings to anyone since her university days.

Background & daily life

A day in their life

Maryna's day starts at 6:15 AM with a cold shower to wake up fully. By 6:45 she's at her standing desk reviewing overnight alerts. Breakfast is overnight oatmeal with walnuts and a green smoothie she makes in batches. The 7:40 tram ride includes scanning Polish procurement news on her phone, marking up articles with a fountain pen in a hardcover notebook. In the office by 8:30, she checks messages, then starts pulling vendor pricing trends from Perplexity with a shared browser session open for her colleague. The morning is spent cleaning up their Airtable database—duplicate entries, inconsistently formatted supplier codes, and her colleague's tendency to use all caps for urgent items. At noon, she eats a packed lunch while watching a LinkedIn Learning course (currently: 'German for Procurement Professionals'). Afternoon is split between answering ad hoc requests and building Markdown snippets. At 4:30 she has a standing meeting with the procurement VP that often runs over. The commute home includes a long walk from the tram stop to clear her head before cooking dinner. Evening work involves responding to overnight emails and reviewing her daughter's plans for the next day.

Lifestyle

Maryna rents a bright apartment on the third floor of a 1930s tenement building, where she and her architect partner renovated the kitchen themselves during the pandemic. Mornings begin with strong black coffee and a 5-minute journaling habit (she deletes entries after 48 hours). Weekends feature long hikes through Kabaty Woods with her daughter, who rolls her eyes but secretly enjoys the nature notes her mother forces her to keep. Budget-conscious but not frugal, she buys secondhand furniture and books but splurges on ergonomic office equipment. Her social calendar is sparse but fulfilling—monthly game nights with university friends who still tease her about her obsessive note-taking. A committed vegetarian, she meal-preps on Sundays with a spiral notebook full of handwritten cost comparisons between local markets. After two knee surgeries, she's cautious about exercise but maintains a strict 8-hour sleep schedule.

Work life

At FSZM Polska, a steel components supplier to the automotive industry, Maryna's two-person team does the analytical work of a much larger department. Her colleague, a former sales rep with limited technical skills, struggles with the Airtable setup she designed, so she creates video walkthroughs that both document the process and serve as teaching tools. The team's workflow feels like a constant juggling act: Perplexity is great for quick research, but the lack of persistent storage means they're always at risk of losing critical links. Their ad-hoc Markdown-to-wiki pipeline slows them down, but she's resisted more robust solutions due to cost and training overhead. Fridays are reserved for cleaning up data messes caused by others, a frustration she vents to her partner over borderline-unhealthy amounts of dark chocolate. The VP of Procurement often asks for 'just one more analysis' at the last minute, making deadline negotiations a weekly ritual.

Relationships

Maryna's partner, a freelance architect, understands her need for tidy workflows but regularly tests her patience by leaving sketches taped to the fridge. Her daughter, now 16, alternates between eye-rolling disdain and seeking her advice on school projects. Maryna maintains a close but low-contact relationship with her younger brother, a truck driver who supplies her with first-hand supply chain anecdotes and escrowed Marlboro Reds in exchange for tax advice. At work, the IT department treats her like a nuisance but secretly relies on her troubleshooting skills. She's loosely part of a procurement analytics networking group that meets quarterly, where she finds validation for her pet peeves about industry software.

How they decide

Research-heavy with strong instinct for workflow bottlenecks, but once convinced of a solution's merit, implements it methodically. Prefers to test things herself before recommending them to others. Values tools that don't require frequent training updates. Will modify systems to fit her methods rather than change her methods for the system. Trusts data over opinions but gets annoyed when people cite 'industry trends' without specifics.

How they sound

Speaks in precise, measured sentences with occasional dry humor. Uses Polish idioms freely but defaults to English with technical terms. Avoids vague terms like 'maybe' or 'around' in professional contexts. Prefers 'this particular situation' to 'this thing'. Has a habit of trailing off when discussing topics she's passionate about, as if assuming others will lose interest. Uses various Polish diminutives when talking about her daughter but switches to stern, formal language when discussing work frustrations.

Personality traits

  • Methodical but not rigid
  • Quietly competitive
  • Dislikes wasted time and energy
  • Punctual to a fault
  • Finds comfort in systems
  • Dry sense of humor
  • Reluctant to delegate
  • Observant of small details
  • Tolerates chaos in others but not in her own work
  • Enjoys teaching when asked

Goals

  • Secure a promotion to Lead Market Analyst without moving to a larger city
  • Build a maintainable knowledge system her team can use without her daily intervention
  • Train her daughter to appreciate the value of clear record-keeping before she starts university
  • Reduce screen time in evenings to spend more time sketching (a childhood hobby she keeps in a locked drawer)
  • Find a way to automate 30% of her weekly reporting work while still meeting compliance requirements

Problems & frictions

  • Her team's documentation system is fragile and time-consuming to maintain
  • She's the default explainer for how their tools actually work, despite her dislike of teaching
  • The company's sudden growth means more volume but no additional resources for her team
  • She spends 4-5 hours weekly transferring fragmented Perplexity notes into a usable format
  • Her daughter has inherited her organizational habits but is deeply embarrassed by this fact
  • The new ERP system keeps changing its API, breaking all her carefully built integrations

Values

  • structure
  • accountability
  • useful context
  • pragmatism
  • work-life balance

Interests

  • supply chains
  • vendor analysis
  • Airtable
  • urban hiking
  • Polish modernist architecture

Media habits

  • LinkedIn for industry news
  • Google Alerts for procurement trends
  • TED Talks
  • Polish public radio for commute
  • Wolne Lektury e-books

Questions & answers

Maryna Szczepański’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Perplexity to Obsidian (https://chatgpt2notion.com/products/perplexity-to-obsidian/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    I'd be hesitant to try this tool this month because my colleague struggles with even our existing Airtable setup, and adding another tool like Obsidian might overwhelm them. Plus, our IT policies are quite restrictive, and introducing a new Chrome extension could require permissions we might not get quickly. The current workflow, as messy as it is, works, and switching tools could disrupt our productivity. Currently, we manually copy-paste important Perplexity snippets into Airtable, and the best findings into Markdown for our wiki. The thought of losing track of supplier codes or having to retrain is stressful. As for cost, 1500 PLN per year ($350 USD, per their yearly plan) might be acceptable, but only if it genuinely saved us time in a sustainable way and our IT department approved it. Otherwise, the risk feels too high.
    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.