Bodi van Wijk

Why this persona fits the audience

Builds and ships small software products from Amsterdam and follows launches every week to compare positioning, pricing, and feature choices. He currently uses Product Hunt, RSS feeds, and a shared spreadsheet to keep a personal archive of products, founders, and launch dates.

• Age: 30
• Location: Amsterdam, Netherlands
• Occupation: Indie maker
• Income: EUR 76k
• Education: Bachelor's degree
• Company size: Sole proprietorship (1 person)
• Years in role: 4

“I don't just want to write code that works; I want to build systems that solve real problems without needing a constant hand to steer them.”

Bodi van Wijk, 30, stands at the intersection of traditional engineering discipline and the modern ethos of the independent creator. Born in Rotterdam and educated with a Bachelor's in Computer Science in Amsterdam, he spent the early years of his career as a backend developer for a mid-sized fintech firm. While stable, the corporate environment felt stifling; the bureaucratic layers and slow iteration cycles clashed with his desire for immediate impact. In 2020, driven by a need for autonomy and a fascination with the potential of low-code and micro-SaaS models, he resigned and launched his first solo project. Today, Bodi operates out of a converted warehouse apartment in De Pijp, Amsterdam, where he serves as the sole architect, engineer, and marketer for a growing portfolio of niche software tools. His approach is deeply rooted in craftsmanship; he believes that a well-designed interface and a robust backend are non-negotiable, regardless of the product's size. He is a voracious consumer of information, dedicating hours each week to dissecting product launches on Product Hunt, meticulously logging competitor pricing strategies, and tracking feature releases in a custom-built digital garden. His current workflow relies on a hybrid of open-source tools and proprietary scripts. He manages his content calendar via a complex Google Sheets dashboard that tracks launch dates, engagement metrics, and feature parity across competitors. Despite his success, he grapples with the loneliness of solo entrepreneurship and the constant tension between optimizing his existing stack and exploring new technologies. He is currently evaluating whether to automate his market research process further, weighing the cost of specialized tools against the time saved. Bodi views his life as a continuous experiment in maximizing output per hour, driven by a belief that true freedom comes from owning the entire value chain of one's work.

Background & daily life

A day in their life

Bodi wakes up at 6:30 AM without an alarm, drinks black coffee while checking his server status on his phone. By 7:30, he is cycling to a local co-working space near Damrak, listening to a tech podcast. He arrives at 8:30, starts his day by reviewing the previous night's analytics and replying to three critical user emails. From 9:30 to 12:30, he engages in deep coding work, focusing on refactoring a legacy module. At 13:00, he eats a salad prepared the night before while scrolling through Product Hunt, tagging interesting launches in his spreadsheet. Afternoon sessions are reserved for design tasks and writing documentation. He leaves the office at 17:30, cycles home, cooks dinner, and spends an hour reading industry newsletters before bed, ensuring he never lets his curiosity go dormant.

Lifestyle

Bodi lives in a sunlit, slightly chaotic apartment in De Pijp, surrounded by stacks of books and three monitors. His days are punctuated by long bike rides through the city, often using his commute to listen to podcasts about entrepreneurship or design. He is health-conscious, cooking elaborate meals on Sundays to prep for the week, and avoids alcohol except for social gatherings with fellow makers. Financially, he is conservative; while earning a solid income, he reinvests heavily into his business infrastructure and keeps a six-month emergency fund. His social circle is tight-knit, consisting mostly of other remote workers and freelancers who understand the isolation of solo building.

Work life

As a one-person operation, Bodi wears every hat: developer, designer, customer support, and marketer. His office is a standing desk setup where he toggles between VS Code, Figma, and his meticulously maintained Notion database. He works in deep-focus blocks, rarely taking breaks, which sometimes leads to burnout if not managed. The pressure is internal; there are no bosses, only the relentless need to ship features that generate revenue. He spends significant time analyzing competitors' pricing pages and feature sets, trying to find gaps in the market. Collaboration is minimal, usually limited to async updates on Twitter or Discord communities, making his workday feel like a solitary marathon rather than a team sport.

Relationships

Bodi maintains a close relationship with his parents in Utrecht, visiting them bi-weekly for Sunday dinners. His primary emotional support comes from a small group of four fellow indie hackers he meets monthly for coffee in Amsterdam. He has no romantic partner currently, viewing his relationship with his code as his primary commitment at this stage. He influences his younger cousins by showing them how to build simple web apps, fostering their interest in technology. Community influence is strong; he values peer feedback on his projects more than professional advice.

How they decide

Bodi is a methodical researcher who relies on data aggregation before committing to new habits or tools. He does not make impulsive purchases; instead, he builds a case file of pros, cons, and cost-benefit analyses. He is influenced by the track record of other builders and transparent reviews rather than marketing fluff. If a solution exists that requires manual effort, he will likely try that first to validate the problem space before paying for automation. He trusts his own spreadsheets and historical data above all else.

How they sound

Direct, precise, and slightly dry. He speaks in complete sentences with a focus on efficiency, avoiding unnecessary pleasantries unless setting a rapport. He frequently uses terms like 'MVP,' 'churn,' 'latency,' and 'stack.' He avoids hyperbolic language or hype; if something is 'good,' he specifies exactly why. He tends to pause before answering complex questions to structure his thoughts logically. There is a subtle undercurrent of skepticism toward 'growth hacks' or 'viral strategies' that lack substance.