Archie Langworth

Why this persona fits the audience

He maintains roughly a dozen client sites for local contractors, therapists, and niche retailers, mostly static HTML or light WordPress builds. Their contact and quote-request forms currently route to a shared Gmail inbox through simple SMTP settings, and he is the person who updates those form paths when a site changes.

• Age: 33
• Location: Austin, Texas, US
• Occupation: Freelance web developer
• Income: $95k
• Education: Bachelor's degree in computer science
• Company size: 1 (Sole Proprietor)
• Years in role: 7

“The best kind of work is the kind that just *works* without anyone having to think about it too much, especially the form submissions.”

Archie Langworth's journey into web development began not with a grand ambition, but with a practical need. During his undergraduate studies in Computer Science at UT Austin, he built a personal portfolio site and soon found himself fielding requests from friends and local businesses needing simple online presences. After graduating and spending a brief, uninspiring year at a small software firm doing backend support, he realized his knack for front-end development and client interaction was better suited to freelance work. He struck out on his own seven years ago, initially taking on small projects for friends. Over time, he cultivated a niche focusing on local small businesses – contractors, independent health practitioners, and niche retailers – who needed reliable, no-frills websites. His income has steadily grown to a comfortable $95k annually, allowing him a stable life in Austin, though he remains deliberately frugal, prioritizing reinvestment in his business and long-term security over conspicuous consumption. His current focus is on maintaining and incrementally improving about a dozen client sites, most of which are static HTML or basic WordPress builds. A recurring point of friction, and a constant minor annoyance, is the way contact and quote request forms are handled; they currently funnel into a shared Gmail inbox via simple SMTP. Archie is the de facto IT support for this aspect, meaning he's the one who has to track down why a form isn't working or update the recipient address when a client changes their email. This task, while seemingly minor, consumes valuable time and interrupts his development flow. Recently, he's been exploring more efficient ways to handle form data, considering anything that promises greater reliability and less manual intervention. He’s recently decided against pursuing a full-time role at a larger company, valuing the autonomy and direct client relationships his freelance career offers, even with its inherent instabilities.

Background & daily life

A day in their life

Archie's typical weekday begins around 7:30 AM with coffee and a walk with Pixel. By 9:00 AM, he's at his desk, reviewing Trello boards and emails. The morning is usually spent coding – perhaps refactoring some JavaScript for a local bakery's online ordering system or tweaking a WordPress theme for a therapist's website. Lunch is a quick affair, often a sandwich at his desk while catching up on tech news. Afternoons are more varied: a 1:00 PM video call with a contractor client about a new project quote, followed by addressing an urgent email about a broken contact form on a pet groomer's site. He aims to wrap up client work by 5:30 PM, then spends an hour or so on personal learning or practicing guitar before making dinner. Evenings are for winding down, maybe watching a documentary or reading.

Lifestyle

Archie lives in a rented two-bedroom bungalow in South Austin, sharing with a Golden Retriever named Pixel. He's a creature of habit, starting most mornings with a pour-over coffee brewed in his kitchen and checking project boards before heading to his home office. His income supports a comfortable but not extravagant lifestyle; he prioritizes experiences and tools that enhance his work over material possessions. He enjoys weekend hikes in the greenbelt, regular visits to local breweries with a few close friends, and tinkering with his Fender Stratocaster in the evenings. Financial discipline is key; he meticulously tracks business expenses and sets aside a significant portion of his income for taxes and future investments.

Work life

Archie's workday is a balancing act between client communication, coding, and site maintenance. He typically dedicates mornings to focused development and debugging, while afternoons are reserved for client calls, responding to emails, and managing server updates. His toolkit is lean but effective: VS Code for coding, Git for version control, and a local development environment using Docker. He rarely uses project management software beyond Trello boards for his own tracking, preferring direct communication with clients for task clarification. The pressure comes from managing multiple deadlines and ensuring the seamless operation of sites that are critical to his clients' small businesses, especially the intermittent chaos of form submissions going astray.

Relationships

Archie maintains a close-knit circle of friends, mostly met through university or shared professional interests. His parents, who live in a suburb of Dallas, are supportive but don't fully grasp the intricacies of his freelance work. He has a few long-term clients who he considers collaborators rather than just customers, and their trust is a significant motivator. His Golden Retriever, Pixel, is his primary confidant.

How they decide

Archie is primarily a research-driven decision-maker, especially when it comes to tools or processes that impact his workflow. He'll investigate options thoroughly, read reviews, check documentation, and often test solutions in a sandbox environment before committing. He values pragmatism and efficiency, leaning towards established, reliable solutions over flashy or unproven ones, unless a clear technical advantage is demonstrated. Peer recommendations carry some weight, particularly from developers he respects.

How they sound

Speaks clearly and at a moderate pace, with a slight Southern inflection that softens the edges of his technical jargon. He avoids overly casual slang in professional contexts but might use terms like 'sweet,' 'nifty,' or 'that's slick' when discussing elegant code or efficient solutions. He tends to be direct and to the point, but not abrupt, often prefacing potentially complex explanations with 'So, the way it works is...' or 'Essentially, we need to...' He's comfortable with technical terms but will simplify when necessary for clients.