Why this persona fits the audience
Co-founds a 4-person boutique studio in London that builds mobile MVPs for local businesses; he is not a full-time engineer, so he pairs Figma files with a freelance React Native developer and has so far relied on free plugins and manual handoff notes rather than paying for design-to-code software.
- Age: 29
- Location: London, UK
- Occupation: Co-founder
- Income: £48k owner draw
- Education: BA in Digital Media
- Company size: 4
- Years in role: 3
“Every day is about making things work smoother, for us and for the clients. If we can shave off an hour here or there, that's an hour we can use to build something better, or even just grab a decent pint.”
Peter Brakus's journey into app development wasn't through a traditional computer science degree, but rather a BA in Digital Media from a London university. His early career involved freelance web design and a brief stint at a small digital agency, where he saw firsthand the gap between ambitious ideas and the practicalities of execution. This experience, coupled with a burgeoning interest in indie hacking and the rise of mobile-first businesses, led him to co-found Pixel Pioneers three years ago with two friends. The studio, now a lean team of four including a dedicated freelance React Native developer, focuses on building Minimum Viable Products for London-based SMEs. Peter isn't a coder by trade; his strength lies in translating complex client visions into tangible, user-friendly designs within Figma. He meticulously crafts the bridge between Maya’s design vision and Alex’s coding reality, relying on detailed annotations and free plugins. This hands-on approach, while effective, consumes significant time. He's keenly aware of budget constraints for their clients and the studio itself, leading him to favour free tools and manual processes over expensive, specialised software. His income of around £48k is drawn as an owner’s draw, reflecting the studio’s growth but also the need for reinvestment. Peter views time as his most valuable commodity and is constantly seeking efficiencies that allow for faster project delivery and more strategic business growth, viewing every saved minute as a direct investment in the company’s future and his own independence.
Background & daily life
A day in their life
Peter's day usually starts around 7:30 AM with a quick scan of emails and industry news while making coffee. He’s on his bike by 8:30 AM, cycling to the small Shoreditch office they share. The morning is typically filled with client calls – discussing feedback on a fintech app MVP or kicking off a new e-commerce project. After lunch, he’ll spend a few hours in Figma, refining user flows and annotating screens for Alex, the developer, who works remotely. He'll also be juggling admin tasks, reviewing invoices, or scoping out potential new leads. The late afternoon often involves a quick sync with Maya or Sam to align on project status before he heads home around 6:30 PM, often with more work to do in the evening, perhaps researching a new integration or answering client queries.
Lifestyle
Peter lives in a shared flat in Hackney, splitting rent with two friends from university. His income as an owner draw means money is comfortable but not extravagant; he prioritises saving for the business's future and occasional weekend trips rather than luxury goods. He cycles everywhere, finding it the quickest way to navigate London's streets and a good way to clear his head. Evenings are often spent working or researching new tools, but he makes time for a weekly pub quiz with friends and catching a local football match when possible. He’s conscious of his health but mostly through active commuting rather than a dedicated fitness routine.
Work life
As co-founder of 'Pixel Pioneers', Peter is deeply involved in client acquisition and project management, acting as the primary liaison. His role isn't hands-on coding but overseeing the product development lifecycle, translating client needs into actionable specs for his small team and their freelance React Native developer, Alex. He spends a lot of his day in client calls, refining Figma designs, and meticulously crafting handoff notes. The pressure is on to deliver high-quality MVPs quickly and within budget, which means constantly optimising workflows and finding the most efficient tools, often favouring free or low-cost solutions to maintain profitability.
Relationships
Peter is close with his two co-founders, Maya (lead designer) and Sam (project manager), who share his entrepreneurial drive. His primary external professional relationship is with Alex, the freelance React Native developer, whom he trusts implicitly but still needs to provide clear guidance. Socially, he maintains a tight-knit group of university friends, often meeting up for football or pub nights, and relies on their shared experiences for informal advice.
How they decide
Peter tends to be pragmatic and research-oriented when it comes to business tools. He'll investigate options thoroughly, compare features and pricing, and often seek out reviews or opinions from peers in online communities. He's not impulsive but will act decisively if he sees a clear path to improving efficiency or client satisfaction, especially if the cost is low or manageable. He values solutions that are intuitive and can be implemented quickly.
How they sound
Speaks with a clear, mid-Atlantic accent common in London, often using a slightly hurried but articulate cadence. He's generally positive and direct, avoiding overly technical jargon with clients but comfortable with it when speaking to other developers or peers. He tends to use phrases like 'you know', 'basically', 'the thing is', and 'we're trying to' when explaining processes. He’ll avoid sounding overly corporate or sales-y, preferring a friendly, problem-solving tone.
Personality traits
- Pragmatic
- Resourceful
- Detail-oriented (in his own way)
- Client-focused
- Independent
- Adaptable
- Slightly impatient
- Analytically minded
Goals
- Grow Pixel Pioneers into a recognised name for mobile MVP development in London.
- Achieve a more predictable revenue stream for the studio.
- Develop a more robust internal process for design-to-code handoff.
- Gain more time for strategic business development rather than constant operational tasks.
- Explore potential for a proprietary tool or service to streamline their own workflow.
Problems & frictions
- The time-consuming nature of manually documenting design specifications for the developer.
- Ensuring consistent handoff quality as project volume increases.
- Balancing client demands for rapid turnaround with the need for thoroughness.
- Occasional communication friction between design intent and developer implementation.
- The administrative overhead of managing freelance contracts and payments.
- Finding affordable tools that genuinely improve efficiency without a steep learning curve.
Values
- speed
- independence
- client trust
- efficiency
- problem-solving
Interests
- indie hacking
- football
- no-code tools
- fintech trends
- urban cycling
Media habits
- Listens to tech podcasts during commutes
- Scans Hacker News and Reddit for industry insights
- Follows design and development influencers on Twitter
- Reads online tech blogs and newsletters
- Watches YouTube tutorials for new tools