Why this persona fits the audience
He co-founded a 5-person SaaS startup in Seattle and manages both Google and Meta campaigns because no one else on the team does paid acquisition. He keeps performance notes in Notion, exports campaign tables to CSV, and uses a free dashboard plus a simple spreadsheet model to decide whether budgets should move.
- Age: 27
- Location: Seattle, WA, USA
- Occupation: Founder / CTO
- Income: $105k
- Education: Bachelor's degree
- Company size: 5 employees
- Years in role: 2.5 years
“If you can't measure it in a spreadsheet, you don't know if it's working.”
Dana Renner, 27, is the co-founder and CTO of a nascent Seattle-based SaaS startup, operating with a lean team of four others. Holding a Bachelor's degree in Computer Science from a state university, Dana entered the entrepreneurial scene three years ago, driven by a desire to build something scalable without the baggage of venture capital expectations. His professional identity is rooted in the intersection of rigorous engineering and pragmatic business operations. Unlike many founders who delegate early, Dana insists on handling the technical infrastructure and the critical path of user acquisition himself. This hands-on approach has defined his recent workflow: he personally manages the company's Google and Meta advertising campaigns, a role typically filled by a specialized growth marketer. He maintains a granular level of control by keeping detailed performance notes in Notion and regularly exporting raw campaign data into CSV files. These exports feed into a custom-built, free-tier dashboard and a personal spreadsheet model where he simulates budget reallocations before executing them. His philosophy centers on 'technical clarity' and 'bootstrapping,' believing that efficiency comes from understanding the full stack of the business, from the database schema to the cost-per-click. Despite his young age, Dana carries the weight of a seasoned operator, making rapid, data-driven decisions that keep the company solvent and growing. He navigates the Seattle tech ecosystem with a mix of skepticism toward flashy tools and a relentless curiosity for AI applications that might automate his manual workflows. His life is a calculated balance of intense coding sessions, strategic ad management, and physical exertion on mountain bike trails, all aimed at building a sustainable, profitable enterprise from the ground up.
Background & daily life
A day in their life
Dana wakes at 5:30 AM, immediately heading out for a 90-minute mountain bike ride on the Burke-Gilman Trail to clear his mind. Back home, he showers quickly and prepares a high-protein breakfast while scanning Hacker News and industry newsletters. By 8:00 AM, he is in his office, starting with the most cognitively demanding coding task, usually tackling a backend bottleneck or refactoring legacy code. Around noon, he switches contexts to marketing, spending 90 minutes analyzing yesterday's ad spend, exporting CSVs from Google Ads and Meta Business Suite, and updating his Notion performance tracker. Lunch is a quick sandwich eaten at his desk while reviewing GitHub pull requests. Afternoons are split between team stand-ups, customer support tickets, and A/B testing ad copy variations. He finishes work by 6:30 PM, often staying late if a critical bug appears. Evenings are reserved for cooking, reading technical papers, or planning the next day's sprints, ensuring he never goes to sleep without a clear plan.
Lifestyle
Dana lives in a modest, slightly cluttered apartment in Capitol Hill, sharing rent with his co-founders to keep overhead low. His mornings are rigid: wake up at 5:30 AM, brew pour-over coffee, and spend an hour mountain biking on local trails before work, using this time to decompress from code. He is health-conscious but not obsessed, prioritizing functional fitness over aesthetics. Financially, he practices strict bootstrapping; every dollar spent on software or ads is scrutinized against potential ROI. Socially, his circle is narrow but deep, consisting mostly of fellow technical founders and weekend hiking buddies. He avoids expensive dining out, preferring cheap, high-quality meals prepared at home or quick lunches while coding.
Work life
As the CTO of a five-person SaaS startup, Dana wears multiple hats, splitting his week between backend architecture and managing paid acquisition channels. Since the team lacks a dedicated marketer, he personally runs Google and Meta campaigns, treating ad spend like a variable in a complex equation. His workspace is dominated by dual monitors displaying terminal windows, Notion dashboards, and raw CSV exports. The pressure is constant; he must balance feature development with customer acquisition, often making critical budget decisions late at night after reviewing performance data. He relies heavily on spreadsheets and free-tier analytics tools, manually reconciling data points to ensure no wasted spend, viewing these manual processes as a necessary filter against noise rather than a burden.
Relationships
Dana is closest to his two co-founders, whom he views as brothers-in-arms; their relationship is built on shared struggle and mutual trust. His parents live in Oregon and visit occasionally, offering financial support only when absolutely necessary, which Dana accepts reluctantly. He has a small group of friends from college who remain active in tech, meeting monthly for dinner to swap stories about scaling struggles. He rarely seeks advice from non-technical mentors, preferring to solve problems through independent research or peer-to-peer networks in online developer communities.
How they decide
Dana operates as a 'slow-fast' decider: he takes extensive time to gather raw data and verify logic (slow), but once the parameters are clear, he executes changes instantly and decisively (fast). He is highly resistant to social proof or hype, relying exclusively on empirical evidence and first-principles reasoning. He prefers options that offer maximum control and transparency, avoiding solutions that obscure underlying mechanics or require long-term contracts. His decision-making process is solitary and iterative, often involving multiple rounds of simulation in spreadsheets before committing resources.
How they sound
Dana speaks in a direct, efficient cadence, favoring precise technical terminology over metaphors. He tends to avoid emotional qualifiers or hedging language, preferring statements like 'The data indicates' or 'The constraint is.' He rarely uses corporate jargon or buzzwords, finding them imprecise. When explaining concepts, he breaks them down into logical steps, often pausing to verify facts mentally. His tone is calm and analytical, even when discussing stressful situations. He avoids small talk, preferring to get straight to the point of any conversation, though he can be surprisingly warm when discussing shared interests like outdoor sports or open-source projects.
Personality traits
- hyper-logical
- resourceful
- stoic under pressure
- skeptical of marketing fluff
- process-oriented
- independent operator
- pragmatic
- detail-obsessed
- direct communicator
- frugal by principle
Goals
- Achieve profitability within the next 12 months without external funding
- Refactor the core API to handle 10x current traffic volume
- Build a self-sustaining organic growth loop to reduce reliance on paid ads
- Develop a robust documentation system for future engineering hires
- Maintain a consistent work-life balance through disciplined routine management
Problems & frictions
- The friction of manually exporting and cleaning CSV data from ad platforms
- Lack of real-time visibility into cross-channel attribution without enterprise tools
- Time scarcity preventing deep focus on architectural improvements
- Difficulty validating hypothesis testing speed due to manual reporting cycles
- Balancing technical debt accumulation with urgent revenue-generating tasks
Values
- speed
- technical clarity
- bootstrapping
- autonomy
- data integrity
Interests
- coding
- mountain biking
- AI tools
- system architecture
- indie hacking
Media habits
- Hacker News daily digest
- Substack newsletters from technical founders
- GitHub trending repos
- r/SaaS and r/startups
- Local trail running podcasts
- Product Hunt for new utility apps