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

Roan van den Berg

Roan van den Berg

Product analyst / ops at a marketplace

Full-depth AI personas

Why this persona fits the audience

He monitors scheduled webhook calls for price checks, inventory snapshots, and partner-status updates on a 9-person product team. The team self-hosts n8n and edits cron expressions directly, splitting the setup between product and engineering.

  • Age: 33
  • Location: Amsterdam, Netherlands
  • Occupation: Product Analyst / Operations
  • Income: €78,000
  • Education: Master's degree in information systems
  • Company size: startup (9-person product team)
  • Years in role: 4
“I tried to explain to my mother what I do for a living, and she nodded like it made perfect sense. Then she asked if I could fix her wifi. That's my professional life in a nutshell.”

Roan van den Berg cut his teeth automating inventory systems at a tiny Dutch marketplace before joining his current startup, where he became the accidental custodian of their increasingly complex webhook ecosystem. His master's thesis on marketplace data pipelines might have been dry reading, but it gave him the vocabulary to explain to engineers why 'just use cron' isn't a real solution. At work, he's the bridge between product team's ambitious automation desires and engineering's reality constraints. His current workflow is a mix of GitHub repos, Slack channels, and half-written documentation—the team's unofficial CMO jokes that their stack runs on 'Roan's SeeD-Esque glares of authority.' Roan's personal mantra is 'if you can't monitor it, you don't own it,' which is why he's currently building a monitoring dashboard for their homegrown automation. Outside work, he's trying to replicate the joy of his market simulation game, which currently consists of spreadsheet formulas and a deepening obsession with algorithmic pricing strategies. His apartment is littered with half-built automation projects and Tulips. His greatest fear is that his partner will finally get tired of him muttering about 'eventually consistent systems' during dinner. Status to him is measured in uptime percentages and how often his bike stays locked. Money is spent on coffee machines that he insists on scripting. He once spent an entire weekend rewriting his partner's Excel macros in Python 'just to see if it was possible.' His professional identity is deeply tied to the phrase 'that's not how webhooks work,' which he's had to say at least twice this month. The startup's engineering team secretly hopes he'll never leave, though they'd never admit it—they just know their uptime metrics would suffer. Roan's worldview is shaped by the belief that all systems are temporary, and the only constant is the need to automate the things that annoy you. He's currently trying to find the right balance between 'good enough' and 'perfectly consistent,' which is why he's both envied and occasionally mocked by his colleagues. His whiteboard is covered in flowcharts that look suspiciously like his personal life's decision trees. He's the kind of person who will build a tool to automate a problem entirely to prove that the problem shouldn't exist, then immediately move on to the next one. His biggest professional regret is that he never learned enough of Go to rewrite their infrastructure himself. His bike is, coincidentally, also his favorite metaphor for how all systems inevitably break.

Background & daily life

A day in their life

Roan's day starts at 6:45 AM with his coffee machine's timer-induced gurgles. After a shower and a moment of indecision between two nearly identical work sweaters, he bikes to the office, locking his bike with a disturbingly familiar sense of doom. At work, he opens his first monitor to find a Slack message from an engineer asking about a failing webhook (it's the timezone issue again). He spends the morning debugging while nodding at the engineering team's debate about whether they should containerize their n8n instance. By midday, he's in a standup explaining why their inventory sync needs better error handling, interrupting himself to sketch a flow diagram on the whiteboard. Lunch is a sandwich from the café next door, eaten while reading Hacker News on his phone. The afternoon is consumed by adding logging to their price-check workflow and arguing against adding a new API endpoint 'just because'. On his way home, he stops at the hardware store to buy yet another bike lock, already calculating how much time he could save by automating lock combinations. Dinner with Lotte involves comparing their respective 'automation wins' of the day (she built a grasshopper script, he added error retries), then they both collapse on the couch with their laptops—him to finally tackle his game's pricing algorithm, her to finalize her thesis diagrams. He falls asleep during an Indie Hackers YouTube video about cron job alternatives.

Lifestyle

Roan shares a converted 19th-century office building apartment in De Pijp with his partner, Lotte. They keep the plumbing loud and the radiators louder. His mornings start with oat milk coffee brewed on a timer—he built the automation script before buying the machine. Weeknights are spent prototyping indie games (he's working on a market sim about cheese distribution) or arguing about why De Pijp's bike lanes are terrible. He runs every other Sunday and spends too much on fresh tulips. Money goes to: rent, savings (for a future tiny house), and the weekly 'automation tax' (he once bought a Raspberry Pi just to replace a $10 timer switch). Social life is small but dense—a circle of former classmates and tech colleagues who meet at brown cafés to debate whether n8n will ever replace Make.com.

Work life

At work, Roan mediates between his team's over-engineering tendencies and the reality of their minimalist stack. He's currently debugging a webhook failure that turned out to be a timezone edge case in their self-hosted n8n instance (again). The team runs on Slack messages and Miro boards, with the occasional physical whiteboard sketch during standups. Pressure comes from pipeline disruptions that require manual overrides, and from engineers who want to rewrite everything in Go. He's recently pushed to add observability to their workflows after a silent failure went unnoticed for 12 hours. His ideal day is spent refactoring cron expressions and explaining to marketing why 'run_every_hour' isn't a valid time interval.

Relationships

Roan's tightest bonds are with his collegue Marc, their de facto team engineer, and his former university mentor who now works at a Dutch SRE startup. He stays in touch with a few ex-colleagues through a WhatsApp group dedicated to trash-talking legacy systems. His partner Lotte is his default soundboard for ideas and his only reliable braingasmic about the same problems for the 23rd time. His parents in Groningen call weekly—his mother asks about dating, his father about bicycles. The community that matters most to him is the small but vocal group of n8n enthusiasts who gather in Discord threads to argue about node configurations.

How they decide

Methodical but prone to sudden pivots when presented with elegant solutions. Research-heavy, but will trust his gut if the research is inconclusive. Prefers to prototype personally before pushing changes to systems. Hates group decisions that result in 'difficult to trigger' webhooks. When overwhelmed, defaults to 'just automate it and see what breaks'.

How they sound

Speaks in measured, slightly sarcastic sentences with frequent tech metaphors. Uses Dutch and English interchangeably, especially when frustrated. Avoids vague language in professional settings but will say 'that's a load of webhook nonsense' among friends. Voice rises noticeably when explaining technical concepts to non-technical people. Pronounces 'workflow' like it's a four-syllable word. Occasionally lapses into Dutch when describing particularly irritating systems. Ends emails with 'Cheers' even when he's not cheering.

Personality traits

  • Process-obsessed but hates rigid systems
  • Optimizes personal workflows before team workflows
  • Knows more about cron syntax than he'd like to admit
  • Loses patience with vague requirements
  • Hoards useful shell scripts like souvenirs
  • Prefer automated but will manually intervene
  • Quietly competitive about system uptime
  • Cynical about
  • Describes himself as a 'professional middleman between chaos and spreadsheets'
  • Doodles state machine diagrams when bored

Goals

  • Build a full-scale automation for their inventory system without engineering help
  • Finish his cheese distribution game (currently stuck on realistic price fluctuation algorithms)
  • Convince the team to adopt a proper monitoring tool (they currently use Slack alerts)
  • Move to a house with better bike storage by 2026
  • Learn enough of Python to stop asking engineers to write his scripts for him

Problems & frictions

  • The team's ad-hoc automation solutions keep breaking when partners make API changes
  • His partner complains he comes home muttering about 'cron witchcraft'
  • Finds himself tweaking personal automation systems when he should be sleeping
  • Team debates about 'what constitutes a webhook' are getting tiring
  • His bike gets stolen 3 times a year—'Amsterdam's bike thieves respect no schedules'
  • Feels like he spends half his time explaining what webhooks actually do

Values

  • clarity
  • experimentation
  • systems thinking
  • autonomy
  • efficiency

Interests

  • marketplaces
  • n8n
  • data dashboards
  • automation
  • bike commuting
  • indie game design

Media habits

  • Hacker News
  • Indie Hackers
  • YouTube automation deep dives
  • Dutch tech podcasts
  • Twitter threads on workflow tools

Questions & answers

Roan van den Berg’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Cronhooks (https://cronhooks.io) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Honestly, I’d consider Cronhooks if it reliably solved our timezone issues with webhooks, which trip us up way too often. Currently, we’re manually editing cron expressions in n8n, splitting work between product and engineering, and it’s a fragile setup. The promise of timezone-aware, cron-triggered webhooks with failure alerts is appealing—our team would love to offload that maintenance. That said, we’re a tight-knit shop; I’d need to vet its APIs and Slack alerts in our workflow before committing. The $5/month ‘Startup’ plan looks like a fit, but I’d need to verify it supports our ~100 monthly schedules. My max budget? $10/month. Anything beyond that would need sign-off from our CTO, and our current DIY approach feels ‘good enough’ for now. I’d also need to confirm if Cronhooks integrates with our existing n8n setup—no one here has time for a full stack overhaul.
    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.