Why this persona fits the audience
Technical cofounder of an 8-person US remote startup selling developer tooling. He often starts outreach from GitHub contributors and LinkedIn profiles, logs contacts in a spreadsheet, and personally verifies emails before small founder-led campaigns. Most lists are built one account at a time for targeted outreach.
- Age: 35
- Location: Seattle, Washington, US
- Occupation: Co-founder / CTO
- Income: US$110k salary equivalent + equity
- Education: M.S. in computer science
- Company size: 8
- Years in role: 3
““If you can't measure it, you can't improve it. And if it's not worth improving, why are we building it?””
Ricardo Thompson, 35, is a co-founder and CTO of a burgeoning developer tooling startup based in Seattle, though the company operates fully remotely. His journey into entrepreneurship was a natural progression from a deep-seated passion for building elegant, efficient systems, honed during his M.S. in Computer Science. He views software development not just as a profession, but as an intricate craft demanding rigor and continuous learning. Early in his career, he contributed significantly to several open-source projects, developing a keen appreciation for collaborative development and the power of well-designed APIs. This background instilled in him a strong preference for 'high signal' interactions and a deep skepticism towards superficial metrics or buzzwords. He co-founded his current venture with a singular focus: to solve a specific pain point he and his peers experienced in managing developer workflows. His current role is a demanding fusion of architecting the company's core technology and engaging directly with potential users. This founder-led outreach is a critical, hands-on activity for Ricardo. He personally identifies promising leads by analyzing GitHub contributor activity and LinkedIn profiles, meticulously logging each prospect in a detailed spreadsheet. Before initiating any outreach, he dedicates time to verifying email addresses and other contact details, ensuring his campaigns are highly targeted and efficient. This methodical approach reflects his core values of technical rigor and independence; he believes in understanding the problem and the potential customer at a granular level before scaling. He lives a focused life, prioritizing deep work and intellectual stimulation over broad social engagement, viewing his current startup phase as a high-stakes optimization problem where every interaction and every line of code counts towards achieving a robust, scalable solution.
Background & daily life
A day in their life
Ricardo's typical weekday begins at 6 AM with coffee and a walk, followed by an hour of focused coding or system review before the rest of the team logs on. From 9 AM to noon, he's in stand-ups, code reviews, or deep-dive technical discussions. Lunch is a quick, healthy meal eaten at his desk while scanning Hacker News. The afternoon is split between architectural planning, debugging complex issues, and his founder-led outreach: meticulously researching individuals on GitHub, cross-referencing LinkedIn, verifying email addresses using internal tools, and logging findings in his CRM spreadsheet. He might have a brief sync with his co-founder. Evenings are for more coding, system monitoring, or catching up on technical reading, often working until 9 or 10 PM before winding down.
Lifestyle
Ricardo maintains a disciplined, almost Spartan, lifestyle. His Seattle condo is functional, with minimal decor, prioritizing utility. Mornings begin at 6 AM with a strong black coffee and a review of overnight system alerts or key GitHub activity. He prioritizes sleep hygiene and avoids excessive social engagements, preferring focused work or solitary pursuits. Financial discipline is key; he lives well within his means, viewing his salary as a baseline and focusing on equity growth. Weekends are for deep-dive personal projects or catching up on technical reading, occasionally punctuated by a quiet dinner with a few trusted engineer friends.
Work life
As CTO and co-founder, Ricardo's days are a blend of deep technical work and the necessary, albeit sometimes tedious, tasks of building a company. He spends significant time architecting new features, optimizing existing codebases, and ensuring the reliability of their developer tooling. A substantial portion of his week is dedicated to founder-led outreach: meticulously researching potential users on GitHub and LinkedIn, verifying contact information, and crafting personalized outreach messages. He feels the pressure of scaling the team and product while maintaining technical integrity, often wrestling with the trade-offs between rapid iteration and robust engineering. His primary tools include VS Code, Docker, Kubernetes, a meticulously organized Google Sheet for CRM, and various internal monitoring dashboards.
Relationships
Ricardo maintains a small, tight-knit circle of friends, mostly fellow engineers and founders he met during his Master's program or through the startup scene. His parents, retired academics, are supportive but don't fully grasp the intricacies of his work. He values intellectual sparring partners and relies on his co-founder for strategic and emotional support, though their communication is often highly technical and direct.
How they decide
Ricardo is a research-heavy, analytical decision-maker. He gathers data, explores technical feasibility, and weighs pros and cons rigorously. He trusts empirical evidence and well-reasoned arguments over gut feelings or trends. For technical decisions, he'll often prototype or run small experiments. For business decisions, he seeks high-signal input from his co-founder and trusted advisors, but the final call is based on his own logical assessment.
How they sound
Speaks with a measured, precise cadence. Avoids hyperbole and marketing jargon. Tends to use technical analogies. His tone is generally calm and analytical, but can become more intense when discussing complex technical challenges or inefficiencies. He's direct and gets to the point quickly, often skipping pleasantries. Uses terms like 'signal-to-noise ratio,' 'optimization,' 'robustness,' and 'scalability' naturally.
Personality traits
- analytical
- methodical
- detail-oriented
- skeptical of hype
- values directness
- prefers async communication
- impatient with inefficiency
- self-reliant
- deeply curious about systems
- pragmatic problem-solver
Goals
- Achieve product-market fit with their core developer tool.
- Build a world-class engineering team that values technical excellence.
- Establish a sustainable, profitable business model without compromising core values.
- Contribute meaningfully to the open-source ecosystem.
- Maintain personal technical expertise and avoid becoming solely a manager.
Problems & frictions
- Finding and filtering genuinely interested, high-signal leads for outreach.
- The time sink of manually verifying contact details for targeted campaigns.
- Balancing rapid feature development with the need for rigorous testing and architectural soundness.
- Hiring engineers who possess both strong technical skills and a good cultural fit.
- The constant pressure to demonstrate growth and traction to potential investors or stakeholders.
- Managing the inherent chaos and unpredictability of early-stage startup life.
Values
- technical rigor
- independence
- high signal
- focus
- autonomy
- efficiency
Interests
- open source
- GitHub
- developer tooling
- startup growth
- performance optimization
- distributed systems
Media habits
- Hacker News
- Ars Technica
- specific tech subreddits
- GitHub trending repos
- technical blogs (e.g., Joel Spolsky, Martin Fowler)
- podcasts on software architecture