Andrew Sauer

Why this persona fits the audience

Bootstraps a two-person devtools company in Manchester and handles the homepage, onboarding copy, and prospect interviews himself. He uses Google Docs, Sheets, and call recordings to test wording with early users, then updates the landing page after each small batch of conversations.

• Age: 28
• Location: Manchester, UK
• Occupation: Co-founder, DevTools Startup
• Income: £48k draw + equity
• Education: BEng in Computer Science
• Company size: 2
• Years in role: 3

““If you can’t measure it, and prove it works, then it’s just a guess. I’d rather spend an hour getting the data than a week building the wrong thing.””

Andrew Sauer, 28, is a co-founder of a nascent devtools startup based in Manchester. His journey into entrepreneurship stemmed from a BEng in Computer Science and a growing frustration with existing developer tools' inefficiencies. While his university peers gravitated towards established tech giants or lucrative finance roles, Andrew was drawn to the raw challenge of building something from the ground up. He and his co-founder, Liam, operate on a shoestring budget, bootstrapping their venture and drawing a modest £48k annual salary combined, with equity representing their primary future reward. Andrew embodies the 'technical founder' archetype: he’s the architect of their product, meticulously crafting code and optimising performance. However, his role extends far beyond the terminal. Recognizing the critical importance of product-market fit, Andrew has taken personal responsibility for crucial aspects of customer validation. He insists on personally conducting prospect interviews, meticulously analysing call recordings stored in cloud services, and using Google Docs and Sheets to refine messaging and onboarding flows. This hands-on approach is driven by a deep-seated value for tangible proof and technical depth; he believes fervently in iterating based on hard data rather than assumptions. His income reflects his early-stage commitment, and his frugality extends to his personal life, where he prioritises practical needs over discretionary spending. He views his independence and the ability to steer the company's technical trajectory as paramount. Recent decisions have focused on systematically testing different homepage value propositions, using qualitative feedback from each small batch of user conversations to inform micro-adjustments to the landing page copy, a process he finds both demanding and deeply rewarding.

Background & daily life

A day in their life

Andrew's typical weekday begins around 7:30 AM with a quick breakfast and checking Hacker News. He’s usually at his desk by 8:30 AM, diving straight into coding for 2-3 hours, focusing on core feature development or bug fixes. Lunch is a simple, often pre-prepped meal eaten at his desk while reviewing code or watching a short technical tutorial. The afternoon (from 1 PM) is dedicated to user-centric tasks: listening to recorded user calls, meticulously documenting feedback, drafting new landing page copy in Google Docs, and then updating the live site. He might have a brief sync with Liam around 4 PM to discuss progress. Evenings often involve further refinement of the product, occasional cycling if the weather permits, or reading industry blogs before winding down around 11 PM.

Lifestyle

Andrew lives in a modest two-bedroom flat in Chorlton, Manchester, shared with his co-founder. His commute is a brisk 20-minute cycle ride. He's a creature of habit, prioritising focused work sessions and evenings spent tinkering with personal projects or reading technical documentation. Financial prudence is key; he eats out infrequently and prefers to cook at home, often batch-cooking meals to save time and money during busy weeks. Socially, he's content with a small circle of close friends, preferring deep conversations over large gatherings. His cycling isn't just for transport; it's his primary stress relief and a way to clear his head.

Work life

As co-founder and lead engineer, Andrew’s days are a constant juggle. He spends mornings deep in code, architecting features and optimising the backend of their devtools product. Afternoons are dedicated to user-facing activities: meticulously analysing call recordings from prospect interviews, refining landing page copy in Google Docs, and updating their product's onboarding flow based on feedback. His co-founder handles sales and marketing outreach, but Andrew is the one testing messaging directly. The pressure is immense, driven by the need to bootstrap and prove product-market fit with limited resources. He relies heavily on their shared CRM (a meticulously organised Google Sheet) and cloud-based project management tools.

Relationships

Andrew's closest relationship is with his co-founder, Liam, with whom he shares a flat and the intense pressures of the startup. They have a complementary dynamic, balancing Andrew's technical focus with Liam's commercial drive. His parents, retired teachers, offer emotional support but little practical business advice. He maintains a few friendships from university, mostly other developers or tech enthusiasts, with whom he discusses industry trends and technical challenges.

How they decide

Andrew is highly analytical and evidence-driven. He meticulously gathers data, whether it's from user interviews, A/B tests on landing page copy, or performance metrics from his code. He prefers to test hypotheses rigorously before committing significant resources. He’ll often create detailed spreadsheets or flowcharts to weigh options and looks for quantifiable proof of concept before making a move. He’s not easily swayed by trends or hype; practical, demonstrable results are paramount.

How they sound

Speaks with a clear, measured cadence, often pausing to find the precise technical term. Uses UK English phrasing naturally, but avoids overt slang unless in a very casual setting. His tone is generally serious and focused, especially when discussing work, but can become more animated when explaining a complex technical concept or a new hardware gadget. He tends to be concise and dislikes ambiguity. He avoids hyperbole and relies on factual statements.