Ranjeet Jangid

Why this persona fits the audience

Co-founder of a fintech startup in Bangalore with 5 full-time engineers. The product is in beta. He handles all customer acquisition personally. Currently relies on cold DMs and manual community engagement without any dedicated lead-gen software. Budget is zero until Series A funding.

• Age: 27
• Location: Bangalore, India
• Occupation: Co-founder & CTO
• Income: ₹1,200,000 - ₹1,800,000
• Education: Bachelor's Degree in Engineering
• Company size: 5
• Years in role: 1.5

“If I'm spending my day manually copy-pasting emails, I'm not building a company; I'm running a very expensive internship program for myself.”

Ranjeet Jangid is a 27-year-old technical co-founder navigating the treacherous waters of a pre-Series A fintech startup in Bangalore. Holding a Bachelor's degree in Computer Science from a top-tier Indian institute, he transitioned from a comfortable role at a mid-sized IT firm to founding a venture aimed at simplifying B2B payment compliance for small businesses. Sixteen months ago, he left his job with nothing but a laptop, a prototype, and a fierce belief that the existing market was too slow and expensive. Today, he leads a team of five engineers, acting as both Chief Technology Officer and the de facto Head of Sales. His technical philosophy is rooted in extreme efficiency; he refuses to outsource core functions until absolutely necessary, believing that the founder must intimately understand the product's friction points. Consequently, Ranjeet spends nearly 30% of his week manually engaging with potential customers on platforms like Reddit and LinkedIn, scouring for pain points that his product can solve. This hands-on approach has kept costs near zero but has created a significant bottleneck in his ability to focus on scaling the codebase. He is currently wrestling with the classic early-stage dilemma: whether to build a custom internal tool to automate his lead generation or to wait until he secures external funding to buy enterprise-grade software. His life is a delicate balance of high-stakes technical decision-making and the gritty reality of survival, where every hour counts and every rupee is scrutinized. Despite the stress, he remains driven by a desire to innovate, constantly experimenting with open-source solutions to keep the ship moving forward.

Background & daily life

A day in their life

Ranjeet wakes at 6 AM, immediately hits the road for a 45-minute cycle ride through the city's less congested lanes to decompress. By 7:30 AM, he's at his desk, checking GitHub notifications and deploying a hotfix to the beta environment. From 9 AM to 12 PM, he focuses on deep work: architecting the new KYC verification module. Lunch is a quick samosa and chai break while reading Hacker News. Afternoons shift to 'sales mode': he spends two hours manually scrolling Reddit threads, identifying prospects mentioning financial friction, drafting personalized DMs, and logging them in a Google Sheet. Evenings are reserved for team stand-ups and debugging sessions with his engineers. Dinner is late, around 9 PM, followed by either more coding or reading AI papers until 11:30 PM. Sleep comes after midnight, exhausted but driven by the ticking clock of their runway.

Lifestyle

Ranjeet lives in a shared apartment in Koramangala, a hub for Bangalore's tech scene, where the rent is manageable but the noise constant. His routine is rigid: 6 AM wake-up, 45 minutes of intense cycling to clear his head before diving into code. He avoids alcohol-heavy social gatherings, preferring quiet dinners with fellow founders or late-night coding sessions. Health is maintained through high-protein home cooking and occasional yoga, as gym memberships feel like an unnecessary expense. Financially, he lives frugally despite his income, reinvesting every rupee back into the company or emergency savings. He views money strictly as fuel for growth, not a status symbol, often skipping luxury brands to fund server costs instead.

Work life

His days are a blur of context switching between writing core backend logic for their fintech platform and manually hunting for leads. With only five engineers, he cannot afford to hire a sales team, so he spends three hours daily scanning Reddit, Twitter, and niche forums to find potential clients asking about payment gateways or compliance. He uses a mix of Notion for project tracking and a personal spreadsheet for CRM, refusing to buy tools that cost more than his monthly coffee budget. The pressure is immense; every line of code must be production-ready, and every outreach message must convert. He often works until midnight, fueled by strong filter coffee and the anxiety of burning through runway.

Relationships

Ranjeet is close to his parents in Pune, who worry about his erratic schedule but support his ambition. His closest confidants are his two co-founders, with whom he shares a living space and deep professional trust. He has a small circle of friends from college who are now working in corporate jobs; they offer perspective but rarely understand the startup stress. He actively engages with a WhatsApp group of ten other early-stage founders in Bangalore, exchanging advice and resources rather than just complaining.

How they decide

He makes decisions based on hard data and resource constraints, avoiding impulse buys. If a solution isn't free or open-source, it must demonstrate immediate, measurable ROI to justify the cost. He heavily weighs peer reviews and technical feasibility over marketing claims. His process involves a quick mental calculation of 'hours saved' versus 'rupees spent,' often leading to building custom scripts rather than purchasing SaaS subscriptions.

How they sound

Ranjeet speaks with a clipped, efficient cadence, favoring direct statements over pleasantries. He mixes standard English with Hinglish slang like 'jugaad' (making do) and 'chalta hai' (it'll work). He avoids jargon unless discussing specific tech stacks, preferring plain language to explain complex concepts. He rarely says 'maybe' or 'I think'; instead, he uses 'the data shows' or 'let's test.' He gets impatient with vague questions and values brevity above all else in conversation.