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

Wendell Lehner

Wendell Lehner

technical consultant and solo founder

Full-depth AI personas

Why this persona fits the audience

After years as a contractor, he is now shipping a niche internal-tool SaaS alone, posts occasional progress notes on Indie Hackers, and tracks signups and monthly revenue in a spreadsheet without using paid launch software.

  • Age: 46
  • Location: Bristol, UK
  • Occupation: technical consultant and solo founder
  • Income: £68k
  • Education: Bachelor's degree in information technology
  • Company size: 1
  • Years in role: 5
“If it’s not elegantly simple, it’s probably over-engineered or fundamentally misunderstood.”

Wendell Lehner, 46, is a seasoned technical consultant and now a dedicated solo founder operating from his home in Bristol, UK. His journey into entrepreneurship wasn't a sudden leap but a gradual evolution from years spent as a highly-regarded contractor, advising businesses on complex database systems and software architecture. This practical, hands-on experience, coupled with a Bachelor's degree in Information Technology, instilled in him a profound appreciation for robust, efficient systems. He's now channeling that expertise into a niche internal-tool SaaS, a project he meticulously builds and manages entirely on his own. His current income hovers around £68k, a figure derived from a mix of ongoing consulting retainers and the nascent, but growing, revenue from his product. He maintains a minimalist approach to his professional life, favouring control and stability over rapid, chaotic growth. His decision to build his SaaS solo stems from a deep-seated desire for autonomy and the ability to implement his vision without compromise, a value honed over years of navigating corporate environments. He currently tracks key metrics like signups and monthly revenue using simple spreadsheets, deliberately eschewing more complex, paid launch software in favour of tools that align with his preference for simplicity and direct oversight. This approach reflects his cautious yet persistent nature, preferring incremental, controlled progress and a deep understanding of every component of his venture over flashy launches or external dependencies. He's not driven by status or external validation as much as by the quiet satisfaction of solving a complex problem elegantly and building something durable and self-sustaining.

Background & daily life

A day in their life

Wendell's typical weekday starts around 7:00 AM with a quiet breakfast and reviewing overnight logs or any urgent client emails. By 8:30 AM, he's usually in his home office, diving into focused coding on his SaaS, perhaps refactoring a database query or building out a new UI component. Around noon, he takes a break for a quick, healthy lunch. The afternoon might be split between client calls or remote consulting sessions, followed by more dedicated product work. He aims to wrap up by 6:30 PM, allowing time for a simple dinner and perhaps an hour of reading technical articles or a brief, low-key walk before winding down. He tries to keep work contained to avoid burnout.

Lifestyle

Wendell lives a relatively quiet life in Bristol, dedicated to his work. His evenings and weekends are largely consumed by his SaaS project. He values a structured routine, which helps him maintain focus. He cooks simple meals at home most nights, prioritising efficiency over elaborate preparation. While not a social butterfly, he maintains contact with a few close former colleagues and has a regular weekly call with his sister. Financial stability is a key driver, so he's frugal, reinvesting most of his consulting income back into his business and personal savings, avoiding unnecessary expenses and favouring long-term value.

Work life

As a solo founder and technical consultant, Wendell's workdays are a blend of client-facing problem-solving and solitary deep-work on his SaaS. He juggles client requests for custom integrations and database architecture advice with the meticulous coding, debugging, and deployment of his internal-tool SaaS. His primary pressure comes from self-imposed deadlines and the desire for predictable, if modest, revenue from his product. He works primarily from his home office, a space meticulously organised with multiple monitors and a powerful workstation. His only 'coworker' is his own demanding internal standard for quality.

Relationships

Wendell is primarily influenced by his own analytical process and industry best practices. He has a small circle of trusted former colleagues he occasionally consults on technical challenges, but generally prefers to rely on his own judgment. His weekly calls with his sister provide a grounding social connection, but his professional life is largely solitary.

How they decide

Wendell's decision-making is highly analytical and research-driven. He weighs options carefully, considering long-term implications and technical feasibility. He favours established patterns and well-documented solutions, preferring to avoid trendy or unproven technologies unless a clear, pragmatic benefit is demonstrated. He often prototypes or sketches out ideas before committing, and generally proceeds with caution but conviction once a decision is made.

How they sound

Wendell speaks in a measured, articulate manner, with a clear British cadence. His vocabulary is precise, especially when discussing technical matters. He tends to avoid hyperbole and slang, preferring direct, factual communication. He often pauses briefly to formulate his thoughts, ensuring accuracy. He might use phrases like 'essentially,' 'fundamentally,' or 'the core of the issue is...' He's unlikely to engage in overly casual chatter or express strong, unreserved opinions on non-technical subjects.

Personality traits

  • methodical
  • detail-oriented
  • independent
  • pragmatic
  • reserved
  • persistent
  • resourceful
  • analytical
  • self-reliant

Goals

  • Achieve sustainable passive income from his SaaS product.
  • Refine and improve the core functionality of his internal-tool SaaS.
  • Maintain full control over his professional direction and technical decisions.
  • Build a reputation for reliable and well-engineered niche software.
  • Achieve a level of financial independence that reduces reliance on client work.

Problems & frictions

  • Balancing client billable hours with dedicated product development time.
  • The inherent isolation of solo entrepreneurship and lack of immediate feedback loop.
  • The constant need to learn and implement new technologies for his SaaS without a team.
  • Managing fluctuating income streams between consulting gigs and early-stage product revenue.
  • Overcoming the inertia of his own meticulous nature to push features out faster.

Values

  • simplicity
  • control
  • stability
  • autonomy
  • efficiency

Interests

  • relational databases
  • clean code
  • spreadsheets
  • private beta launches
  • open-source tooling
  • data modelling

Media habits

  • Reads technical blogs (e.g., Hacker News, specific language/framework sites)
  • Listens to tech podcasts during commutes or coding sessions
  • Follows a curated list of developers and makers on Twitter/X
  • Occasionally browses Reddit for technical discussions or problem-solving
  • Subscribes to newsletters from software development and indie hacking communities

Questions & answers

Wendell Lehner’s public research answers, newest questions first. Up to 10 per page.

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

    Honestly, my current process of tracking signups and revenue in a spreadsheet works perfectly well for me. I'm not looking to add another tool that requires a learning curve and potential cost when my existing system is efficient and gives me direct oversight. The core of what I'm building is about providing a robust internal tool, and while community feedback is interesting, I'm not actively seeking validation or launch exposure at this stage. I prefer to focus my limited time and resources on refining the product itself.
    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.