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

Jose Durgan

Jose Durgan

Boutique agency owner using a paid alternative

Full-depth AI personas

Why this persona fits the audience

He runs a 4-person design-and-build studio in Chicago. For client projects that start in Webflow, the team exports code into GitHub repositories as part of their standard handoff and archive process, and the studio is on a paid subscription to a third-party Webflow-to-GitHub sync tool. He still keeps a spreadsheet of which clients are on which repo.

  • Age: 46
  • Location: Chicago, IL, US
  • Occupation: Agency owner
  • Income: $140k
  • Education: Some college, self-taught web design
  • Company size: 4
  • Years in role: 12
“I didn't start this agency to get rich - I started it to build something that lasts. Every tool we add has to prove it'll keep working when the next shiny thing comes along.”

Jose Durgan grew up in a blue-collar Boston neighborhood, the son of a plumber and a bookkeeper. After dropping out of community college, he taught himself web design through forums and trial-and-error. His first agency job was with a Chicago marketing firm, where he honed his skills building websites for small businesses. In 2010, he struck out on his own with a promise to deliver quality work without the big agency price tag. The 4-person studio he runs today specializes in Webflow development for boutique retailers and service businesses. His team's workflow is a carefully refined process: client projects start in Webflow, get exported to GitHub via a paid sync tool, and are meticulously tracked in an increasingly unwieldy spreadsheet. Jose is skeptical of 'disruptive' tools but recently upgraded to a newer sync service after numerous sync failures with the old one. He's particularly proud of his team's ability to deliver consistent results, though he worries about scaling the business without losing that personal touch. Money is tight but stable, and he's careful about where he invests - preferring reliable over cutting-edge. His biggest professional fear isn't competition, but the quiet dread of a tool failure during a critical project. At home, he's the coach and project manager, balancing family life with the demands of running a small business. His biggest challenge isn't finding work, but finding the right work - clients who value craftsmanship over cheap solutions. On weekends, you might find him at a Cubs game, debating the finer points of bullpen management with fellow small business owners, or at home working on weekend DIY projects with his sons. His approach to business reflects his baseball fandom: well-prepared, patient, and always looking for solid singles rather than swinging for the fences.

Background & daily life

A day in their life

Jose's alarm goes off at 6:00 AM. After a quick run, he showers and grabs coffee while checking Cubs pre-game coverage. By 8:00 AM, he's in his Logan Square office, reviewing the day's schedule. First up is a client call about a website redesign. He spends 90 minutes going over Webflow mockups before lunch. Afternoon is split between team standup and debugging a GitHub sync error. At 5:30 PM, he wraps up admin work, then heads home for dinner with his family. After the boys are in bed, he'll skim industry blogs or listen to a business podcast before bed.

Lifestyle

Jose lives in a 1920s bungalow in Logan Square that he and his wife spent years renovating. His morning routine includes a black coffee while checking baseball box scores, then a 5-mile run through the neighborhoods. Weeknight dinner is often a quick meal while helping his sons with homework or baseball practice. He budgets carefully, preferring to invest in tools that save time over luxury items. His social life revolves around a small group of fellow small business owners, with whom he exchanges war stories over beers at a local gastropub. Health-wise, he's vigilant about recovery runs and keeps a protein shake in his office for after lunchtime headaches.

Work life

Running a small studio means Jose wears many hats, from client calls to managing his two designers and one developer. His team's workflow follows a meticulous process: Webflow prototypes get built, exported to GitHub via their paid sync tool, and managed through an elaborate spreadsheet that tracks which client owns which repo. He's constantly balancing the need for automation with cost control, which is why he's skeptical of new tools despite his team's requests. His office smells like fresh coffee and vinyl records - he plays classic soul while working. client projects often involve late nights when deadlines loom, but he strictly enforces family dinner time.

Relationships

Jose's closest relationships are with his wife of 18 years (a high school math teacher) and his two sons, both baseball players. His business relationships are a mix of fellow boutique agency owners and long-term clients. He trusts one particular developer friend for technical advice but is wary of most industry

How they decide

Methodical research paired with gut instinct after gathering facts. Slow to adopt new systems, but once convinced, implements thoroughly. Relies on recommendations from peers and detailed feature comparisons. Prefers incremental improvements over disruptive changes. Will test new tools in private before rolling out to team.

How they sound

Speaks in measured, deliberate sentences with occasional dry humor. Uses baseball metaphors liberally. Prefers concrete examples over abstract concepts. Avoids tech jargon with clients. Direct but not abrupt. Occasionally lapses into Irish brogue from his childhood in Boston. His voice lowers when discussing failure or financial risks. Uses spreadsheets as both tools and worry objects ('let me pull up the numbers').

Personality traits

  • methodical in onboarding processes but flexible in execution
  • prone to competitive pricing anxiety despite stable bookings
  • secretly enjoys tinkering with automation systems
  • maintains a meticulous but slightly outdated client spreadsheet
  • will debate baseball strategies with surprising passion
  • avoids technical jargon with non-developer clients
  • always checks sync tool logs before client meetings
  • keeps snacks in his office for impromptu team brainstorming

Goals

  • Grow the agency to 6 people within 3 years
  • Buy a small cabin near Lake Michigan
  • Coach his son's high school baseball team
  • Improve the studio's project handoff documentation
  • Build a client onboarding system that doesn't rely on spreadsheets

Problems & frictions

  • The current GitHub sync tool occasionally misses dependencies
  • Client handoffs keep requiring last-minute manual fixes
  • Team members have different preferences for design systems
  • Finding reliable subcontractors for overflow work
  • Worried about being undercut by freelancers on big projects
  • His spreadsheet tracking system is becoming untenable

Values

  • client trust
  • business stability
  • repeatable delivery
  • work-life balance
  • pride in craftsmanship
  • skepticism of flashy solutions

Interests

  • small business operations
  • design tools
  • baseball
  • podcasting
  • local food scene
  • DIY home projects

Media habits

  • listens to business podcasts during morning commute
  • reads industry blogs 2-3 times per week
  • watches Cubs games on TV with family
  • binges documentary series on weekends
  • avoids LinkedIn afterburner culture

Questions & answers

Jose Durgan’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Automatically export Webflow code to GitHub repositories What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest headache is when our sync tool messes up dependencies. Last month, we had a client handoff where half their assets didn't transfer right—I spent three billable hours manually fixing it. Worse, one client noticed and asked why we couldn't just give them a clean repo. I tried different sync services before settling on this one, but even paying $50/month for the 'premium' version hasn’t solved it. The tool’s logs say it’s 'complete,' but I catch errors every other project. My dev swears it’s the sync tool’s fault, but I can’t afford downtime to re-test everything. At this point, I’d pay to avoid another late-night fix, but only if it actually works.
    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.