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

Dave Spinka

Dave Spinka

Co-founder and CEO at an early-stage startup

Full-depth AI personas

Why this persona fits the audience

He co-founds an 8-person SaaS startup in Austin and still handles most onboarding and offboarding himself. New hires get accounts in Google Workspace, Notion, Linear and 1Password, while laptops and badge access are tracked in a shared doc.

  • Age: 29
  • Location: Austin, TX, US
  • Occupation: Co-founder and CEO
  • Income: US$130k/year
  • Education: Bachelor's degree
  • Company size: 8 employees (fully remote/hybrid)
  • Years in role: 2
“If I'm spending more than ten minutes a day on something that doesn't directly make money or ship code, I'm probably doing it wrong.”

Dave Spinka, 29, is the co-founder and CEO of a lean SaaS startup based in Austin, Texas, operating in the competitive B2B space. With a Bachelor's degree in Computer Science from a state university, Dave launched his venture two years ago alongside two former classmates. Currently, the company employs eight people, ranging from senior backend engineers to a junior sales rep. Unlike many CEOs who delegate immediately, Dave retains ownership of the entire employee lifecycle. This includes the gritty reality of onboarding: provisioning Google Workspace accounts, setting up Notion permissions, creating Linear project boards, and distributing 1Password licenses. Conversely, offboarding is equally hands-on; he physically collects laptops, revokes badge access, and meticulously updates a master tracking document to ensure no security gaps exist. This level of micromanagement stems from a core value of frugality and a desire for absolute clarity in operations. While he earns a salary of $130,000, the company's burn rate dictates that every dollar spent on software must prove immediate value. Dave is currently navigating the transition from a 'founder-led' operation to a structured organization, a phase fraught with the risk of process collapse. He is a devout cyclist, finding solace in the rhythmic motion of riding around Lady Bird Lake, which helps him maintain the neurotic stability required to lead a high-growth team. Recently, he rejected a proposal to use a generic HR platform because it lacked the granular control needed for their specific security requirements, opting instead to continue managing the process via spreadsheets and manual checks—a decision that consumes valuable time but ensures total visibility into who has access to what.

Background & daily life

A day in their life

Dave rolls out of bed at 5:30 AM, brews a double-shot espresso, and heads out for a 15-mile bike ride through downtown Austin. By 7:30 AM, he's back at his desk, sifting through overnight GitHub commits and Slack messages from the European engineering team. At 9:00 AM, he leads a stand-up, then pivots to a deep-dive session reviewing a potential hire's portfolio. Lunch is a quick burrito bowl eaten while scrolling through competitor pricing pages. The afternoon is a blur of customer discovery calls and debugging a deployment issue. Around 4:00 PM, the real chaos begins: a contractor is leaving today, so he spends two hours manually revoking API keys, collecting their MacBook Air, and updating the shared Notion sheet. He finishes work at 7:00 PM, grabs a salad, and spends an hour planning the next day's sprint before calling it a night.

Lifestyle

Dave lives in a converted warehouse loft in East Austin, furnished with IKEA pieces he's assembled himself to save cash. He wakes up at 5:30 AM for a 45-minute road ride along the Lady Bird Lake trail before work, using this time to decompress from the mental load of running a company. His diet is strictly functional: high-protein meals prepped on Sundays and expensive espresso shots purchased at local roasters that support the community. He drives a 2018 Toyota Corolla with over 100k miles, refusing to upgrade until the transmission fails, viewing car payments as a tax on his productivity. Socially, he gravitates toward other founders at happy hours where the conversation is 80% deal flow and 20% venting, preferring deep one-on-one coffee chats over large networking events.

Work life

As the sole CEO of an 8-person SaaS startup, Dave wears every hat from CTO to HR. Despite having a team, he personally manages all employee lifecycle events; last week, he manually created Gmail aliases, set up Slack channels, and emailed IT tickets for three new engineers while simultaneously negotiating a vendor contract. His office is a chaotic mix of code reviews and hiring calls, often conducted from his laptop in a corner booth at a noisy coffee shop. The primary pressure is the fear of 'technical debt' in both their product and their internal processes. He spends roughly 30% of his week on administrative overhead—reconciling expenses, updating the master asset spreadsheet, and ensuring no one has lingering access to old servers. He prides himself on being the first to arrive and the last to leave, believing his direct involvement sets the cultural tone.

Relationships

Dave is close with his two co-founders, who serve as his primary sounding board for strategic decisions, though they occasionally clash on pacing. He maintains a tight-knit circle of four friends from college, mostly developers, who meet bi-weekly for dinner. His parents live in Ohio and visit once a year, offering emotional support but little technical advice. He is influenced heavily by the anonymous wisdom found in niche online communities rather than traditional mentors, valuing peer validation from fellow operators who understand the specific grind of early-stage scaling.

How they decide

Dave operates on a heuristic of 'fast trial, slow commit.' He will test a new tool immediately if it solves a bleeding neck problem, often doing a 3-day free trial with full intensity. However, once a solution is adopted, he becomes rigid about sticking with it unless a critical failure occurs, fearing the cost of switching. He relies heavily on reading user reviews and checking integration compatibility before pulling the trigger, but ultimately defers to his own gut feeling about whether a tool feels 'built for humans' rather than just enterprise corporations.

How they sound

Dave speaks with a rapid, clipped cadence typical of someone who values time above all else. He uses startup jargon naturally ('circle back,' 'ship it,' 'blocker') but avoids corporate fluff. His tone is direct and unapologetically practical; he rarely says 'I think' or 'maybe,' preferring definitive statements like 'We need to fix this now.' He gets frustrated by vague answers and tends to interrupt slightly when he senses inefficiency in a conversation. He avoids discussing luxury spending or status symbols, focusing instead on utility, ROI, and process optimization.

Personality traits

  • hyper-organized yet constantly reinventing the system
  • pragmatic optimist
  • hands-on operator
  • direct communicator
  • time-poor but energy-rich
  • skeptical of bureaucracy
  • resourceful
  • competitive in hobbies but collaborative at work
  • anxious about efficiency gaps
  • tech-native

Goals

  • Scale the team to 20 people without losing operational control or culture
  • Achieve profitability within the next 18 months to extend the runway
  • Reduce personal administrative overhead by 50% to focus on product strategy
  • Build a sustainable long-term cycling routine despite travel demands
  • Establish the company as a recognized player in the Austin dev ecosystem
  • Automate all manual HR tasks to eliminate human error in access management

Problems & frictions

  • Maintaining accurate inventory of hardware across a distributed team
  • Ensuring security compliance when offboarding contractors quickly
  • The cognitive load of context-switching between coding and HR admin
  • Finding reliable, low-cost tools that integrate seamlessly with existing stacks
  • Preventing 'ghost accounts' or shared password drift as the team grows
  • Balancing the need for speed with the necessity of documentation

Values

  • speed
  • clarity
  • ownership
  • frugality
  • autonomy

Interests

  • startups
  • cycling
  • espresso
  • product blogs
  • mechanical keyboards
  • urban exploration

Media habits

  • Lobsters.org threads
  • Indie Hackers podcast
  • The Hustle newsletter
  • Local cycling group chats
  • Product Hunt daily digests
  • Twitter/X tech circles

Questions & answers

Dave Spinka’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Handover (https://handoverhq.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Handover 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, I'm manually managing onboarding and offboarding. This includes provisioning accounts in Google Workspace, Notion, and Linear, and tracking hardware like laptops in a shared doc. I'd need Handover to automate the *actual* account revocation, not just create a checklist for someone else to do it. If it could directly interact with apps like Google Workspace, that would be a huge time-saver. Otherwise, it's just another step in my manual process. I'd pay $15 per month, but only if it truly automated revoking access, not just creating a to-do list.
    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.