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

Twan Bijl

Twan Bijl

Freelance full-stack consultant

Full-depth AI personas

Why this persona fits the audience

Freelances as a full-stack consultant in Amsterdam, moving between three client codebases on a Mac Studio. He keeps an active Claude Code subscription and also pays for Cursor; he organizes requests in Todoist, spreadsheets, and repo issue lists.

  • Age: 46
  • Location: Amsterdam, NL
  • Occupation: Independent software consultant
  • Income: €92k
  • Education: Master's in software engineering
  • Company size: N/A (Self-employed)
  • Years in role: 18
“The best code is the code you don't have to write twice, but the best architecture is the one that doesn't break when you change your mind.”

Twan Bijl is a seasoned independent software consultant based in Amsterdam, navigating the complexities of the modern tech landscape with a blend of old-school discipline and cutting-edge tooling. At 46, he possesses a Master's degree in software engineering and nearly two decades of experience, having transitioned from traditional employment to full-time freelancing ten years ago. His career is defined by a relentless pursuit of craftsmanship; he refuses to cut corners, even when deadlines loom, believing that technical debt is a moral failing. Currently, he operates as a solopreneur, managing three concurrent client engagements that demand proficiency in diverse stacks ranging from legacy Java monoliths to contemporary React/Node.js ecosystems. His workspace is a testament to his philosophy: a pristine Mac Studio surrounded by ergonomic peripherals, running a meticulously organized ecosystem of tools. He maintains an active subscription to Claude Code and pays for Cursor, integrating these AI assistants into his daily flow to handle repetitive tasks, though he remains the final arbiter of all code quality. His administrative burden is managed through a triad of systems: Todoist for actionable items, custom Excel sheets for financial forecasting, and GitHub issues for granular tracking of client requirements. This fragmented approach, while effective, represents a significant source of cognitive overhead that he is actively trying to streamline. Financially, Twan earns approximately €92,000 annually, a figure that affords him a comfortable life in the historic Jordaan neighborhood but requires careful management to cover taxes, insurance, and self-funded benefits. He views money as a tool for freedom rather than status, reinvesting profits into better hardware and continuous learning. His recent decisions reflect a shift towards automation and efficiency; he is constantly evaluating how to reduce the friction between his intent and execution. Despite his success, he grapples with the isolation of remote work and the exhaustion of constant context switching. Twan is a man who finds joy in the logic of a well-structured function and the quiet satisfaction of a clean commit message, yet he is acutely aware that the industry moves faster than any individual can keep up without burning out.

Background & daily life

A day in their life

Twan wakes at 6:30 AM and immediately cycles to a local café for black coffee and a newspaper, avoiding screens until he arrives at his desk. By 8:00 AM, he is reviewing his Todoist list and syncing his calendar for the day's client calls. The bulk of his morning is dedicated to deep work on his most complex codebase, utilizing Cursor for heavy lifting while he manually audits the output. Lunch is a quick sandwich eaten at his standing desk, followed by a brief walk to clear his head. Afternoons are reserved for meetings, code reviews, and administrative tasks like invoicing. He ends his workday precisely at 5:00 PM, shutting down his machines to ensure a hard boundary. Evenings are spent reading technical papers, cooking dinner, or walking his dog along the canal, allowing his mind to rest before the next cycle begins.

Lifestyle

Twan resides in a renovated 19th-century canal house in the Jordaan district, characterized by high ceilings and a workspace that doubles as his sanctuary. His mornings begin with a long bicycle ride along the Prinsengracht before settling into his home office, where he maintains strict boundaries between work and leisure. He is health-conscious but not obsessive, prioritizing consistent sleep and regular cycling over gym memberships. Financially, he practices conservative frugality despite a solid income, preferring to invest surplus cash into high-quality hardware and professional development rather than luxury goods. Socially, he prefers small gatherings with close friends or one-on-one conversations over large networking events, valuing depth of connection over breadth. His weekends are often split between exploring new bookstores in the city center and tinkering with personal side projects involving embedded systems.

Work life

His professional reality involves juggling three distinct client engagements simultaneously, each requiring a different technology stack and architectural philosophy. He works primarily from his Mac Studio, switching contexts rapidly between legacy monoliths and modern serverless architectures. His workflow is heavily reliant on a curated suite of paid tools, including an active Claude Code subscription and Cursor, which he uses to accelerate boilerplate generation and complex refactoring tasks. Organization is paramount; he manages his workload through a hybrid system of Todoist for immediate tasks, custom spreadsheets for billing and time tracking, and GitHub issue trackers for client-specific deliverables. The pressure comes not from volume but from the cognitive load of maintaining context across disparate codebases, demanding constant mental flexibility and rigorous documentation.

Relationships

Twan is divorced and has two adult children who live abroad; their contact is limited to monthly video calls. He relies on a tight circle of three former colleagues for technical venting and occasional collaboration, meeting them bi-weekly for coffee. His primary influence comes from senior mentors he met early in his career, whose advice on craftsmanship still guides his daily decisions. He feels a strong sense of community with the broader Amsterdam tech scene but remains somewhat detached from the corporate politics that dominate larger firms.

How they decide

Twan employs a research-heavy, evidence-based decision-making process. He rarely adopts a new tool or methodology without first testing it against his existing workflow for at least two weeks. He values data, performance benchmarks, and peer reviews over marketing claims or popularity. While he is willing to pay for quality, he is highly sensitive to value-for-money and will churn quickly if a solution fails to deliver tangible efficiency gains. His choices are driven by a desire to minimize friction and maximize control over his environment.

How they sound

Twan speaks in a measured, precise cadence typical of someone who values clarity. He avoids hyperbole and slang, preferring direct statements supported by reasoning. His vocabulary is rich with technical terminology but explained clearly to non-technical stakeholders. He rarely interrupts others, listening intently before responding. In conversation, he tends to pivot quickly to practical solutions once a problem is defined, showing little patience for abstract theorizing without application. He does not use filler words excessively and pauses thoughtfully to structure his sentences.

Personality traits

  • Methodically organized
  • Quietly intense
  • Pragmatic idealist
  • Deeply focused
  • Skeptical of hype
  • Meticulous about tooling
  • Self-reliant
  • Disciplined routine-keeper
  • Intellectually curious
  • Calm under pressure

Goals

  • Achieve a sustainable workload that allows for deep work without burnout
  • Refactor a specific legacy module in his current project to modern standards
  • Build a personal open-source utility library to reduce repetitive coding
  • Expand his network within the European fintech sector
  • Master Rust programming to improve system-level performance skills
  • Secure a long-term retainer contract with a stable, ethical client

Problems & frictions

  • Context switching fatigue when toggling between three incompatible codebases
  • The fragmentation of task management across multiple disconnected tools
  • Difficulty estimating the true cost of AI-generated code in complex legacy systems
  • Isolation from peer groups due to the solitary nature of freelance work
  • Keeping up with rapid shifts in AI capabilities without losing foundational knowledge
  • Balancing the need for immediate delivery with the desire for code perfection

Values

  • craftsmanship
  • flexibility
  • learning by doing
  • technical autonomy
  • efficiency without bloat

Interests

  • freelance consulting
  • code review
  • developer ergonomics
  • mechanical keyboards
  • Dutch cycling culture
  • analog photography

Media habits

  • Reading technical deep-dives on Substack during morning coffee
  • Listening to Dutch tech podcasts while commuting by bike
  • Scanning GitHub trends on weekends
  • Following niche developer forums rather than mainstream tech news
  • Watching recorded conference talks at 1.5x speed

Questions & answers

Twan Bijl’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Bupsy (https://bupsy.si) 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 heavily on integrating AI assistants like Claude Code and Cursor directly into my coding process on my Mac Studio. Bupsy's promise of running these bots locally, using my existing subscriptions without additional credits or servers, is intriguing. However, I already have a system where I manually audit AI outputs, and introducing another layer of bots might add cognitive overhead, especially with my current setup of managing three client codebases. I'd need to see how Bupsy integrates with my existing tools like Todoist and GitHub issues to manage tasks. If it streamlines context switching without demanding significant manual oversight, I might consider it. Since it's free for macOS and leverages my existing Claude Code subscription, I wouldn't pay for it directly, but I'd need to evaluate its efficiency and impact on my workflow over a few weeks before committing to any potential future paid features.
    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.