Software buyers: target customers (?)
Likely buyers (individuals and small teams) in the US, UK, EU and India who are the target customers for a software product that does the following (described from a product site; the product itself is not named here): Maker launch on DevHunt: Free IDE skill that turns a GitHub pull request into a two-zone review map. - Free IDE skill that turns a GitHub pull request into an interactive two-zone... More context: /the product — pull request review maps | Free IDE skill that turns a GitHub pull request into a two-zone review map. Open maps at the product or run the viewer yourself. They currently handle this with free tools, spreadsheets, a competitor or by hand; mixed technical confidence and budget sensitivity. Include skeptics, people already paying for an alternative, and people who have never paid for a tool like this.
10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations
10 personas · Use case: validation
Questions & insights
Meet the personas
Gerald Spinka
Gerald Spinka, a 29-year-old Senior Frontend Engineer residing in Austin, Texas, has carved out a significant niche in the SaaS development landscape. Holding a Bachelor of Science in Computer Science from a reputable state university, he quickly demonstrated a knack for building robust and user-friendly interfaces. His career trajectory led him to his current role on a 12-person product team at a growing SaaS company, where he's been for the past four years. His compensation, a $138k base salary, reflects his expertise and the demands of his role, allowing him a comfortable but not extravagant lifestyle. He lives in an apartment with a roommate to optimize his budget, prioritizing savings and investing for future financial security while still indulging in occasional travel and tech upgrades. Gerald's approach to work is deeply rooted in his personality traits: his high conscientiousness drives him to meticulousness, ensuring code quality and thoroughness, while his openness fuels his curiosity for new technologies and architectural patterns. He actively seeks out opportunities to improve development workflows, driven by a core value of shipping reliably and fostering low-friction collaboration. Recently, his team adopted a more structured approach to code reviews, partly in response to the friction caused by reviewer rotation. They now meticulously track reviewer ownership, file hotspots, and open comments in a shared spreadsheet, a system Gerald advocated for, believing it brings much-needed clarity to a distributed process. This decision, born from practical necessity, exemplifies his pragmatic problem-solving and commitment to optimizing team efficiency. He’s not driven by status as much as by the satisfaction of building well-engineered systems and continuously learning. His relationship with time is one of careful allocation, ensuring he dedicates sufficient focus to his professional responsibilities while carving out space for personal growth and downtime. Money is a tool for security and enabling experiences, rather than an end in itself.
Leticia Willms
Leticia Willms is a 37-year-old Engineering Manager based in Manchester, UK, operating at the intersection of high-level strategy and low-level code execution. With an MSc in Software Engineering and nearly fifteen years in the industry, she has transitioned from a pure backend developer to a leader who believes in leading by example. Currently, she steers a six-person cross-functional team at a Series A startup, where the margin for error is slim and the pace is relentless. Unlike many managers who delegate all technical oversight, Leticia insists on reviewing the majority of GitHub pull requests herself, a habit born from a belief that code quality is a cultural artifact, not just a metric. Her team utilizes a suite of established tools: Slack for communication, Jira for ticket tracking, and a subscription-based review-mapping competitor for visualizing code changes. However, Leticia frequently finds these tools insufficient for providing the granular, real-time insight she craves. She often finds herself manually cross-referencing Slack threads with PR comments, a tedious workflow that eats into her capacity for strategic planning. Her recent decision to tighten code review standards was met with initial resistance but ultimately improved deployment stability. Financially secure with a £92k income, she prioritizes investing in her team's growth and infrastructure reliability over personal luxuries. She views her role as a guardian of predictability, ensuring that the chaotic nature of software development yields consistent, reliable outcomes for the business.
Bheeshma Banerjee
Bheeshma Banerjee, 26, is a dedicated Full-stack Developer operating out of Bengaluru, India, earning ₹22L annually. His academic foundation is a BTech in Information Technology, which he has since built upon through practical, hands-on experience. He currently works at a small, three-person agency where the entire client codebase resides within a single monorepo. This lean structure necessitates a high degree of resourcefulness and personal initiative. Bheeshma's daily reality involves a constant cycle of feature development, code review, and deployment, all managed with a minimalist toolset. Code reviews are conducted via GitHub comments, with progress tracked using a Notion checklist, and review coverage meticulously logged in a personal spreadsheet. He has never felt the need to invest in a dedicated code review tool, preferring to adapt existing free resources to his agency's specific needs. This approach reflects his core value of 'learning by doing' and his commitment to 'clean client delivery' even under tight constraints. His income allows for a comfortable, albeit frugal, lifestyle, enabling him to live independently in a rented apartment while diligently saving. He views his work not just as a job, but as a continuous learning process, constantly seeking to optimize workflows and deepen his understanding of web app development and efficient system design. His recent decision to meticulously document his review process in a spreadsheet stems from a desire to bring more structure to an otherwise ad-hoc system, a testament to his conscientious nature and his drive for tangible improvements, even if they are self-initiated and unglamorous. He values autonomy, preferring to define his own processes rather than conform to rigid, potentially inefficient, corporate structures. This self-reliance shapes his approach to problem-solving, where he often dives deep into documentation and open-source libraries to find elegant, efficient solutions.
Mirja Kúhnert
Mirja Kúhnert grew up in a quiet town in Bavaria, where her early fascination with how things worked led her to pursue computer science. She excelled in her studies, earning a Diplom Informatik from a reputable German university, and developed a strong foundation in algorithms and data structures. Her initial career steps were in more traditional, on-site roles, but she found herself drawn to the challenges and flexibility of distributed systems. About five years ago, she joined her current company, attracted by their innovative product and the opportunity to work on a globally distributed team. This move marked a significant shift, requiring her to adapt to asynchronous communication and the nuances of coordinating work across different continents and time zones. She quickly became proficient with tools like GitHub for code management and a shared sprint board, which became central to her daily workflow. Mirja's approach to her work is deeply rooted in her value for systematic work and technical quality; she believes that robust backend systems are the bedrock of any successful product. She is meticulous in her code reviews, often spending extra time to ensure clarity and adherence to best practices, which sometimes puts her at odds with those who prioritize speed. Her income of €84k allows her a comfortable life in Berlin, but she remains pragmatic about her finances, having diligently paid off her student loans and preferring to invest in experiences and personal development rather than excessive material goods. She recently championed a small initiative within her team to standardize logging formats across their microservices, a decision driven by her desire to improve debugging efficiency and overall system observability. This project, though small, took considerable effort to gain consensus, reflecting her persistent yet diplomatic approach to driving technical improvements. Mirja views time as a valuable resource, both for her professional output and her personal well-being, and actively seeks ways to optimize her workflow to prevent burnout and maintain her high standards.
Irvin D'Amore
Irvin D'Amore carved out his niche in the freelance software consulting world by focusing on meticulous execution and client trust. After earning his BS in Software Engineering from the University of Washington, he spent a few years at a mid-sized tech firm, honing his skills in backend development and system architecture. However, the rigid corporate structure and slow decision-making processes began to chafe. He craved more autonomy and the ability to directly impact project outcomes. Around eight years ago, he transitioned to full-time freelancing, initially taking on smaller, independent projects. His reputation for reliability and thoroughness quickly grew, leading him to coordinate multiple contractors for larger engagements. He currently juggles three client repositories, a demanding role that requires him to be both a technical lead and a project manager. His workflow is heavily reliant on tools like GitHub for version control and code reviews, but he supplements this with Google Sheets, where he maintains detailed, manual checklists for tracking code changes across different branches and projects. This hybrid approach, while time-consuming, gives him a granular level of control he values. Irvin is driven by a desire for independent execution and scope discipline, viewing client trust as paramount. He finds satisfaction in solving complex technical problems and ensuring smooth, successful releases. While his income is solid, he remains pragmatic about his spending, prioritizing investments in his business and future security over immediate gratification. He sees time as his most valuable, and often scarcest, resource, constantly seeking ways to optimize his processes without sacrificing quality.
Evelien Boer
Evelien Boer, 30, is the backbone of the engineering culture at a fledgling fintech startup in Amsterdam. With a BSc in Software Engineering from TU Delft, she entered the workforce during the rise of DevOps practices and quickly realized that traditional manual testing was incompatible with the velocity of modern startups. Two years ago, she stepped into the role of QA Automation Lead, becoming the de facto guardian of code quality in a team of eight ambitious but inexperienced engineers. Unlike her peers who chase shiny new technologies, Evelien champions pragmatism; she believes that a robust, repeatable process is worth more than a sophisticated tool that no one understands. Her daily reality is a constant negotiation between speed and safety. The company operates on a shoestring budget, forcing the team to rely on a patchwork of free tools, a low-cost visual review competitor, and a meticulously maintained Google Drive document that serves as their single source of truth for approvals. This manual overhead consumes significant mental energy, often leaving Evelien with less time to focus on strategic improvements to the test architecture. She recently made the difficult decision to pause the addition of new features to the test suite to refactor existing ones, a move that caused initial friction with the development team eager to ship. However, the subsequent drop in production incidents validated her choice. Evelien views time as her most finite resource. She carefully curates her schedule to protect deep work blocks for coding, refusing to be interrupted by trivial administrative tasks. Her income of €71k allows her a comfortable life in Amsterdam, but she remains frugal, investing her surplus into professional development courses and ergonomic equipment rather than luxury goods. Status is irrelevant to her; what matters is the integrity of the software she helps build. She is currently navigating the challenge of scaling her automation efforts without hiring, a constraint that requires her to be exceptionally efficient with every line of code she writes.
Wilson Fahey
Wilson Fahey has spent his career at the intersection of nonprofits and technology, a niche he fell into by accident but never left. After graduating with a BEng in Computer Systems from the University of Manchester in 1999, he worked briefly at an enterprise software firm that treated junior devs as 'training budget investments'. The culture clash led him to freelance, then join a charity building public sector tools. That's where he developed his philosophy of 'usable enough' code: nonprofits can't afford the perfectionism of Silicon Valley, but they also can't afford technical debt that cripples them when funding dries up. At 45, he's the longest-tenured employee at Code for Commons, a role he took partly because they valued his ability to translate complex concepts into Actionable™ bullet points for grant applications. His biggest professional pride is the volunteer management system they built, which is now used by 30+ organizations. His current frustration centers around code review processes. The team's manual spreadsheet method has grown increasingly unwieldy, especially as pull requests get longer and more complex. He's tried two open-source tools but found them either too opinionated or too fragile for his team's hybrid technical skills. He's consciously avoided recommending paid solutions—the nonprofit's budget is already stretched, and he won't add recurring costs without clear ROI. Personally, Wilson values stability above all. His flat is sparsely decorated, his wardrobe consists of 12 identical wardrobe shirts, and his weekend plans rarely vary. He's been saving for a touring bike trip around Scotland for years, but keeps putting it off because 'the codebase needs one more cleanup cycle first'. His approach to both work and life could be summarized as: 'If it's worth doing, do it well enough that you won't regret it in six months.'
Philothée Simon
Philothée Simon, 38, is a quintessential modern digital craftsman residing in the heart of Paris. Holding an MSc in Computer Science, he transitioned six years ago from a traditional corporate role to become a full-time open-source maintainer and independent consultant. His flagship library, a lightweight Python utility for data serialization, has grown organically to serve thousands of developers, yet its governance remains a fragile, human-centric operation. Unlike large corporations, Philothée lacks a dedicated project manager; instead, he acts as the sole gatekeeper, relying on a patchwork of GitHub labels and a shared spreadsheet to coordinate a volunteer force spanning six continents. This manual coordination is his greatest friction point, consuming hours daily that could be spent coding. Financially, he sits comfortably in the upper-middle class with an income of €88,000, derived from a mix of grant funding, donation streams, and selective client contracting. However, this stability is tenuous, as the bulk of his time is consumed by the unpaid labor of maintaining community trust. He recently made the difficult decision to reject a lucrative acquisition offer for his library to preserve its open nature, a move that solidified his reputation but added personal financial pressure. He is currently evaluating whether to hire a part-time coordinator or automate his current spreadsheet-based workflow, though he remains wary of proprietary tools that might lock away community data. His life is a constant negotiation between the idealism of free software and the pragmatic need for sustainable livelihood, driving him to seek tools that respect both the code and the people who write it.
Dhaanyalakshmi Bhadresha
Dhaanyalakshmi Bhadresha, a 34-year-old MTech Computer Science graduate from Pune, is the CTO of a nine-person bootstrapped startup specializing in [redacted for privacy]. Her journey into tech began with a fascination for problem-solving, leading her through a rigorous academic path and several years as a software engineer at a mid-sized product company. The allure of building something from the ground up, coupled with a desire for greater technical autonomy, propelled her into the startup world four years ago. As CTO, she embodies the 'lean operations' ethos, meticulously overseeing every aspect of the development lifecycle. Her current focus is on refining the team's workflow, particularly the code review process, which she manages with a blend of GitHub, Slack, and a meticulously maintained spreadsheet. This system, while functional for their current size, is a constant source of friction and requires her direct intervention to prevent delays. She champions 'technical ownership,' encouraging every team member to feel responsible for the product's success. Dhaanyalakshmi is driven by a deep-seated belief in 'speed with discipline,' aiming to deliver features rapidly without compromising on quality or long-term maintainability. Her income of ₹28L reflects her senior role and the financial realities of a bootstrapped venture, necessitating careful budgeting and a pragmatic approach to resource allocation. She views time as a critical, non-renewable asset, both for herself and her team, constantly seeking ways to optimize processes and reduce overhead. Her professional life is a testament to her commitment to building a solid technical foundation for her company, balancing immediate product delivery needs with strategic architectural planning.
Gedeon Rutkowski
Gedeon Rutkowski is a 28-year-old DevOps engineer based in Warsaw, Poland, operating at the intersection of high-stakes infrastructure management and pragmatic engineering. With a BSc in Computer Engineering and four years of professional experience, he has evolved from a sysadmin handling server racks to a critical guardian of cloud-native architectures. Currently employed by a mid-sized Series A startup, Gedeon serves as the de facto reliability officer for a four-person platform team. His primary responsibility is ensuring that every line of Infrastructure as Code (IaC) pushed to GitHub meets rigorous standards for security and stability. Unlike larger enterprises with mature governance tools, Gedeon's team operates in a lean environment where he must build his own safety nets. His workflow is defined by a unique blend of modern automation and stubborn reliance on legacy methods. While the rest of the company uses GitHub Actions for CI/CD, Gedeon maintains a hand-tracked spreadsheet to monitor approval coverage for infrastructure changes. This manual process, coupled with a suite of lightweight, self-written shell scripts, acts as his final checkpoint before deployment. He recently spent three weeks debugging a race condition in his monitoring script that failed to catch a misconfigured load balancer, reinforcing his belief that no tool is infallible without human oversight. Gedeon's life outside work mirrors his professional ethos: structured and efficient. He lives in a modest apartment in Mokotów, commuting via bicycle to avoid Warsaw's notorious traffic. He is financially prudent, saving aggressively for a home purchase, and views his €62k salary as a means to secure stability rather than fund luxury. Technologically, he is a skeptic of 'black box' solutions, preferring transparent, scriptable tools that he can inspect line-by-line. His recent decisions have focused on reducing technical debt, specifically by automating the manual reporting he currently performs. Despite his introverted nature, he is highly respected by peers for his ability to translate complex infrastructure risks into actionable business logic. Gedeon represents the archetype of the modern engineer who values control above all else, constantly balancing the need for speed with the imperative of absolute reliability.
Want a panel built for your exact market?
Create your own audience