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

Claude Kub

Claude Kub

Conservative technical cofounder at a marketplace startup

Full-depth AI personas

Why this persona fits the audience

He is the technical cofounder in a 4-person vintage-furniture marketplace in Bristol, where he maintains a custom Next.js storefront, a Vendure backend, and manual supplier feeds from two warehouses.

  • Age: 33
  • Location: Bristol, UK
  • Occupation: Technical cofounder
  • Income: £65k–£90k salary + equity
  • Education: BSc software engineering
  • Company size: 4 people (including founders)
  • Years in role: 4 years
“There's a solid way to build things, and then there's the 'quick fix' that bites you later. I prefer the former, even if it takes a bit longer to get there.”

Claude Kub, 33, is a cofounder and the technical architect behind a burgeoning vintage furniture marketplace based in Bristol. Holding a BSc in Software Engineering from a reputable UK university, his career path has been one of diligent progression through roles as a junior developer, then a senior engineer, before co-founding his current venture four years ago. He possesses a deeply ingrained sense of craftsmanship, evident not only in his meticulous approach to code but also in his off-hours pursuit of woodworking. His conservative nature manifests in a preference for stable, well-understood technologies – hence the choice of Next.js and Vendure – over the latest fleeting trends. He champions control over his codebase and infrastructure, which is why he’s maintained a custom setup, including manual supplier feeds, despite the inherent friction. This hands-on approach stems from a fundamental belief in understanding every layer of the system he’s responsible for. His income, a mix of salary and equity, reflects his significant contribution but is managed with a frugal mindset; he views money as a tool for security and enabling future projects, both professional and personal, rather than a means for ostentatious display. He recently pushed back against a cofounder's suggestion to rapidly adopt a new, unproven third-party inventory API, advocating instead for a phased internal integration strategy to mitigate risks. This decision, while saving potential headaches, extended the timeline for a desired feature, highlighting his pragmatic, albeit sometimes slow-moving, approach to innovation. He feels the pressure of time most acutely when operational issues pull him away from strategic development, viewing each unaddressed technical debt as a ticking clock.

Background & daily life

A day in their life

Claude’s weekday typically begins around 7:00 AM. After a quick breakfast and checking personal finance apps, he’s at his desk by 7:30 AM, often reviewing overnight logs or responding to urgent messages before the rest of the team logs on. The morning is usually dedicated to focused coding on a new feature or tackling a persistent bug, punctuated by short syncs with his cofounders. Lunch is a simple affair, eaten at his desk while catching up on Hacker News. The afternoon might involve diving into the intricacies of the Vendure backend, debugging supplier feed integration issues, or planning the next deployment. He tries to wrap up by 6:00 PM, but sometimes stays later if a critical issue arises. Evenings are reserved for unwinding, perhaps some light reading on woodworking techniques or a brief walk.

Lifestyle

Claude lives a fairly predictable life in a rented terrace house in Southville, Bristol, with his partner. He values routine and efficiency, often meal-prepping on Sundays to streamline his weekdays. His income is comfortable, but he's naturally frugal, preferring to invest in quality tools for his woodworking hobby or save for a future down payment rather than on lavish purchases. Weekends often involve either a visit to a local pub with his partner, a woodworking project in their small garden shed, or watching Bristol City play football. He’s not one for spontaneous nights out, preferring planned social engagements.

Work life

As technical cofounder, Claude is the sole custodian of the company's digital infrastructure. His days are a mix of deep-focus coding on the Next.js frontend and Vendure backend, troubleshooting supplier data issues, and architecting minor infrastructure improvements. He feels the pressure of being the primary technical bottleneck, especially with manual supplier feeds requiring constant vigilance. Coworkers (fellow founders) are generally supportive, but he often has to translate technical constraints into business terms, a process he finds draining. The constant need to 'ship' features while maintaining stability is his primary daily challenge.

Relationships

Claude is in a stable, long-term relationship with his partner, who provides a grounding influence and a different perspective on problem-solving. His cofounders are colleagues he respects but doesn't socialize deeply with outside of work. His closest friendships stem from university or his early career, and he maintains contact through occasional meetups or online discussions.

How they decide

Claude is highly analytical and research-driven when it comes to technical decisions. He meticulously weighs pros and cons, often creating spreadsheets or flowcharts to visualize options. For non-technical matters, he relies on data and logic, consulting his partner or trusted colleagues for input but ultimately making choices based on his own assessment of risk and efficiency. He is generally risk-averse, preferring incremental improvements over radical changes unless a clear, quantifiable benefit exists.

How they sound

Speaks with a measured, precise cadence. Uses technical jargon naturally but is capable of simplifying it when necessary, though sometimes with a slight tone of exasperation. Avoids hyperbole and buzzwords. His tone is generally calm and even, betraying frustration through subtle pauses or a slightly more clipped delivery rather than raised volume. He’s not overly chatty and prefers direct communication.

Personality traits

  • Methodical
  • Detail-oriented
  • Resourceful
  • Pragmatic
  • Reserved
  • Patient
  • Independent
  • Slightly cynical about hype

Goals

  • Achieve sustainable profitability for the marketplace
  • Build a robust, scalable technical foundation for future growth
  • Develop mastery in specific areas of backend and frontend architecture
  • Eventually own a small workshop space for woodworking projects
  • Maintain a healthy work-life balance without sacrificing company progress

Problems & frictions

  • The fragility of manual supplier data integration
  • Balancing feature development with essential maintenance and bug fixes
  • Limited bandwidth for strategic technical planning due to operational demands
  • The inherent limitations and performance quirks of managing two warehouse feeds manually
  • Communicating complex technical trade-offs to non-technical cofounders
  • The constant pressure to optimize performance and reduce infrastructure costs

Values

  • control
  • frugality
  • craftsmanship
  • shipping

Interests

  • vintage furniture
  • Node.js
  • woodworking
  • football

Media habits

  • Reads Hacker News daily for tech trends and discussions
  • Follows specific Node.js and JavaScript developers on Twitter/X
  • Listens to podcasts on technology and business during commutes
  • Watches YouTube tutorials for woodworking techniques
  • Occasional browser of Reddit's r/woodworking and r/cscareerquestions

Questions & answers

Claude Kub’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Storecraft (https://storecraft.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Storecraft 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).

    Today, we're managing our supplier feeds manually, which is, frankly, a constant source of friction. I'm the one wrestling with the data coming in from two warehouses. Storecraft's promise of a 'Commerce As Code' backend with flexibility in databases and cloud deployment sounds intriguing, especially the extensibility. However, I'd need to see how it handles real-time, complex supplier integrations and if it can replace the fine-grained control I currently have over our Vendure backend and custom Next.js storefront. The manual process is painful, but it's predictable. A sudden shift to a new system needs to demonstrate a clear, quantifiable improvement in reliability and a significant reduction in my operational overhead. I wouldn't pay more than $50 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.