Delbert MacGyver

Why this persona fits the audience

He oversees a five-person software consultancy and uses acquisition lists, shutdown archives, and manual scoring to pick software categories that could be rebuilt with AI during internal hack weeks. He cross-checks everything himself before letting the team spend dev time.

• Age: 42
• Location: Manchester, UK
• Occupation: CTO at a B2B software consultancy
• Income: £110k + bonus
• Education: BEng Software Engineering
• Company size: 5 full-time employees
• Years in role: 6

“You can build anything with AI, but you have to know exactly why you're building it, or you're just automating waste.”

Delbert MacGyver is a 42-year-old software architect and CTO based in Manchester, leading a boutique consultancy of five engineers specializing in B2B solutions. With a BEng in Software Engineering from the University of Manchester and over two decades of industry experience, Delbert has transitioned from pure development to strategic leadership, focusing heavily on the intersection of legacy systems and emerging AI capabilities. Unlike many executives who delegate technical vetting, Delbert insists on personally auditing every potential project. His methodology involves mining historical acquisition databases and shutdown archives to identify software categories that were once viable but have become obsolete due to technological shifts. He believes these 'ghost' applications hold immense value if rebuilt with modern AI leverage. His role is defined by a paradox: he leads a small team that must move fast, yet he imposes a slow, meticulous validation phase to prevent wasted effort. This 'gatekeeper' mentality stems from a deep-seated belief in accountability; he refuses to let his team burn billable hours on ideas that haven't been rigorously stress-tested against market reality. Recently, he has been spending significant evenings and weekends manually scoring hundreds of potential ideas using custom spreadsheets, a process he finds tedious but necessary. He views the current wave of AI hype with suspicion, preferring to wait for concrete use cases where AI solves actual business problems rather than chasing novelty. Financially, Delbert is secure but not extravagant, earning a solid salary plus performance bonuses. He values stability and is focused on growing the consultancy's equity value rather than seeking a quick exit. His professional identity is built on resilience and precision; he is the person who stays calm when a deployment fails, immediately pivoting to root cause analysis. In his free time, he retreats to the outdoors, finding solace in long cycling rides where the rhythmic motion allows his mind to process complex architectural problems without the distraction of screens. He is a man who respects the craft of coding, even as he embraces the tools that promise to change it.

Background & daily life

A day in their life

Delbert wakes at 5:30 AM, immediately checking emails for any critical alerts from overnight deployments, then heads out for a 45-minute commute into central Manchester. His morning is dedicated to deep work: analyzing a spreadsheet of 400 acquired software companies, cross-referencing them with current market trends to find gaps ripe for AI reconstruction. At 10:00 AM, he joins a client call to discuss a migration strategy, acting as the translator between business needs and technical feasibility. Lunch is a quick sandwich eaten at his desk while reading a paper on transformer architectures. Afternoon meetings involve reviewing pull requests from his team, often rejecting half of them for minor architectural flaws. By 4:30 PM, he steps back from coding to plan the next week's hack week topics, manually scoring ideas against his own rubric. He leaves the office by 6:00 PM, avoiding late-night crunch unless absolutely necessary, and spends his evening cooking dinner with his family before bed.

Lifestyle

Delbert lives in Chorlton, an area known for its independent coffee shops and cycling infrastructure. His weekends are split between school runs, helping his kids with homework, and long-distance cycling rides along the Peak District trails where he can think clearly without digital interruptions. He is financially prudent, prioritizing mortgage repayment and pension contributions over luxury goods, though he splurges occasionally on high-end mechanical keyboards or vintage tech. Health-wise, he manages stress through consistent exercise rather than meditation apps, which he finds too abstract. Socially, he prefers deep one-on-one conversations over large networking events, often meeting old university mates for pints and technical debates rather than drinking to unwind.

Work life

As the CTO of a tight-knit consultancy, Delbert is the final gatekeeper for all technical decisions. His days are a mix of client strategy calls, code reviews, and managing the 'hack week' pipeline. He personally audits every potential project idea, digging into historical acquisition data and churn reports to validate concepts before the team writes a single line of code. The pressure comes from the need to prove ROI quickly to clients while maintaining the team's morale; if a project fails, it eats directly into their billable hours. He relies heavily on GitHub Copilot but never trusts it blindly, manually verifying every generated module against architectural standards.

Relationships

Delbert is married to Sarah, a primary school headteacher, whose pragmatic outlook keeps him grounded. Their friendship with other parents at the local schools provides a buffer against work stress. Professionally, he maintains a small circle of trusted peers—mostly CTOs of smaller firms—who act as sounding boards for difficult strategic decisions. He rarely seeks public validation, preferring private feedback from these few trusted sources over broad social media engagement.

How they decide

Delbert employs a rigorous, evidence-based decision-making framework. He is inherently cautious, requiring multiple data points and personal verification before committing resources. He does not rely on peer consensus or marketing narratives; instead, he builds mental models based on historical patterns and first-principles reasoning. While he is open to new technologies, his default setting is skepticism until proven otherwise through tangible results or reproducible data.

How they sound

Delbert speaks in a measured, articulate Mancunian accent, favoring precise vocabulary over colloquialisms. He avoids hyperbole, rarely using words like 'revolutionary' or 'game-changing' unless he has hard data to back it up. His cadence is steady and deliberate, pausing frequently to ensure accuracy. He tends to speak in conditional statements ('If we do X, then Y should happen') rather than absolutes. He avoids jargon when speaking to non-technical stakeholders but switches to dense technical terminology with his team. He dislikes small talk and prefers to get straight to the point, viewing time as a finite resource that must be spent efficiently.