Adheesh Bharadwaj

Why this persona fits the audience

He runs a two-person automation consultancy in Pune with one contractor, building workflows in Claude Code, Cursor, Zapier, and Google Workspace for client demos. He already pays for a competing voice tool and uses it across multiple apps during long screen sessions.

• Age: 33
• Location: Pune, India
• Occupation: Freelance automation consultant
• Income: ₹38 lakh annual income
• Education: BTech in Computer Engineering
• Company size: Sole proprietorship with one part-time contractor
• Years in role: 5

“If the machine doesn't think exactly how I intend, then I haven't built it right yet.”

Adheesh Bharadwaj is a 33-year-old freelance automation consultant operating out of Pune, India, who carved a niche in the competitive Indian tech market by specializing in end-to-end workflow automation. With a BTech in Computer Engineering and five years of experience, he has transitioned from corporate roles to running a lean, highly efficient two-person consultancy. His business model relies on leveraging cutting-edge tools like Claude Code, Cursor, and Zapier to build bespoke solutions for small to mid-sized enterprises, particularly those struggling with manual data entry and fragmented app ecosystems. Adheesh is not merely a coder; he is a systems architect who views every client process as a puzzle to be optimized. He recently expanded his toolkit to include a paid competitor voice tool, which he utilizes extensively during long development sprints to navigate applications hands-free, though he remains critical of its limitations regarding accent recognition and command precision. His income sits at ₹38 lakh annually, a figure that reflects his high value but also his strict financial discipline; he reinvests heavily in hardware and software licenses rather than lifestyle upgrades. Despite his success, he faces the constant friction of human error in existing tools and the physical toll of his profession. Adheesh is driven by a desire to eliminate the mundane, believing that true efficiency lies in making technology invisible. He is currently exploring ways to productize his custom workflows, aiming to shift from hourly billing to licensing models, all while maintaining the meticulous standards that have earned him a reputation for reliability in a chaotic market.

Background & daily life

A day in their life

Adheesh starts his day with a cup of strong filter coffee and a quick session of table tennis to wake up his hands. By 9 AM, he is deep in Cursor, refactoring a legacy Python script for a logistics client in Mumbai. Lunch is a brief affair, usually leftovers, eaten while scanning GitHub trends. The afternoon is a blur of Zoom calls where he demonstrates live automations, followed by troubleshooting a failed webhook connection that requires digging into server logs. He switches contexts frequently, jumping between Google Sheets for project tracking and Discord for contractor updates. Around 6 PM, he takes a break to cycle around Kothrud, clearing his mind before returning to debug a complex JSON payload issue. Dinner is simple, and evenings are reserved for learning new API endpoints or reading technical papers, rarely ending before midnight.

Lifestyle

Adheesh lives in a modest but meticulously organized 2BHK in Kothrud, Pune, where the only clutter is his collection of mechanical keyboard keycaps. His routine is rigid: he wakes at 6 AM for an hour of table tennis practice or cycling before diving into work. He treats his health seriously, meal-prepping on Sundays to avoid reliance on local street food during crunch weeks. Financially, he is cautious, maintaining a six-month emergency fund despite his solid freelance income, preferring to reinvest profits into better hardware rather than luxury goods. Socially, he maintains a small circle of fellow engineers and weekend badminton partners, valuing quality interaction over large gatherings.

Work life

His day is a marathon of context switching between coding in Cursor, debugging Python scripts for Claude Code integrations, and managing client expectations via Google Workspace. He employs a single remote contractor who handles initial data scraping, allowing Adheesh to focus on complex logic flows. The pressure comes from the need to deliver flawless, automated demos within tight deadlines; a broken workflow means a dissatisfied client and lost reputation. He spends hours fine-tuning Zaps and API connections, often staying late when a specific integration fails to trigger as expected, driven by a deep-seated need for system perfection.

Relationships

He is close with his parents in Hyderabad, calling them every Sunday evening, though they struggle to understand the nuances of his work. His primary professional influence is his former university professor who now mentors him on business scaling. He has no romantic partner currently, viewing dating as a distraction from his career growth phase. His contractor, Rajiv, is a trusted peer with whom he shares technical frustrations, forming a bond based on mutual respect for code quality rather than casual friendship.

How they decide

Adheesh operates as a high-caliber researcher. He rarely makes impulsive purchases; instead, he creates a comparison matrix of features, pricing models, and API documentation. He values peer validation and technical depth over marketing hype. If a tool claims to solve a problem, he expects a sandbox environment to test it against his specific use cases first. He is skeptical of 'magic' solutions and prefers transparent, documented architectures. His decisions are driven by long-term ROI and integration capabilities rather than immediate feature sets.

How they sound

Adheesh speaks with a calm, measured cadence, blending standard Indian English with occasional technical jargon like 'latency,' 'orchestration,' and 'edge case.' He avoids hyperbole and emotional language, preferring precise descriptions. He doesn't use slang unless joking with peers. In conversation, he pauses frequently to formulate the most accurate technical explanation, showing a preference for clarity over speed. He tends to say 'let me verify that' rather than guessing, reflecting his analytical nature.