Aaron Brakus

Why this persona fits the audience

Co-runs a 4-person operations consulting shop in Chicago and spends a lot of time turning meeting notes into proposals, project plans, and client-ready summaries. He already uses a mainstream AI assistant for some drafting, but keeps other work in offline documents and spreadsheets because much of the material is tied to client contracts and internal planning.

• Age: 52
• Location: Chicago, Illinois, US
• Occupation: Co-founder and consultant
• Income: $118k
• Education: MBA
• Company size: 4 people
• Years in role: 6

“Efficiency means nothing if you have to trade the integrity of your work for it.”

Aaron Brakus is a 52-year-old co-founder of a boutique operations consultancy in Chicago, specializing in helping mid-sized manufacturers streamline their supply chains and internal workflows. With an MBA from the University of Chicago Booth School of Business earned twenty years ago, Aaron built his firm from the ground up, driven by a philosophy that operational excellence requires both rigorous analysis and deep human understanding. Unlike many tech-forward entrepreneurs, Aaron remains deeply skeptical of the 'move fast and break things' mentality. He has spent the last decade refining a hybrid work model where he leverages mainstream AI assistants for initial drafting but insists on keeping all final contracts, financial models, and strategic roadmaps in offline, locally stored documents. This stance stems from a specific incident five years ago when a competitor leaked client data via a third-party API, cementing his belief that true privacy requires air-gapped solutions. His daily reality is a constant negotiation between the desire for automation and the fear of obsolescence. He finds himself spending nearly forty percent of his week on the mundane task of converting rough meeting notes into polished, client-ready proposals—a bottleneck that limits the firm's ability to scale beyond four consultants. While he recognizes the potential of on-device AI to solve this friction, he is currently paralyzed by the lack of verified, offline-only solutions that meet his strict security criteria. He drives a reliable, ten-year-old Subaru Outback, wears tailored suits that have seen better days but remain pressed, and keeps a leather-bound planner on his desk that he updates by hand every evening. For Aaron, success is not about being the fastest in the room, but about being the most reliable. He views his role not just as a service provider, but as a steward of his clients' confidential information, a responsibility he takes with a gravity that often slows him down but never compromises his output.

Background & daily life

A day in their life

Aaron wakes at 5:30 AM to a quiet house, making coffee and reviewing his calendar on a tablet that hasn't synced overnight to ensure privacy. By 7:00 AM, he is at his desk, sifting through voicemails from a morning client call in downtown Chicago. He spends the first hour transcribing key points into a local Word document, carefully filtering out irrelevant chatter. At 9:00 AM, he joins a virtual meeting with a manufacturing client, taking handwritten notes in a Moleskine notebook alongside his laptop screen. Lunch is a quick sandwich eaten while reviewing a complex budget spreadsheet, avoiding email distractions. The afternoon is dedicated to drafting a project proposal, where he struggles to summarize the client's ambiguous requirements into clear milestones without over-promising. He finishes work at 6:00 PM, shuts down his computer completely, and heads to the gym. Dinner with Elena is device-free, focusing on decompressing from the day's mental load. He reads for an hour before bed, ensuring he sleeps enough to tackle the synthesis work again tomorrow.

Lifestyle

Aaron lives in a renovated Victorian row house in Lincoln Park with his wife, Elena. Their financial life is conservative; they prioritize paying off their mortgage early and funding college savings over luxury vacations or high-risk investments. His routine is rigid: he wakes at 5:30 AM to review the day's schedule before the household noise begins, exercises by jogging along the lakefront three times a week, and maintains a strict separation between work and family time. While he enjoys fine dining occasionally, he prefers cooking simple, healthy meals at home. Socially, his circle consists mostly of long-standing colleagues and neighborhood friends rather than a wide network of acquaintances. He values quiet evenings reading physical books or working on his antique watch collection, viewing leisure as a time for restoration rather than stimulation.

Work life

As co-founder of a four-person ops consultancy, Aaron splits his week between client strategy sessions and the unglamorous backend of running the firm. His days are fragmented by back-to-back Zoom calls, often followed by intense periods of synthesizing raw audio transcripts into polished deliverables. He relies heavily on Microsoft Excel for financial modeling and keeps sensitive contract drafts in local Word files rather than the cloud, citing confidentiality concerns. The team operates out of a shared office space in the Loop, where Aaron acts as the de facto quality control officer, manually editing every proposal before it goes to a client. The pressure comes not from revenue generation, which is stable, but from the administrative bottleneck of translating vague client conversations into actionable, legally sound project scopes without losing the human nuance in the process.

Relationships

Aaron's closest relationship is with his wife, Elena, who manages their household finances and offers a grounding perspective on business risks. He has a cordial but professional rapport with his co-founder, Sarah, who handles sales while he focuses on delivery. His children are adults living in different states, so contact is limited to weekly video calls. He belongs to a local alumni group from his MBA program, which serves as his primary source of peer advice. He trusts no one implicitly with his private data, preferring to vet any new tool through a rigorous, personal trial period before introducing it to his team.

How they decide

Aaron is a cautious, research-heavy decider who prioritizes security and proven utility over novelty. He rarely adopts a new technology until it has been validated by a trusted peer or has survived a prolonged beta phase in his own environment. He avoids impulsive purchases, preferring to weigh the long-term implications of data ownership and integration costs. When evaluating options, he creates a pros-and-cons matrix based on specific constraints like offline capability and encryption standards, often spending weeks testing a single feature before committing to a workflow change.

How they sound

Aaron speaks with a measured, midwestern cadence, using precise vocabulary but avoiding corporate jargon unless necessary for client alignment. He tends to speak in complete, well-formed sentences, often pausing to choose the exact right word rather than filling silence. He is direct but polite, rarely raising his voice even when frustrated. He avoids slang and internet acronyms, preferring formal phrasing like 'I would suggest' over 'Let's do this.' In conversation, he listens more than he talks, often nodding thoughtfully before responding. He does not use hyperbole, describing situations with factual accuracy rather than emotional intensity. When discussing technology, he is skeptical and asks probing questions about security protocols before accepting any claim of efficiency.