Why this persona fits the audience
He manages operations at a 22-person logistics SaaS startup in Manchester and oversees the prompts used for release notes, help articles, and internal process docs. He keeps most references in Notion and spreadsheets and treats prompt writing as one piece of an already documented workflow.
- Age: 44
- Location: Manchester, UK
- Occupation: Operations director
- Income: GBP 82k base
- Education: BSc in Business Information Systems
- Company size: 22 people
- Years in role: 3.5
“If you can't document the process clearly enough for someone else to follow it tomorrow, then the process isn't ready for scale.”
Santiago Conroy is a 44-year-old Operations Director based in Manchester, operating at the helm of a lean 22-person logistics software startup. With a BSc in Business Information Systems, he has spent nearly two decades navigating the intersection of technical infrastructure and human workflow. Unlike many of his peers who chase the latest flashy trends, Santiago is driven by a singular obsession: reliability. He views his role not just as management, but as the architect of organizational memory. His daily reality involves a constant tug-of-war between the chaotic energy of a growing startup and the rigid discipline required to maintain operational integrity. Currently, Santiago personally curates the prompts that drive the company's external communications. He treats these prompts not as creative exercises but as functional code, embedding them into a sprawling Notion workspace alongside hundreds of spreadsheets that track everything from server uptime to customer satisfaction scores. He recently made the decision to halt the adoption of several experimental AI tools because they failed to integrate cleanly with his existing documentation hierarchy. To him, a tool is only valuable if it reduces friction, not if it adds another silo of data. Financially, Santiago is comfortable but conservative. His £82k salary allows for a secure life in Didsbury, yet he remains wary of unnecessary expenditures. He believes that money should be spent on infrastructure that prevents future headaches, not on perks that offer temporary relief. Professionally, he is respected for his ability to bring order to chaos, though this sometimes makes him appear inflexible to younger, more agile team members. As the company looks toward its next funding round, Santiago is preparing to transition from a hands-on operator to a strategic leader, knowing that the systems he builds today must sustain the organization when it doubles in size.
Background & daily life
A day in their life
Santiago wakes at 6:30 AM, checks emails while having coffee, and cycles to the office by 7:45 AM. His morning is reserved for deep work, specifically reviewing the previous day's prompt performance metrics and updating the master Notion database. By 10:00 AM, he shifts to meetings, fielding questions from developers about API constraints or from sales on how to explain recent feature updates. Lunch is usually eaten alone at his desk while reading a newsletter on supply chain logistics. Afternoons are spent refining internal processes, often debugging a broken automation script or rewriting a help article to ensure clarity. He leaves the office by 6:00 PM sharp to pick up his children from school. Evenings are strictly for family, followed by a brief period of reading or planning the next day's priorities before bed.
Lifestyle
Santiago lives in a semi-detached home in Didsbury, a leafy suburb of South Manchester, commuting 15 minutes to his office. His evenings are rigidly structured around family dinner and helping his children with homework before reading industry reports or tinkering with personal spreadsheet macros late into the night. He is health-conscious, cycling to work twice a week when the weather permits, though he admits his diet often defaults to convenience during crunch weeks. Financially, he is prudent; he maxes out his pension contributions early in the year and avoids luxury spending, preferring to invest in tools that save time. Socially, he maintains a small, tight-knit circle of friends from university and former colleagues, meeting monthly for dinner rather than frequenting loud bars.
Work life
As the sole Operations Director at a 22-person logistics SaaS startup, Santiago wears the 'glue' hat, bridging the gap between engineering velocity and customer success needs. His day is dominated by maintaining the single source of truth in Notion, where he meticulously structures prompt libraries for release notes and help articles. He spends hours auditing spreadsheets that track API usage and support ticket resolution times, ensuring every process has a clear owner and a defined output. The pressure comes from the constant tension between rapid product iteration and the need for stable, repeatable documentation. He rarely delegates high-level prompt strategy, preferring to personally craft the logic to ensure consistency across the team's AI outputs.
Relationships
Santiago relies heavily on his wife, Sarah, for emotional grounding and household management, allowing him to focus intensely on work during the week. His primary professional influence is the CTO, with whom he shares a long-standing friendship from their days at a previous firm. He has no direct reports but acts as a mentor to the head of Customer Success, guiding them on how to structure their internal comms. He is not active in large networking groups, finding value only in peer-to-peer exchanges with other Ops Directors in the UK tech sector.
How they decide
Santiago employs a highly cautious, evidence-based decision-making process. He rarely commits to a new tool or methodology without a pilot phase, a detailed cost-benefit analysis, and a review of existing documentation standards. He is influenced more by data points, case studies, and peer recommendations from trusted networks than by marketing hype or sales pitches. If a solution disrupts his current workflow without a clear, quantifiable return on investment, he will reject it immediately.
How they sound
His speech is measured, precise, and devoid of filler words. He speaks with a standard Manchester accent but adopts a formal, corporate tone in professional settings, avoiding slang entirely. He prefers declarative sentences that outline cause and effect, often using phrases like 'the data suggests' or 'the protocol dictates.' He does not use hyperbole or emotional language when discussing business problems. In casual conversation, he remains polite but distant, quickly steering topics back to practical matters or shared interests like technology and sports.
Personality traits
- methodical
- systematic
- pragmatic
- reliable
- detail-oriented
- reserved but approachable
- structure-seeking
- risk-averse
- direct communicator
- efficiency-focused
Goals
- Standardize all AI-generated content workflows within the next fiscal quarter
- Reduce internal administrative overhead by 15% through better system integration
- Achieve a promotion to COO role within three years as the company scales past 50 employees
- Maintain a perfect audit trail for all operational changes to satisfy future compliance needs
- Build a robust knowledge base that requires zero training for new hires
- Secure a stable retirement fund without taking excessive financial risks
Problems & frictions
- Fragmented documentation scattered across multiple Notion pages and local files
- Difficulty tracking version history for complex prompt iterations without a dedicated tool
- Time spent manually formatting AI outputs to match company style guides
- Resistance from junior staff who prefer ad-hoc methods over documented workflows
- Balancing the speed of startup growth with the need for rigorous process control
- Limited budget for enterprise-grade tools that justify the cost for a 22-person team
Values
- process reliability
- low-friction documentation
- accountability
- operational consistency
- data integrity
Interests
- operations systems
- spreadsheets
- business process design
- supply chain optimization
- workflow automation architecture
Media habits
- LinkedIn technical deep dives
- Substack newsletters on SaaS scaling
- The Guardian morning briefing
- Podcasts on operational efficiency
- Reddit r/sysadmin and r/ops
- Internal Slack channels