Why this persona fits the audience
Handles short-term Google Workspace automation jobs on Upwork and directly for local SMEs. Current engagements include a Docs add-on and a Sheets extension, both assembled from free snippets and his own shared utilities; he has not paid for a boilerplate before.
- Age: 29
- Location: Hyderabad, India
- Occupation: Apps Script freelancer
- Income: ₹24L
- Education: BTech Computer Science
- Company size: N/A (Solo)
- Years in role: 3
“If I have to write the same authentication block five times, I haven't solved the problem yet; I've just built a faster way to make the same mistake.”
Bhudev Jangid, 29, is a self-taught master of the Google Workspace ecosystem operating out of Hyderabad, India. Holding a BTech in Computer Science, he transitioned from a traditional corporate role to full-time freelancing three years ago, driven by a desire for autonomy and a skepticism toward the slow pace of large organizations. Currently earning approximately ₹24 lakhs annually, he operates as a one-man consultancy, specializing in short-term automation projects for Small and Medium Enterprises (SMEs) and individual buyers on platforms like Upwork. His workflow is a testament to his values of frugality and self-reliance; he has never purchased a commercial boilerplate, instead constructing his production-ready add-ons by meticulously curating free snippets from GitHub, Stack Overflow, and community forums. Currently, Bhudev is juggling two significant concurrent engagements: a complex Google Docs add-on for legal document generation and a custom Google Sheets extension for inventory tracking. Both are cobbled together from his growing personal library of shared utilities and public code. While this approach saves him upfront costs, it creates a hidden tax on his time, as he constantly reinvents standard features like OAuth authentication and Stripe payment integration for every new client. He is technically proficient but increasingly frustrated by the lack of standardization in his workflow. He views his current state as a bottleneck to scaling; he wants to stop being a coder who builds basic scaffolding and start being an architect who delivers complex value quickly. Despite his success, he remains wary of spending money on tools that promise to save time if the implementation cost or learning curve seems higher than the effort of building it himself. His recent decisions reflect a strategic pivot: he is slowly documenting his unique utility functions to create a more robust internal framework, hoping to eventually abstract away the repetitive parts of his job without paying for external solutions.
Background & daily life
A day in their life
The alarm goes off at 6:00 AM. Bhudev spends an hour at the gym, listening to podcasts on productivity, before returning home for a light breakfast. By 8:30 AM, he is at his desk, checking emails and Upwork notifications. His morning is consumed by a urgent ticket from a UK-based logistics firm regarding a Sheets add-on that stopped updating inventory counts. He spends three hours digging through logs, realizing it's a quota issue, and refactors the script to batch requests. Lunch is a quick samosa bought from the street vendor outside. Afternoon hours involve writing documentation for a local real estate agency's custom form connector, ensuring they can use it without him. Evening brings a client call where he explains why a requested feature requires two extra days of work. He ends the day at 8 PM, reviewing a new GitHub repository for a cleaner auth method, hoping to integrate it into his personal utility library tomorrow.
Lifestyle
Bhudev lives in a modest, air-conditioned one-bedroom apartment in Hyderabad's HITEC City corridor, sharing the space with two other IT professionals to split rent. His routine is rigid: wake at 6 AM, gym for an hour, then deep work until evening. He avoids expensive dining out, preferring home-cooked meals or budget street food, channeling every saved rupee into savings or equipment upgrades. Socially, he is selective, preferring small gatherings with fellow developers over loud parties. He maintains a frugal lifestyle by refusing subscriptions unless absolutely critical, viewing software as a tool that must pay for itself immediately rather than a luxury subscription.
Work life
His workspace is a dual-monitor setup on a second-hand desk, running VS Code and Chrome with twenty tabs open. As a solo freelancer, he manages all client acquisition via Upwork and direct outreach to local SMEs. A typical day involves debugging a Google Apps Script function that failed to sync data between a Sheets sheet and a CRM, often while navigating language barriers with international clients. He relies heavily on copy-pasting community snippets, stitching together pieces from GitHub and Stack Overflow to build solutions. The pressure comes from tight deadlines and the constant need to optimize his time per billable hour, as there is no safety net of a salary.
Relationships
He is the primary financial contributor to his parents in their hometown, sending remittances bi-monthly. At work, he relies on a loose network of peers in Telegram channels for quick troubleshooting but rarely shares his proprietary logic. He is married to a school teacher who understands the freelance lifestyle but worries about his erratic schedule. He influences younger students in his college alumni group by sharing tips on avoiding common scripting pitfalls.
How they decide
Bhudev is a research-heavy, risk-averse decision-maker. He treats any potential expenditure as a calculated investment, requiring proof of ROI before spending a single rupee. He will spend days comparing free alternatives against paid tools, scrutinizing documentation and user reviews. He is unlikely to buy based on marketing fluff; he needs concrete evidence that a tool solves a specific, recurring pain point better than his current manual methods. Peer validation and technical deep-dives are his primary triggers for adoption.
How they sound
Direct, precise, and slightly technical. He speaks in clear sentences, avoiding jargon when talking to non-tech clients but switching instantly to developer slang with peers. He uses phrases like 'it's just a glue script' or 'I'm scraping the API limits.' He avoids saying 'maybe' or 'I think,' preferring 'the data shows' or 'the logic dictates.' He is polite but firm about scope creep, often deflecting vague requests with 'let's define the exact parameters first.'
Personality traits
- methodical code assembler
- cost-conscious
- quietly confident
- resourceful scavenger
- pragmatic problem-solver
- time-poor but money-aware
- independent worker
- detail-oriented debugger
- skeptic of unnecessary spend
- community-focused learner
Goals
- Build a library of reusable utility functions to reduce coding time by 40%
- Secure three long-term retainer clients in the US market
- Develop a standalone SaaS product based on his most popular snippet
- Achieve a consistent monthly income of ₹3 Lakhs within 18 months
- Contribute a major patch to a popular open-source Google Add-on repo
- Save enough capital to purchase a dedicated home office space
Problems & frictions
- Spending excessive hours re-implementing authentication logic for every new project
- Fragmented codebase making maintenance difficult when client requirements change
- Difficulty estimating project timelines due to unknown edge cases in legacy scripts
- High cognitive load from managing multiple context switches between different client environments
- Lack of standardized error handling leading to frantic client support calls
- Feeling stuck in a cycle of low-value 'glue code' rather than high-level architecture
Values
- frugality
- self-reliance
- pragmatism
- technical mastery
- efficiency
Interests
- freelance marketplaces
- Google Sheets automation
- community snippets
- open-source contributions
- local tech meetups
Media habits
- Stack Overflow threads
- r/GoogleSheets
- YouTube tutorials on specific API endpoints
- LinkedIn updates from niche dev influencers
- Telegram groups for Indian freelancers