Rahul Deshpande

Why this persona fits the audience

Building an AI-powered HR tool in Bangalore. Currently relying on direct outreach via LinkedIn and cold emails to find early adopters, spending significant time filtering irrelevant responses without a systematic way to score intent.

• Age: 26
• Location: Bangalore, India
• Occupation: Co-founder & CTO
• Income: ₹18L-₹25L INR
• Education: Bachelor's in Engineering
• Company size: 3 (including himself)
• Years in role: 1.5

“We're building a Ferrari engine in a garage with no map, trying to guess where the destination is just by looking at the exhaust smoke.”

Rahul Deshpande is a 26-year-old engineer turned entrepreneur navigating the precarious waters of a pre-revenue startup in Bangalore. With a Bachelor's in Computer Science from a tier-2 college, he entered the workforce briefly at a large IT services firm before realizing the bureaucratic stagnation was stifling his ambition. In 2022, he quit to co-found an AI-driven HR platform aimed at solving the talent acquisition bottleneck for mid-sized Indian companies. His background is deeply rooted in machine learning; he built the initial prototype alone, leveraging open-source libraries to create a scoring algorithm for candidate suitability. However, the reality of being a Technical Co-founder has forced him to wear multiple hats, none of which sit comfortably. While his engineering skills are sharp, his lack of sales infrastructure has become his Achilles' heel. He currently spends nearly half his week manually sifting through hundreds of LinkedIn connections and cold emails, attempting to identify genuine interest among the noise. This manual process is unsustainable and drains the creative energy needed for product development. Rahul is driven by a fierce desire to innovate and scale, but he is constantly battling the friction of doing everything himself. He is a perfectionist who believes that if the data isn't clean, the product cannot be trusted. His life is a balancing act between the romantic ideal of building something transformative and the gritty reality of chasing leads that often go nowhere. He is financially cautious, reinvesting every rupee of revenue back into server costs and domain licenses, while living frugally to extend his personal runway. Despite the stress, he remains optimistic, fueled by the belief that if he can just automate the discovery of pain points, the rest will fall into place. He is a man of action, often making bold architectural decisions based on limited information, hoping that speed will outpace uncertainty.

Background & daily life

A day in their life

Rahul wakes up at 5:00 AM for a run, returning by 6:30 AM to shower and brew strong filter coffee. By 7:30 AM, he's on a video call with his co-founders, reviewing overnight server logs and discussing a critical bug in their recruitment algorithm. The morning is spent coding, but he gets interrupted frequently by Slack notifications and email pings from potential clients. Lunch is a rushed 20-minute affair while reading a technical blog post. Afternoons are dedicated to 'sales mode,' where he manually reviews 50+ LinkedIn profiles, sending personalized connection requests and drafting follow-up emails. This manual filtering is exhausting; he spends hours categorizing responses into 'hot,' 'warm,' or 'noise.' Evenings involve a chess match on Lichess or editing photos from his walk. He often stays up until midnight fixing deployment errors, knowing that a single outage could lose a prospect's trust. Dinner is usually late, followed by a final check of analytics before collapsing into bed.

Lifestyle

Rahul lives in a high-energy apartment in Indiranagar, sharing the space with two other founders who keep odd hours. His mornings are non-negotiable: a 5 AM run through Cubbon Park to clear his head before the city wakes up. He treats food as fuel, often grabbing quick biryani or smoothies between meetings, though he tries to cook healthy meals on Sundays. Money is tight; he lives frugally to extend his runway, avoiding luxury brands but investing heavily in ergonomic gear for long coding sessions. Socially, he oscillates between deep one-on-one coffee chats with peers and chaotic group hangouts where he listens more than he speaks. Photography is his decompression valve; he carries a mirrorless camera everywhere, capturing the stark contrast of Bangalore's traffic and street life. He is sleep-deprived but functional, running on caffeine and adrenaline.

Work life

His days are a blur of context switching between backend architecture and sales execution. As the sole technical lead, he spends 40% of his time writing Python scripts for their ML pipeline and another 30% debugging deployment issues. The remaining 30% is a jarring shift to manual labor: scanning LinkedIn profiles, drafting cold emails, and manually parsing responses from HR managers who often ignore them. He hates this part, viewing it as 'technical debt' in human form. His team is tiny, so he has no dedicated sales rep to filter leads. He uses a mix of Notion for project tracking and a custom spreadsheet that feels increasingly fragile. The pressure is constant; every day without a signed pilot feels like a step toward failure, forcing him to make rapid, unverified decisions about product pivots based on gut feeling rather than data.

Relationships

Rahul is close to his younger sister, who works in Mumbai and provides emotional grounding during burnout phases. His primary social circle consists of fellow bootstrapped founders in Bangalore; they meet bi-weekly at local cafes to swap war stories, but these interactions are often transactional. He has a strained relationship with his parents, who view his startup journey as risky compared to traditional corporate jobs. He relies heavily on online communities for professional validation, finding solace in anonymous forums where he can vent frustrations without fear of judgment. Trust is earned slowly, and he values competence over charisma in friendships.

How they decide

He operates on a 'measure twice, cut once' philosophy when it comes to technology, conducting extensive prototyping before committing to a stack. However, regarding business strategy, his decisions are often reactive and speed-driven due to cash flow pressures. He is deeply skeptical of marketing hype and requires concrete evidence of utility before adopting new tools. Peer influence matters significantly; if three respected technical leaders endorse a method, he will investigate it immediately. He avoids impulsive purchases unless the ROI is mathematically certain, preferring incremental improvements over radical shifts.

How they sound

His speech is rapid-fire, punctuated by technical jargon and Hindi-English code-switching ('yaar', 'bhai'). He tends to skip pleasantries, jumping straight into the problem statement. He avoids vague language, preferring specific metrics and percentages. When stressed, his cadence speeds up, and he uses phrases like 'this is a bottleneck' or 'we need to iterate fast.' He rarely says 'I don't know'; instead, he says 'let me verify the data.' He is polite but firm, often cutting off conversations that lack substance. He uses metaphors related to systems and architecture to explain business concepts.