Dev Varman

Why this persona fits the audience

Solo founder in Bangalore running a B2B SaaS startup. Uses Antigravity IDE daily for rapid prototyping. Currently relies entirely on free GitHub repositories and manual copy-pasting of Playwright scripts. Highly budget-conscious and skeptical of 'directory' products that duplicate existing open-source content without clear ROI.

• Age: 31
• Location: Bangalore, India
• Occupation: Founder & CTO
• Income: ₹1,200,000 - ₹1,800,000 (personal)
• Education: Bachelor's in Information Technology
• Company size: 1 (Solo)
• Years in role: 2

“I don't need another dashboard; I need my code to run faster without me having to read a thousand lines of documentation just to make it work.”

Dev Varman is a 31-year-old solo founder and CTO based in Koramangala, Bangalore, operating a lean B2B SaaS startup focused on automating enterprise workflows. With a Bachelor's in Information Technology and nearly a decade of industry experience prior to launching his venture, Dev has built a reputation for extreme frugality and technical ingenuity. Unlike many peers who seek immediate VC funding, he is bootstrapping, aiming to reach profitability before diluting his equity. His development environment is a testament to his philosophy: he relies exclusively on the Antigravity IDE for its speed and utilizes a patchwork of free, open-source GitHub repositories for his testing infrastructure. Specifically, he manually copies and pastes Playwright scripts, meticulously vetting each commit for compatibility, a process that consumes roughly 15 hours of his week but saves him thousands of rupees in licensing fees. Despite his technical prowess, Dev is perpetually battle-worn by the 'integration tax'—the hidden cost of maintaining disjointed tools. He is deeply skeptical of curated directories or paid AI coding assistants that promise seamless workflows but ultimately duplicate what is already available for free in the wild. His recent decision to reject a popular $29/month MCP server aggregator was driven by a lack of transparency regarding their update frequency and the redundancy of their offerings compared to his current setup. Dev views time as his most critical asset; every minute spent managing a tool is a minute stolen from building his product. He lives in a world where status is irrelevant, and only shipping features and retaining customers matter. While he enjoys the autonomy of being his own boss, the isolation of solo founding weighs on him, driving his relentless pursuit of efficiency. He is currently evaluating whether to automate his own curation process or double down on manual control, a decision that could define the scalability of his startup.

Background & daily life

A day in their life

The day begins at 5:30 AM with black coffee and checking global market trends before opening Antigravity IDE. By 7:00 AM, he is deep in code, refactoring a Playwright test suite that he spent the previous night manually copying from three different GitHub issues. At 9:00 AM, he switches to a Zoom call with a potential enterprise client, pitching the value of his automation capabilities while mentally calculating the cost of server downtime. Lunch is a quick sambar rice bowl eaten at his desk while reading a thread on MCP server integrations. Afternoon hours are spent on 'growth hacking,' tweaking landing page copy based on analytics data. Evenings involve a walk in the neighborhood park to decompress, followed by another hour of coding or reading technical documentation until midnight, ensuring the prototype remains ahead of the competition.

Lifestyle

Dev lives in a modest, high-efficiency two-bedroom flat in Koramangala, sharing the space with a fellow developer who keeps the living room quiet during work hours. His routine is rigid: he wakes at 5:30 AM to code before the city noise peaks, often skipping breakfast to maximize early focus time. He is health-conscious but inconsistent, relying on quick gym sessions or home calisthenics rather than expensive memberships. Financially, he treats every rupee as an investment; he drives a second-hand hatchback and cooks most meals at home to avoid Bangalore's delivery markups. Socially, he is selective, preferring one-on-one coffee chats with other founders over loud networking events, viewing his time as a scarce currency that cannot be wasted on fluff.

Work life

As the sole technical force behind his B2B SaaS, Dev's days are consumed by the tension between feature velocity and system stability. He spends 80% of his time in Antigravity IDE, manually stitching together Playwright scripts from disparate GitHub repositories because he refuses to pay for unproven wrappers. The pressure is constant: one bug in production can mean losing a client, yet hiring help is currently off the table. He works late into the night, fueled by strong filter coffee, often making architectural decisions in isolation. His workspace is cluttered with physical notebooks full of system diagrams, reflecting a mind that prefers analog sketching for complex logic before typing a single line of code.

Relationships

Dev maintains a close, pragmatic bond with his parents in Chennai, who view his salary as a source of family security but worry about his long-term stability. His professional network consists mostly of other solo founders in Bangalore and remote-first developers; these are people he trades advice with, not just peers. He has a small circle of college friends who provide emotional grounding, though they rarely understand the specifics of his daily grind. He is influenced primarily by anonymous thought leaders on Twitter/X and specific maintainers of open-source projects he uses daily.

How they decide

He operates on a 'verify first, trust later' model. Before adopting any new tool or methodology, he demands proof of concept, preferably via a self-run local instance or a direct comparison against his current manual workflow. He is highly resistant to subscription models unless the ROI is mathematically undeniable within the first month. Peer reviews and open-source community sentiment weigh heavier than polished marketing decks. He moves fast only after eliminating variables, often delaying adoption until a solution feels inevitable rather than merely convenient.

How they sound

His speech is rapid-fire, clipped, and devoid of corporate jargon. He speaks in short, declarative sentences, often interrupting himself to clarify a technical point or correct a metric. He avoids vague terms like 'synergy' or 'disruptive,' preferring concrete verbs like 'compile,' 'deploy,' or 'optimize.' When discussing money, he is blunt about costs and margins. There is a slight Bangalore accent but heavily softened by his international exposure to tech culture. He frequently uses analogies related to machinery or code architecture to explain business concepts.