Software buyers: target customers (?)

Joanne Swaniawski

Joanne grew up in a suburban town outside of Chicago, the daughter of a librarian and an accountant. From an early age, she was drawn to puzzles and logic, which naturally led her to computer science in college. She earned her BSc from the University of Illinois Urbana-Champaign, where she developed a strong theoretical foundation but also a practical appreciation for well-built systems. After graduating, she spent a few years at a larger, more established tech company, gaining valuable experience in enterprise-level development but finding the pace and bureaucracy stifling. Seeking a more dynamic environment where her contributions would have a direct impact, she moved to Austin about four years ago and joined her current seed-stage SaaS startup. She was initially drawn to the company's mission and the opportunity to build backend systems from the ground up. Her current role involves significant ownership over critical, albeit often unglamorous, backend processes like email delivery, billing synchronization, and resilient webhook handling. She's learned to be incredibly resourceful, leveraging tools like cron, S3, and even Google Sheets to keep these systems operational. Jo makes a conscious effort to maintain a work-life balance, understanding that burnout is a real risk in startups. She’s pragmatic about her finances, contributing consistently to her 401k and building an emergency fund, with a growing interest in smart, long-term investments beyond her company's equity. The complexity and inherent messiness of building software in a resource-constrained environment are challenges she embraces, driven by a core belief in the power of reliable engineering.

Nathaniel Weber

Nathaniel Weber, 41, is the operational anchor of a six-person digital agency in Islington, London. Holding a BA in Business Management, he transitioned from traditional corporate logistics to the fast-paced world of digital agencies five years ago, drawn by the challenge of building structure out of chaos. Over the last half-decade, he has evolved from a general administrator into a specialist in workflow orchestration, mastering the intersection of low-code platforms like Airtable and Zapier with bespoke Python scripting. His professional identity is defined by a relentless pursuit of predictability; he believes that in a volatile market, the only competitive advantage is a flawless, repeatable delivery engine. His daily reality is a delicate balancing act. He manages the flow of information between clients, creatives, and developers, ensuring that data integrity remains uncompromised despite the frequent changes in external APIs. Currently, his operations rely on a fragile ecosystem of spreadsheets and partial automations, maintained largely by a single part-time developer whose availability is inconsistent. This dependency creates a constant background hum of anxiety for Nathaniel, who knows that one missed update could cascade into a client-facing disaster. He has recently initiated a rigorous audit of all active workflows, identifying over forty points of potential failure. Financially, Nathaniel earns £78k, a salary that reflects his seniority but leaves little room for frivolous spending. He views money as a tool for stability, prioritizing his pension and emergency fund over lifestyle inflation. His home life in Islington is a sanctuary of order, contrasting with the digital turbulence he navigates daily. He is married to Sarah, a graphic designer, and they are saving for a future that includes travel and perhaps starting a family, though his career demands currently take precedence. Nathaniel is not looking for a magic bullet; he is looking for a reliable foundation upon which to build a scalable, resilient operation. He trusts logic over charisma and evidence over promises, embodying the quiet competence required to keep a modern agency alive.

Miguel Leberer

Miguel Leberer, 29, is a full-stack engineer at a dynamic 12-person fintech startup based in Berlin. Holding an MSc in Software Engineering, he possesses a deep-seated drive for system correctness and auditability, values that stem from his early fascination with how complex systems function and fail. His career trajectory has been marked by a consistent focus on robust engineering practices, even within the fast-paced startup environment. He lives in a shared apartment in Prenzlauer Berg, a choice that reflects his pragmatic approach to finances and his preference for a communal living experience over solitary isolation. His income of €92k allows for comfortable living and a degree of financial security, which he supplements with diligent saving. Miguel's current professional focus is on maintaining critical account-verification and ledger reconciliation jobs. To address the inherent complexities and the need for reliable execution, he recently spearheaded the adoption of Temporal Cloud for one of these key processes. This decision was driven by a desire for better visibility, built-in retry mechanisms, and a more auditable workflow, moving away from the inherent fragility of his previous approach. However, the remaining critical jobs still operate on a less sophisticated stack of scheduled scripts and database flags, a compromise he finds increasingly concerning and a constant source of low-level anxiety. This duality in his operational landscape highlights the ongoing tension between rapid development and the imperative for rock-solid infrastructure in fintech. He is deeply interested in distributed systems and developer tooling, constantly seeking ways to improve the reliability and maintainability of his team's codebase. His personality, characterized by high conscientiousness and moderate openness, means he approaches problems methodically, meticulously analyzing solutions before committing. He is not prone to impulsive decisions, preferring to build a solid understanding before acting. This deliberate approach extends to his personal life, where he values routine and predictability, finding comfort in well-structured systems, both digital and analog.

Asha Butt

Asha Butt's journey into engineering management began with a strong academic foundation, earning her BTech in Information Technology from a reputable institution in India. Early in her career, she gravitated towards backend systems and the intricate logic that powers applications. She spent several years as a senior software engineer, honing her skills in Python and gaining deep insights into the operational challenges of B2B SaaS platforms. Recognizing her knack for problem-solving and her ability to guide technical discussions, she transitioned into management five years ago, taking on the role of Engineering Manager for Internal Workflows at her current company. Her team, a compact but crucial unit of five engineers, is responsible for the backbone of the company's data operations. This includes the complex dance of customer data synchronization, the processing of various document types, and the reliable dispatch of batch notifications. Asha's team currently orchestrates these tasks using a combination of Python scripts, scheduled jobs on Cloud Run, and, critically, a shared Google Sheet that serves as their makeshift control panel for tracking retries and exceptions. This hybrid approach, while functional, has become a source of increasing friction as the company scales. She is acutely aware of the fragility of their current system, particularly the manual oversight required for the spreadsheet, which consumes valuable engineering time and introduces a risk of human error. Asha is driven by a desire for stability and predictability in her team's output. She values clear ownership and accountability, ensuring each team member understands their contribution to the larger system. Her income of ₹38L reflects her experience and the critical nature of her role within the organization. She lives with her husband and parents, a common arrangement in Bengaluru, and while her professional life demands significant attention, she consciously carves out time for family and personal well-being, understanding that sustained performance requires balance. Her recent focus has been on identifying ways to professionalize their workflow management, moving away from ad-hoc solutions towards more robust, automated systems that can scale with the company's ambitions.

Yseult Vidal

Yseult Vidal's journey into the world of no-code automation began during her Licence in Digital Marketing at a Parisian university. While she excelled in understanding digital strategy, she quickly became frustrated by the manual processes and inefficient workflows she observed in many small businesses, even within her internships. She saw a clear gap: small retailers and service providers were often overwhelmed by administrative tasks, lacking the budget or technical expertise for custom software solutions. This realization sparked her entrepreneurial drive. After graduating, she worked briefly for a digital agency, but the corporate structure felt stifling. She craved the direct impact she could have on smaller enterprises. Teaming up with Louis, a former classmate with a knack for data organization, they founded their consultancy five years ago. Their focus has always been on practical, accessible solutions for the Parisian small business scene. They built their reputation by meticulously wiring together tools like Make (formerly Integromat), Airtable, and Google Sheets, creating custom workflows that automate everything from customer inquiries and appointment scheduling to inventory tracking and sales reporting. Yseult is particularly adept at translating complex technical possibilities into understandable benefits for her clients, emphasizing time savings and reduced operational friction. She reinvests a significant portion of the consultancy's income back into the business, primarily for software subscriptions and continuous learning, rather than personal luxuries. Her income of €62k reflects a successful, albeit demanding, niche practice. She recently decided to standardize their client onboarding process, creating a more detailed questionnaire to better capture initial needs, aiming to reduce the time spent on discovery calls and improve project scoping accuracy. This decision stems from a desire to scale their operations without compromising the personalized service that defines their brand, reflecting her core value of client practicality and efficiency.

Corey Hackett

Corey Hackett, 27, is the quintessential solo founder, carving out his niche in the competitive micro-SaaS landscape from his base in Chicago. His journey into software development wasn't through a traditional degree; after a couple of semesters of college, he found his calling in the self-taught path, driven by an insatiable curiosity and a knack for problem-solving. This led him to build his current micro-SaaS product, a tool designed to streamline specific business workflows. His approach to operations is deeply rooted in resourcefulness and a profound distrust of unnecessary complexity. Instead of investing in dedicated orchestration platforms, Corey has meticulously crafted his own system using a combination of cron jobs, shell scripts, and a series of hand-maintained CSV files. This DIY ethos extends to customer onboarding, usage tracking, and even invoice reminders. He draws a modest but sufficient income of $88k annually, which he largely reinvests into the business, prioritizing growth and stability over personal luxury. His decision to operate entirely solo stems from a strong desire for autonomy and the satisfaction of building something end-to-end. He's not afraid of hard work, viewing the long hours and the constant need for vigilance as inherent parts of the entrepreneurial journey. Recently, he spent two weeks refactoring his customer data export script, optimizing it to handle larger datasets more efficiently and reduce processing time by nearly 30%, a testament to his dedication to incremental improvement and system robustness. He views time as his most valuable asset, and his current operational setup, while requiring significant personal effort, grants him the ultimate control over how that asset is deployed.

Mable Bergnaum

Mable Bergnaum's journey into data analytics began with a fascination for patterns and order, which led her to pursue a BSc in Statistics at the University of Manchester. Upon graduating, she secured a role as a junior analyst at a growing e-commerce company, where she quickly demonstrated a knack for untangling complex data issues. Over the past four years, she has risen to become a key data analyst within the three-person analytics team. Her primary responsibility is the meticulous maintenance of nightly data pipelines, encompassing product feed synchronisation, warehouse inventory imports, and rigorous exception checking. She relies heavily on dbt for data transformation, custom Python scripts for automation and ad hoc tasks, and spreadsheets for quick checks and reporting. Mable is deeply committed to data accuracy and operational stability, viewing her role as the silent guardian of the company's data integrity. She recently championed the adoption of more robust logging within her Python scripts after a particularly disruptive incident involving a delayed product feed update that impacted a major marketing campaign. This decision, though requiring extra effort upfront, was driven by her core value of repeatability and a desire to prevent future chaos. She finds satisfaction in building reliable systems and is constantly looking for ways to improve efficiency and reduce manual intervention. Her current income of £54k supports her modest lifestyle, allowing for savings towards a property deposit and occasional travel, but she remains budget-conscious, preferring to leverage open-source tools where possible. Mable is acutely aware of the technical debt accumulating in some of her older scripts and is actively seeking more sustainable solutions, though budget constraints often limit her options. She sees her role as foundational, ensuring the business has trustworthy data to make informed decisions, and takes pride in the quiet competence with which she manages these critical processes.

Bhagavaan Mishra

Bhagavaan Mishra is a 31-year-old freelance automation specialist based in Pune, India, who carved out a niche by mastering the art of connecting disparate digital services into seamless, reliable workflows. Holding a Diploma in Computer Engineering, he entered the workforce early, working briefly in IT support before transitioning to freelance consulting four years ago. Driven by a desire for autonomy and a dislike for rigid corporate structures, he now operates as a one-person consultancy, serving 4–5 small and medium-sized businesses (SMBs) concurrently. His toolkit is a testament to his pragmatic philosophy: he relies heavily on the open-source version of n8n for orchestrating complex logic, leverages Google Sheets as a flexible database layer, and writes lightweight Python scripts for tasks that require specific data manipulation or API handling beyond standard connectors. Bhagavaan's work often involves inheriting messy, partially documented setups left behind by previous developers or DIY attempts by business owners. Instead of discarding these, he meticulously reverse-engineers them, adding error handling, logging, and modular structure to ensure longevity. This approach has earned him a reputation for trustworthiness among his clients, who value his ability to stabilize their operations without demanding exorbitant fees. He earns approximately ₹24 Lakhs annually, a figure that reflects both his technical proficiency and his disciplined approach to resource management. Unlike many peers who chase high-profile enterprise contracts, Bhagavaan focuses on the 'boring' but critical infrastructure of small businesses—lead routing, invoice processing, and notification systems—where his interventions yield immediate, tangible ROI. Living in a rented 2BHK in Kothrud, he maintains a home lab that serves as both a testing ground for new ideas and a personal sanctuary. He is deeply invested in the concept of self-hosting, believing that data sovereignty and control are paramount. His decision-making style is cautious and research-heavy; he never adopts a new tool without validating its community support and long-term viability. While he enjoys the freedom of his schedule, he faces the constant challenge of scaling his impact without compromising his quality of life or becoming dependent on a single client. Recently, he made the strategic decision to document his most successful workflows into reusable templates, aiming to reduce repetitive coding and free up time for more complex architectural challenges. To Bhagavaan, success isn't about the latest tech stack, but about creating systems that work silently, reliably, and efficiently, allowing his clients to focus on their core business while he ensures the invisible gears turn smoothly.

Luke de Bruyn

Luke de Bruyn’s journey into product operations is a natural evolution of a fascination with systems and efficiency. Growing up in a family that valued order and diligence, he developed an early aptitude for understanding how things fit together. His MSc in Business Information Systems provided a strong theoretical foundation, but it was his early roles in various tech companies that honed his practical skills. He gravitated towards the 'glue' roles, the ones that ensured processes didn't break under the strain of rapid growth. Landing at the current marketplace startup four years ago felt like a perfect fit; the dynamic environment offered constant challenges in process design and optimization. He's built his current role from the ground up, establishing the core operational cadences. Luke’s personal finances are managed with the same discipline as his work, consistently saving a portion of his €71k income, though he’s realistic about the long-term housing market in Amsterdam. Time is a precious commodity; he views it as a resource to be optimized, both for professional output and personal well-being, ensuring that his dedication to operational excellence doesn’t come at the cost of his own mental or physical health. He recently pushed back on a request to 'quickly' build a new tracking system in spreadsheets, insisting on a more structured approach involving requirements gathering and a pilot phase, demonstrating his commitment to sustainable operational discipline over quick fixes.

Byron Ritchie

Born in Spokane and raised in the shadow of Boeing factories, Byron Ritchie inherited a pragmatic appreciation for complex machinery early in life. Holding a BS in Electrical Engineering from the University of Washington, he spent his twenties designing embedded systems for industrial automation before the internet boom shifted his focus toward software. In 2019, sensing the impending shift toward generative AI, he left a stable role at a large defense contractor to launch his own boutique studio in Seattle. Today, his seven-person team handles critical infrastructure for regional law firms and healthcare providers, executing millions of document extractions and batch summarizations monthly. Despite the modern veneer of his work, Byron's operational backbone remains surprisingly analog: a meticulously maintained Google Sheet that tracks the status of every single request, paired with a suite of custom Python scripts and GitHub Actions runners he wrote himself. This hybrid approach offers him granular control but introduces significant fragility. He frequently finds himself acting as the human glue holding together distributed tasks that should ideally be managed by a robust, queue-based orchestration platform. Byron views time as his scarcest resource. He has rejected opportunities to scale too quickly, fearing that adding headcount without solving the underlying orchestration inefficiencies would only amplify chaos. His recent decisions have focused entirely on hardening the existing stack—rewriting retry logic, optimizing token usage, and creating better logging visibility. He is not looking for a magic bullet; he needs a tool that integrates seamlessly into his existing Python-centric workflow without forcing a total architectural rewrite. For now, he accepts the friction of the spreadsheet because it gives him total visibility, even if it limits his ability to sleep soundly during high-volume batches.