Daryl Jast

Why this persona fits the audience

He runs a pre-scale SaaS in London and rebuilds the marketing site every few months using Webflow, Figma, and an AI code assistant. He compares free templates, spreadsheet-tracked asset links, and occasional paid downloads while keeping his spend tight as the product is still small.

• Age: 38
• Location: London, UK
• Occupation: Founder, B2B SaaS
• Income: £110k
• Education: MSc Computer Science
• Company size: 1 (solo)
• Years in role: 4

“I don't need more features; I need a system that stops me from having to think about the same problem twice.”

Daryl Jast is a 38-year-old London-based founder who carved out a niche in the B2B SaaS space four years ago after leaving a senior engineering role in fintech. Holding an MSc in Computer Science, he possesses the technical depth to build complex systems but the entrepreneurial drive to prioritize speed-to-market over perfection. Currently operating as a solo founder, Daryl runs a pre-scale SaaS product focused on streamlining workflows for small teams. His approach to business is defined by extreme capital discipline; he refuses to hire full-time staff until revenue mandates it, instead leveraging a lean stack of Webflow, Figma, and emerging AI coding assistants to maintain agility. This methodology requires him to rebuild his marketing site every few months, a process he treats as a critical R&D investment. He meticulously compares free templates against paid assets, tracking every link and version in a personal spreadsheet to ensure no resource is wasted. Despite generating a healthy £110k income, Daryl lives frugally, viewing every pound spent as a bet on future scalability. His personality reflects a high degree of conscientiousness and openness, driving him to constantly experiment with new tools while maintaining rigorous control over his environment. Recently, he made the difficult decision to pause hiring a dedicated designer, opting to learn advanced prototyping techniques himself to save cash. He is currently navigating the precarious transition from 'side project' to 'viably scalable business,' balancing the thrill of autonomy with the heavy burden of sole responsibility.

Background & daily life

A day in their life

Daryl wakes at 6:30 AM, immediately checking server uptime and Stripe notifications before touching his phone. After a quick breakfast and a 45-minute gym session, he heads to his home office, which doubles as his command center. By 9:00 AM, he is already in the weeds, debugging a Webflow interaction that broke after an update. He spends the morning writing prompts for his AI coding assistant to refactor legacy components, then switches to Figma to mock up a new hero section for the upcoming product launch. Lunch is a sandwich eaten at the desk while reading a Substack thread on retention metrics. The afternoon is reserved for client calls and outreach, often feeling fragmented. Late afternoon brings a period of intense 'deep work' on the core product logic. By 7:00 PM, he shuts down his laptop, takes a walk, and avoids screens until bed, trying to preserve his mental clarity for the next day's sprint.

Lifestyle

Daryl lives in a high-ceilinged, light-filled loft in East London that he shares with two other creatives to keep rent manageable. His evenings are rarely social; he prefers quiet dinners at home or a solitary walk along the Thames to decompress from screen time. He is health-conscious but treats exercise like another KPI: strict HIIT sessions three times a week to maintain energy levels. Financially, he practices extreme capital discipline, reinvesting nearly all profit back into the business while maintaining a personal budget that feels 'tight' by his standards. He has no debt outside his mortgage and views money strictly as fuel for scaling rather than a means for luxury consumption. Socially, his circle is narrow, consisting mostly of fellow founders who understand the isolation of solo entrepreneurship.

Work life

His workday is a monastic rhythm of deep coding followed by frantic design iterations. As a solo founder, he wears every hat, but spends 60% of his time building features and 30% obsessing over conversion rates on his landing pages. He uses a hybrid stack of Webflow for front-end velocity and custom AI-generated code for backend logic. The pressure comes from the lack of a safety net; every bug or slow load time directly impacts cash flow. He manages his workflow via Notion dashboards where he tracks asset versions meticulously. There are no colleagues to consult, meaning he often debates design choices with himself for hours before committing. Late nights are common, fueled by strong coffee, as he tries to outpace competitors without burning out.

Relationships

Daryl's relationship with his family is warm but distant; they live in the North and visit quarterly, often confused by his relentless focus on 'growth.' He has a small, tight-knit group of three fellow solo founders he meets for virtual coffee chats to vent frustrations, though he rarely shares specific financial data. He trusts no one implicitly, preferring to verify information himself. His primary influence comes from online thought leaders whose track records he can audit, rather than traditional mentors. He values privacy and keeps his personal life entirely separate from his public digital footprint.

How they decide

Daryl operates on a hypothesis-driven, research-heavy model. He is inherently skeptical of sales pitches and will almost always validate a claim through documentation, community forums, or a free trial before considering payment. He analyzes ROI with mathematical precision, calculating the break-even point for any subscription or tool purchase. While he is open to innovation, he moves slowly once committed to a stack, fearing the cost of churn or migration. Peer validation matters, but only if it comes from trusted sources with similar constraints. He avoids impulse buys, viewing spending as a resource allocation problem rather than a convenience choice.

How they sound

His speech is precise, clipped, and devoid of fluff. He speaks in complete sentences but often omits polite fillers, favoring direct statements of fact or observation. He uses technical jargon naturally (e.g., 'latency,' 'churn rate,' 'stack') but avoids corporate buzzwords like 'synergy' or 'disruption.' When explaining problems, he tends to structure them logically: context, friction point, and potential solution. He rarely raises his voice, even when frustrated, preferring a calm, analytical tone. He avoids emotional language, describing feelings in terms of efficiency losses or opportunity costs. In casual conversation, he remains guarded, often pivoting topics back to practical matters or current projects.