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

Igino Torrisi

Igino Torrisi

Small-team SaaS builder at a boutique studio

Full-depth AI personas

Why this persona fits the audience

Leads a boutique software studio in Milan with two developers and one designer, and the group is turning internal portal work into a packaged SaaS product; he spends most weeks stitching together auth, payments, and deployment for each new build.

  • Age: 38
  • Location: Milan, Italy
  • Occupation: Studio principal / software product lead
  • Income: €95,000 annual income
  • Education: Engineering degree (Politecnico di Milano)
  • Company size: 4 employees total (including himself)
  • Years in role: 6 years as principal
“We spend too much time building the plumbing and not enough time designing the house.”

Igino Torrisi is the architect and heartbeat of a four-person software studio nestled in the industrial-chic district of Porta Romana, Milan. A graduate of the prestigious Politecnico di Milano with a degree in Computer Engineering, Igino spent his early twenties climbing the ladder at larger enterprise firms in Turin and Rome. However, the rigid bureaucracy and slow pace of development eventually drove him to found his own boutique agency six years ago. Driven by a desire to blend high-end engineering with agile entrepreneurship, he built a team that prioritizes craftsmanship over quantity. Currently, the studio is in a pivotal transition phase, attempting to pivot from purely custom client portals to a proprietary SaaS product based on their accumulated internal tools. Igino is the primary engineer, responsible for the hardest parts of the stack, particularly identity management and financial integrations. While his team handles the visual layer and initial client communication, Igino finds himself bottlenecked by the repetitive nature of setting up OAuth providers, configuring Stripe webhooks, and managing CI/CD pipelines for every single new contract. This redundancy is his greatest frustration; he sees it as a theft of time that could be spent on innovation. He is financially comfortable, earning a salary that reflects his dual role as employee and owner, yet he is fiercely protective of the studio's cash flow, viewing every euro spent on external tools as a necessary trade-off against future engineering hours. His personality is a study in controlled intensity. With high conscientiousness, he maintains rigorous code standards and a pristine documentation library, often clashing gently with clients who demand immediate, untested features. He is not a loud leader; his authority comes from competence and calm demeanor. He is deeply interested in the intersection of software architecture and human behavior, often drawing parallels between React component lifecycles and social dynamics. Despite the pressures of running a business, he maintains a disciplined lifestyle, channeling his stress into marathon training and a curated appreciation for Italian coffee culture. He is currently weighing the long-term viability of maintaining these internal libraries versus adopting third-party solutions, a decision that will define the studio's next fiscal year.

Background & daily life

A day in their life

Igino wakes at 6:00 AM, immediately brewing a double espresso and scrolling through GitHub notifications before checking his email. By 7:30 AM, he is commuting to the studio via metro, listening to an engineering podcast. At 9:00 AM, he leads a stand-up, focusing on blocking issues rather than status updates. The morning is dedicated to deep work: he spends three hours refactoring the authentication module for their upcoming SaaS launch, meticulously testing edge cases in the payment flow. Lunch is a quick panini eaten at the desk while reviewing a PR from a junior dev. Afternoons are fragmented with client calls and design reviews, often requiring him to switch contexts multiple times. By 6:30 PM, he leaves the office, heading to the track for a run. Evenings are reserved for family time or reading about software history, avoiding screens entirely after 9:00 PM to ensure restorative sleep.

Lifestyle

Igino lives in a renovated 1920s apartment in Porta Romana, balancing minimalist Italian design with modern smart-home tech. His routine is anchored by a strict 6:00 AM wake-up for a black espresso at a standing bar nearby before heading to his home office or studio. He runs three times a week, using the city's parks as his gym, which doubles as mental decompression time. Financially, he is conservative; he reinvests heavily into the company but maintains a six-month personal emergency fund. Socially, he prefers deep conversations over large gatherings, often hosting small dinner parties for fellow engineers and architects where the debate shifts between political economy and UI patterns.

Work life

As the sole technical decision-maker, Igino spends his days orchestrating a delicate dance between client demands and product vision. The team of four operates in a tight loop: he codes the core authentication flows while his two junior developers handle frontend components, and the designer refines the user experience. Recently, he has been frustrated by the repetitive nature of rebuilding payment gateways and email verification systems for every new client portal. He views this redundancy as a tax on their creativity. His workdays are filled with context switching—moving from debugging a Stripe webhook failure to reviewing a junior developer's Git commit, always ensuring that the architectural integrity remains uncompromised despite tight deadlines.

Relationships

He shares a stable, supportive partnership with his wife, Elena, who works in non-profit management; she provides the emotional grounding that allows him to take calculated risks in business. His professional circle consists of a tight-knit group of five other studio owners in Northern Italy whom he meets monthly for informal strategy sessions. He looks up to a former professor from Politecnico di Milano whose advice on 'building for longevity rather than speed' still guides his architectural choices. He is less connected to the broader Silicon Valley hype cycle, preferring local, tangible feedback loops.

How they decide

Igino employs a cautious, data-driven approach. He rarely commits to a new tool without running a localized proof-of-concept (POC) that takes at least 48 hours. He values documentation quality and community support over flashy marketing claims. His decisions are peer-influenced; if a trusted colleague vouches for a solution, he moves faster, but he will independently verify the security posture and pricing model before approval. He avoids impulsive purchases and views technology as an investment in time savings rather than a quick fix.

How they sound

His speech is measured, articulate, and devoid of unnecessary jargon unless explaining a specific technical concept. He speaks with a slight Lombard accent but maintains formal professionalism in client settings. In team meetings, he uses direct, concise language, often asking 'What is the cost of this complexity?' rather than 'Is this cool?'. He avoids hyperbolic adjectives like 'amazing' or 'revolutionary,' preferring terms like 'robust,' 'scalable,' or 'maintainable.' When discussing money, he is blunt about ROI and efficiency.

Personality traits

  • methodical
  • pragmatic
  • quietly confident
  • perfectionist about code structure
  • calm under pressure
  • protective of team time
  • disciplined
  • selective
  • analytical
  • culturally aware

Goals

  • Productize their internal tools into a standalone revenue stream within 18 months
  • Reduce boilerplate coding time by 40% to focus on complex business logic
  • Achieve €150k net profit for the studio to secure a partner hire
  • Maintain a sustainable work-week cap of 45 hours to prevent burnout
  • Mentor junior developers to become autonomous problem solvers

Problems & frictions

  • The relentless cycle of rewriting authentication and billing logic for every new project
  • Difficulty finding senior-level talent willing to join a 4-person boutique firm
  • Balancing the need for rapid delivery with the desire for clean, scalable architecture
  • Managing client expectations regarding feature scope versus timeline constraints
  • Personal time fragmentation due to being the primary point of contact for all technical issues
  • Keeping up with the rapidly shifting landscape of cloud provider integrations

Values

  • quality
  • client retention
  • efficiency
  • professionalism
  • technical debt reduction
  • work-life balance

Interests

  • entrepreneurship
  • software architecture
  • espresso culture
  • React ecosystem
  • Italian design history
  • marathon training

Media habits

  • Weekly 'Software Engineering Daily' podcast
  • GitHub trending repos on Sunday mornings
  • Local Milan tech meetups (offline)
  • Twitter/X threads on serverless infrastructure
  • Substack newsletters from European indie hackers
  • Architectural photography blogs

Questions & answers

Igino Torrisi’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.launchfa.st/ (LaunchFast) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core value proposition of skipping auth, payments, and infra setup is immediately clear and directly addresses my biggest frustration. The sheer number of integrations for each component is impressive, and the "swap providers without rewriting" promise is compelling. However, I'd want to see a more in-depth look at the actual codebase structure and how easy it is to customize beyond just swapping providers. The $49 price for a single framework kit seems reasonable for the time savings, but I'd need to do a 48-hour POC to be certain before committing.
    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.