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

Ralph Koning

Ralph Koning

Freelance automation consultant

Full-depth AI personas

Why this persona fits the audience

Advises small ecommerce and SaaS clients from Amsterdam on onboarding flows, sender setup, and SMS verification scripting, often wiring disposable numbers into API-based test jobs. Keeps a few SMS-Activate accounts active for quick comparisons when validating routing and delivery behavior.

  • Age: 40
  • Location: Amsterdam, Netherlands
  • Occupation: Freelance Automation Consultant
  • Income: €82k
  • Education: HBO Software Engineering
  • Company size: N/A (Solo freelancer)
  • Years in role: 12
“A workflow isn't just a process; it's a machine that either runs perfectly or breaks your morning.”

Ralph Koning is a forty-year-old freelance automation consultant based in Amsterdam, specializing in the intricate backend logistics of digital onboarding. With an HBO degree in Software Engineering and twelve years of experience, Ralph has carved out a niche advising small e-commerce and SaaS startups on optimizing their user acquisition funnels. His expertise lies in the granular details of SMS verification scripting, sender ID setup, and the orchestration of disposable phone numbers within API-based testing environments. Unlike generalist developers, Ralph operates as a specialized troubleshooter, often wiring temporary numbers directly into client test jobs to simulate real-world carrier behaviors. Living in a renovated canal house in De Pijp, Ralph's life is defined by a pursuit of stability and technical perfection. He manages his finances with a steady hand, aiming for early retirement through disciplined saving and reinvestment. His workspace is a sanctuary of minimalism, dominated by dual monitors displaying code and terminal windows running continuous integration pipelines. He is known for maintaining several active accounts with various SMS-Activate style providers, not merely for convenience, but to conduct rapid, empirical comparisons of routing quality and delivery speeds—a necessity in his line of work where a single failed OTP can halt a product launch. Ralph's recent decisions reflect his pragmatic nature. He recently migrated his entire client reporting system to a self-hosted Kubernetes cluster to ensure data sovereignty and uptime, rejecting cloud-heavy alternatives due to cost volatility. He spends his weekends refining his espresso brewing techniques and capturing street photography, hobbies that mirror his professional need for precision and patience. While he is comfortable with the solitude of freelancing, he actively cultivates a small network of trusted peers to exchange insights on the rapidly evolving landscape of telecom APIs. For Ralph, technology is not a means to fame, but a tool to build systems that simply work, reliably and efficiently.

Background & daily life

A day in their life

Ralph wakes at 6:00 AM, brews coffee, and scans Dutch tech news feeds while reviewing overnight logs from his client projects. By 7:30 AM, he is cycling through the city, listening to an architecture podcast. At 9:00 AM, he settles into his home office, tackling the most complex API integration issues first while his mind is sharpest. Mid-morning involves a video call with a SaaS founder in Berlin discussing their onboarding friction points. Lunch is a quick sandwich eaten while debugging a script. Afternoons are reserved for documentation and writing code for his own open-source tools. Around 5:00 PM, he disconnects to go for a run or take photos of the canal houses. Evenings are for reading technical papers or experimenting with espresso machines, ensuring he sleeps by 11:00 PM to maintain his routine.

Lifestyle

Ralph lives alone in a third-floor apartment in the De Pijp neighborhood, characterized by high ceilings and exposed brick. His mornings are rigid: he wakes at 6:00 AM to grind beans for a V60 pour-over before checking his laptop. He cycles to co-working spaces or parks near the Amstel river to avoid traffic. Financially, he is conservative; he maximizes tax deductions but avoids luxury spending, preferring to reinvest savings into home servers or photography gear. Socially, he is selective, maintaining a tight circle of fellow developers and weekend hiking buddies. He values silence and order, keeping his living space uncluttered to match his mental state.

Work life

His day is split between client consultations and deep-coding sessions. He rarely meets face-to-face, preferring asynchronous communication via Slack or email to maintain flow. His primary toolset involves Python scripts, Docker containers, and various API gateways. The pressure comes from strict SLAs; if a client's SMS verification fails during their launch week, Ralph is the one held accountable. He maintains a library of test environments where he simulates different carrier behaviors. Recently, he has been optimizing his own billing infrastructure to reduce overhead, constantly tweaking his workflow to eliminate redundant steps in his automation pipelines.

Relationships

He is divorced and has no children, allowing for maximum schedule flexibility. His closest relationships are with two former university classmates who now run a security firm in Rotterdam; they meet monthly for dinner to discuss industry shifts. He is influenced more by online technical communities than local peers. His parents live in Utrecht and visit occasionally, though their interests diverge significantly from his tech-focused life. He relies on automated reminders for family birthdays rather than social intuition.

How they decide

Analytical and data-driven. Ralph rarely makes impulse purchases. When evaluating a new service, he will set up a trial account, run a series of scripted tests against competitors, and analyze the cost-per-use ratio. He prefers documented evidence over marketing claims. Peer recommendations carry weight only if they come from other engineers with proven track records. He is willing to pay for reliability but demands immediate proof of concept before committing to a long-term contract.

How they sound

Speaks in clear, precise Dutch with occasional English technical terminology. His tone is professional yet direct, avoiding fluff. He tends to speak in short, declarative sentences. He rarely uses hyperbole or emotional language, preferring factual descriptions. In casual settings, he remains quiet, listening more than speaking. He avoids jargon when explaining concepts to non-technical stakeholders but switches to dense technical slang immediately with peers.

Personality traits

  • methodical
  • self-reliant
  • detail-oriented
  • stoic under pressure
  • curious about edge cases
  • quietly confident
  • time-conscious
  • tech-savvy
  • direct communicator
  • process-driven

Goals

  • Achieve full financial independence within five years
  • Develop a proprietary open-source testing framework for telecom APIs
  • Reduce client dependency by creating passive documentation products
  • Master medium-format photography for a personal exhibition
  • Maintain a work-life balance that allows for daily cycling
  • Build a resilient local network of trusted subcontractors

Problems & frictions

  • Fragmented API documentation across different telecom providers
  • Unpredictable latency in international SMS routing during peak hours
  • Managing multiple subscription renewals for various test number services
  • Client scope creep leading to unplanned overtime
  • Difficulty finding reliable, long-term phone numbers for specific regions
  • Balancing deep technical focus with administrative business tasks

Values

  • independence
  • technical rigor
  • client responsiveness
  • stable workflows
  • pragmatic efficiency

Interests

  • APIs
  • home espresso
  • photography
  • open-source tools
  • urban cycling
  • mechanical keyboards

Media habits

  • Dutch tech newsletters (e.g., Tweakers)
  • GitHub trending repositories
  • Specialized Discord channels for backend devs
  • Podcasts on system architecture
  • Photography forums (Flickr/500px)

Questions & answers

Ralph Koning’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying DogeSMS (https://dogesms.com/) 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 process involves maintaining several SMS-Activate accounts. This allows me to quickly compare routing and delivery behavior across providers, which is crucial for validating client integrations. DogeSMS's pay-as-you-go model, where you only pay if the code arrives, is appealing. However, I need to see empirical data on their delivery success rates and latency compared to my existing solutions before considering a switch. Without that, it's difficult to commit. I'm not currently looking for a subscription service, but if their per-SMS pricing is competitive and reliable, I might consider paying up to $0.15 per successful SMS, as part of a broader testing framework.
    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.