10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Matthew Wolf

Matthew Wolf

Small architectural team lead

Full-depth AI personas

Why this persona fits the audience

Leads a 3-person residential architecture practice in Seattle that exchanges SketchUp files with consultants, and the office archive is split across 2022 and 2023 installs while incoming vendor files often arrive from 2024–2026 versions. He keeps a paid conversion utility in the workflow and logs project file versions in a shared spreadsheet.

  • Age: 41
  • Location: Seattle, WA, US
  • Occupation: Architectural team lead
  • Income: $118k
  • Education: Master's degree in architecture
  • Company size: 3 employees
  • Years in role: 5
“Architecture is 90% coordination and 10% inspiration; if you can't get the files to talk to each other, the best design in the world is just a pretty picture nobody can build.”

Matthew Wolf has been navigating the complexities of residential architecture in Seattle for nearly two decades. Holding a Master's degree from the University of Washington, he transitioned from working at large firms to founding his own boutique practice five years ago, driven by a desire for autonomy and a more human-scale approach to housing. At 41, he sits comfortably in the upper-middle class, earning $118,000 annually, which allows him to live in a historic home in Capitol Hill and provide a solid foundation for his young family. His professional identity is deeply tied to precision; he views the architecture profession not just as art, but as a rigorous exercise in problem-solving and risk management. His current operational reality is defined by a specific technological bottleneck: the fragmentation of file formats within the industry. While his firm operates on a stable mix of 2022 and 2023 SketchUp installations, the broader ecosystem of structural engineers, interior designers, and fabricators has already migrated to 2024, 2025, and even 2026 versions. This disparity forces Matthew to act as a digital translator. He cannot simply upgrade his entire suite immediately due to budget constraints and the learning curve for his small team, nor can he ask vendors to downgrade their outputs. Consequently, he has integrated a paid conversion utility into his daily routine, treating it as essential infrastructure rather than a luxury. This reliance on manual processes extends beyond file conversion. Matthew maintains a highly detailed, shared spreadsheet that logs every project file, its source version, and the date of conversion. This system is his insurance policy against data loss and version conflicts. It reflects his personality: conscientious, organized, and slightly anxious about the unknown variables introduced by external partners. He is a man who finds comfort in systems and spreadsheets, believing that if a process is documented, it can be controlled. Despite the pressures of running a small business in a competitive market, Matthew remains optimistic, viewing his role as a stabilizer for both his team and his clients. He is currently focused on scaling his operations without sacrificing the quality control that defines his brand, constantly evaluating whether new tools will truly streamline his workflow or merely add complexity to an already intricate puzzle.

Background & daily life

A day in their life

The day begins at 5:30 AM with a run along the canal, a non-negotiable ritual to clear his mind. By 7:30 AM, he is at his desk, checking emails and reviewing the overnight email queue from international consultants. At 9:00 AM, a stand-up with his two associates covers the morning's priorities, focusing heavily on the 'Westlake Townhouse' model which arrived in an incompatible format this morning. Matthew spends the next hour manually downconverting the file using his paid utility, then meticulously logging the hash and version in their shared tracker. Lunch is eaten quickly at his desk while reviewing construction documents. Afternoon hours involve client calls and refining design details. Late afternoon is reserved for administrative cleanup, ensuring all project folders are named correctly for the next fiscal year. He leaves by 5:30 PM sharp to attend his daughter's soccer game, refusing to let work bleed into family time.

Lifestyle

Matthew lives in a renovated Craftsman home in Capitol Hill, a choice reflecting his appreciation for structural integrity and local history. His weekday mornings are rigid: a 5:30 AM run along the Burke-Gilman Trail before the city wakes, followed by a quick breakfast with his wife and toddler. Weekends are reserved for family time or solo 'urban walks' where he critiques neighborhood zoning and building facades. Financially, he is conservative; every dollar spent on software or household repairs must yield immediate, tangible utility. He avoids debt but invests heavily in high-quality tools that last, viewing his career longevity as a direct result of consistent, disciplined habits rather than risky leaps.

Work life

Running a three-person studio means Matthew wears every hat, from lead designer to billing clerk. His office relies on a hybrid legacy system: two workstations run SketchUp 2022/2023, while his own machine is updated to 2024. This creates a constant friction point when external engineers or contractors send models created in 2025 or 2026. To maintain data integrity, he maintains a strict version control spreadsheet in Google Sheets, logging every file exchange and its corresponding software version. He spends roughly 20% of his week managing these digital handoffs, ensuring that no geometry is lost during translation. The pressure isn't just creative; it's logistical, requiring him to be the ultimate gatekeeper of technical compatibility.

Relationships

Matthew is married to Elena, a pediatric nurse who grounds him with her practicality. They rely on a close-knit circle of five other architect couples for weekend gatherings. Professionally, he trusts his two associates implicitly but feels isolated in his role as the sole decision-maker for technical workflows. He values feedback from senior mentors in the AIA but rarely seeks validation on financial decisions, preferring to calculate risks himself. His relationship with clients is formal yet warm; they view him as a steady hand in a chaotic industry.

How they decide

Matthew is a research-heavy, cautious decider. He does not impulse buy software or tools. Instead, he tests free tiers extensively, reads documentation line-by-line, and consults peer reviews on niche forums. He prioritizes stability over novelty; if a tool introduces a new variable into his established workflow, he demands proof of reliability before adoption. He prefers transparent pricing and clear ROI calculations, often creating spreadsheets to compare long-term costs versus immediate benefits.

How they sound

Matthew speaks with a measured, mid-Atlantic cadence, typical of Pacific Northwest professionals. He avoids slang and hyperbole, preferring precise verbs like 'coordinate,' 'verify,' and 'integrate.' He rarely says 'I think' or 'maybe'; instead, he uses 'the data shows' or 'based on the specs.' He avoids complaining about technology failures, framing them as 'workflow gaps' to be solved. When discussing money, he is blunt but polite, focusing on value rather than price tags.

Personality traits

  • meticulously organized
  • calm under pressure
  • pragmatic
  • detail-oriented
  • methodical
  • reliable
  • systematically skeptical
  • collaborative but firm
  • future-planning
  • resourceful

Goals

  • Stabilize the firm's revenue stream to hire a dedicated project coordinator
  • Complete the current 'Greenwood Rowhouse' renovation with zero change orders due to modeling errors
  • Reduce administrative overhead by automating file version tracking
  • Maintain a 40-hour work week to preserve family time
  • Establish the firm as a leader in sustainable, adaptive-reuse residential design

Problems & frictions

  • Constant manual intervention required when receiving newer SketchUp files from vendors
  • Risk of data corruption when converting complex geometries between disparate versions
  • Time lost searching through archived project folders spanning multiple OS and software years
  • Difficulty keeping junior staff aligned on version standards without a centralized plugin
  • Balancing the cost of new licenses against the need to keep older client files accessible
  • Frustration with inconsistent file naming conventions from outside consultants

Values

  • accuracy
  • coordination
  • reliability
  • efficiency
  • transparency

Interests

  • residential architecture
  • project planning
  • urban walks
  • mid-century modernism
  • local trail running

Media habits

  • ArchDaily for trend monitoring
  • SkyscraperCity forums
  • Local neighborhood Nextdoor groups
  • Podcasts on urban design history
  • LinkedIn professional updates

Questions & answers

Matthew Wolf’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying DOWNCONVERT SKETCHUP FILES (https://downconvert-sketchup-files.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My current workflow relies on a paid conversion utility, which I've integrated and logged meticulously in a spreadsheet. While this tool works, I'm always evaluating options. The biggest hurdle for me is ensuring reliability and data integrity, as I can't afford any geometry loss or compatibility issues. The "Unlimited lifetime" option for $24.90 is intriguing, as it would eliminate the per-conversion cost and the need for manual logging if it proves consistently reliable. I'd need to test its performance with various vendor file versions before committing.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.