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

Connor Kempe

Connor Kempe

automation studio co-founder

Full-depth AI personas

Why this persona fits the audience

Co-runs a 2-person studio that delivers Docs and Slides add-ons to consulting firms across DACH. He maintains one shared boilerplate for OAuth, web app endpoints, and per-client configuration, then adapts it for each contract.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Co-founder, automation studio
  • Income: €120k
  • Education: MSc Computer Science
  • Company size: 2
  • Years in role: 5
“The elegance is in the system that works reliably, not just the code itself.”

Connor Kempe, 41, is a co-founder of a specialized automation studio based in Berlin, Germany, where he lives with his partner. Holding an MSc in Computer Science, his career path has been driven by a desire to build efficient, robust systems. After several years working as a software engineer in larger tech companies, he felt constrained by corporate bureaucracy and sought greater autonomy. This led him to co-found his current venture five years ago with a former colleague. Their studio focuses on developing custom Google Workspace add-ons, primarily for consulting firms across Germany, Austria, and Switzerland (DACH). Connor is the technical architect and lead developer, responsible for the core infrastructure and codebase. He has meticulously crafted a shared boilerplate that handles essential functionalities like OAuth authentication, web app endpoints, and client-specific configurations. This boilerplate is the foundation for every project, significantly reducing initial setup time. However, a substantial part of his work involves adapting and extending this boilerplate for each unique client contract, a process he finds both challenging and rewarding. He values clean, well-structured code and systems that are easy to maintain and scale. His income of €120k reflects his expertise and the niche market they serve. Recently, he's been exploring ways to further modularize their boilerplate to reduce the per-client adaptation overhead, aiming to increase their capacity without compromising quality. He’s also considering how to better integrate error reporting and logging across their deployed add-ons to proactively identify and address issues before clients report them. This drive for optimization stems from his core belief in building sustainable, trustworthy solutions for his clients, fostering long-term relationships based on reliability and efficiency.

Background & daily life

A day in their life

Connor's typical weekday begins around 7:30 AM with coffee and a quick scan of Hacker News. He's at his home office by 8:30 AM, diving into client work – perhaps debugging an issue with a recent Docs add-on deployment or refining a new feature for a Slides add-on. He dedicates blocks of time to coding, often using his well-organized boilerplate as a starting point, then meticulously customizing it. Lunch is usually a quick, healthy meal prepared at home. The afternoon might involve a video call with his business partner to discuss project status or a client inquiry. He aims to wrap up by 6:00 PM, often spending the evening with his partner, perhaps cooking or watching a documentary, before winding down with a book or some light coding on a personal project.

Lifestyle

Connor lives in a modern, minimalist apartment in Prenzlauer Berg with his partner, a graphic designer. Their routines are fairly structured, with shared cooking responsibilities and a commitment to weekend downtime. He’s not overly concerned with luxury goods, preferring quality over quantity, and his income is primarily directed towards savings, investments, and occasional travel. He enjoys cycling through Berlin's parks and occasionally visits local craft breweries, but his social life is more focused on a small circle of close friends and professional acquaintances rather than large gatherings. Health-wise, he tries to maintain a balanced diet and gets regular exercise through cycling and occasional gym visits.

Work life

As co-founder of a two-person automation studio, Connor's days are a blend of client-facing problem-solving and deep technical work. His primary focus is on building and refining Google Workspace add-ons for consulting firms in the DACH region. He spends a significant portion of his time managing their shared boilerplate code, ensuring it’s robust for OAuth, web app endpoints, and client-specific configurations. The pressure comes from tight project deadlines and the need to deliver highly customized solutions that integrate seamlessly into client workflows. He collaborates closely with his business partner, who handles sales and client communication, allowing Connor to concentrate on the technical execution and system architecture.

Relationships

Connor's closest relationships are with his partner, who provides a grounding influence, and his business partner, with whom he shares a strong professional synergy built on mutual respect for each other's skills. He maintains a small network of former university colleagues who are now in similar tech roles, occasionally exchanging insights. His family lives in a different part of Germany, and contact is primarily through calls and occasional visits.

How they decide

Connor is a methodical and research-driven decision-maker. He weighs options carefully, often creating pros and cons lists, and seeks out technical documentation and community discussions before committing to a path. He values proven solutions and is less swayed by hype, preferring to understand the underlying architecture and long-term implications.

How they sound

Speaks with a clear, measured cadence. His tone is generally calm and professional, even when discussing complex technical issues. He avoids overly casual slang or jargon unless speaking with peers in a technical context. He tends to use precise language and can be quite direct when explaining technical concepts or project constraints. He rarely expresses strong emotions vocally, maintaining a composed demeanor.

Personality traits

  • Methodical
  • Detail-oriented
  • Pragmatic
  • Resourceful
  • Calm under pressure
  • Independent
  • Systematic
  • Patient
  • Reliable

Goals

  • Achieve a stable, predictable revenue stream for the studio
  • Develop a more modular and reusable codebase for future projects
  • Expand the studio's service offering to include Sheets and Forms add-ons
  • Achieve a better work-life balance by optimizing internal processes
  • Become a recognized expert in Google Workspace automation for consulting

Problems & frictions

  • The overhead of adapting the boilerplate for each new client's unique requirements
  • Balancing custom development with the desire for standardized, maintainable code
  • Managing client expectations regarding timelines and feature scope
  • The constant need to stay updated with Google Workspace API changes
  • Finding time for proactive system improvements amidst client project demands

Values

  • independence
  • clean systems
  • client trust
  • efficiency
  • long-term stability

Interests

  • consulting automation
  • Google Workspace
  • micro-agency operations
  • serverless architectures
  • developer productivity tools

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows specific developers on Twitter
  • Subscribes to industry newsletters (e.g., for Google Workspace updates)
  • Watches YouTube tutorials for new tools

Questions & answers

Connor Kempe’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of ShipAddons (https://shipaddons.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make ShipAddons 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, my partner and I handle all of our boilerplate development in-house. We maintain a shared codebase for common functionalities like OAuth and client configurations. ShipAddons seems to offer a pre-built solution for many of these components, which could save us time. However, the main challenge for us is the customization overhead for each client. While ShipAddons might handle the initial setup, I'm concerned about how much adaptation would still be needed. The $49 one-time purchase price is certainly appealing for lifetime access, especially compared to the ongoing costs of other solutions. I would consider paying up to $100 USD on a one-time basis for a product like this, provided it significantly reduces our per-client adaptation effort.
    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.