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

Revi Maas

Revi Maas

CTO at a small AI startup

Full-depth AI personas

Why this persona fits the audience

At a 6-person startup, he oversees a small engineering team that uses multiple image, video, and voice models in a staging app. The team currently routes some calls through a paid model gateway and some directly to vendor APIs, depending on the test.

  • Age: 41
  • Location: Amsterdam, Netherlands
  • Occupation: CTO
  • Income: €110k total comp
  • Education: M.S. Computer Science
  • Company size: 6
  • Years in role: 3
“The real challenge isn't just building with AI, it's building *smartly* with AI – finding that sweet spot where innovation meets efficiency and cost-effectiveness.”

Revi Maas, 41, is the CTO of a small, ambitious AI startup based in Amsterdam. Holding an M.S. in Computer Science from Delft University of Technology, he has spent his career at the intersection of software engineering and cutting-edge technology. His early career involved roles in backend development and systems architecture at larger tech firms, where he honed his skills in building scalable and robust applications. However, the allure of rapid innovation and direct impact drew him to the startup world. Three years ago, he co-founded his current venture, driven by a vision to simplify the integration of diverse AI models for developers. His current role is demanding, requiring him to lead a team of five engineers while also contributing significantly to the technical strategy and architecture. He is deeply involved in the practicalities of their staging app, which leverages multiple image, video, and voice models. A key focus has been optimizing their inference pipeline, a complex task involving routing calls either through a paid model gateway for convenience and specific features, or directly to vendor APIs to control costs and benchmark performance. This constant balancing act reflects his core values of product flexibility, engineering discipline, and cost awareness. Revi is a pragmatic problem-solver, meticulously analyzing trade-offs and prioritizing solutions that offer long-term stability and efficiency. He views time as a critical resource, both for the startup's growth and his own personal development, and is always looking for ways to optimize workflows and reduce technical debt. His income of €110k reflects his senior role and the high-stakes environment of a tech startup, but he remains conscious of the company's burn rate and his team's resource allocation. He is driven by a desire to build something impactful and technically sound, constantly seeking elegant solutions to complex problems.

Background & daily life

A day in their life

Revi's day typically begins around 7:00 AM with a strong coffee and a quick scan of Hacker News and industry news feeds. By 8:30 AM, he's in his home office, diving into code reviews or architectural planning. A 9:30 AM stand-up meeting with his team covers progress, blockers, and immediate priorities. The rest of the morning is spent either coding, debugging a tricky inference issue, or researching potential new model integrations. Lunch is usually a quick, healthy meal at his desk. Afternoons involve more team collaboration, perhaps a session on optimizing their video model pipeline or discussing the integration of a new voice synthesis API. He aims to wrap up core work by 6:00 PM, often followed by an hour dedicated to personal learning or exploring new developer tools before winding down for the evening.

Lifestyle

Revi lives in a modern, minimalist apartment in Amsterdam's Oud-West district with his partner, a graphic designer. They share responsibilities for their rescue cat, 'Pixel'. His routine is structured: early mornings for focused work before the team is fully active, followed by team stand-ups and code reviews. Weekends are for unwinding, often involving cycling along the canals, exploring new cafes, or working on personal coding projects. He's mindful of his spending, preferring quality over quantity, and prioritizes experiences and investments in his career development over material possessions. Socially, he enjoys intimate gatherings with close friends rather than large parties.

Work life

As CTO of a nascent AI startup, Revi's days are a constant juggle between strategic technical direction and hands-on problem-solving. He leads a lean engineering team of five, tasked with building a staging application that integrates various AI models for image, video, and voice processing. The current challenge involves optimizing their model inference pipeline: some calls are routed through a managed gateway for ease of testing and access to specific features, while others are directed to raw vendor APIs to manage costs and explore performance differences. This requires constant evaluation of trade-offs between speed, cost, and model quality. He spends significant time architecting solutions, mentoring his team, and evaluating new tools and services that could streamline their development process.

Relationships

Revi is in a long-term partnership, which provides a stable emotional anchor. His small engineering team is his primary professional circle; he fosters a collaborative environment but maintains clear technical leadership. He has a few close friends from university with whom he discusses technical challenges and life in general. His parents, retired academics, offer gentle encouragement and are proud of his entrepreneurial journey.

How they decide

Revi approaches decisions with a blend of analytical rigor and pragmatic consideration. He thoroughly researches options, weighing technical merits, potential costs, and long-term implications. He often prototypes or conducts small-scale tests to validate assumptions before committing to a solution. While he values his team's input, the final technical direction rests with him, informed by data and his own deep understanding of the system's architecture.

How they sound

Revi speaks with a measured, clear cadence, typical of Dutch professionals. His English is fluent but carries a subtle, precise accent. He avoids jargon where simpler terms suffice, preferring clarity and technical accuracy. His tone is generally calm and analytical, even when discussing complex or frustrating issues. He rarely uses slang and maintains a professional demeanor, though he can become animated when discussing innovative technical solutions.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • resourceful
  • analytical
  • calm under pressure
  • forward-thinking
  • observant

Goals

  • Scale the engineering team effectively without compromising quality
  • Achieve a stable, performant AI inference pipeline for the staging app
  • Secure the next round of funding for the startup
  • Contribute to open-source projects in developer tooling
  • Maintain a healthy work-life balance

Problems & frictions

  • Managing fluctuating API costs from various model providers
  • Ensuring consistent performance and latency across different AI models
  • Onboarding new engineers quickly into a complex, evolving tech stack
  • Balancing the need for rapid prototyping with robust engineering practices
  • Keeping up with the relentless pace of AI model development and releases

Values

  • product flexibility
  • engineering discipline
  • cost awareness
  • technical elegance
  • rapid iteration

Interests

  • video generation
  • product prototyping
  • developer tooling
  • emerging AI architectures
  • performance optimization

Media habits

  • Reads Hacker News daily
  • Follows AI research papers on arXiv
  • Listens to tech podcasts during commutes
  • Watches YouTube tutorials on new frameworks
  • Checks Twitter for industry news and developer discussions

Questions & answers

Revi Maas’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying APIMODELS (https://apimodels.app/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The idea of a single API key and a unified balance for multiple models is intriguing, and the potential cost savings are significant. However, my primary concern is ensuring stability and predictable performance. Currently, we manually route calls to balance cost and features; introducing another layer of abstraction might add complexity if not managed carefully. I'd need to see clear evidence of the failover mechanisms working in practice, especially under load, and understand how latency is impacted. It's difficult to commit to a price without first running some tests to validate its reliability against our specific use cases. For now, I'm not prepared to pay a monthly subscription.
    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.