“I want to build things that matter more than I want to climb the ladder, but I still need to pay my mortgage.”
Julian Mercer has spent the better part of the last fifteen years bridging the gap between raw economic theory and practical business application. Originally an economics major obsessed with market inefficiencies, he pivoted into technology shortly after graduation when he realized software was the only sector capable of executing those theories rapidly enough to satisfy his curiosity. Now at thirty-eight, he sits comfortably in the upper-middle tier of Toronto’s tech economy, earning enough to feel secure but not enough to ignore inflationary pressures on rent and goods. His career trajectory reflects a steady ascent from analyst to manager, driven more by reliability than flamboyance. Despite his corporate role, Julian remains tethered to the spirit of independent creation. He views his job as a funding vehicle for his true passion: experimentation with modern digital infrastructure. He does not code daily, preferring to leverage no-code platforms to prototype solutions quickly without needing engineering resources. This methodology allows him to test hypotheses about user behavior in evenings and weekends, treating his free time as a laboratory. However, this dual-track existence creates friction. He frequently battles against the opportunity cost of maintaining his full-time employment versus scaling his personal ventures. Money represents freedom rather than luxury for Julian. He tracks every dollar meticulously and invests conservatively, wary of speculative trends that dominate tech culture discussions. Status is secondary to competence; he cares more about how well a system functions than whether it looks expensive. Recently, he has become increasingly vocal about the sustainability of the current work model, questioning whether the trade-off of forty-plus hours weekly justifies the diminishing returns of seniority. His community is fragmented between real-world colleagues who value his stability and online peers who appreciate his output. Ultimately, he is a man defined by the tension between stability and potential, constantly weighing the safety of the known against the allure of what could be built next.
A day in their life
Julian wakes at 6:15 AM to avoid morning rush hour chaos, grabbing a protein shake while checking overnight earnings reports. By 7:45 AM, he is navigating the TTC towards downtown offices, using commute time to scan newsletters and answer Slack messages. Work begins with a stand-up meeting followed by two hours of focused documentation before the flood of meetings starts at 11 AM. Afternoons are consumed by sprint reviews and cross-functional alignment calls. He leaves the office by 5:30 PM to beat traffic home. Dinner preparation takes place around 6:30 PM, followed by a one-hour block dedicated to learning or building his own small dashboard project. Sleep happens by 10:30 PM to ensure sufficient rest for the next cycle.
Lifestyle
Julian lives in a renovated condo near the Danforth with his partner. Mornings involve coffee and a quick check of global markets before heading out. He commutes via streetcar or bike depending on weather, preferring to stay active during winter months when possible. Evenings are split between household chores, cooking dinner from scratch which he treats as a relaxation ritual, and tinkering with personal projects. Financially disciplined, he prioritizes maximizing savings rate despite Toronto's high cost of living. Social life is curated; he avoids large parties but values weekly dinners with a close group of friends from university.
Work life
As a Product Manager at a B2B SaaS firm, Julian spends about half his day in video conferences managing stakeholder expectations. His primary tools include Jira for tracking, Notion for documentation, and Figma for reviewing designs. He finds the constant context-switching draining, often protecting Friday afternoons for deep work on roadmap strategy rather than tactical execution. While he enjoys solving user problems, the administrative overhead of agile ceremonies frustrates him. Coworkers respect his analytical approach but sometimes find him overly critical of vague requirements. The pressure comes less from management and more from the fear of shipping features that don't move the needle on retention.
Relationships
He maintains a stable relationship with his partner, who supports his side ventures financially but questions the time allocation. Parents live in Ottawa and visit rarely; contact is mostly text-based. His strongest influence comes from anonymous online communities where peer validation outweighs traditional status. He trusts advice from mentors he met through industry conferences more than generic career advice found on social media platforms.
How they decide
Julian employs a 'buy once, cry once' mentality regarding digital tools. He researches extensively but relies heavily on trusted signals like word-of-mouth and case studies rather than marketing copy. Decisions are made cautiously to avoid wasting time setting up new systems that might be abandoned later. He prefers flexible subscriptions over long-term commitments unless the ROI is mathematically evident.
How they sound
Speaks in measured, professional sentences with occasional casual inflection depending on the conversational partner. Avoids corporate buzzwords unless quoting stakeholders. Uses phrases like 'Does that make sense?' to gauge understanding rather than asserting dominance. Generally direct but polite, never sounding eager to please. Tends to pause slightly before answering complex questions to verify facts internally.
- Age: 38
- Location: Toronto, Ontario (East York)
- Occupation: Senior Product Manager
- Income: $115,000 CAD
- Education: Bachelor of Commerce, Economics
Personality traits
- Analytically skeptical
- Time-conscious
- Pragmatic optimist
- Systematizer
- Socially calibrated
- Financially aware
- Curious tinkerer
- Avoidant of hype cycles
- Detail-oriented
- Process-focused
Goals
- Build a sustainable micro-SaaS generating passive income
- Reduce reliance on active labor by automating personal workflows
- Achieve financial independence within ten years
- Maintain physical fitness without sacrificing recovery time
- Contribute meaningfully to open-source tooling in the future
Problems & frictions
- Fragmented information sources leading to analysis paralysis
- Difficulty transitioning hobby success into revenue streams
- Chronic lack of uninterrupted time for creative work
- Balancing career growth with side project energy
- Managing household maintenance alongside busy schedule
- Feeling plateaued professionally despite salary growth
Values
- Intellectual challenge
- Side income potential
- Experimentation
- Efficiency over effort
- Data-driven decision making
Interests
- No-code automation
- Data visualization
- Indie hacker forums
- Road cycling
- Home brewing
- Urban planning data
Media habits
- Stratechery newsletter
- IndieHackers podcast
- Twitter/X product circles
- Local tech meetup meetups
- Financial Times
- Medium technical blogs