Dev Guneta

Why this persona fits the audience

Manages customer support for a 4-person edtech team in Pune, doing ticket triage, response templates, and escalation tracking in free tools and shared sheets while the company keeps software spend tight.

• Age: 27
• Location: Pune, India
• Occupation: Support Operations Generalist
• Income: ₹18 lakh
• Education: Bachelor's in business administration
• Company size: 4 employees (Founder, 2 Developers, 1 Sales)
• Years in role: 1.5

“You don't need fancy software to run a good operation; you just need a system that doesn't break when the lights go out.”

Dev Guneta is a 27-year-old Support Operations Generalist navigating the precarious balance of growth and frugality in Pune's vibrant edtech scene. Born and raised in a middle-class household, he graduated with a Bachelor's in Business Administration, drawn initially to finance but quickly pivoting to operational logistics after realizing his strength lay in organizing chaos rather than balancing ledgers. Currently, he serves as the de facto backbone of a four-person edtech startup, where the founder prioritizes product development over infrastructure, leaving Dev to manage customer support with nothing but free-tier tools and sheer grit. His daily reality involves a high-stakes game of digital whack-a-mole. Without a dedicated CRM, Dev maintains a sprawling, color-coded Google Sheet that acts as the single source of truth for thousands of customer interactions. He manually tags tickets, tracks SLA breaches, and builds rudimentary dashboards to visualize trends, often working late to refine these spreadsheets so they don't collapse under the weight of increasing volume. Despite the constraints, he has developed a reputation for resourcefulness, creating custom email filters and automated response templates that save the tiny team hours of manual work each week. Financially, Dev is ambitious but cautious. Earning ₹18 lakh annually, he lives comfortably but refuses to indulge in unnecessary luxuries, channeling his savings into a future home and vehicle. His personality reflects a steady conscientiousness; he is not easily rattled by setbacks but is deeply bothered by inefficiency. While he enjoys the thrill of technology reviews and the camaraderie of weekend cricket matches, his true passion lies in optimizing systems. Recently, he made the difficult decision to decline a job offer from a larger firm with a higher salary, opting instead to stay and help his current team scale, believing that mastering operations in a resource-constrained environment will make him indispensable in the long run. He views his current role not as a temporary stopgap, but as a rigorous training ground for future leadership.

Background & daily life

A day in their life

Dev starts his day with a quick jog and a hot cup of chai at a roadside stall near his home, scanning local news and cricket scores on his phone. By 9:15 AM, he is at his desk, immediately diving into the 'Urgent' folder of the shared Gmail account, sorting tickets into priority buckets based on a color-coded logic he built himself. He spends the next two hours drafting template responses for common queries about course enrollment and payment failures, carefully tweaking tone to match the educational context. Around noon, he attends a chaotic stand-up meeting where the developers explain why a bug delayed a feature launch; he documents the impact on customers in a master sheet. Lunch is a hurried meal of thali from the office canteen. Afternoon is spent troubleshooting a specific escalated case involving a dissatisfied teacher, requiring him to coordinate directly with the founder to find a workaround. The evening involves closing loops on pending tickets and spending 30 minutes researching how to automate a specific data pull using free scripts. He leaves the office by 7 PM, heading home to cook dinner and relax with a tech review video before sleeping.

Lifestyle

Dev lives in a modest but well-maintained flat in Baner, sharing expenses with his parents who are retired school teachers. His routine is disciplined: he wakes up at 6 AM, jogs around the nearby Symbiosis University tracks, and grabs a vada pav from a street stall before heading out. He spends evenings cooking simple meals or watching tech reviews, often critiquing the latest gadgets with a critical eye. Financially, he is conservative; he saves aggressively for a down payment on a car and invests in mutual funds, avoiding credit card debt. Socially, he balances work with weekly cricket matches at a local club and dinner gatherings with college friends who have moved to different cities.

Work life

As the sole support operations generalist for a four-person edtech startup, Dev wears every hat except code-writing. His day is a constant cycle of triaging incoming tickets via a shared Gmail inbox, updating a master Google Sheet for escalation tracking, and drafting standardized response templates to ensure consistency. The founder insists on zero software spend, forcing Dev to build complex workflows using free tiers of collaboration tools and manual data entry. He manages the emotional labor of frustrated educators while trying to maintain system integrity without a dedicated CRM. The pressure comes from the lack of automation; every minute saved by a spreadsheet hack feels like a win against the inevitable chaos of scaling.

Relationships

Dev is deeply connected to his parents, who provide emotional stability and occasional financial advice. His closest circle consists of three college friends who now work in Mumbai and Bangalore; they meet virtually once a month to discuss career pivots. At work, he has a respectful but distant relationship with the founder, whom he admires for vision but finds difficult to push back on financially. He is respected by his few peers in the Pune startup community for his ability to keep order out of chaos, though he rarely seeks validation from them.

How they decide

Deliberate and evidence-based. Dev avoids impulsive choices, preferring to gather data, test small-scale solutions, and consult trusted peers before committing to a new process or purchase. He is naturally skeptical of marketing claims and requires concrete proof of efficiency gains before changing a workflow.

How they sound

His speech is clear, professional yet grounded in Marathi-English colloquialisms. He speaks in complete sentences, avoiding jargon unless explaining technical concepts to non-technical staff. He tends to pause briefly to think before answering complex questions, favoring accuracy over speed. In conversation, he uses phrases like 'let's check the data first' or 'we can manage this for now,' reflecting his pragmatic nature. He avoids overly enthusiastic language, preferring measured assertions.