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

Samuel Sandoval Juárez

Samuel Sandoval Juárez

Product manager and side-project founder at a small team

Full-depth AI personas

Why this persona fits the audience

Works in a 5-person startup in Barcelona and is also building a small side app with two colleagues on evenings and weekends. Keeps the feature map in spreadsheets, uses Lovable for quick prototypes, and coordinates the next build steps with the team.

  • Age: 32
  • Location: Barcelona, Spain
  • Occupation: Product manager
  • Income: €58k
  • Education: Master's degree in business analytics
  • Company size: 5 employees (startup)
  • Years in role: 4 years
“If I can't visualize the next three steps, I can't commit to the timeline.”

Samuel Sandoval Juárez is a 32-year-old Product Manager navigating the precarious waters of a five-person startup in Barcelona while simultaneously acting as the architect of a nascent side venture. Born into a middle-class family in Valencia, he developed an early affinity for systems and logic, eventually earning a Master's degree in Business Analytics from a top university in Madrid. This academic background instilled in him a relentless drive for data-driven decision-making, a trait that now defines his professional identity. Currently, he earns €58,000 annually, a figure he considers fair compensation for the intense responsibility he shoulders, yet it leaves little room for financial error. His life is a study in duality: by day, he manages the delicate ecosystem of a lean startup, where a single misstep in resource allocation could jeopardize the company's survival. By night, he transforms into a founder, collaborating remotely with two former classmates to build a micro-SaaS application. Samuel's workflow is a testament to his pragmatism and his struggle with the limitations of current tools. He refuses to adopt expensive enterprise software, viewing it as unnecessary bloat for a team of his size. Instead, he clings to Google Sheets, meticulously organizing feature maps, user stories, and dependency trees. While he embraces the power of AI development tools like Lovable, Bolt, and Cursor, he finds himself constantly manually translating his spreadsheet logic into prompts for these agents. He recently made the critical decision to pause hiring a dedicated project manager for his side project, choosing instead to absorb the administrative burden himself to preserve cash. This choice has led to a significant time deficit, forcing him to sacrifice sleep and social events to keep the momentum going. Despite the exhaustion, Samuel remains optimistic, driven by the belief that execution is the ultimate differentiator in a world saturated with ideas. He is currently evaluating ways to automate his planning process, seeking a solution that respects his need for visual clarity without disrupting his established, albeit messy, workflow.

Background & daily life

A day in their life

Samuel wakes up at 6:30 AM, skipping breakfast to cycle 20 minutes to his office in the Poble Sec district. His morning starts with checking emails and updating his master spreadsheet, a ritual he performs before any human interaction. The workday is a blur of meetings: a 10-minute sync with the CEO, a 45-minute design review with the UX lead, and endless Slack interruptions. Lunch is usually a quick sandwich eaten at his desk while reading a thread about Lovable updates. Afternoons are reserved for deep work, attempting to map out the next sprint's user stories, often getting stuck trying to translate abstract requirements into precise JSON structures for his team. By 6:30 PM, he heads home, grabs a quick dinner, and shifts gears to his side project. The evening is spent debugging a prototype built with AI, coordinating with his remote colleagues, and manually updating the same spreadsheet he hates so much. He tries to disconnect by 10:30 PM, though the glow of his laptop screen often lingers in his dreams.

Lifestyle

Samuel lives in a sun-drenched, slightly chaotic apartment in the Gràcia neighborhood of Barcelona, filled with plants and whiteboards covered in half-finished diagrams. He cycles to work daily regardless of the weather, maintaining a routine that balances physical activity with his sedentary job. His financial habits are disciplined; he tracks every euro spent on software subscriptions and prioritizes cash flow, often delaying non-essential upgrades until the end of the quarter. Socially, he is grounded in a tight-knit circle of fellow entrepreneurs and developers who meet occasionally at casual tapas bars to swap stories about server costs and burnout. He values his weekends fiercely as the only time he can fully detach, though his mind often drifts back to the side project's roadmap before sleep.

Work life

At his 5-person startup, Samuel acts as the operational glue, bridging the gap between vague executive ideas and developer implementation. His days are fragmented: morning stand-ups, deep work on Jira tickets, and constant context switching to answer Slack queries. He relies heavily on Google Sheets for feature mapping because existing paid tools feel too bloated for their current scale. Recently, he has been coordinating with his two side-project colleagues via late-night Zoom calls, manually converting their brainstorming sessions into structured prompts for Lovable. The pressure is constant; one bug or missed deadline feels like a existential threat to the company's runway, forcing him to make rapid decisions on scope reduction rather than feature expansion.

Relationships

Samuel is married to Elena, a graphic designer who provides a grounding counterbalance to his analytical nature. They influence each other's views on aesthetics versus functionality. His closest professional allies are his two side-project partners, Mateo and Sofia, whom he trusts implicitly but finds difficult to manage due to their differing paces. He maintains a distant but respectful relationship with his parents in Valencia, who view his tech career with pride but confusion. He rarely seeks advice from older industry veterans, preferring to learn directly from peer-to-peer online communities where the noise is lower and the signals are stronger.

How they decide

Samuel operates on a 'verify then deploy' model. He is not impulsive; he requires evidence of utility before committing resources, often running small-scale experiments or free trials. However, he becomes impatient with lengthy sales processes or overly theoretical comparisons. His decisions are heavily influenced by practical constraints—specifically cost and time-to-value—and peer validation from trusted developer circles. If a solution looks elegant on paper but requires a steep learning curve, he will likely reject it in favor of something that integrates immediately with his existing workflow.

How they sound

Samuel speaks with a calm, measured cadence, typical of someone used to explaining complex logic to non-technical people. He avoids hyperbole and emotional language, preferring terms like 'scope,' 'iteration,' and 'ROI.' He naturally switches between English and Spanish (Catalan) depending on his audience, often using English technical jargon even in Spanish sentences. He tends to pause frequently to gather his thoughts, especially when discussing budget or timelines, and rarely says 'I don't know' without immediately offering a hypothesis or a plan to find the answer. He is polite but direct, cutting off rambling explanations with a gentle 'let's get to the point.'

Personality traits

  • Hyper-organized but prone to spreadsheet hoarding
  • Quietly ambitious
  • Resourceful under budget constraints
  • Collaborative without being dominant
  • Skeptical of over-engineering
  • Prone to working through dinner
  • Values visual clarity over abstract theory
  • Highly adaptive to new tech stacks
  • Detail-oriented regarding data integrity
  • Balanced between work urgency and weekend rest

Goals

  • Launch the side project to generate passive income within 18 months
  • Transition from manual spreadsheet tracking to an automated product visualization tool
  • Reduce technical debt in the main startup codebase by refactoring legacy modules
  • Build a sustainable work-life balance where weekends are truly device-free
  • Establish a reputation as a pragmatic leader in the Barcelona tech scene
  • Save enough capital to take a sabbatical for travel after the next funding round

Problems & frictions

  • The mental friction of maintaining complex spreadsheets that never sync with reality
  • Difficulty communicating the 'why' behind technical decisions to non-technical stakeholders
  • Time scarcity leading to decision fatigue by 6 PM every evening
  • The risk of the side project bleeding into personal life and causing burnout
  • Uncertainty about which AI coding tool will remain stable long-term
  • Struggling to find clear documentation for integrating new AI agents into legacy systems
  • Feeling isolated in decision-making when the core team is too small to debate nuances
  • Managing budget constraints while trying to maintain high-quality output

Values

  • execution
  • teamwork
  • cost discipline
  • clarity
  • efficiency
  • pragmatism

Interests

  • Lovable
  • product roadmaps
  • startup side projects
  • spreadsheets
  • AI coding agents
  • urban cycling

Media habits

  • Reading TechCrunch and local Catalan tech blogs during lunch
  • Listening to productivity podcasts while commuting by bike
  • Scanning Twitter/X threads about AI dev tools late at night
  • Watching YouTube tutorials on prompt engineering for Cursor
  • Following specific indie hacker communities on Discord
  • Subscribing to newsletters from niche SaaS founders

Questions & answers

Samuel Sandoval Juárez’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Flowmaps (https://flowmaps.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Flowmaps 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 using spreadsheets to map out features and dependencies for both my startup and my side project. I also use Lovable for quick prototypes. Flowmaps seems like it could be useful because it automates the planning process, which is a huge time sink for me. I'm currently spending too much time manually translating my spreadsheet logic into prompts for AI tools. The idea of it suggesting features I might forget and generating a step-by-step plan for my AI builder is very appealing. I'd be willing to pay up to $12 per month for a lifetime deal if that early bird offer is still available, otherwise, I'd consider paying $19 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.