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

Colin Goodwin-Daugherty

Colin Goodwin-Daugherty

Founder and product lead at a legaltech microstartup

Full-depth AI personas

Why this persona fits the audience

He runs a 4-person legaltech startup where an AI intake agent triages document requests and sends status updates to Slack and email; the team has kept the setup inside a mix of spreadsheets, webhooks, and a few manual checks.

  • Age: 33
  • Location: Edinburgh, UK
  • Occupation: Founder and product lead
  • Income: £64k salary plus equity
  • Education: LLB and self-taught coding
  • Company size: 4
  • Years in role: 2.5
“In this line of work, a mistake isn't just a bug; it's a breach of someone's trust, and you only get one chance to fix it before the cost becomes real.”

Colin Goodwin-Daugherty is a 33-year-old polymath operating at the intersection of law and software engineering in Edinburgh. Holding an LLB from the University of Edinburgh, he initially practiced commercial law for four years before becoming disillusioned with the inefficiencies of manual document processing. This frustration sparked a transition into self-taught coding, driven by a desire to build tools that solved his own pain points. Two and a half years ago, he founded a micro-startup focused on legal intake automation. With a team of three others, he manages a lean operation where the core product relies on a bespoke AI agent that triages incoming documents via email and Slack. The infrastructure is a testament to his resourcefulness: a patchwork of Google Sheets, Zapier-style webhooks, and custom Python scripts hosted on affordable cloud servers. Despite the simplicity of the stack, the stakes are high; accuracy is paramount, and Colin personally audits the output of every automated decision before it reaches a client. He earns a modest £64k salary alongside significant equity, a trade-off that reflects his belief in long-term value creation over immediate liquidity. His recent focus has been on stabilizing the notification pipeline, having manually intervened dozens of times to prevent data loss during peak usage. Colin is known in his niche for his meticulous documentation and his refusal to scale until the underlying processes are bulletproof. He balances this intense professional focus with a disciplined personal life centered on marathon training and a deep commitment to his local football club, using physical exertion to manage the mental load of building a business in a highly regulated sector.

Background & daily life

A day in their life

Colin rises at 5:30 AM, lacing up his running shoes for a ten-kilometre loop around the Water of Leith. By 7:15 AM, he is brewing strong coffee and reviewing the overnight logs in his local terminal, checking for any failed webhooks or untriaged documents. He arrives at the shared office space in Leith by 8:30 AM, immediately joining a quick stand-up with the three other founders to align on daily priorities. Mornings are dedicated to deep work: refactoring the Python script that parses PDF contracts or debugging a webhook integration issue that caused a duplicate entry yesterday. Lunch is usually a quick sandwich eaten while reading a Substack newsletter about GDPR updates. Afternoons involve client calls, explaining why the AI needs more context on a specific case file, followed by time spent updating the master spreadsheet which serves as their CRM. The day winds down around 6:30 PM, often with a walk through Old Town to decompress, ensuring he leaves work at work before heading home to dinner with Sarah.

Lifestyle

Colin lives in a converted warehouse flat in Leith, a vibrant but gritty part of Edinburgh that mirrors his own professional aesthetic: functional, slightly industrial, but warm. He wakes up at 5:30 AM for a run along the waterfront before work, a ritual that grounds him against the chaotic nature of startups. His diet is strictly managed for energy efficiency—mostly home-cooked meals prepared in batches on Sundays. He is a season ticket holder for Hibernian FC, viewing football as a necessary escape from the high-stakes logic of law and code. Financially, he lives below his means, reinvesting almost all surplus cash into server costs or personal upskilling rather than luxury goods, viewing money primarily as fuel for operational resilience rather than status. Socially, he prefers small, deep conversations over large networking events, often meeting friends for coffee or a pint after a match rather than industry mixers.

Work life

As the sole technical founder, Colin's day is a juggling act between being a lawyer, a developer, and a customer support agent. The core product relies on a fragile ecosystem of Google Sheets acting as the source of truth, webhooks triggering Slack notifications, and occasional Python scripts running on cheap cloud instances. He spends mornings auditing logs for data anomalies and afternoons writing documentation or fixing bugs introduced by the previous night's automated intake. His three co-founders are specialists in sales, legal compliance, and marketing, leaving Colin as the central nervous system of the operation. The pressure is constant; a single missed webhook can mean a client's legal document sits unprocessed for hours, breaching trust. He maintains a 'manual override' mentality, frequently double-checking automated outputs because he doesn't fully trust the abstraction layer yet.

Relationships

Colin shares a close partnership with his girlfriend, Sarah, who works in graphic design; she is his primary sounding board for stress and life decisions. His professional network is tight-knit, consisting mostly of other founders in the 'LegalTech Scotland' circle and a few mentors from his LLB days who now practice in Glasgow. He trusts peer recommendations over industry analysts, often seeking advice from the IndieHackers community regarding technical debt. Family interactions are reserved for weekends, where he focuses entirely on disconnecting from work to play board games with his younger sister. He values loyalty deeply and rarely engages with people who prioritize hype over substance.

How they decide

Colin operates on a principle of 'verify then automate.' He is naturally cautious, preferring to prototype a solution manually before committing to a complex architectural shift. Decisions are data-driven but heavily influenced by risk assessment; if a new tool introduces a potential point of failure without clear, immediate ROI, he will defer adoption. He researches extensively, reading documentation and community forums, but ultimately makes the final call based on his own gut feeling about reliability. He is not swayed by flashy marketing or FOMO, requiring concrete proof of stability before integrating anything new into his stack.

How they sound

Colin speaks with a soft Edinburgh accent, precise and measured. He avoids hyperbole, preferring terms like 'likely,' 'probable,' or 'verified' over absolute statements. In conversation, he pauses frequently to formulate thoughts, showing he values accuracy over speed of speech. He rarely uses corporate buzzwords, finding them vague and often misleading. When discussing technology, he gets specific about protocols and error rates. He avoids complaining publicly, instead framing problems as 'optimization opportunities.' His tone is generally calm, even when discussing stressful deadlines, reflecting his low neuroticism score.

Personality traits

  • meticulous about data integrity
  • self-reliant
  • analytically skeptical
  • efficient communicator
  • understated enthusiasm
  • risk-aware
  • disciplined
  • curious about edge cases
  • pragmatic builder
  • quietly confident

Goals

  • Achieve product-market fit with a stable retention rate of 90% for beta clients
  • Automate 95% of the current manual verification steps within the next six months
  • Secure seed funding to hire a dedicated DevOps engineer
  • Publish a whitepaper on ethical AI application in Scottish conveyancing
  • Maintain a healthy work-life balance without sacrificing company velocity
  • Build a reputation as a trusted voice in the UK legal-tech space

Problems & frictions

  • The fragility of the current spreadsheet-based workflow creates single points of failure
  • Difficulty scaling the manual check process without increasing headcount prematurely
  • Integrating disparate data sources (Slack, Email, internal DB) without a unified API layer
  • Managing client anxiety when the AI intake agent encounters ambiguous document formats
  • Limited budget prevents purchasing enterprise-grade monitoring tools
  • Balancing rapid feature iteration with rigorous legal accuracy requirements

Values

  • accuracy
  • trust
  • speed
  • lean operations
  • pragmatism

Interests

  • legal tech
  • reading
  • football
  • indie software
  • historical architecture
  • marathon training

Media habits

  • The Lawyer's Weekly (digital)
  • IndieHackers podcast
  • Scottish Football news apps
  • Substack newsletters on regulatory change
  • NPR/Classic FM for commute
  • GitHub trending repositories

Questions & answers

Colin Goodwin-Daugherty’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on DevHunt: Custom notification hub for AI agents and everything else - the product is a notification relay platform built for the AI era. It lets your AI agents,... 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.

    Right now, the biggest problem is reliability in our notification pipeline. We're cobbling together Google Sheets, webhooks, and custom scripts, and it's brittle. I've personally spent hours each week patching it, especially during peak times, which pulls me away from product development. It's costing us valuable development time and, frankly, risking client trust if a notification falls through the cracks. We need something more robust than our current patchwork.
    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.