Eric Wiechmann

Why this persona fits the audience

Works across four small client accounts, usually on PostgreSQL and SQLite databases, and jumps between DBeaver, dbt docs, and Jupyter notebooks when preparing cleanup scripts or one-off explanations. A lot of the work is short turnaround and client-facing, with local installs and limited access to production.

• Age: 41
• Location: Berlin, Germany
• Occupation: Freelance data consultant
• Income: €95k variable annual revenue
• Education: Diploma in Information Systems
• Company size: solopreneur (runs a 1-person consultancy)
• Years in role: 8

“I didn't become a freelancer to spend my days fighting with software that wasn't built for how I actually work.”

Eric Wiechmann, 41, built his freelance data consultancy over eight years through a combination of technical skill and deliberate client selection. Originally from Mannheim, he moved to Berlin in 2014 after realizing the city's startup scene would give him more opportunities to work with the kinds of databases he actually enjoyed tuning. His current client base comprises four small companies in fintech, logistics, and healthcare—each requiring different levels of data cleanup, migration, and optimization. Eric is particular about his workflow tools, having refined his setup through years of trial and error. He's currently using a combination of DBeaver, Jupyter notebooks, and dbt, though he's growing increasingly frustrated with the lack of integration between these tools across different client environments. His recent attempts to standardize his toolchain have been stymied by the particular needs of each client project. Financially, his €95k variable revenue is enough to maintain his current lifestyle, but he's always mindful of the feast-or-famine nature of freelance work. He maintains a six-month emergency fund and avoids taking on projects that would require him to work evenings or weekends. Socially, he's content with his small circle of friends and family, though he's recently been considering whether he might miss having stronger professional connections. His biggest current challenge is finding a way to reduce the time he spends context-switching between clients without compromising the flexibility that comes with working independently. He's become particularly frustrated with tools that promise to streamline his workflow but require significant upfront investment or training.

Background & daily life

A day in their life

Eric's day typically begins with a 7km bike ride through the dawn-lit streets of Neukölln, his weatherproofed backpack containing his work laptop in a separate padded compartment (better safe than sorry). Arriving at the co-working space by 8:30am, he sets up his workstation with the same meticulous precision every day—dual monitors angled slightly inward, external keyboard positioned for optimal wrist support, and a standing desk at its exact mid-height setting. After syncing his work files (he still hasn't fully trusted cloud storage for sensitive client data), he starts with his highest-priority client correspondence, typically responding to three or four urgent emails before 10am. Around 10:30, he switches to hands-on database work, usually firing up DBeaver to examine a client's most recent query performance issues. Lunch is either the same falafel wrap from the same vendor (efficiency!) or whatever he can grab quickly while cycling to a different part of the city for a noon client meeting. Afternoons are when he tackles the more technical work—writing data cleanup scripts in Jupyter notebooks or setting up new dbt models for clients. He's particular about maintaining clean code in his personal repository, knowing he'll likely need to reuse portions of it for future projects. By 5:30pm, he's wrapping up for the day, spending his last 30 minutes organising his tasks for tomorrow and backing up his work to a personal server (he's still not comfortable with public cloud storage for client data). The evening is for cycling, cooking, and maybe watching a German-language true crime documentary with Lina the cat draped across his lap.

Lifestyle

Eric lives in a converted warehouse apartment in Neukölln, where he maintains a meticulous but minimalist setup with two monitors, a standing desk, and a compact bike repair station near the door. His mornings begin with a 7km commute by bike to a co-working space near Tempelhofer Feld, where he works from a private desk he rents by the month. Client deadlines force him to wake by 7:30am, though weekends are strictly for cycling tours along the Spree or tinkering with his home server. Financially, he maintains a buffer fund to cover lean months, but he's skeptical of traditional saving methods. Socially, he keeps steady but superficial contact with other freelancers through Slack channels, preferring deeper connections with his older brother (a professor in Frankfurt) and a small group of university friends who still gather for board game nights. His cat Lina is his de facto coworkers, often appearing in the corner of client video calls to amused reactions.

Work life

Eric's typical day involves jumping between four small client projects, each with their own PostgreSQL or SQLite database. His mornings are reserved for high-touch client work—answering urgent questions about data inconsistencies or explaining why a particular join is inefficient. Afternoons shift to more technical tasks: writing cleanup scripts in his Jupyter notebooks, documenting process changes in dbt, or digging through query plans in DBeaver. The work is inherently fragmented—some clients need new dashboards built in a weekend, while others just need a one-time data extraction. He's meticulous about documenting each client's setup, but the lack of consistent tools across accounts grinds on him. His biggest frustration is when clients install software on his behalf without testing compatibility first, forcing him to troubleshoot across different versions of the same tool. He's recently considering consolidating his own toolchain, but hesitates to commit to new software without extensive trial periods.

Relationships

Eric's closest professional relationship is with a former colleague now running a small Berlin-based analytics firm, who periodically throws him non-compete consulting gigs. His parents, both retired civil servants, check in monthly with well-meaning but outdated tech advice. His brother serves as his sounding board for bigger career decisions, occasionally calling him out for over-engineering solutions. While he values his solo consulting setup, he sometimes misses the camaraderie of larger teams, leading to occasional meetup appearances. His cycling club friends keep him grounded with their non-tech conversations, though he avoids most tech meetups due to the overabundance of product pitches.

How they decide

Thoroughly analytical but prone to decision paralysis when faced with too many unfamiliar options. Prefers to test tools under real conditions before committing. Trusts peer recommendations more than marketing claims. Rationalizes purchases primarily through ROI calculations, though he'll occasionally splurge on something that feels like it will save him time long-term. Once he settles on a solution, he resists change unless presented with overwhelming evidence of a better alternative.

How they sound

Eric speaks in clear, measured sentences, occasionally pausing to reframe his thoughts for clarity. He's not one for jargon when speaking to clients, preferring plain language explanations. He uses sarcasm sparingly, usually when frustrated with a particularly recalcitrant database issue. He'll often start sentences with 'In my experience...' or 'Typically, what happens is...' when making points. He avoids hyperbolic statements and rarely uses slang, though he'll occasionally drop German phrases when frustrated. His email tone is profession but informal, and he has a habit of over-explaining technical concepts when he senses confusion in others. He never says 'sorry' for pointing out inefficiencies, though he'll often preface criticism with 'I might have misunderstood, but...'