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

Luke Doyle

Luke Doyle

Independent no-code consultant

Full-depth AI personas

Why this persona fits the audience

Uses a spreadsheet of startup tools and competitor products to prep demos for small clients; he scans daily launch newsletters, maker forums, and directories by hand, and already pays for one paid startup newsletter that he treats as a reference source.

  • Age: 38
  • Location: London, UK
  • Occupation: independent no-code consultant
  • Income: £92k variable
  • Education: MSc in computer science
  • Company size: Sole trader (1 employee: himself)
  • Years in role: 6
“I don't just build apps; I build the architectural logic that allows businesses to survive their first year without burning cash on the wrong stack.”

Luke Doyle is a 38-year-old independent no-code consultant based in London, operating out of a converted warehouse space in Shoreditch. With an MSc in Computer Science from Imperial College London, he pivoted from traditional software engineering six years ago to embrace the agility of low-code platforms. His career was born from a frustration with the rigidity of legacy development cycles and a desire to empower non-technical founders to ship products rapidly. Today, he commands a variable annual income of £92,000, derived from project-based contracts and ongoing maintenance retainers. Luke's workflow is a unique hybrid of high-tech execution and analog organization. He does not rely on automated discovery tools for finding new technologies; instead, he personally curates a massive spreadsheet of startup tools and competitor products. This manual effort involves scanning daily launch newsletters, digging into maker forums, and cross-referencing directories to identify viable solutions for his small clients. He currently pays for a single premium startup newsletter, which he treats not as a subscription service but as a critical reference source, annotating it heavily for internal use. His recent decisions reflect a shift toward standardization; he has begun building a library of pre-configured no-code templates to reduce the time spent on repetitive setup tasks. Despite his technical prowess, he remains deeply skeptical of the 'hype cycle' surrounding new AI wrappers, preferring to validate tools through rigorous, hands-on testing before recommending them. Luke views his time as his most valuable asset, constantly seeking ways to automate his own curation process to reclaim hours for high-value client strategy. He is driven by a need for clear documentation and long-term recall, believing that a well-organized knowledge base is the true competitive advantage in the fast-moving world of SaaS.

Background & daily life

A day in their life

Luke wakes at 6:30 AM, skipping coffee initially to hydrate and review his overnight global market news digest. By 8:00 AM, he is at his standing desk, spending the first hour manually scanning three specific newsletters and five maker forums, noting any new SaaS tools in his master spreadsheet. He flags potential competitors for a client demo due tomorrow. Lunch is a light sandwich eaten while watching a tutorial on a new API integration. The afternoon is dedicated to deep work: coding a dashboard for a fintech startup, meticulously documenting each step in Notion. Late afternoons involve client calls, where he navigates scope creep with polite firmness. Evenings are reserved for family video calls or reading industry whitepapers. Before bed, he reviews his 'long-term recall' folder to ensure all daily learnings are archived, feeling a sense of relief when the system is up to date.

Lifestyle

Luke lives in a minimalist, high-ceilinged loft in East London where order is paramount. His days are punctuated by long walks along the canal to clear his head, often with noise-canceling headphones on. He maintains a rigorous health routine involving swimming three times a week, viewing physical stamina as essential for sustaining long consulting sprints. Financially, he is disciplined; despite a variable income, he automates savings and invests heavily in his own knowledge base rather than luxury goods. Socially, he prefers intimate dinners with fellow founders or solo evenings reading technical papers over loud networking events, valuing depth of conversation over breadth of connections.

Work life

His work revolves entirely around rapid prototyping for early-stage startups who need MVPs delivered in weeks, not months. He spends his mornings manually curating tool stacks in a complex, color-coded Google Sheet, cross-referencing features against client budgets. Afternoons are spent building functional demos using Bubble, Softr, and Make, ensuring every integration is documented. He has no colleagues, only a rotating roster of Slack contacts. The pressure comes from the constant need to stay ahead of market trends; if a new AI wrapper emerges, he must evaluate its viability for his current client within hours. Documentation is his primary deliverable alongside the code itself.

Relationships

He is divorced and has two young children he sees on weekends, whom he tries to keep away from screens. His closest friends are a mix of former university mates and other independent consultants he met at niche meetups. He rarely seeks advice publicly, preferring to test ideas internally first. His mentorship network is informal, consisting mostly of senior engineers he respects online, with whom he exchanges insights via direct messages rather than public comments.

How they decide

Cautiously analytical and evidence-driven. Luke avoids impulsive choices, requiring a period of observation before adopting new workflows. He relies on triangulation: comparing free resources, paid reports, and hands-on testing. Peer validation matters less to him than logical consistency and long-term utility. He is willing to pay for information but only if the return on investment is clear and immediate, treating purchases as capital expenditures on his own efficiency.

How they sound

Luke speaks with a precise, measured cadence typical of a Londoner with academic training. He avoids slang and hyperbole, preferring terms like 'viability,' 'integration points,' and 'scalability.' He pauses frequently to structure his thoughts, often saying, 'Let me check the documentation on that,' rather than guessing. He is never overly enthusiastic about a product unless he has tested it himself. He tends to avoid emotional language, focusing instead on functional outcomes. His tone is professional yet approachable, though he can become terse when discussing inefficiencies or poorly designed user flows.

Personality traits

  • Methodical archivist
  • Quietly confident
  • Deeply skeptical of hype
  • System-obsessed
  • Self-directed
  • Detail-oriented
  • Analytical listener
  • Pragmatic innovator

Goals

  • Establish a proprietary library of reusable no-code templates for faster delivery
  • Transition from hourly billing to retainer-based advisory roles
  • Publish a definitive guide on 'The State of No-Code in 2024' for industry authority
  • Reduce administrative overhead by at least 30% through better automation
  • Build a sustainable passive income stream via digital products
  • Maintain a work-life balance that prevents burnout during peak seasons

Problems & frictions

  • Information overload makes it difficult to distinguish genuine innovation from marketing fluff
  • Manually tracking hundreds of tool changes across different spreadsheets is time-consuming
  • Fragmented data sources prevent quick retrieval of past decisions for future proposals
  • Difficulty in quantifying the value of his curation work to justify higher rates
  • Isolation leads to occasional blind spots regarding emerging community standards
  • Keeping personal documentation systems updated while managing active client deadlines

Values

  • efficiency
  • clear documentation
  • long-term recall
  • intellectual autonomy
  • pragmatism

Interests

  • startup newsletters
  • SaaS directories
  • maker communities
  • low-code architecture patterns
  • analog productivity systems

Media habits

  • Daily manual scan of Product Hunt and BetaList
  • Reading The Hustle and specific niche founder digests
  • Participating in IndieHackers and MakerLog threads
  • Curated RSS feeds for tech Crunchbase updates
  • Listening to deep-dive tech podcasts during commutes

Questions & answers

Luke Doyle’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: the product is a curation of the best new products, every day. Discover the latest mobile apps, websites, and technology products that everyone's talking about. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The challenge isn't discovering new products; I do that manually every day by scanning newsletters and forums. My primary problem is effectively organizing and recalling the information for client use. I've tried extensive spreadsheets and tagging systems, but the sheer volume of information means I spend hours sifting through data to find the right tool for a specific client need. This manual curation and recall process costs me at least 3-4 hours each week, which is time I'd rather spend on strategic client work or developing my own templates.
    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.