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

Corey Swaniawski

Corey Swaniawski

Freelance headless commerce developer

Full-depth AI personas

Why this persona fits the audience

He freelances for 2–3 small Shopify and custom storefront clients at a time, usually building Next.js front ends plus Node backends and keeping product data in spreadsheets or Airtable when the client has no dedicated ops team.

  • Age: 31
  • Location: Austin, TX, US
  • Occupation: Freelance full-stack developer
  • Income: $110k–$150k fluctuating freelance
  • Education: BSc computer science
  • Company size: N/A (self-employed)
  • Years in role: 7
“The real satisfaction comes from building something that’s not just functional, but elegant and maintainable – a system that works so well it almost disappears.”

Corey Swaniawski, 31, has carved out a distinct niche for himself as a freelance headless commerce developer operating out of Austin, Texas. His journey into freelancing began after a few years at a small software consultancy post-graduation from his computer science program. He found the corporate structure stifling and the project cycles too slow, craving the autonomy and direct impact that independent work offered. He established his freelance practice about seven years ago, initially focusing on general web development before specializing in e-commerce, particularly leveraging modern JavaScript frameworks like Next.js. His market fit is defined by his ability to serve small to medium-sized businesses that need robust online storefronts but lack the resources for enterprise-level solutions. Corey typically manages two to three clients concurrently, building custom Next.js frontends that connect to Node.js backends. A critical aspect of his service, as highlighted in his market fit, is his proficiency in managing product data for clients who don't have dedicated operations teams, often utilizing Airtable or advanced spreadsheet configurations to bridge the gap. This dual role as developer and quasi-data manager is a key differentiator. His income fluctuates significantly, ranging from $110k to $150k annually, a reality that fuels his drive for efficiency and predictable billing structures. He values craftsmanship in his code, striving for clean, performant, and scalable solutions, but also understands the need for speed to meet client deadlines. His decision to focus on headless commerce stemmed from a desire to work with more modern, flexible architectures and to escape the limitations of traditional monolithic platforms. He recently turned down a larger, more complex project that promised higher immediate revenue but involved a legacy technology stack he felt would be a poor fit for his skills and values, opting instead to take on two smaller projects that aligned better with his preferred tech stack and allowed for more focused, high-quality delivery. This decision reflects his commitment to his craft and long-term career trajectory over short-term financial gains, prioritizing sustainable growth and professional satisfaction.

Background & daily life

A day in their life

Corey's typical weekday starts around 7:00 AM with a meticulously prepared pour-over espresso. He spends the next two hours coding, often tackling complex logic for a current client project or exploring a new library. After a quick, healthy breakfast, he transitions to client-facing activities: responding to emails, attending a stand-up call, or providing project updates. Lunch is usually a simple, prepped meal. The afternoon is dedicated to focused development work, debugging, or implementing new features. Around 5:00 PM, he might take a break for a short bike ride. Evenings are a mix of learning (watching tutorials, reading articles), personal coding projects, and winding down with a book or a quiet activity. He aims to be offline by 10:00 PM.

Lifestyle

Corey lives a focused, minimalist life in Austin, prioritizing his work and personal development. His 1-bedroom apartment is tidy and functional, with a dedicated corner for his espresso setup. He’s a creature of habit: early mornings are for coding and coffee, afternoons for client calls or deep work, and evenings often involve learning a new tech stack or catching up on industry news. He cycles three times a week for exercise and mental clarity, often exploring trails around the city. Money is managed pragmatically; he saves diligently for future investments and avoids unnecessary expenses, valuing financial stability and the freedom it affords.

Work life

As a freelance developer, Corey juggles multiple small clients, typically 2-3 simultaneously. His core work involves building Next.js frontends and Node.js backends for e-commerce sites. A significant part of his role, especially with smaller clients lacking dedicated operations, is managing product data, often using Airtable or even sophisticated spreadsheets. This requires him to be adaptable and wear multiple hats, from developer to data manager. The fluctuating income is a constant consideration, driving his need for predictable billing and efficient project management. He thrives on the autonomy but feels the pressure to constantly find new clients and deliver high-quality work to maintain his reputation.

Relationships

Corey maintains a small, close-knit circle of friends, mostly fellow developers he met through university or online communities. He values their technical insights and occasional collaboration. His family lives out of state, and they connect via video calls weekly. He doesn't have a romantic partner currently, dedicating most of his free time to his career and personal projects. His professional network, primarily online, serves as a source of leads and technical advice.

How they decide

Corey is a research-heavy decision-maker, especially concerning technology and work processes. He meticulously compares options, reads documentation, and often prototypes solutions before committing. For client projects, he prioritizes solutions that offer the best balance of performance, maintainability, and cost-effectiveness. He values long-term stability and avoids trendy, unproven technologies unless there's a clear, compelling benefit. His personal purchases are usually practical and driven by utility, often influenced by reviews and technical specifications.

How they sound

Speaks clearly and precisely, with a moderate pace. He tends to use technical jargon naturally when discussing work but can simplify explanations when needed. Avoids overly casual slang or hyperbole. His tone is generally calm and measured, reflecting his analytical nature. He might pause to formulate his thoughts, especially when explaining complex concepts. He's not prone to emotional outbursts but expresses enthusiasm for elegant technical solutions.

Personality traits

  • detail-oriented
  • independent
  • pragmatic
  • analytical
  • resourceful
  • methodical
  • introverted but polite
  • focused
  • optimistic about technology

Goals

  • Build a portfolio of successful, scalable e-commerce projects.
  • Achieve a more stable, predictable freelance income stream.
  • Develop a niche expertise in a specific area of headless commerce.
  • Eventually transition to building and maintaining his own indie SaaS product.
  • Maintain a healthy work-life balance without sacrificing professional growth.

Problems & frictions

  • Client scope creep and managing expectations on smaller budgets.
  • Inconsistent cash flow due to project-based freelance work.
  • The overhead of administrative tasks (invoicing, contracts, chasing payments).
  • Keeping up with the rapid pace of front-end and backend framework updates.
  • Finding clients who truly understand the value of well-architected headless solutions.

Values

  • craftsmanship
  • autonomy
  • speed
  • predictable billing
  • efficiency

Interests

  • Next.js
  • espresso
  • indie SaaS
  • cycling
  • serverless architecture
  • minimalist design

Media habits

  • Reads Hacker News daily
  • Follows tech influencers on Twitter
  • Listens to coding podcasts during commutes/chores
  • Watches YouTube tutorials for new frameworks
  • Subscribes to developer newsletters

Questions & answers

Corey Swaniawski’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Storecraft (https://storecraft.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Storecraft 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 managing product data for my clients using spreadsheets or Airtable, depending on their setup. It works, but it's definitely a manual process and can be a bottleneck for clients without ops teams. Storecraft's promise of a 'Commerce As Code' backend is interesting, especially the flexibility in databases and cloud deployment. The AI features could streamline things, but I'd need to see how well it integrates with existing workflows and if it genuinely reduces the data management overhead I currently handle. The biggest unknown is the learning curve and how much customization is truly possible without becoming overly complex. I'd be willing to pay around $50 per month, but that's contingent on a much clearer understanding of its capabilities and ease of integration.
    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.