Johnathan Ziemann

Why this persona fits the audience

Runs a 4-person web design agency in Manchester and keeps live chat active on a dozen client websites; he checks messages between project work and uses a single inbox shared with a part-time account manager, including several sites already on Tawk.to.

• Age: 41
• Location: Manchester, UK
• Occupation: Agency owner
• Income: £68k
• Education: Bachelor's degree
• Company size: 4 full-time employees
• Years in role: 7 years

“You can't build a great website if you're constantly putting out fires caused by bad processes.”

Johnathan Ziemann is a 41-year-old agency owner based in Manchester, operating a lean four-person web design firm that specializes in bespoke WordPress solutions for SMEs. With a Bachelor's degree in Computer Science earned a decade ago, he transitioned from being a senior developer to running his own practice seven years ago, driven by a desire for autonomy and a frustration with the rigid structures of large corporate firms. Today, his agency manages twelve active client websites, each requiring ongoing maintenance and real-time support. Johnathan personally oversees the technical architecture and handles the most complex integrations, while delegating routine design tasks to junior staff. However, the operational friction of managing live chat support remains a persistent challenge. He currently utilizes a shared Tawk.to inbox alongside a part-time account manager, a setup that works adequately but suffers from latency during peak hours and occasional miscommunication regarding ticket ownership. This fragmentation forces him to interrupt deep coding sessions repeatedly, eroding his productivity and increasing the risk of oversight. Despite these hurdles, Johnathan has maintained steady growth, prioritizing reliability and efficient handoffs over rapid expansion. He is financially prudent, earning approximately £68,000 annually, which allows for a comfortable lifestyle but leaves little room for error in cash flow management. His recent decisions have focused on optimizing internal workflows rather than aggressive sales tactics, believing that a smooth operation is the best marketing tool available. Outside of work, he finds solace in the rhythm of long-distance cycling and the camaraderie of local rugby, activities that provide necessary mental decompression from the digital noise of his profession.

Background & daily life

A day in their life

Johnathan wakes up at 6:30 AM for a quick shower and a cup of tea before the house gets loud. By 7:30 AM, he's dropped the kids off at school and heads to his office in Chorlton. Mornings are dedicated to coding and theme customization, a time when he demands absolute silence. Around 10:30 AM, he shifts gears to check emails and the shared Tawk.to inbox, responding to urgent client queries before his morning stand-up with the team at 11:00 AM. Lunch is usually a sandwich eaten at his desk while listening to an industry podcast. Afternoons involve client calls, reviewing designs, and troubleshooting server issues. At 5:00 PM, he logs off to pick up the kids, cook dinner, and help with homework. Evenings are reserved for relaxation or light cycling if the weather permits, strictly avoiding work unless a critical bug strikes.

Lifestyle

Johnathan lives in a semi-detached Victorian terrace in Chorlton, Manchester, with his wife Sarah and their two kids. Their Saturday mornings are sacred for family bike rides along the Irwell Valley, often covering 30 miles together. He is an avid cyclist who maintains his own road bike and prioritizes fitness as a counterbalance to desk work. Financially, they are comfortable but deliberate; they save aggressively for university fees and avoid unnecessary luxury spending. Socially, he balances quiet evenings at home with a weekly rugby match at the local club and occasional drinks with fellow agency owners at a pub near Deansgate. He values health, cooking fresh meals most nights, and maintaining a clear boundary between work hours and family time.

Work life

As the sole proprietor of a four-person design studio, Johnathan wears every hat from lead developer to accounts payable. His day is fractured by context switching: building custom WordPress themes in the morning, then managing client expectations via email and chat in the afternoon. He currently relies on a shared Tawk.to inbox with a part-time account manager, which often leads to overlapping responses or missed nuances when he steps away for deep coding work. The pressure comes from juggling tight deadlines for six simultaneous projects while ensuring client satisfaction remains high. He spends significant mental energy organizing handoffs between the dev team and the support staff, trying to prevent bottlenecks without micromanaging his small crew.

Relationships

Johnathan is deeply embedded in the Manchester creative community, frequently attending meetups at WeWork Spinningfields. His wife Sarah manages the household finances and acts as a sounding board for business stress, though she rarely discusses the technicalities of web development. He has a close-knit group of three other agency owners he meets monthly for coffee, where they vent about common industry frustrations. His parents, retired teachers in Leeds, are supportive but find his job abstract, so he limits tech-talk at family dinners. He trusts his long-standing accountant for financial advice more than generic online articles.

How they decide

He is a cautious, research-heavy decision-maker who prefers peer validation over marketing claims. Before adopting any new tool, he typically reads user reviews, checks compatibility with existing stacks like WordPress, and asks trusted colleagues for their experiences. He avoids impulse buys and is particularly wary of complex implementations that require heavy training for his small team. If a solution promises efficiency, he needs to see concrete evidence of how it integrates into his current workflow rather than just hearing about features.

How they sound

His speech is measured and precise, reflecting a background in both technical logic and client service. He tends to use British idioms sparingly, preferring direct, functional language like 'let's get this sorted' or 'that's not going to fly.' He avoids hyperbole and corporate jargon, favoring plain English. When discussing work, he speaks in terms of workflows, bottlenecks, and outcomes rather than abstract concepts. He pauses frequently to think, ensuring his sentences are complete and logical, and rarely interrupts others mid-sentence.