John Lebsack

Why this persona fits the audience

Co-founds a 3-person B2B SaaS in London and maintains a shared Notion page for renewal dates across AWS, GitHub, analytics, and the team's design tools; he also records a few personal streaming and cloud subscriptions in the same workflow.

• Age: 29
• Location: London, UK
• Occupation: Startup founder
• Income: £78k + variable equity upside
• Education: Master's degree
• Company size: 3
• Years in role: 1.5

“I don't need another shiny tool; I need a system that doesn't break when I'm tired.”

John Lebsack, 29, is the technical co-founder of a nascent B2B SaaS company based in London, operating out of a shared workspace in Shoreditch alongside two other passionate founders. Holding a Master's degree in Computer Science from Imperial College London, John pivoted from a high-paying corporate role five years ago to pursue the autonomy of building his own product. Today, he earns a base salary of £78,000 plus significant equity upside, a structure that demands absolute vigilance regarding the company's cash flow. His professional life is defined by a paradox: he builds sophisticated, scalable software solutions for clients while personally relying on a rudimentary, manually updated Notion page to track his team's critical software renewals. This system spans AWS bills, GitHub Enterprise seats, various analytics platforms, and design tool licenses, with a few personal subscriptions like Spotify and Netflix tacked onto the bottom for good measure. Despite his technical prowess, John admits to a nagging anxiety about missing a renewal date, fearing the chaos of a disrupted service or an unexpected charge from an expired card. His approach to life is deeply pragmatic; he views time as the scarcest resource and money as a lever for control rather than status. Recently, he decided to automate his morning routine to reclaim thirty minutes of focus time, yet he still struggles to find a seamless way to monitor recurring payments across multiple devices without introducing new complexity. He is currently weighing the pros and cons of switching his entire financial tracking to a dedicated app but remains hesitant due to the friction of migrating his current data. John represents the modern indie founder: technically brilliant, financially cautious, and perpetually balancing the tension between rapid growth and operational stability.

Background & daily life

A day in their life

John wakes at 5:30 AM for a ten-mile run along Regent's Canal, listening to a podcast on fintech regulation. By 7:30 AM, he's home, showered, and reviewing his Notion dashboard to check for any upcoming renewals or billing anomalies. At 8:30 AM, he joins a quick stand-up with his co-founders, discussing yesterday's deployment and today's priorities. The bulk of his morning is dedicated to deep work: refactoring the payment gateway module and optimizing database queries. Lunch is a quick sandwich eaten at his desk while scanning Hacker News. Afternoons are reserved for meetings, customer support tickets, and strategic planning. Around 6:00 PM, he steps away from the screen, heading to the gym or walking the dog. Evenings are for learning new frameworks or occasionally gaming, though he keeps a strict cutoff time to ensure sleep quality. Before bed, he double-checks his personal subscription tracker to ensure no surprises await him tomorrow.

Lifestyle

John lives in a converted warehouse flat in East London, surrounded by exposed brick and industrial lighting. His routine is rigid: 5:30 AM runs along the canal to clear his head before code hits the keyboard. He treats money as a resource to be allocated, not just spent, often auditing bank statements on Sunday evenings. Socially, he balances late-night pub sessions with close friends against early morning solo training. He avoids debt aggressively, preferring to reinvest cash flow into server credits or better hardware. His apartment is minimalist, devoid of clutter, reflecting a mind that prioritizes function over form. He values silence for deep work but enjoys the hum of a busy co-working space when isolation becomes too heavy.

Work life

As the technical co-founder of a three-person B2B SaaS, John splits his time between writing core backend logic and managing operational logistics. The team is remote-first but meets virtually every Tuesday and Thursday for sync-ups. His days are fragmented between sprint planning, debugging production issues, and the relentless administrative burden of keeping the business running. He is the primary architect of their tech stack, meaning he decides which services to use and how to integrate them. The pressure is constant; with only two other founders, any downtime or service outage feels like a direct threat to the company's survival. He spends hours weekly reconciling invoices and ensuring the team's access to essential tools remains uninterrupted.

Relationships

John is married to Sarah, a graphic designer who works freelance; they manage finances together but keep separate project buckets. He has a tight-knit circle of four fellow founders in London whom he meets bi-weekly for coffee to vent and trade war stories. His parents live in Manchester and visit monthly, often critiquing his career choices despite his success. He influences his team through transparency, openly sharing his own budget spreadsheets to model thriftiness. He relies heavily on his roommate, a junior developer, for casual social interaction and technical brainstorming during evening walks.

How they decide

John approaches decisions with a 'measure twice, cut once' philosophy. He rarely buys software immediately without a trial period or extensive reading of documentation and community feedback. He is skeptical of enterprise sales tactics and prefers tools that offer immediate value without long-term contracts. His process involves listing criteria, comparing options side-by-side, and checking if the solution integrates seamlessly with his existing ecosystem. If a tool requires a steep learning curve or hides pricing details, he abandons it quickly. He values speed but will delay a purchase if the long-term cost-benefit analysis isn't clear.

How they sound

John speaks with a clipped, efficient British cadence, avoiding filler words like 'um' or 'you know.' His vocabulary is precise, often leaning into technical jargon when explaining complex systems but switching to plain English when discussing finances. He tends to speak in bullet points, even in conversation, and frequently interrupts himself to correct a statistic or clarify a timeline. He avoids emotional grandstanding, preferring data-backed arguments. When stressed, his speech speeds up and becomes more monotone. He uses slang sparingly, mostly related to tech culture ('deploy', 'merge', 'scalable'), and dislikes corporate buzzwords like 'synergy' or 'circle back.'