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

Willard Witting

Willard Witting

solo SaaS founder

Full-depth AI personas

Why this persona fits the audience

He runs a niche compliance SaaS and is currently building the customer onboarding portal with one contract engineer who joins twice a week. Most changes are discussed in live screen-shares, with copy and flow details tracked in Figma, Notion, and a small Airtable base.

  • Age: 34
  • Location: Austin, TX, US
  • Occupation: founder/operator
  • Income: US$180k + equity
  • Education: BA in economics
  • Company size: 1 (part-time contractor)
  • Years in role: 4
“The real magic isn't in the grand vision, it's in obsessively refining the details that make it work for the people who actually use it.”

Willard Witting, 34, is a dedicated solo founder operating out of Austin, Texas, driven by a deep-seated need for autonomy and a belief in the power of efficient execution. After earning an economics degree, he found himself drawn to the burgeoning indie hacking scene, identifying a gap in the market for specialized compliance software for small businesses. He launched his SaaS four years ago and has since bootstrapped it to a comfortable $180k+ annual income, with significant equity in a company he built from the ground up. His personal life is highly structured, reflecting his work ethic; mornings are sacred for focused development, often fueled by meticulously prepared espresso. He views time as his most valuable, non-renewable resource, a principle that guides his decisions about where to invest his energy. Willard isn't chasing hyper-growth at all costs; his current focus is on building a robust, trustworthy product and a sustainable business. He recently made the strategic decision to invest heavily in the customer onboarding portal, recognizing it as a critical bottleneck for user adoption and retention. This involves close collaboration with a single contract engineer, an arrangement he carefully manages through rigorous documentation in Figma and Notion, and frequent, focused screen-sharing sessions. He values clarity and trust above almost all else, believing that these are the foundations of lasting customer relationships, especially in the sensitive field of compliance. His financial habits are pragmatic; he lives relatively frugally, reinvesting most profits back into the business, viewing his equity as the primary long-term reward. He's not looking for external validation or a flashy lifestyle; his satisfaction comes from solving complex problems and building something of genuine value.

Background & daily life

A day in their life

Willard's weekday begins around 6:30 AM with a strong espresso and a review of overnight analytics and support tickets. He dedicates the next 2-3 hours to deep work on the onboarding portal, often coding or refining user flows. Around 10:00 AM, he connects with his contract engineer for a screen-share session to review progress and plan immediate tasks. The afternoon is a mix of customer calls, updating documentation in Notion, and experimenting with product analytics tools. He might squeeze in a short bike ride before dinner, followed by an hour of planning for the following day or reading industry blogs. He aims to disconnect by 9:30 PM.

Lifestyle

Willard lives a disciplined, solo life focused on his business. His Austin apartment is minimalist and functional, prioritizing a dedicated workspace. Mornings begin with a precisely brewed espresso and a quick check of key metrics before a cycling commute or an intensive work block. Evenings are often spent planning the next day or catching up on industry news. He's careful with his money, reinvesting most of his income back into the business, but allows himself small luxuries like high-quality coffee beans and cycling gear. Social life is limited to occasional meetups with a small circle of tech-minded friends.

Work life

As a solo founder of a niche compliance SaaS, Willard wears every hat. His primary focus is product development, currently wrestling with the onboarding portal. He relies heavily on a single contract engineer, coordinating through screen shares and meticulously documenting everything in Figma and Notion. The pressure to deliver a polished, trustworthy product is constant, driving his commitment to clarity and speed. He spends his days toggling between coding, customer support, planning marketing tasks, and analyzing user data, always aiming to optimize workflows and reduce friction for his customers.

Relationships

His primary professional relationship is with his contract engineer, built on clear communication and shared project goals. His closest friends are a few fellow founders he met online, with whom he exchanges tactical advice and commiserates about the startup grind. Family is supportive but distant; he calls his parents weekly but rarely discusses the nitty-gritty of his work.

How they decide

Willard is a research-driven decision-maker, prioritizing data and logical frameworks. He'll meticulously compare options, solicit feedback from trusted sources when necessary, and analyze potential impact on execution speed and long-term viability. He avoids impulsive choices, preferring a measured approach that minimizes rework and maximizes clarity.

How they sound

Speaks with a measured, precise cadence. Avoids jargon when speaking to customers, but uses industry-specific terms with peers. Tends to explain his reasoning thoroughly, focusing on the 'why' and the intended outcome. His tone is generally calm and thoughtful, but can become more direct when discussing technical requirements or critical process steps. He rarely uses filler words and prefers to articulate his thoughts clearly.

Personality traits

  • Analytical
  • Detail-oriented
  • Self-reliant
  • Driven
  • Methodical
  • Skeptical of hype
  • Resourceful
  • Focused
  • Practical

Goals

  • Achieve predictable monthly recurring revenue (MRR) growth
  • Build a reputation for reliability and exceptional customer support in his niche
  • Develop a robust, scalable onboarding process
  • Transition from solo operator to building a small, high-performing team
  • Maintain personal autonomy and control over his work

Problems & frictions

  • Balancing feature development with essential but unglamorous compliance updates
  • Finding and retaining high-quality, reliable contract talent
  • Scaling customer support without a dedicated team
  • The mental overhead of managing all operational aspects
  • Avoiding burnout while pursuing aggressive growth targets

Values

  • autonomy
  • speed of execution
  • clarity
  • customer trust
  • pragmatism

Interests

  • indie hacking
  • product analytics
  • espresso
  • cycling
  • deep work
  • process optimization

Media habits

  • Listens to tech podcasts during commutes and workouts
  • Reads newsletters from indie hackers and product builders
  • Scans Hacker News and Reddit for industry trends
  • Watches YouTube tutorials for new tools
  • Follows key figures in the SaaS space on Twitter

Questions & answers

Willard Witting’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying jambuild (https://jambuild.dev/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The idea of building collaboratively in real-time is intriguing, especially if it truly reduces iteration time. However, my current focus is on the customer onboarding portal, and my contract engineer and I manage our workflow through screen-sharing and detailed documentation in Figma and Notion. We have a well-established, albeit manual, process. I'd need to see how jambuild integrates with or improves upon that specific workflow, particularly for detailed UI/UX design and copy refinement. Without a clear demonstration of how it streamlines my current, documented process, I wouldn't be able to justify trying it out this month. I'd be willing to pay $30 per month for a tool that demonstrably accelerates my onboarding portal development.
    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.