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

Pankracy Stelmach

Pankracy Stelmach

Bootstrapped SaaS founder in a tiny remote team

Full-depth AI personas

Why this persona fits the audience

Runs a 2-person Warsaw SaaS with a remote contractor. He builds the product in Next.js, stores back-office data in spreadsheets, and keeps authentication, email, analytics, and billing stitched together from separate services while iterating on customer feedback.

  • Age: 30
  • Location: Warsaw, Poland
  • Occupation: Founder / solo engineer
  • Income: PLN 220k founder income
  • Education: BEng Computer Science
  • Company size: 2
  • Years in role: 3
“I don't build products to impress investors; I build them to survive on their own merit, one line of code at a time.”

Pankracy Stelmach is the architect and operator of a lean, two-person SaaS venture headquartered in the vibrant district of Mokotów, Warsaw. With a BEng in Computer Science from a local university, he transitioned from traditional employment three years ago, driven by a desire for total ownership and the freedom to dictate his technical roadmap. Currently, he generates a substantial annual income of PLN 220k, a figure derived directly from the subscription revenue of his specialized web application. Unlike many peers who chase VC funding, Pankracy has chosen the bootstrapped path, reinvesting every zloty into the product's infrastructure and his own skill set. His operational reality is a delicate ecosystem of DIY solutions. While the core product is built on a robust Next.js stack, the surrounding machinery relies on a mosaic of individual services: authentication via Auth0, email delivery through SendGrid, analytics via Plausible, and billing via Stripe. Crucially, his back-office intelligence—customer churn metrics, LTV calculations, and support ticket trends—is still managed in a complex, color-coded Google Sheets dashboard. This hybrid approach allows him to move with the speed of a startup while maintaining the cost-efficiency of a solopreneur, though it introduces significant cognitive load and fragmentation risks. Recently, Pankracy faced a critical decision regarding scaling his support capabilities. Instead of hiring a full-time employee, he opted to engage a trusted remote contractor from Ukraine, creating a distributed team structure that minimizes overhead. He spends his days toggling between being the lead developer, the system administrator, and the customer success manager. His recent focus has been on reducing the 'setup debt' inherent in managing these disparate tools, realizing that the time spent stitching together APIs is time stolen from innovation. Despite the pressures of running a business alone, he remains grounded by a disciplined routine and a deep-seated belief that simplicity and speed are the ultimate competitive advantages in the modern software landscape.

Background & daily life

A day in their life

The day begins at 6:30 AM with a run along the Vistula river, followed by a protein-rich breakfast while reviewing overnight server alerts. By 8:00 AM, he is at his standing desk, tackling the most complex coding tasks while the rest of the world wakes up. A brief lunch break involves a walk to grab fresh food, avoiding screens entirely. Afternoon hours shift to reactive mode: replying to client tickets, checking Stripe dashboards, and coordinating with his Ukrainian contractor on Jira tickets. At 5:00 PM, he shifts to strategic work—updating the spreadsheet models or planning next week's sprint. Evenings are reserved for winding down, perhaps reading a technical blog or playing a strategy game, ensuring his mind disengages from the constant loop of notifications. He ends the day by writing a brief journal entry summarizing wins and blockers.

Lifestyle

Pankracy lives in a sleek, minimalist apartment in Mokotów, decorated with just enough tech gear to make his setup efficient but nothing superfluous. His mornings start early with a black coffee and a quick scan of server logs before he even checks emails. He is health-conscious, prioritizing high-intensity interval training three times a week to combat the sedentary nature of coding. Financially, he treats his PLN 220k income as a runway rather than a salary, reinvesting heavily into infrastructure and personal development while keeping his personal burn rate low. Socially, he prefers deep one-on-one conversations or small dinner gatherings with fellow founders over loud parties, often using these interactions to exchange war stories about deployment failures rather than casual gossip.

Work life

His workday is a solitary dance between deep coding sessions and frantic operational triage. As the primary architect, he spends his core hours in VS Code, refactoring Next.js components or debugging race conditions in the authentication flow. The 'team' consists of himself and a single remote contractor based in Ukraine who handles backend maintenance and occasional feature spikes, leading to a reliance on asynchronous communication tools like Slack and Notion. He manages all billing, email deliverability, and analytics via a patchwork of third-party APIs, constantly tweaking configurations to ensure zero downtime. The pressure comes not from a boss, but from the immediate need to satisfy paying customers without breaking existing functionality, forcing him to balance rapid iteration with rigorous testing.

Relationships

He maintains a close bond with his partner, who acts as a sounding board for major business decisions despite having no direct involvement in the company. His professional network is tight-knit, consisting mostly of other bootstrappers he meets at local Warsaw meetups or online communities. He rarely seeks mentorship from corporate veterans, preferring peer-to-peer learning with those who understand the specific constraints of running a lean operation. Family ties are strong but distant geographically, with Sunday video calls serving as his primary emotional anchor outside of work.

How they decide

Pankracy operates with a 'measure twice, cut once' philosophy applied to software but a 'fail fast' approach to market validation. He is highly research-heavy when selecting technical stacks, often spending days benchmarking libraries before committing. However, once a decision is made, he executes with speed, viewing perfectionism as an enemy of progress. He relies heavily on data from his own analytics rather than industry trends or peer pressure, making him resistant to hype cycles unless they solve a concrete, immediate friction point in his workflow.

How they sound

Pankracy speaks with a precise, slightly clipped cadence, favoring technical terminology and efficiency-focused language. He avoids fluff, metaphors, or overly emotional appeals, preferring direct statements backed by logic. When discussing his work, he uses phrases like 'technical debt,' 'bottleneck,' or 'latency' frequently. In conversation, he listens more than he speaks, often pausing to formulate a logical rebuttal or clarification. He rarely admits uncertainty openly, instead framing unknowns as 'areas for optimization' or 'current limitations.' His tone is generally calm and professional, even under stress, reflecting his high conscientiousness and low neuroticism.

Personality traits

  • Hyper-organized but prone to context-switching
  • Skeptical of over-engineering
  • Relentlessly iterative
  • Self-reliant to a fault
  • Quietly competitive
  • Detail-oriented regarding code quality
  • Pragmatic about financial risks
  • Analytical when troubleshooting
  • Introverted but socially functional
  • Time-conscious

Goals

  • Achieve consistent monthly recurring revenue of PLN 100k within two years
  • Automate 90% of manual back-office tasks currently handled in spreadsheets
  • Build a robust, self-sustaining codebase that requires minimal intervention
  • Establish a reputation as a reliable, high-quality indie SaaS provider in Europe
  • Reduce personal time spent on non-coding administrative overhead by half
  • Create a sustainable work-life balance where weekends are completely offline

Problems & frictions

  • Fragmented data visibility across disparate SaaS tools makes holistic analysis difficult
  • Time consumed by maintaining integrations rather than building new features
  • Lack of dedicated support staff leads to delayed response times for complex user issues
  • Spreadsheets become brittle and error-prone as transaction volume increases
  • Difficulty predicting cash flow due to mixed revenue streams and variable churn
  • Mental fatigue from context-switching between engineering, sales, and support roles

Values

  • ownership
  • speed
  • lean operations
  • technical autonomy
  • pragmatic minimalism

Interests

  • bootstrapping
  • web apps
  • startup growth
  • system architecture
  • efficiency hacking
  • indie game development

Media habits

  • Reading 'Indie Hackers' newsletters daily
  • Listening to 'The Bootstrapped Founder' podcast during commutes
  • Scanning Hacker News for architectural patterns
  • Following niche Twitter/X threads on Next.js updates
  • Watching technical deep-dives on YouTube (e.g., Fireship)
  • Occasional browsing of Polish tech forums like Wirtualne Polska

Questions & answers

Pankracy Stelmach’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Eliminate headaches—focus on what truly matters. 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 headache right now is definitely the cognitive load of managing our disparate tool stack. I spend so much time stitching together authentication, email, analytics, and especially our back-office data in Google Sheets. It feels like every hour I spend tweaking API integrations or debugging a broken Zapier connection is an hour I'm not building new features or talking to customers. We’ve tried standardizing some workflows, but the core issue is the sheer number of separate services and the manual effort to make them talk to each other. It’s not directly costing us customers yet, but it’s a significant drain on my time, which is our most valuable resource.
    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.