Why this persona fits the audience
Leads a 5-person software agency in Chicago where project time is split across sales calls, implementation, support, and internal admin. The team works on MacBooks and currently mixes spreadsheets with a shared time tracker to keep client work and non-billable work separate.
- Age: 44
- Location: Chicago, Illinois, US
- Occupation: Agency founder
- Income: USD 145k owner's draw
- Education: Bachelor's in Information Systems
- Company size: 5
- Years in role: 8
“I don't need another dashboard; I need to know exactly where my time went so I can stop selling it for less than it's worth.”
Claude Mertz is the founder of a boutique software development agency in Chicago, a role he has held for eight years after earning a Bachelor's in Information Systems. Born and raised in the Midwest, he combines a pragmatic, engineering-focused upbringing with a modern entrepreneurial drive. At 44, he sits at the intersection of technical expertise and business ownership, managing a lean team of five developers and designers. His agency specializes in custom enterprise solutions, a niche that demands rigorous attention to detail and strict adherence to timelines. Despite the company's modest size, the complexity of their projects mirrors that of much larger firms, placing immense pressure on Claude to wear every hat—from lead architect to HR manager to CFO. Currently, Claude operates with a 'fix-it-as-you-go' mentality regarding operations. The team utilizes MacBooks and relies on a hybrid system of Google Sheets and a rudimentary time tracker to manage billable hours. This approach, while functional, creates significant friction at month-end when reconciling non-billable internal work against client deliverables. Claude is acutely aware that this manual overhead erodes margins and distorts his view of cash flow visibility. He recently made the decision to audit his entire workflow, realizing that his reliance on intuition rather than data was becoming a liability as the agency grew beyond his personal oversight capacity. Financially, Claude draws $145,000 annually, a figure he considers fair compensation for the risk he undertakes, yet he remains vigilant about reinvesting profits into better infrastructure. He views his time not just as a currency for income, but as a finite resource that must be optimized to sustain long-term growth. His recent decisions have focused on stabilizing the team's culture and reducing administrative drag, driven by a desire to reclaim weekends for his family. While he is open to new tools, his threshold for adoption is high; he seeks systems that offer immediate, tangible relief from the chaos of manual tracking rather than abstract promises of efficiency.
Background & daily life
A day in their life
Claude wakes at 5:30 AM for a quiet hour of reading and coffee before his family stirs. By 7:00 AM, he's commuting to his Lincoln Park office, listening to industry podcasts. The workday starts with a stand-up meeting to review the previous day's time entries, followed by a deep-dive into financial spreadsheets to reconcile the morning's invoices. Mid-morning is reserved for sales calls and client demos, requiring a sharp switch to a more charismatic persona. Lunch is often eaten at his desk while reviewing code documentation or supporting a stuck developer. Afternoons are fragmented by ad-hoc support issues and internal admin, leaving late afternoon for strategic planning. He leaves by 6:30 PM to ensure dinner with his family, though he often checks Slack until 8:00 PM. Evenings are spent helping kids with homework or prepping for the next day's critical tasks.
Lifestyle
Claude resides in a renovated two-story home in Lincoln Park with his wife and two young sons. His mornings begin at 5:30 AM with a precise pour-over coffee ritual before the house wakes up. Weekends are reserved for family activities, often involving hiking or local museum visits, though he remains mentally tethered to the week ahead. He maintains a disciplined running schedule three times a week, viewing physical endurance as a direct metaphor for business stamina. Financially, he is conservative; while he earns a solid draw, he keeps personal spending distinct from business capital, prioritizing an emergency fund that covers six months of payroll over luxury purchases.
Work life
As the de facto CEO and Chief Operations Officer of a five-person shop, Claude's day is a chaotic mix of high-level strategy and granular execution. He manages a distributed team using a patchwork of Google Sheets and a basic time-tracking tool, leading to constant reconciliation efforts at month-end. His primary friction point is the lack of real-time visibility into billable versus non-billable hours, which obscures true profitability. He spends significant time mediating between client expectations and developer capacity, often stepping in to handle critical support tickets himself when deadlines loom. The mental load involves constantly switching contexts between financial planning and technical troubleshooting.
Relationships
Claude is deeply embedded in the Chicago tech ecosystem but keeps his circle tight. He relies heavily on his wife for emotional stability and household management, allowing him to focus on the agency. His professional network consists mostly of other small agency owners who serve as sounding boards for operational challenges rather than sales leads. He trusts recommendations from peers who have faced similar scaling pains more than generic marketing claims. While he enjoys social gatherings, he often leaves early to prepare for the next day's critical meetings.
How they decide
Cautiously analytical and peer-influenced. Claude rarely makes impulsive technology purchases; he requires proof of concept and a clear ROI calculation before committing funds. He prefers solutions that integrate seamlessly with existing workflows rather than forcing a paradigm shift. Decisions are often validated by consulting a trusted mentor or a specific niche forum post. He values transparency and dislikes hidden fees or complex contract terms.
How they sound
His speech is measured, articulate, and devoid of hype. He uses industry terminology like 'billable utilization' and 'margin erosion' naturally but avoids jargon when explaining concepts to clients. He speaks with a mid-Western cadence—grounded and direct. He tends to ask clarifying questions before offering opinions, preferring to gather all variables first. He avoids vague promises and never speaks negatively about competitors publicly, focusing instead on specific functional gaps.
Personality traits
- methodical
- pragmatic
- direct
- protective of team time
- data-obsessed
- resilient
- systematic
- moderately social
- detail-oriented
- steady under pressure
Goals
- Achieve 30% net profit margin without increasing headcount
- Standardize the onboarding process to reduce implementation time by 20%
- Eliminate manual spreadsheet reconciliation by Q3
- Establish a predictable weekly rhythm for the team to prevent burnout
- Secure a recurring revenue stream that covers 60% of operating costs
- Take a fully unplugged two-week vacation with family once a year
Problems & frictions
- Difficulty distinguishing billable client work from internal R&D in current tracking tools
- Time lost manually consolidating data from multiple sources for financial reporting
- Inconsistent time-entry habits among junior developers affecting billing accuracy
- Uncertainty about true hourly value per employee due to administrative overhead
- Client scope creep eating into project margins without immediate detection
- Lack of a single source of truth for project health and resource allocation
Values
- cash flow visibility
- responsibility
- team coordination
- client retention
- operational clarity
- work-life boundaries
Interests
- small agencies
- systems optimization
- specialty coffee brewing
- family travel planning
- local architecture tours
- marathon training
Media habits
- Substack newsletters on SaaS metrics
- Morning NPR podcasts during commute
- Hacker News for tool discovery
- LinkedIn for industry peer updates
- Local Chicago business journals
- YouTube tutorials on Rust/DuckDB