Why this persona fits the audience
He is the CTO and cofounder at a 9-person collaboration SaaS in Manchester. As the technical backstop for the trial period, he answers setup and integration questions directly and keeps the support flow intentionally lean.
- Age: 36
- Location: Manchester, UK
- Occupation: CTO & Cofounder, Collaboration SaaS
- Income: £85k–£110k
- Education: MSc in Software Engineering
- Company size: 9
- Years in role: 5
“The elegance of a solution lies not just in its functionality, but in its inherent simplicity and robustness.”
Omar Towne, 36, is a foundational figure in his Manchester-based collaboration SaaS startup, serving as both CTO and cofounder. His journey into tech began with a fascination for how systems fit together, leading him to pursue an MSc in Software Engineering. After several years in established tech companies, he felt the pull to build something from the ground up, co-founding his current venture five years ago. His role is multifaceted; he’s the architect of the platform's core infrastructure, a hands-on coder, and crucially, the technical 'backstop' during customer trial periods. This deliberate choice to personally handle initial setup and integration queries for trial users is a strategic decision to maintain a lean support operation and glean direct, unfiltered customer feedback. Omar thrives on technical correctness and values control over his technical domain, which translates into a deep focus on software architecture and developer experience for his small team. He’s not driven by status or overt displays of wealth, preferring the quiet satisfaction of solving complex problems and building efficient, scalable systems. His income, while comfortable, is largely reinvested into the company or saved for future stability. Recent decisions have focused on refactoring a key module for better performance and evaluating new CI/CD pipelines to streamline deployment. He views time as a critical resource, constantly seeking ways to optimise workflows and minimise technical debt, understanding that every hour spent on maintenance is an hour not spent on innovation. His approach to building the product is akin to crafting a meticulously engineered machine: functional, efficient, and built to last.
Background & daily life
A day in their life
Omar’s day typically begins around 6:30 AM. After a quick coffee, he dedicates an hour to focused coding on core features or architectural improvements, free from distractions. By 8:00 AM, he’s checking Slack and emails, addressing any urgent issues and preparing for the 9:00 AM team stand-up. The morning is usually filled with code reviews, architectural discussions with his lead engineer, or diving into technical support tickets that require his expertise. Lunch is a quick, often solitary affair at his desk. Afternoons might involve planning sprints, researching new technologies, or troubleshooting complex integration problems for trial users. He aims to wrap up by 6:00 PM, though occasional late nights occur when critical bugs arise or investor updates are due. Evenings are for winding down with his partner.
Lifestyle
Omar shares a modern two-bedroom flat with his partner in a quieter, residential part of Manchester, a short tram ride from the city centre. They value their shared space, keeping it organised and uncluttered. His routine is fairly structured: early mornings for focused coding before the team wakes up, followed by team stand-ups and deep dives into architecture or support escalations. Weekends are for decompressing, often involving a long run along the canal, exploring local breweries with his partner, or tackling a personal coding project. He’s mindful of his health but not obsessive, preferring to walk or cycle when possible. Financially, he’s prudent, prioritising savings for future company growth and personal stability over extravagant spending.
Work life
As CTO and cofounder, Omar is the technical linchpin for his 9-person SaaS startup. His days are a constant juggle between strategic software architecture, hands-on coding, and being the primary technical point of contact for trial users during their critical evaluation phase. He deliberately keeps the support system lean, viewing direct customer interaction as a way to deeply understand pain points and identify areas for product improvement. This means he’s often the one personally answering complex integration questions or debugging setup issues for potential clients, a role he embraces for its direct feedback loop, even if it pulls him away from core development. The pressure is on to ensure the product’s technical reliability and scalability as they grow.
Relationships
Omar maintains a close, supportive relationship with his partner, who understands the demands of startup life. His core professional circle includes his two co-founders, with whom he shares a deep mutual respect and often engages in intense, but productive, strategic debates. Socially, he has a small group of long-term friends from university, most of whom work in tech, providing a valuable sounding board for both technical and business challenges.
How they decide
Omar is highly analytical and research-driven when making significant decisions. He meticulously gathers data, weighs pros and cons, and often seeks out technical documentation or expert opinions before committing. He prefers to understand the underlying mechanisms and potential implications thoroughly, favouring well-reasoned, evidence-based choices over impulsive ones. He’s not afraid to iterate, but the initial decision process is typically slow and deliberate.
How they sound
Speaks with a clear, measured cadence, often using precise technical terminology. His tone is generally calm and rational, even when discussing complex issues. He avoids overly casual slang and prefers to articulate his points thoroughly. When explaining technical concepts, he’s patient but direct. He tends to use phrases like 'fundamentally,' 'from a technical standpoint,' and 'the logical approach would be...' He rarely expresses strong emotions outwardly, maintaining a professional and composed demeanour.
Personality traits
- Analytical
- Methodical
- Reserved
- Detail-oriented
- Pragmatic
- Problem-solver
- Calm under pressure
- Independent
Goals
- Achieve product-market fit with a stable, scalable SaaS offering.
- Build a robust, efficient engineering team that can operate autonomously.
- Contribute meaningfully to the open-source community with a key library.
- Maintain a healthy work-life balance to prevent burnout.
- Secure Series A funding within the next 18 months.
Problems & frictions
- Balancing immediate customer support needs with long-term product development.
- Finding and retaining top-tier engineering talent in a competitive market.
- The inherent technical debt that accrues in a fast-growing startup.
- Ensuring the SaaS platform remains performant and secure as user numbers increase.
- Managing the psychological toll of startup uncertainty and constant problem-solving.
Values
- technical correctness
- simplicity
- control
- efficiency
- autonomy
Interests
- software architecture
- developer experience
- team collaboration
- performance optimisation
- open-source contributions
Media habits
- Following technical blogs (e.g., Hacker News, Martin Fowler's)
- Listening to engineering podcasts during commutes
- Subscribing to newsletters on AI and SaaS trends
- Participating in niche developer forums
- Occasional LinkedIn scrolling for industry news