Alexis Emmerich

Why this persona fits the audience

She runs a 2-person SaaS from home and handles the companys directory presence herself, including submission forms, update requests, and tracking which pages are indexed. She currently uses a competitor tool for one product and keeps a separate notes file for the rest of the listings.

• Age: 41
• Location: Bristol, UK
• Occupation: Founder and Product Lead
• Income: GBP 78k
• Education: MSc in Computer Science
• Company size: 2
• Years in role: 3

“I don't need more noise; I need a system that actually tells me what's working so I can stop guessing and start building.”

Alexis Emmerich is a 41-year-old software architect turned solo entrepreneur, operating out of a converted Victorian terrace in Bristol. With an MSc in Computer Science from a leading UK university, she left the corporate sector seven years ago to pursue autonomy, eventually founding her current micro-SaaS focused on developer productivity tools. Three years into the venture, she has stabilized the business with a loyal user base but faces the classic bottleneck of a two-person operation: the sheer volume of administrative drag. Unlike many peers who hire generalists, Alexis insists on handling the company's directory presence herself to maintain absolute fidelity in how the product is described. This manifests as a hybrid workflow where she pays for one premium listing service but relies on a meticulously maintained, albeit aging, Google Sheets document for forty other directories. She frequently finds herself refreshing pages manually to check indexing status, a ritual that consumes hours weekly. Despite her high technical competence, she struggles with the fragmentation of modern SaaS discovery channels, often feeling that the industry's complexity is designed to sell tools rather than solve actual discoverability issues. She is pragmatic about money, viewing every pound spent as a vote for the kind of world she wants to build—one where efficiency is king and time is the ultimate currency. Recently, she made the difficult decision to pause hiring a virtual assistant, choosing instead to optimize her own no-code workflows, reflecting her deep-seated belief that true independence requires mastering the basics before outsourcing them.

Background & daily life

A day in their life

Alexis wakes at 6:00 AM, avoiding her phone until after a 9km cycle ride through the city. By 8:30 AM, she is at her desk with black coffee, checking Stripe notifications and server logs before opening email. The morning is reserved for deep work: refactoring the database schema. At 11:00 AM, she switches contexts to the tedious reality of directory management, logging into five different portals to submit updates for her latest feature release. Lunch is a quick sandwich eaten while reading a thread about AI indexing strategies. Afternoon hours involve client support tickets and planning the week's content. Evenings are strictly off-limits for work unless a critical deployment fails, allowing her to decompress with a book or a long walk along the harbourside.

Lifestyle

Alexis lives in a light-filled, slightly cluttered flat in Bedminster, Bristol, filled with ergonomic furniture and second-hand Scandinavian design pieces she's curated over years. Her routine is rigidly structured; she prioritizes sleep and early morning cycling before work begins, using the ride to clear her mind. Financially, she is conservative despite her income, reinvesting almost all profits back into the business rather than upgrading her lifestyle immediately. Socially, she prefers deep, one-on-one coffee meetings over loud networking events, often finding connection through shared technical challenges rather than small talk. She maintains a healthy balance, treating exercise as non-negotiable maintenance for her brain rather than vanity.

Work life

Her office is a dedicated corner of her living room, dominated by three monitors displaying analytics dashboards and code repositories. As the sole full-time employee alongside a single contractor, she wears every hat: engineering, support, marketing, and sales. Her day is fragmented between writing backend logic for her core product and manually updating directories across dozens of platforms. She manages a chaotic mix of tools: a paid subscription for one major listing service and a sprawling, color-coded spreadsheet for the rest. The pressure is constant but self-imposed; there are no bosses to answer to, only the relentless need to maintain visibility and revenue growth without burning out.

Relationships

Alexis has a small, tight-knit circle of fellow indie founders in the West of England, mostly meeting for weekly virtual co-working sessions or occasional pub visits in Stokes Croft. She relies heavily on her remote contractor, David, for technical heavy lifting, maintaining a relationship built on mutual respect and clear deliverables rather than office politics. Family is supportive but distant geographically; she speaks to her mother weekly but rarely discusses the granular details of her business stress. Her primary influence comes from online communities where she feels seen and understood, rather than local professional networks which can feel exclusionary.

How they decide

She is a cautious, research-heavy decider who values ownership of the process above all else. Alexis will not adopt a tool simply because it is popular; she needs to verify the data model, understand the API limits, and ensure she retains control over her own data export. She prefers a 'try before you buy' approach or a very clear refund policy. Her decisions are driven by a cost-benefit analysis of time saved versus money spent, often rejecting expensive solutions if they require significant setup time or lock-in contracts.

How they sound

Her speech is clipped, efficient, and devoid of corporate jargon. She tends to use precise verbs and avoids hedging phrases like 'I think' or 'maybe.' When discussing technical debt, she sounds tired but determined. She rarely complains loudly; instead, she frames frustrations as problems to be solved systematically. She avoids saying 'team' when she means 'me and a contractor' and dislikes the word 'scaling' unless accompanied by a concrete plan. Her tone is generally calm but becomes sharp when someone suggests a workflow that lacks logical consistency.