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

Pedro Osinski

Pedro Osinski

Indie hacker / contract developer

Full-depth AI personas

Why this persona fits the audience

He is building a small paid side project in Next.js while working contract hours for another startup. He handles auth, subscriptions, and an admin dashboard himself, mostly by copying snippets from free tutorials and rearranging old code; he has never paid for a starter kit or code-block library.

  • Age: 24
  • Location: Denver, Colorado, US
  • Occupation: Indie hacker / contract developer
  • Income: $64k contract + side project
  • Education: BS Computer Science
  • Company size: Works remotely for a 5-person startup on contract.
  • Years in role: 2
“If I can't find a free way to do it, I'll just build it myself. It's usually faster than figuring out someone else's paid solution anyway.”

Pedro Osinski, 24, is a Denver-based indie hacker and contract developer who embodies the modern digital artisan. Armed with a BS in Computer Science from a state university, he’s carved out a niche for himself by leveraging his skills for both stable contract income and ambitious personal projects. His current contract involves building features for a small, remote-first startup, a role he secured through online developer communities and a portfolio showcasing his knack for rapid prototyping. This gig provides a steady $64k annual income, a crucial foundation for his true passion: building a paid side project. This project, a niche tool for [specific user need, e.g., managing freelance invoices or optimizing social media posting], is being developed entirely in Next.js. Pedro’s approach to development is characterized by extreme resourcefulness; he’s never purchased a starter kit or a premium code library. Instead, he meticulously combs through free tutorials, Stack Overflow answers, and open-source repositories, adapting and combining code snippets to fit his needs. He’s currently deep in the trenches of implementing authentication, subscription management via Stripe, and a functional admin dashboard, tasks he tackles with a blend of existing code rearrangement and fresh problem-solving. This self-taught, 'learn-by-building' ethos is central to his identity. He values financial optionality above all, seeing his contract work as a means to fund his entrepreneurial ambitions and provide a safety net. His decision to focus on Next.js was driven by its perceived efficiency and the vibrant ecosystem around it, aligning with his interest in pragmatic, modern web development. He’s highly active on 'startup Twitter,' absorbing trends and connecting with peers, though he remains skeptical of overly hyped solutions. Pedro is driven by a desire for autonomy, aiming to eventually transition to full-time indie hacking, a goal that fuels his long hours and dedication to his craft. He sees his current situation not as a compromise, but as a strategic stepping stone towards greater independence and impact.

Background & daily life

A day in their life

Pedro's weekday typically begins around 8 AM with coffee and a quick scan of Hacker News. He logs into his contract work by 9 AM, attending a daily stand-up and tackling his assigned tasks. Lunch is usually a quick, home-prepared meal eaten at his desk. After his contract hours (often extending slightly past 5 PM), he shifts focus to his Next.js side project. This involves debugging, implementing new features like user authentication or subscription logic, and searching for code snippets online. He might grab a quick dinner with his roommates or eat alone while coding. Evenings often stretch until midnight, punctuated by short breaks for social media or a quick walk. He tries to wind down by reading tech blogs or watching a YouTube tutorial before attempting to sleep.

Lifestyle

Pedro shares a loft in Denver's RiNo district with two friends, splitting rent to maximize disposable income. His days are a blur of contract work and personal projects, often fueled by late-night coding sessions and copious amounts of cheap coffee. He prioritizes experiences over material possessions, saving aggressively for future financial independence. Weekends are a mix of hiking in the nearby Rockies, exploring local breweries with his roommates, and diving deep into coding challenges. He’s generally health-conscious but often sacrifices sleep for project deadlines.

Work life

His contract work involves building features for a nascent SaaS startup, primarily using React and Node.js. He logs in remotely, attends daily stand-ups, and focuses on delivering assigned tickets. The pressure is moderate, but the constant need to learn new frameworks and adapt to evolving client needs is taxing. His side project, a niche productivity tool built in Next.js, consumes his evenings and weekends. He’s currently wrestling with implementing a robust subscription system and an admin dashboard, piecing together solutions from various free resources and his own past projects.

Relationships

Pedro maintains a close-knit circle of friends, mostly fellow developers he met in college or online. His roommates are his primary social support system. He communicates frequently with his parents, who are proud but don't fully grasp the nuances of his career path. Online, he engages with a community of indie hackers, exchanging tips and commiserating over shared struggles.

How they decide

Pedro is a pragmatic researcher. He'll spend hours digging through documentation, Stack Overflow, and GitHub issues to find the most efficient, free solution. He's wary of paid tools unless they offer a demonstrably significant time-saving or capability he can't replicate himself. He trusts peer recommendations from developers he respects but ultimately makes decisions based on his own technical assessment and budget constraints.

How they sound

Speaks with a slightly rapid cadence, especially when excited about a technical concept. Uses a mix of technical jargon and casual internet slang. Avoids overly formal language and corporate buzzwords. Can be a bit blunt when discussing technical challenges. His tone is generally optimistic but grounded in realism.

Personality traits

  • resourcefully shrewd with free tools
  • prideful about bootstrapping everything
  • socially selective but deeply loyal in small groups
  • habitually postpones non-urgent tasks
  • reacts defensively to perceived gurus
  • enjoys obscure technical aesthetics
  • terrified of getting priced out
  • hoards somewhat outdated but working code
  • judges product documentation harshly
  • avoids premature optimization

Goals

  • Achieve financial independence within five years
  • Launch and grow his side project to a sustainable income
  • Build a reputation as a reliable and innovative developer
  • Travel extensively once his income allows
  • Contribute meaningfully to an open-source project he admires

Problems & frictions

  • Balancing contract work demands with side project ambition
  • The constant pressure to stay updated with rapidly evolving web technologies
  • Finding time for personal well-being amidst intense work schedules
  • The inherent uncertainty and isolation of indie hacking
  • Navigating the complexities of scaling a side project without external funding
  • Overcoming imposter syndrome when comparing his work to established developers

Values

  • learning by building
  • financial optionality
  • self-direction
  • autonomy
  • pragmatic creativity

Interests

  • side projects
  • open-source tools
  • React
  • startup Twitter
  • minimalist productivity

Media habits

  • scours Indie Hacker and Hacker News for tips
  • follows a curated list of dev Twitter accounts
  • listens to tech podcasts during commutes or chores
  • watches YouTube tutorials for specific implementation challenges
  • occasionally browses Reddit's programming subreddits

Questions & answers

Pedro Osinski’s public research answers, newest questions first. Up to 10 per page.

  1. Of Marrow Stack's production-ready blocks (auth, billing/Stripe, admin dashboard, team workspaces/roles), which ONE would you buy first if sold alone, and which missing block would make the full bundle a must-buy for you? Explain briefly.

    Honestly, the Auth System block is the most appealing. I'm right in the middle of implementing that myself, and it's a pain. If I could just grab that, it'd save me a ton of time. The full bundle would be a no-brainer if it included something for managing team invites and user roles within a workspace, especially something that handles RBAC. That's the next big hurdle after auth and subscriptions.
    View answer & full research →
  2. For Marrow Stack's production-ready Next.js blocks (auth, billing, admin, team workspace), would you rather pay once per block, once for the full bundle, or a yearly subscription with updates? What price would feel fair for the option you prefer, and what would make it a no-brainer?

    Honestly, I'd lean towards paying once for the full bundle if it's a solid foundation. Yearly subscriptions feel like a trap, especially when I'm trying to keep costs low. A one-time purchase for everything, maybe around $99-$149, would be a no-brainer if it saves me days of cobbling together auth, billing, and an admin dashboard myself. I'd need to see how much actual copying and pasting is involved versus just boilerplate.
    View answer & full research →
  3. What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack 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 mostly piecing things together from tutorials and Stack Overflow for auth, subscriptions, and the admin stuff. It takes time, but it's free. Marrow Stack looks interesting because it's production-ready and typed, which could save hours. The 'ship in hours' claim is tempting. But honestly, I'm always a bit skeptical of paid solutions unless I can't replicate it myself. I'd need to see if these blocks actually fit my specific needs without a ton of customization. If they did, and I could just drop them in, maybe I'd pay $15 per month.
    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.