Why this persona fits the audience
He is the technical co-founder of a four-person SaaS in New York and maintains a Metabase dashboard that joins Stripe revenue, product events, and database tables for weekly reviews. The team uses that same view for MRR, conversion, and basic cohort checks instead of a dedicated subscription analytics tool.
- Age: 33
- Location: New York, US
- Occupation: Co-founder and CTO
- Income: $160k variable personal income
- Education: Master's degree in computer science
- Company size: 4
- Years in role: 4
“The beauty of a well-structured database is that it tells you exactly what's happening, if you know how to ask the right questions.”
Clarence Okuneva, 33, is the co-founder and CTO of a burgeoning four-person SaaS company based in New York City. Holding a Master's degree in Computer Science, his career trajectory has been defined by a relentless pursuit of technical excellence and control. From an early age, he was fascinated by how systems worked, spending countless hours dissecting electronics and writing small programs. This innate curiosity led him to pursue a formal education in computer science, where he excelled in database theory and distributed systems. Upon graduating, he co-founded his current venture, driven by a vision to solve a specific problem in the SaaS analytics space. His technical leadership is characterized by a deep commitment to precision and efficiency. He views his role not just as a manager of technology, but as its primary architect and guardian. This philosophy is most evident in his creation and maintenance of a custom Metabase dashboard. This tool, which he built himself, meticulously joins Stripe revenue data, product event logs, and various database tables. It serves as the single source of truth for weekly reviews of key metrics like MRR, conversion rates, and cohort performance. Clarence’s decision to rely on this self-built solution over off-the-shelf subscription analytics tools stems from a desire for granular control and a deep-seated belief in his own technical capabilities. He trusts the integrity of the data he directly manages and the logic he has embedded within his queries. This approach reflects his core values: precision in execution, absolute control over critical systems, and maximum efficiency in resource utilization. His personal life mirrors this methodical approach. He lives a structured existence, optimizing his routines and environment for productivity and order. His apartment is a testament to his interest in home automation, filled with devices he has programmed himself to streamline daily tasks. While he values his professional achievements, he remains grounded, viewing his variable income as a challenge to be managed with prudence, prioritizing reinvestment in the company and building a secure financial future. He is driven by the intellectual challenge of building scalable systems and the satisfaction of creating elegant, efficient solutions.
Background & daily life
A day in their life
Clarence's weekday typically begins around 7:00 AM with a quick check of system alerts and overnight logs, often from his phone while his coffee brews. After a focused coding session for a couple of hours, he joins his team for a brief stand-up meeting at 9:30 AM. The rest of his morning is a mix of code reviews, architectural discussions, and addressing any urgent technical issues. Lunch is usually a quick, healthy meal he prepared the night before. Afternoons are often dedicated to strategic planning, investor updates (when necessary), and refining the Metabase dashboard's queries. He usually wraps up his workday around 6:30 PM, but often logs back in for an hour or two in the evening to work on personal projects or address late-breaking issues.
Lifestyle
Clarence lives in a meticulously organized one-bedroom apartment in Brooklyn, which he's gradually outfitting with smart home devices he's programmed himself. His evenings often involve tinkering with his home automation setup or diving into technical documentation. Weekends are a mix of catching up on industry news, occasional meetups with fellow tech founders, and quiet nights in. He prioritizes efficiency in his personal life, meal-prepping on Sundays to save time during the week. Financial discipline is key; he views his variable income as a challenge to manage prudently, focusing on reinvesting in the company and building a solid personal runway.
Work life
As CTO and co-founder, Clarence is deeply hands-on, architecting the core product and managing the technical infrastructure. His days are a blend of coding, reviewing pull requests, and strategic technical planning. The pressure to scale efficiently is constant, especially with a lean team. He spends a significant portion of his time ensuring data accuracy and system stability, which led him to build and maintain their internal Metabase dashboard. He trusts his own creation implicitly for key business metrics, seeing it as a testament to his technical prowess and a way to maintain direct control over critical insights.
Relationships
Clarence maintains a small, close-knit circle of friends, mostly fellow engineers and founders he met during his Master's program or through industry events. His relationship with his co-founders is professional and collaborative, built on mutual respect for each other's expertise. He occasionally seeks advice from a former professor who now runs a successful tech company, valuing his strategic perspective.
How they decide
Clarence is highly analytical and research-driven, preferring to gather as much data as possible before making a decision. He values evidence and logical reasoning, often building small prototypes or running internal tests to validate hypotheses. He is not easily swayed by trends or peer pressure, trusting his own technical judgment and empirical findings above all else.
How they sound
Speaks with a measured, precise cadence. Avoids jargon when speaking to non-technical people but doesn't shy away from technical terms with peers. His tone is generally calm and rational, rarely raising his voice. He tends to use phrases like 'from a data perspective,' 'empirically,' and 'logically speaking.' He avoids hyperbole and emotional language.
Personality traits
- analytical
- detail-oriented
- methodical
- independent
- resourceful
- pragmatic
- reserved
- driven
Goals
- Achieve sustainable, profitable growth for the SaaS company.
- Build a robust, scalable technical architecture that can support future expansion.
- Become a recognized expert in his niche within the SaaS analytics space.
- Maintain a high degree of technical autonomy and control over the product's direction.
- Develop a more predictable personal income stream as the company matures.
Problems & frictions
- Balancing the need for rapid feature development with maintaining code quality and system stability.
- The inherent limitations and potential for error in a self-built dashboard as data complexity grows.
- Finding time for deep technical work amidst the demands of co-founder responsibilities.
- Ensuring the entire team is aligned on data interpretation when relying on a single, internally managed dashboard.
- The constant pressure to optimize resource allocation with a small team and budget.
Values
- precision
- control
- efficiency
- data integrity
- autonomy
Interests
- databases
- SaaS metrics
- home automation
- distributed systems
- performance optimization
Media habits
- Hacker News
- Ars Technica
- TechCrunch
- Substack newsletters on engineering leadership
- Podcasts on deep tech and startups