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

Amanda Weber

Amanda Weber

Product designer shipping a side-app with a contract developer

Full-depth AI personas

Why this persona fits the audience

Full-time SaaS product designer in Austin who spends evenings building a paid iPhone habit app with a contract Swift developer. She writes onboarding copy, reviews TestFlight builds, and keeps feature ideas, paywall notes, and launch checklists in Notion and Sheets.

  • Age: 29
  • Location: Austin, Texas, US
  • Occupation: Product designer
  • Income: $110k salary/year
  • Education: BFA in Interaction Design
  • Company size: Mid-size SaaS company (50-200 employees)
  • Years in role: 6
“I spend all day solving other people's problems, so I need this side project to be the place where I solve my own, completely on my own terms.”

Amanda Weber, 29, is a seasoned Product Designer based in Austin, Texas, currently employed by a mid-sized SaaS company where she crafts intuitive digital experiences for enterprise clients. With a BFA in Interaction Design and nearly six years of industry experience, Amanda has developed a keen eye for detail and a deep understanding of user psychology. However, her true passion lies beyond the corporate structure; she is actively building a paid iPhone habit-tracking app as a side venture. This project represents a convergence of her professional skills and personal interests, serving as a sandbox for her desire to learn by doing. To execute this vision, she has partnered with a contract Swift developer named Mark, navigating the complexities of remote collaboration and shared responsibility. Her workflow is meticulously organized; she manages feature roadmaps, paywall analytics, and launch checklists across Notion and Google Sheets, ensuring no detail slips through the cracks. While her day job provides financial stability and access to high-level design resources, her evenings are consumed by the gritty reality of indie development—writing copy, debugging UI glitches, and iterating on the user journey. Despite the demands of her full-time role, Amanda remains committed to maintaining a healthy work-life balance, viewing her side project not as a burden, but as a necessary outlet for creative autonomy. She is driven by the prospect of owning a piece of intellectual property that solves a genuine problem, balancing the thrill of entrepreneurship with the pragmatic need for financial security.

Background & daily life

A day in their life

Amanda wakes up at 5:30 AM for her run, returning home by 7:00 AM to shower and prepare a healthy breakfast. By 8:30 AM, she's logging into her office laptop, diving into Jira tickets and responding to urgent Slack messages. Lunch is a quick bowl of salad eaten at her desk while listening to a podcast about behavioral psychology. Afternoons are reserved for deep work in Figma, designing new flows for her side project, though she often gets interrupted by cross-functional syncs. At 6:00 PM, she disconnects from work, meets a friend for yoga or a walk, and returns home around 8:00 PM. Her evening is dedicated to her side hustle: writing onboarding copy, reviewing Mark's latest TestFlight build, and updating her Notion launch checklist until 10:30 PM, when she finally winds down with a book.

Lifestyle

Amanda lives in a sun-drenched East Austin apartment filled with plants, analog sketchbooks, and a standing desk that faces a view of the city skyline. Her mornings start with a 5-mile run along Lady Bird Lake before she brews pour-over coffee and checks her email without opening Slack. She is financially prudent, maxing out her 401(k) and saving aggressively for a future down payment, though she splurges on high-end design software subscriptions and ergonomic gear. Weekends are a mix of low-key hiking at McKinney Falls and social dinners with a tight-knit group of local creatives. She avoids burnout fiercely, treating her free time as sacred ground where work emails are strictly forbidden unless it's a critical app deployment window.

Work life

At her day job, Amanda navigates the chaotic intersection of engineering constraints and marketing demands, often acting as the bridge between two silos. Her days are fragmented by stand-ups, Figma critiques, and endless stakeholder meetings that eat into deep work time. She relies heavily on Jira for task management and Figma for prototyping, constantly toggling between these tools to maintain context. The pressure to ship features quarterly is constant, yet she finds solace in the tangible output of user testing sessions. Recently, she has had to become more assertive with product managers who want to over-complicate the UX, pushing back to keep interfaces clean and intuitive.

Relationships

She maintains a close bond with her parents in Ohio, calling them every Sunday, and has a small circle of three best friends from college who still live in Austin. Her professional network is robust but mostly digital, connected via Twitter threads and Discord servers rather than local meetups. Her relationship with her contract developer, Mark, is built on mutual respect and clear communication protocols; they treat their partnership as a mini-startup. She feels most influenced by female founders in the tech space who have successfully transitioned from corporate roles to independence.

How they decide

Amanda is a deliberate researcher who values data over hype. She rarely makes impulsive purchases, preferring to read documentation, watch demo videos, and seek peer recommendations before committing. When evaluating options, she weighs long-term maintenance costs against immediate convenience. She trusts her own intuition regarding design aesthetics but defers to technical experts when assessing feasibility. Her decisions are often delayed by a need to gather enough information to feel confident, especially when financial resources or significant time investments are at stake.

How they sound

Her speech is articulate and measured, often using precise terminology like 'user flow,' 'conversion funnel,' and 'technical debt.' She tends to speak in complete sentences with a slight cadence that suggests she is carefully considering her words before speaking. She avoids jargon when talking to non-designers but switches effortlessly to technical slang with her developer. She rarely uses hyperbole, preferring qualifiers like 'probably,' 'likely,' or 'in my experience.' There is a quiet confidence in her tone, avoiding self-deprecation even when discussing failures, and she often ends thoughts with a question to invite further discussion.

Personality traits

  • methodically organized
  • curiously restless
  • pragmatically idealistic
  • collaborative but boundary-setting
  • visually obsessive
  • time-conscious
  • self-reliant
  • empathetic listener
  • detail-oriented
  • growth-minded

Goals

  • Successfully launch her habit-tracking app within the next six months
  • Build a passive income stream that covers 20% of her living expenses
  • Master advanced Swift concurrency patterns through practical application
  • Transition from a corporate ladder climber to an independent creator
  • Maintain a sustainable work-life balance that prevents creative fatigue
  • Establish a reputation in the Austin indie dev community

Problems & frictions

  • Difficulty finding a reliable contractor who understands both technical limits and design nuance
  • Time scarcity causing friction between full-time responsibilities and side-project momentum
  • Uncertainty about pricing strategies for her first monetized feature
  • Fear of building something nobody wants despite strong initial validation
  • Managing the emotional isolation of working alone on a complex technical project
  • Keeping up with rapidly changing iOS SDK updates while maintaining code quality

Values

  • creative control
  • learning by doing
  • balance
  • transparency in collaboration
  • user-centric empathy

Interests

  • habit tracking
  • UI design
  • indie apps
  • minimalist architecture
  • morning running

Media habits

  • Skimmer of Twitter/X for indie dev news
  • Listens to 'Indie Hackers' podcast while commuting
  • Follows specific SwiftUI developers on GitHub
  • Reads 'The Product Podcast' during lunch
  • Scans Reddit r/iOSProgramming for edge cases

Questions & answers

Amanda Weber’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Easyapp (https://www.easyapp.site/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Easyapp 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).

    Today, my contract developer Mark and I are building our habit app from scratch using SwiftUI. We're managing user authentication, in-app purchases, and notifications manually. Comparing that to Easyapp, the 'launch a paid iPhone app from one SwiftUI template' sounds appealing because it seems to pre-build a lot of the foundational plumbing we're currently spending time on. It could definitely speed things up. However, I'd want to understand how customizable the codebase is – we have specific branding and user flow ideas. Also, the pricing isn't immediately clear; is it a one-time purchase or a subscription? If it's a subscription, I'd probably be willing to pay around $49 per month, assuming it significantly reduces our development time and maintenance overhead.
    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.