Shannon Block

Why this persona fits the audience

Supports a 2-person consultancy that prototypes client automations, writes internal scripts, and tests prompts across several model APIs. He is comfortable switching between tools by hand, keeps reusable prompts in Git and Sheets, and often routes work to the model that fits the task best.

• Age: 42
• Location: Austin, US
• Occupation: Automation consultant
• Income: $118k
• Education: BS in computer engineering
• Company size: 2-person consultancy
• Years in role: 5

“The real challenge isn't just finding the right tool, it's understanding precisely *why* it's the right tool for this specific job, right now.”

Shannon Block, 42, is a technical automation consultant based in Austin, Texas, co-running a two-person consultancy focused on prototyping client automations. Holding a BS in Computer Engineering, he brings a strong foundation in technical problem-solving to his role. His professional journey has been marked by a deep dive into the practical application of AI, driven by a desire for efficiency and control. He's comfortable navigating the rapidly evolving landscape of large language models, viewing them as powerful, albeit sometimes unpredictable, tools. Shannon's approach is characterized by pragmatism and a relentless pursuit of technical quality. He meticulously manages reusable prompts in Git repositories and tracks model performance and costs in spreadsheets, enabling him to make informed decisions about which API best suits a given task. This hands-on, often manual, switching between tools reflects his comfort with complexity and his commitment to optimizing workflows. He recently spent two weeks evaluating different summarization models for a legal tech client, ultimately selecting a combination of a cost-effective, general-purpose model for initial drafts and a more specialized, higher-cost model for final refinement, a decision driven by both quality requirements and budget limitations. His home life is equally structured, with a passion for DIY electronics and espresso, reflecting his broader interest in understanding and optimizing systems. He views his income of $118k as a means to support his lifestyle and personal projects, rather than a primary status symbol. Time is a critical resource, and he constantly seeks ways to maximize its productive use, both in his professional endeavors and personal pursuits, ensuring that his work directly contributes to tangible improvements for his clients and his own technical mastery.

Background & daily life

A day in their life

Shannon's typical weekday begins around 7:00 AM with a carefully brewed espresso and a review of overnight system logs or relevant tech news on Hacker News. By 8:30 AM, he's at his desk, often starting with client communication or reviewing project requirements. The bulk of his morning is spent prototyping, writing Python scripts to interact with various LLM APIs, and meticulously documenting prompt variations in Git. Lunch is usually a quick, healthy meal prepared at home. Afternoons involve more intensive testing, comparing model outputs for specific tasks like summarization or code generation, and then routing the work to the most suitable API. He might spend an hour troubleshooting an integration issue or optimizing a prompt for cost-efficiency. The workday typically wraps up around 6:00 PM, often followed by a bike ride or time in his home lab.

Lifestyle

Shannon lives a structured but fulfilling life in Austin. He shares a comfortable home with his partner, Rachel, a freelance writer, and they maintain a balanced routine. Mornings often start with a meticulously prepared espresso and a quick scan of tech news before diving into work. Evenings are a mix of cycling to clear his head, working on personal projects in his home lab (currently optimizing a custom home automation system), or enjoying quiet time with Rachel. He's mindful of his finances, preferring to invest in quality tools and experiences rather than fleeting trends. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings.

Work life

Shannon's work is deeply hands-on, supporting a small consultancy where he and his partner prototype client-facing automations. His days are a dynamic mix of coding internal scripts, meticulously testing prompts across various LLM APIs, and architecting solutions. He's adept at manually switching between tools, leveraging Git for prompt version control and Google Sheets for tracking model performance and cost. A significant part of his role involves selecting the most appropriate model for each specific task, a decision driven by technical requirements and efficiency. The pressure comes from delivering robust, cost-effective solutions for clients on tight timelines.

Relationships

Shannon's primary relationship is with his partner, Rachel, a freelance writer, with whom he shares a pragmatic and supportive dynamic. They influence each other's perspectives on technology and work-life balance. His business partner is his closest professional confidant, and they rely heavily on each other's technical and client-facing skills. Socially, he maintains a small circle of friends, mostly fellow engineers or tech enthusiasts, with whom he discusses technical challenges and shares insights.

How they decide

Shannon is highly analytical and research-driven. He meticulously evaluates options, weighing technical merits, efficiency gains, and long-term implications. He trusts data and empirical evidence, often running small-scale tests before committing to a tool or approach. While pragmatic, he's not afraid to adopt new technologies if they demonstrably improve his workflow or the quality of his output. He values control and prefers solutions that offer transparency and customization.

How they sound

Shannon speaks in a clear, measured tone, avoiding jargon unless discussing technical specifics with peers. He tends to be concise, preferring directness over embellishment. His cadence is steady, reflecting his analytical nature. He avoids hyperbole and emotional language, focusing on facts and logical reasoning. When explaining complex topics, he breaks them down systematically. He might use phrases like 'empirically,' 'from a performance standpoint,' or 'the most pragmatic approach.'