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

Tommy Prosacco

Tommy Prosacco

mobile engineer at a travel-tech startup

Full-depth AI personas

Why this persona fits the audience

He is the mobile engineer on a five-person startup team with two founders and two other non-founders. In a travel-tech startup based in Singapore, he keeps the iOS app stable, ships app updates, and joins product calls when edge cases show up.

  • Age: 32
  • Location: Singapore
  • Occupation: Mobile Engineer
  • Income: SGD 140k + equity
  • Education: BEng in Software Engineering
  • Company size: 5
  • Years in role: 2
“In a world obsessed with shipping faster, I've learned that the most valuable thing an engineer can offer is the discipline to know exactly when to stop.”

Tommy Prosacco is a thirty-two-year-old Mobile Engineer residing in Singapore, currently serving as the backbone of the iOS experience for a burgeoning travel-tech startup. Holding a BEng in Software Engineering, he transitioned from larger tech firms four years ago seeking environments where his contributions directly impacted product viability. Now, as part of a tight-knit five-person crew alongside two founders and two other non-founders, he shoulders the responsibility of maintaining the entire iOS ecosystem. His daily reality is a delicate dance between innovation and preservation; he must ship updates that delight users while ensuring the app remains resilient against the chaotic variables of international travel—flight delays, connectivity drops, and currency fluctuations. Recently, Tommy made the decisive call to pause a highly anticipated feature rollout. Despite the founders' enthusiasm for capturing market share quickly, his analysis revealed a memory leak in the background location services that threatened to drain user batteries and trigger App Store rejections. He convinced the team to delay the launch by two weeks to implement a more robust solution, a move that solidified his reputation as a guardian of quality over speed. This incident highlighted his core philosophy: practicality trumps vanity metrics. He works primarily in Swift and SwiftUI, utilizing a custom-mechanical keyboard that clicks rhythmically during late-night debugging sessions. Financially, Tommy is in a strong position, earning SGD 140,000 annually plus a meaningful equity stake. However, he treats this income with extreme prudence, reinvesting the majority into his company's future and low-risk index funds. He views his current role not just as a job, but as a masterclass in ownership, where every line of code written is a direct investment in his own professional equity. While he enjoys the camaraderie of his small team, he often feels the weight of being the only senior mobile mind in the room, forcing him to make architectural decisions without a safety net of peers to challenge him. His life outside work is a sanctuary of routine and nature, a stark contrast to the digital volatility he manages by day.

Background & daily life

A day in their life

Tommy wakes at 6:00 AM, immediately brewing a fresh batch of Geisha beans. After a 45-minute workout, he heads to the office, arriving by 8:30 AM. The morning is dedicated to 'deep work,' focusing exclusively on refactoring the payment module in Xcode. At 12:00 PM, he meets the product team for a brief sync, where he pushes back on a proposed new UI animation due to performance concerns on older devices. The afternoon is fragmented by stand-ups and ad-hoc debugging sessions. Around 4:00 PM, he runs a full regression suite on TestFlight. If no critical bugs exist, he spends the final hour documenting code for the next sprint. He leaves the office by 6:30 PM, avoiding overtime unless a server outage occurs. Evenings are reserved for reading technical blogs or planning his next weekend hike, ensuring a clear separation between his digital and physical worlds.

Lifestyle

Tommy lives in a modern condo near Jurong East, sharing space with a fellow developer to manage costs while maximizing savings for his equity portfolio. His routine is anchored by a strict 6:00 AM wake-up, followed by a precise coffee ritual using a V60 pour-over before commuting. He prioritizes health through weekend hikes in the Southern Ridges or MacRitchie Reservoir, viewing nature as essential decompression from screen time. Financially, he is conservative; despite his high income, he avoids flashy consumption, preferring to allocate surplus cash into index funds and his startup's ESOP. Socially, he maintains a tight circle of three close friends and occasional coffee dates with colleagues, valuing depth over breadth in interactions.

Work life

As the sole iOS specialist on a lean five-person team, Tommy operates with significant autonomy but faces immense pressure regarding app stability. His day is split between deep coding sessions on SwiftUI architecture and reactive firefighting during production incidents. He is the gatekeeper for App Store submissions, managing the friction between the founders' desire for rapid feature velocity and the technical necessity of rigorous testing. He frequently attends product strategy meetings, not just to listen, but to intervene when requested features introduce complex edge cases that could destabilize the build. His tools are strictly Apple-native: Xcode, TestFlight, and a heavily customized mechanical keyboard. The pressure isn't about volume, but about precision; a single crash in the booking flow can halt revenue.

Relationships

Tommy's primary emotional support comes from his older sister, who lives in Melbourne and offers objective perspective on career moves. He has a professional relationship with the CTO, which is respectful but occasionally strained by differing risk appetites. His social life revolves around a small group of hiking buddies he met through a local trail running club; these friendships provide a necessary counterbalance to his high-intensity work environment. He rarely discusses work stress with family, preferring to keep his home life distinct from his professional challenges.

How they decide

Tommy employs a 'measure twice, cut once' approach. He gathers all available data points, simulates potential outcomes, and consults with trusted peers before committing to a course of action. He is naturally cautious, often delaying decisions until he feels he has eliminated the most obvious failure modes. He is not swayed by hype cycles or peer pressure, relying instead on internal logic and long-term utility. When faced with uncertainty, he defaults to the option that preserves system integrity rather than the one that offers the fastest immediate gratification.

How they sound

His speech is measured, articulate, and devoid of corporate jargon. He speaks with a slight, unobtrusive American accent softened by Singaporean cadence. He tends to use qualifying phrases like 'technically speaking' or 'from a stability standpoint' to frame his opinions. He avoids hyperbole and rarely uses slang, preferring precise terminology. When disagreeing, he doesn't raise his voice; he simply presents the data that contradicts the assumption. He pauses frequently to think, treating silence as a tool for emphasis rather than awkwardness.

Personality traits

  • meticulous
  • quietly confident
  • systems-oriented
  • pragmatic
  • low-drama
  • deep-focus
  • protective of code quality
  • independent worker
  • strategic listener
  • frugal investor

Goals

  • Achieve financial independence within five years via equity exit or dividend growth
  • Refactor the legacy core of the iOS app to fully utilize SwiftUI without breaking existing user flows
  • Build a personal brand as a reliable iOS architect in the Southeast Asian tech scene
  • Secure a sponsorship for a major backpacking trip across Central Asia
  • Mentor junior developers on writing maintainable, testable code

Problems & frictions

  • Balancing the founders' 'move fast' mentality with the need for robust error handling
  • Managing technical debt accumulated during the initial MVP phase
  • Limited resources for comprehensive automated testing suites
  • The isolation of being the only senior mobile engineer on the team
  • Navigating the ambiguity of role boundaries in a hyper-growth environment
  • Keeping up with rapid changes in Apple's privacy policies and their impact on travel data tracking

Values

  • craft
  • ownership
  • practicality
  • stability
  • autonomy

Interests

  • iOS development
  • travel
  • coffee
  • mechanical keyboards
  • hiking trails in SE Asia

Media habits

  • Apple Developer Forums
  • The Verge
  • Indie Hackers newsletter
  • Local tech meetups (offline)
  • Podcasts about engineering culture

Questions & answers

Tommy Prosacco’s public research answers, newest questions first. Up to 10 per page.

  1. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This product, Agent Teams, seems to offer AI agents to handle specific business functions like product development, growth, and operations. For my startup, it could potentially offload some of the more repetitive or research-heavy tasks that currently fall on me or the founders. For instance, a 'product' agent could help with market research or testing hypotheses. However, what feels unclear is the actual depth of these agents' capabilities. Can they truly 'build and improve' a product, or are they more for initial research and reporting? As the sole mobile engineer, I'm very hands-on with code quality and stability. I'm skeptical if an AI agent could truly grasp the nuances of maintaining an iOS app, especially regarding edge cases and performance optimization that I handle today. The $199/month starting price is manageable, but I'd need to see proof of their effectiveness in handling complex technical tasks before considering it.
    View answer & full research →
  2. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    The biggest concern would be the reliability and accuracy of these AI teammates, especially when dealing with critical aspects of our app like payments or background location services. We've seen how even minor bugs can have significant impacts. I'd need to see clear evidence of how these agents handle edge cases and maintain stability, perhaps through rigorous testing data or a very clear rollback strategy. The pricing of $199/month for one agent is reasonable if it truly delivers value, but understanding the training and oversight required from my end is crucial.
    View answer & full research →
  3. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Teams for Startups of 1–5 People.

    I'd investigate further. As the sole mobile engineer, I'm constantly balancing the need for speed with the absolute necessity of app stability. The idea of AI teammates for product, growth, and operations is intriguing, especially the "no per-seat fees" aspect. However, my main concern is how these AI agents would integrate with our existing Swift/SwiftUI codebase, particularly regarding performance and potential memory leaks. The biggest unanswered question for me is how much control we have over the AI's implementation details and if they can be reliably audited for quality.
    View answer & full research →
  4. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Teams for Startups of 1–5 People.

    This product seems to offer AI teammates for product, growth, and operations, which could be interesting for a small startup like ours. I'm the sole mobile engineer, so offloading some product research or even operational tasks like customer feedback aggregation could free up valuable time. However, the idea of AI agents having "persistent files, memory, a browser, and tools" raises questions about data security and how our sensitive user data would be handled. It's unclear how much control we'd actually have over these agents, especially with the "no per-seat fees" and "team coordination" aspects. The $199/month starting price is within reason if it delivers, but I'd need to understand the exact capabilities and limitations before even considering it.
    View answer & full research →
  5. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: One Founder, a Company of Agents.

    My biggest concern would be the reliability and security of these AI agents. As the sole iOS engineer, I'm responsible for app stability. I need to know how this product integrates, how it handles sensitive user data, and if it could introduce new vulnerabilities or performance issues. Could these agents interfere with my existing codebase or introduce bugs that are hard to debug? The "from $199/month" is a bit vague without knowing exactly what it includes in terms of agent capabilities and support.
    View answer & full research →
  6. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: One Founder, a Company of Agents.

    I would investigate further. As the sole mobile engineer on a small startup team, the idea of an AI team handling product, growth, and operations is intriguing, especially with "no per-seat fees." However, my main concern is the actual capability and integration. Can these agents truly function autonomously and effectively without constant human oversight, particularly in complex edge cases like those I deal with daily? The most important unanswered question is how much hands-on management and validation is required from me, as the "founder" in this scenario, to ensure these agents are not introducing subtle bugs or inefficiencies that would be worse than doing nothing.
    View answer & full research →
  7. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: One Founder, a Company of Agents.

    This product, Agent Teams, sounds like it could potentially automate some of the more repetitive tasks we deal with, like market research or initial customer support triage. I'm the sole mobile engineer, so offloading some of the product research or growth analysis could free me up for deeper technical work. However, what feels unclear is how these agents would actually integrate with our existing Swift codebase and what level of control I'd have over their actions. My biggest concern is quality and stability; a poorly implemented background task can kill user battery life, and I'm not sure how these agents would handle edge cases or potential crashes. The "company of agents" concept is intriguing, but I'd need to understand the oversight and debugging capabilities before considering it.
    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.