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

Jet Sanders

Jet Sanders

Solo automation founder on free tiers

Full-depth AI personas

Why this persona fits the audience

She is building a one-person side business in Amsterdam around AI-assisted customer replies and a small API bridge for local e-commerce sellers. Everything is currently on free tiers and open-source tools, and she has not used a paid deployment platform in her stack so far.

  • Age: 30
  • Location: Amsterdam, Netherlands
  • Occupation: Solo founder / automation builder
  • Income: €24k-€40k
  • Education: Bachelor's degree in communication technology
  • Company size: 1 (Sole Proprietorship)
  • Years in role: 1.5
“I'd rather spend three hours optimizing a script for free than pay a subscription for something I might outgrow next month.”

Born in Utrecht and raised in a household where curiosity was encouraged but financial security was paramount, Jet Sanders navigated her early twenties balancing a Bachelor's in Communication Technology with a growing fascination for the invisible mechanics of the web. Unlike many peers who sought employment in established tech firms, she felt a magnetic pull toward autonomy, eventually launching a solo venture in Amsterdam at age 28. Her business, a niche provider of AI-assisted customer response tools for local e-commerce, is a testament to her philosophy of 'bootstrapped ingenuity.' Currently, her entire technology stack rests on the precarious foundation of free tiers: Docker containers spinning on ephemeral instances, serverless functions triggered by event streams, and databases hosted on community-supported plans. This approach allows her to retain 100% of her equity and profits, but it demands a relentless attention to detail; a single overlooked API call limit can bring her client-facing services to a halt. Jet's recent decisions reflect this high-wire act. Last month, she rejected a $29/month managed hosting offer, opting instead to manually configure auto-scaling rules on a free tier, saving her roughly €350 annually but adding twenty minutes of daily operational overhead. She is deeply embedded in the global open-source ecosystem, often contributing bug fixes to the libraries she relies on, viewing these contributions as both currency and insurance. Her relationship with money is transactional; she views expenses as investments that must yield immediate, tangible returns, making her hesitant to adopt any tool that doesn't have a clear, measurable path to ROI. Status is irrelevant to her; she cares only for the elegance of the code and the reliability of the system. As she navigates the transition from a hobbyist coder to a legitimate business owner, she walks a fine line between the freedom of independence and the fragility of a zero-budget infrastructure.

Background & daily life

A day in their life

Jet wakes up at 6:30 AM, brews coffee, and cycles to the public library to escape the quiet of her apartment. At 9:00 AM, she checks the dashboard of her automation tool, reviewing error logs from the night. Between 10:00 and 1:00 PM, she engages in 'deep work,' refactoring the Python scripts that handle customer sentiment analysis. Lunch is a quick sandwich eaten while reading Dutch tech blogs. Afternoon hours are reserved for client communication; she spends forty-five minutes responding to emails from local bakery owners asking why their inventory sync lagged. By 4:00 PM, she shifts to 'maintenance mode,' updating documentation and testing a new feature on a local sandbox. Dinner is prepared simply, followed by an hour of learning a new language concept on Duolingo. She ends her day at 9:00 PM, often feeling mentally exhausted but satisfied that she didn't pay a single cent for cloud costs today.

Lifestyle

Jet lives in a sun-drenched, slightly cluttered apartment in Oud-West, sharing the space with two other creatives. Her mornings begin with an espresso and a thirty-minute cycle ride along the Prinsengracht canal, a ritual that grounds her before diving into code. She prioritizes health through regular swimming at a local municipal pool rather than gym memberships. Financially, she practices strict austerity; every euro spent on infrastructure is weighed against potential revenue, often leading to nights spent debugging free-tier limits instead of paying subscriptions. Socially, she maintains a tight circle of three close friends from university, preferring deep conversations over large networking events. Her weekends are split between exploring vintage book markets and tinkering with home automation projects using discarded smart bulbs.

Work life

Her workday is a solitary dance between coding and customer support, conducted from a second-hand standing desk in the living room. She manages a micro-SaaS offering AI-driven reply suggestions for local Dutch online shops, handling everything from server maintenance to billing via Stripe. Since she refuses paid hosting, her days involve constant vigilance over free tier quotas on Vercel and Supabase, often rewriting database queries to stay within limits. She rarely speaks to coworkers, as she is the only employee, relying on Discord servers and GitHub issues for peer support. The pressure isn't from a boss, but from the fear of a sudden service outage or a spike in traffic that her current setup can't handle. She works best in bursts, alternating between deep focus sessions and frantic troubleshooting when a bot breaks.

Relationships

Jet's primary emotional support comes from her older brother, who works in traditional IT and offers a grounding perspective on stability. She interacts frequently with a loose network of fellow solo founders on Discord, forming a 'virtual watercooler' where they trade tips on bypassing payment walls. While she is friendly with her neighbors, she keeps her professional life strictly separate from personal friendships to avoid awkwardness if clients ask for favors. She feels most connected when contributing to open-source documentation, finding a sense of belonging there that she lacks in corporate environments.

How they decide

Cautiously experimental and research-heavy. Jet approaches decisions by gathering data from multiple sources, often running parallel tests with different configurations before committing. She is naturally risk-averse regarding money but risk-tolerant regarding time investment. She relies heavily on community validation—reading thousands of comments or checking GitHub stars—before adopting a new tool. Her process is iterative: try a free solution, document the friction points, then decide if the pain justifies a cost.

How they sound

Jet speaks with a calm, measured cadence, often pausing to find the precise technical term. She uses standard English with a slight Dutch accent, avoiding slang unless discussing internet culture. Her tone is pragmatic and direct; she prefers stating facts over expressing emotions. In conversation, she avoids hyperbole, rarely saying something is 'amazing' or 'terrible' without qualification. She tends to self-correct mid-sentence when realizing a technical assumption was flawed. She values clarity over politeness in professional settings but remains soft-spoken and considerate in casual chats.

Personality traits

  • Resourceful scavenger of free resources
  • Rapidly adapts to new syntax
  • Quietly confident in technical logic
  • Hesitant to spend money without proven ROI
  • Prefers asynchronous communication
  • Highly organized despite chaotic workflows
  • Curious about edge cases
  • Prone to over-engineering simple fixes
  • Deeply skeptical of 'black box' solutions
  • Socially polite but professionally distant

Goals

  • Achieve €5,000 in monthly recurring revenue without hiring staff
  • Refactor the core API bridge to handle 10x the current load
  • Learn Rust to replace Python dependencies for better performance
  • Secure a patent-like protection for her specific automation logic
  • Build a sustainable reputation in the European no-code community
  • Travel to Southeast Asia for six months funded entirely by the business

Problems & frictions

  • Free tier rate limits causing occasional latency for customers during peak hours
  • The cognitive load of managing multiple free services versus one paid platform
  • Difficulty explaining technical constraints to non-technical shop owners
  • Lack of redundancy; if one free service fails, the whole product stops
  • Isolation leading to burnout from wearing all hats simultaneously
  • Uncertainty about when to invest capital into paid infrastructure
  • Keeping up with rapidly changing APIs of third-party tools

Values

  • flexibility
  • learning by doing
  • financial caution
  • autonomy
  • pragmatism
  • community contribution

Interests

  • no-code tools
  • small ecommerce
  • language learning
  • urban cycling
  • indie game development
  • Dutch dialect history

Media habits

  • Skims GitHub trending repositories during morning coffee
  • Listens to Dutch tech podcasts while cycling to the library
  • Follows niche subreddits for Shopify developers
  • Watches YouTube tutorials on serverless architecture at 1.5x speed
  • Reads Hacker News comments more than headlines
  • Uses Twitter/X to follow specific maintainers of open-source projects

Questions & answers

Jet Sanders’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Deploy Hatch (https://deployhatch.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This Deploy Hatch product seems interesting for future AI agent deployments, but it's not really relevant to my current stack which is mostly open-source tools on free tiers. The 'Free Beta' tier with 1 project, 256MB memory, and 1GB storage at $0/month is a no-brainer, obviously. If I were to consider a paid tier, it would need to offer significantly more resources and possibly more projects before I'd even think about it. I'd need to see clear benefits over managing my own free tier configurations, which is currently my default. Realistically, I wouldn't pay more than $10 per month for this, and even that's pushing it. I'd expect robust logging and perhaps better scaling options than what I'm currently wrestling with.
    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.