Mack Konopelski

Why this persona fits the audience

Leads technology for an 8-person Austin startup and already uses a custom spreadsheet plus GitHub issues to track renewals for infrastructure, monitoring, and developer tools; he reviews the sheet during budget planning and stores some personal subscriptions there too.

• Age: 37
• Location: Austin, TX, USA
• Occupation: CTO/cofounder
• Income: $150k
• Education: Bachelor's degree
• Company size: 8 employees
• Years in role: 4 years

“If I can't write a script to automate it in ten minutes, it's not worth my time.”

Mack Konopelski is a 37-year-old CTO and cofounder navigating the precarious waters of an eight-person startup in Austin, Texas. With a Bachelor's degree in Computer Science and nearly two decades of experience in systems architecture, he transitioned from senior engineering roles at larger tech firms to the high-stakes environment of a fledgling venture. Mack's approach to leadership is defined by a relentless pursuit of efficiency and a deep skepticism of bloated enterprise software. He believes that the best tools are those that disappear into the background, allowing the work to speak for itself. Currently, Mack manages the entire technical infrastructure of his company, including a complex web of cloud providers, monitoring services, and developer tools. Rather than subscribing to expensive SaaS platforms for license management, he engineered a custom solution: a meticulously maintained Google Spreadsheet integrated with GitHub Issues. This hybrid system serves as his central nervous system for financial operations, tracking everything from AWS credits to niche developer API keys. He personally reviews this sheet every quarter during budget planning, cross-referencing usage logs against invoices to ensure nothing is wasted. Interestingly, he extends this discipline to his personal life, storing his own streaming and software subscriptions in the same file, blurring the lines between professional rigor and personal finance. Mack's personality reflects a balance of high openness and conscientiousness. He is constantly experimenting with new hardware, often building custom mechanical keyboards or upgrading his home lab, driven by a desire to understand the underlying mechanics of the devices he uses. Despite the chaos of a startup, he maintains a structured routine centered around trail running, which provides the mental space necessary for complex problem-solving. He earns a solid income, yet he remains frugal, viewing every dollar spent as an investment in either time saved or capability gained. His recent decision to reject a popular competitor's offering was based solely on the lack of a local-first architecture, a principle he holds dear. For Mack, control isn't just a buzzword; it's a survival mechanism in a world where a single overlooked notification can cost the company thousands of dollars.

Background & daily life

A day in their life

The alarm goes off at 5:30 AM. Mack wakes up, brews a batch of coffee using a pour-over method, and hits the trails for a 90-minute run through the Lady Bird Lake hike-and-bike path. Back home, he showers quickly, eats a protein-rich breakfast, and sits at his standing desk. By 8:30 AM, he checks the custom renewal spreadsheet, scanning for any expiring licenses or upcoming invoices. He joins a stand-up call with his distributed team, discussing the deployment pipeline. Most of the morning is spent writing Rust code for a new microservice, interrupted only by Slack pings about production errors. Lunch is a quick salad eaten while reading a technical newsletter. Afternoon meetings are reserved for vendor negotiations and strategic planning. Late afternoon is dedicated to reviewing GitHub issues for subscription alerts he created earlier. He leaves the office by 6:30 PM, runs errands to pick up groceries, and spends an hour tinkering with a smart home automation script before bed.

Lifestyle

Mack lives in a sun-drenched, converted garage apartment in East Austin, filled with server racks that hum softly in the corner and a wall of mechanical keyboard switches. His mornings are ritualistic: cold brew coffee, a 10-mile trail run through the nearby greenbelt to clear his head, then immediately diving into code before the market opens. He treats money as a resource to be optimized rather than hoarded, preferring to spend on hardware that lasts or software that saves hours. Socially, he is selective, preferring one-on-one dinners with co-founders or quiet evenings debugging local scripts over loud networking events. His health routine is integrated into his day—running replaces gym time, and he cooks simple, high-protein meals to maintain energy levels for long coding sprints.

Work life

As CTO and cofounder of an eight-person Austin startup, Mack wears every hat except sales. His days are a chaotic mix of architectural planning, code reviews, and fire-fighting infrastructure outages. He manages a stack of cloud services, monitoring tools, and SaaS subscriptions critical to the company's operation. Instead of paying for enterprise management tools, he maintains a bespoke Google Sheet linked to a private GitHub repository where renewal dates are logged as issues. This 'spreadsheet OS' allows him to see exactly when costs hit and negotiate terms personally. The pressure is constant; a missed renewal means downtime for the product, so his attention to detail is razor-sharp. He spends his afternoons in deep focus, often wearing noise-canceling headphones, while his small team relies on his technical decisions to keep the ship moving.

Relationships

Mack has a tight-knit circle of three close friends, mostly fellow founders who understand the unique pressures of early-stage startups. He is estranged from his parents but stays in weekly video calls with his sister, who handles his family finances. His professional network is extensive but shallow, consisting mostly of peers he meets at local Austin meetups or via Discord. He values transparency in relationships and avoids people who are vague about their intentions. His primary influence comes from engineering blogs and peer recommendations rather than marketing campaigns.

How they decide

Mack operates on a 'build it yourself first' heuristic. When faced with a problem, he immediately evaluates if existing tools can be hacked together with minimal configuration. If a solution requires significant setup time or ongoing maintenance overhead, he rejects it regardless of feature richness. He makes decisions based on data he can verify himself, often digging into documentation or source code before committing. Peer validation matters only if it comes from trusted technical sources. He is cautious about locking into long-term contracts without a trial period and prefers monthly billing to maintain flexibility.

How they sound

Direct, efficient, and devoid of corporate jargon. He speaks in short, declarative sentences, often prefacing thoughts with 'Here's the thing' or 'Let's cut to the chase.' He uses technical metaphors casually ('That's a race condition in our workflow') and avoids fluff. There is no enthusiasm for marketing speak; he values precision. He tends to interrupt politely if someone circles the issue, preferring immediate solutions over lengthy explanations. His tone is calm but firm, reflecting a background where ambiguity leads to system failures.