Why this persona fits the audience
Builds small internal tools and data bridges for SMB clients, spending most days in Claude Code and Codex to create scripts, database migrations, and API wrappers; he tracks jobs in spreadsheets and shared notes rather than a formal engineering system.
- Age: 51
- Location: Denver, Colorado, USA
- Occupation: Independent Automation Consultant
- Income: USD 140k-180k
- Education: MS Information Systems
- Company size: Solo practitioner
- Years in role: 15
“The beauty of a well-crafted script is that it just works, day in and day out, without fuss.”
Clint Olson has carved out a niche as an independent automation consultant over the past fifteen years, a path he chose after a decade working in IT support and systems administration for mid-sized corporations. The rigid structures and office politics of his earlier career felt stifling, prompting him to strike out on his own. Armed with an MS in Information Systems from Colorado State University, he found his calling in helping small and medium-sized businesses streamline their operations through custom automation. He built his practice on a foundation of practical problem-solving, eschewing expensive, proprietary orchestration software in favor of open-source tools and his own coding prowess. He spends the majority of his workdays immersed in coding environments like Claude Code and Codex, developing bespoke scripts, handling database migrations, and wrapping APIs for clients who often lack dedicated IT resources. His project tracking system is a testament to his preference for simplicity: a meticulously organized collection of spreadsheets and shared digital notes, which he finds far more efficient than any formal engineering platform he's encountered. Clint's income, typically between $140k and $180k annually, allows for a comfortable lifestyle but doesn't encourage extravagance; he values fiscal prudence and reinvests strategically in his home workshop and outdoor gear. He recently completed a complex data aggregation script for a local manufacturing firm, which involved bridging several disparate legacy systems – a project that took him three weeks of focused development. He deliberately avoids unnecessary complexity, both in his work and his personal life, which extends to his toolchain. He feels no need to pay for orchestration when his custom-built solutions, honed over years of experience, serve his clients reliably and cost-effectively. His independence is paramount; the freedom to choose his tools and methods, and to directly see the impact of his work, is what continues to drive him.
Background & daily life
A day in their life
Clint's day begins around 7:00 AM. After a quick breakfast and coffee, he heads to his home office. He typically starts by reviewing any overnight script outputs or logs in his spreadsheets, checking for errors. The bulk of his morning is spent coding, diving into Claude Code or Codex to build API wrappers, data transformation scripts, or database migration routines for his current client projects. Around noon, he takes a break for lunch, often stepping out for a short walk. The afternoon might involve a client call, further development, or documenting a completed module. He tries to wrap up by 5:30 PM, heading out to his workshop or preparing for dinner with his family. Evenings are for family or personal hobbies.
Lifestyle
Clint lives in a modest but well-maintained home in a Denver suburb with his wife and two teenagers. His weekdays are intensely focused on work, but weekends often involve trips to the mountains for fly fishing or camping, especially during the warmer months. He enjoys the satisfaction of building things, whether it's a custom piece of furniture in his garage workshop or a robust data script for a client. Money is managed carefully; while his income is good, he prioritizes experiences and practical investments over ostentatious displays. He's not one for frequent dining out, preferring home-cooked meals and the occasional BBQ with family.
Work life
As a solo automation consultant, Clint's work is his own. He thrives on the challenge of solving intricate problems for SMBs, often acting as their de facto IT department for automation needs. His 'office' is largely his home study, equipped with multiple monitors and a powerful PC. He spends his days deep in code editors, primarily leveraging Claude Code and Codex to craft bespoke solutions. Project management is a manual affair, tracked via a series of interconnected spreadsheets and digital notes, a system he finds perfectly adequate. Client interactions are typically scheduled calls or remote sessions, and he avoids unnecessary meetings.
Relationships
Clint is married to Sarah, a nurse, who understands and supports his independent work style. They share a practical partnership. His two children, a high school sophomore and a freshman, are navigating their own digital worlds. His closest friends are a mix of old college acquaintances and fellow enthusiasts met through woodworking or fly fishing clubs; they share practical advice and camaraderie, but rarely delve into deep technical discussions.
How they decide
Clint is a methodical and research-driven decision-maker, especially concerning tools and processes. He prioritizes functionality, reliability, and cost-effectiveness. He'll explore multiple options, read reviews cautiously, and often experiment with free or open-source versions before committing to any significant change. He values peer recommendations from trusted sources but ultimately relies on his own rigorous evaluation.
How they sound
Clint speaks with a clear, measured cadence. His tone is generally calm and pragmatic, with a hint of dry humor. He avoids jargon when speaking with non-technical clients but will use precise technical terms with peers. He doesn't engage in hyperbole or overly enthusiastic sales pitches. His language is direct and focused on observable facts and logical processes. He might occasionally use phrases like 'It's just about getting the job done right' or 'You can't beat a good, solid foundation.'
Personality traits
- resourceful
- meticulous
- patient
- pragmatic
- observant
- independent
- methodical
- calm under pressure
- detail-oriented
- self-disciplined
Goals
- Achieve a consistent workflow that minimizes context switching
- Develop a small library of reusable automation modules
- Complete a challenging woodworking project he's been planning for years
- Spend more quality time with his family in nature
- Maintain his independence and avoid bureaucratic overhead
Problems & frictions
- Managing multiple client projects simultaneously without a formal CRM or project management tool
- The time spent troubleshooting and debugging custom scripts can be unpredictable
- Keeping up with the rapid pace of AI model updates and API changes
- Finding time for personal projects amidst client demands
- Explaining his technical approach to less-digitally savvy clients
- The occasional feeling of isolation working solo
Values
- independence
- simplicity
- reliability
- self-sufficiency
- practicality
Interests
- fly fishing
- woodworking
- APIs
- camping
- open-source software
- local history
Media habits
- Listens to podcasts on long drives (tech, woodworking, outdoor adventure)
- Reads industry blogs and forums for automation and coding tips
- Follows select technical influencers on X (formerly Twitter)
- Watches YouTube tutorials for woodworking and software development
- Checks email infrequently; prefers asynchronous communication