Why this persona fits the audience
Owns the feedback queue for a 30-person ecommerce SaaS team in Chicago. He exports Zendesk tickets, chat transcripts, and NPS comments into spreadsheets and uses the same categories month to month.
- Age: 39
- Location: Chicago, US
- Occupation: Support operations specialist at a software vendor
- Income: USD 96k
- Education: BS information systems
- Company size: 30 employees
- Years in role: 4
“If you can't measure it consistently, you can't improve it, and if you're guessing what your customers want, you're just building a product for yourself.”
Tom Spinka is a 39-year-old Support Operations Specialist based in Chicago, holding a Bachelor of Science in Information Systems from a state university. For the past four years, he has been the backbone of the feedback loop for a 30-person ecommerce SaaS vendor. Despite the company's rapid growth in revenue, Tom remains the sole owner of their customer feedback infrastructure, a role that requires a unique blend of technical aptitude and obsessive organizational discipline. He operates in a world of spreadsheets, where the quality of product decisions hinges on his ability to manually parse thousands of unstructured support tickets, chat logs, and NPS responses. His workflow is defined by a rigid, self-imposed taxonomy that he has maintained month after month, a practice born out of necessity rather than preference. While the rest of the company pushes for AI-driven insights, Tom remains skeptical, viewing his manual methods as the only source of truth he can verify. He earns $96,000 annually, a salary that supports a comfortable middle-class life in Lincoln Park, allowing him to prioritize financial security over career risks. Professionally, he is constrained by the legacy nature of the company's tech stack and a lack of budget for enterprise-grade automation tools. This forces him to spend hours on repetitive data entry tasks that could theoretically be solved by modern software, yet he resists adopting new solutions without ironclad proof of their reliability. Tom's recent decisions have focused on optimizing his internal reporting rather than expanding his toolkit, driven by a fear that introducing new variables will compromise the integrity of the data he has spent years curating. He views his job not as a stepping stone, but as a craft, believing that the human element of interpreting customer frustration is irreplaceable. His life outside of work is a sanctuary of order, where he maintains his watches, plays strategic board games, and cherishes the predictability of his family routine. He is a man who believes that success comes from doing the hard, unglamorous work correctly, time and time again.
Background & daily life
A day in their life
Tom wakes up at 5:45 AM to avoid traffic, brewing a fresh pot of coffee while checking emails on his phone. By 7:15 AM, he is driving his sedan through downtown Chicago, listening to a podcast about supply chain logistics. At 8:30 AM, he arrives at the office, greets the team with a nod, and immediately dives into his morning ritual: exporting the previous day's Zendesk tickets. For the next three hours, he is in a state of intense focus, meticulously cleaning data, applying his custom tags, and building the weekly summary spreadsheet. Lunch is a quick sandwich eaten at his desk while reviewing NPS comments. Afternoon meetings with the product team are tense as he presents data on a recurring checkout bug. He leaves the office at 5:30 PM sharp, heading to the grocery store for dinner ingredients before picking up his son from school. Evenings are reserved for family time and his hobby of organizing his watch collection, ensuring he disconnects completely from work by 9:00 PM.
Lifestyle
Tom lives in a modest but well-maintained brick row house in Lincoln Park, where he values quiet over noise. His weekends are a structured balance: Saturday mornings involve long hikes along the lakefront to clear his head, followed by afternoons playing complex strategy board games like Gloomhaven with a small group of friends from high school. Sundays are strictly reserved for meal prep and maintaining his analog watch collection, which he cleans and oils himself. He is financially conservative, contributing heavily to retirement accounts early and avoiding debt except for his mortgage. He doesn't drink alcohol often, preferring high-quality espresso or tea, and maintains a steady exercise routine to manage stress without relying on medication.
Work life
At his 30-person SaaS company, Tom is the gatekeeper of customer sentiment. His days are dominated by the friction of manual data extraction; he spends hours exporting raw ticket logs from Zendesk and pasting them into rigid Excel templates. He manages the 'feedback queue,' ensuring every NPS comment is tagged correctly according to his static, month-to-month taxonomy. While the engineering team builds new features, Tom is the one who manually identifies bugs from chat transcripts. He feels a constant low-level pressure to prove that his manual categorization is as accurate as any automated system, despite having no budget for new software. He collaborates closely with the VP of Product, acting as the human bridge between chaotic user complaints and product roadmaps.
Relationships
Tom is deeply embedded in a local network of professionals who value reliability. He is married to Sarah, an elementary school teacher, and they share the mental load of their household. Their relationship is built on shared routines and mutual respect for each other's professional expertise. He has a tight-knit circle of four close friends from university whom he meets monthly for board games; these relationships are his primary stress relief. He is less connected to broader community organizations, preferring deep, one-on-one interactions over large social gatherings. His parents, retired teachers in Milwaukee, influence his view on education and stability, though they live far enough away to require scheduled calls rather than daily contact.
How they decide
Tom is a deliberate, research-heavy decision-maker who prioritizes proven reliability over novelty. He rarely makes impulsive purchases, especially regarding business tools, preferring to test solutions in sandbox environments or demand extensive case studies before committing. He relies heavily on peer validation from trusted colleagues in his industry rather than marketing claims. If a new tool promises efficiency, he will first calculate the total cost of implementation and potential disruption to his existing workflows. He moves slowly but decisively once the logical framework is sound, valuing long-term stability over short-term gains.
How they sound
Tom speaks with a measured, Midwestern cadence, using precise vocabulary and avoiding hyperbole. He tends to speak in complete sentences, often prefacing statements with qualifiers like 'based on the data' or 'from my experience.' He avoids slang entirely and rarely raises his voice, even when frustrated. In meetings, he pauses frequently to gather his thoughts, preferring accuracy over speed. He does not use buzzwords like 'disruptive' or 'synergy,' finding them hollow. When explaining a process, he breaks it down into linear steps, emphasizing cause and effect. His tone is generally neutral and professional, shifting to warm only when discussing his hobbies or family.
Personality traits
- Methodical
- Skeptical of hype
- Detail-oriented
- Steady-handed under pressure
- Process-driven
- Quietly authoritative
- Cautious about change
- Loyal to established tools
- Systematic thinker
- Pragmatic problem solver
Goals
- Standardize the company's feedback reporting process to eliminate manual errors
- Achieve a promotion to Head of Customer Success Operations within two years
- Reduce personal administrative overhead by automating recurring spreadsheet tasks
- Build a more robust emergency fund for family stability
- Lead the migration to a more integrated CRM platform when the time is right
- Maintain work-life boundaries to ensure consistent presence for family events
Problems & frictions
- The tedium of manually re-categorizing thousands of unstructured support tickets weekly
- Inconsistency in how different support agents tag issues, leading to messy data
- Lack of visibility into emerging trends until it's too late to react
- Feeling undervalued because his critical analysis work is invisible compared to sales numbers
- Frustration with the rigidity of current tools that don't allow for dynamic tagging
- Time scarcity preventing him from learning advanced data visualization techniques
Values
- reliability
- operational order
- customer follow-through
- data integrity
- pragmatism
Interests
- ecommerce ops
- helpdesk workflows
- board games
- analog watch collecting
- Sunday morning coffee brewing
Media habits
- Morning commute listening to 'Reply All' or tech podcasts
- Weekly Sunday edition of The Wall Street Journal (print)
- Niche subreddits for helpdesk admins
- Twitter/X for specific API documentation threads
- Local board game meetup groups