10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Adhrit Suthar

Adhrit Suthar

CRM operations lead at a startup

Full-depth AI personas

Why this persona fits the audience

Runs Salesforce operations for a 45-person B2B SaaS company in Bengaluru with a 4-person revenue systems team. They coordinate releases with engineering, keep a GitHub repo for some metadata, and still rely on spreadsheets for approval tracking.

  • Age: 31
  • Location: Bengaluru, India
  • Occupation: CRM Operations Lead
  • Income: ₹18L–₹26L
  • Education: Bachelor's degree in Information Technology
  • Company size: 45 employees, VC-backed
  • Years in role: 3
“I didn't sign up to be a traffic cop for metadata, but here we are.”

Adhrit Suthar never planned to become a CRM operations leader. After graduating with a degree in Information Technology, he joined a mid-sized IT firm as a Salesforce admin, expecting a quiet career maintaining dashboards. But when a startup offered him a chance to build processes from scratch, he took it—only to find himself drowning in spreadsheets and approval bottlenecks. Now, as the CRM Operations Lead at a 45-person SaaS company in Bengaluru, he's the glue between engineering, sales, and marketing, ensuring their Salesforce instance doesn't become the bottleneck it once was. His team of four is small but scrappy, juggling metadata management in GitHub with approval tracking in—yes, still—spreadsheets. Adhrit is the kind of person who'll stay late to automate a workflow but leave early to teach a coworker how to use it. He's currently pushing hard to eliminate manual processes, but leadership wants to see ROI before approving any new tools. His biggest frustration? Marketing teams who treat Salesforce as a cargo cult rather than a system that requires proper maintenance. Despite the chaos, he loves the problem-solving aspect of his job and the rare moments when a perfectly automated release goes off without a hitch. Outside work, he's trying to balance his desire to upskill with the reality of constant firefighting. His dream? To build a fully automated Salesforce pipeline that doesn't require spreadsheets or weekend heroics. But for now, he's content with small wins—like the time he convinced engineering to prioritize a metadata merge tool, saving his team 10 hours a week. His biggest fear isn't failure but inertia—knowing his company will continue using inefficient processes simply because 'it works for now.'

Background & daily life

A day in their life

Adhrit's alarm goes off at 6:30 AM, and after grudgingly shutting it off three times, he drags himself to the kitchen. His morning routine is chai, toast, and 20 minutes of Twitter before getting dressed. He leaves for work by 7:45 AM, either walking or taking the office scooter. The first hour is reserved for triaging Slack messages and emails—usually requests from sales reps who need new reports or engineering tickets that need prioritization. By 9 AM, he's in his first sync: the bi-weekly release planning meeting. Today, it's contentious because marketing missed their deadlines again. He spends the next two hours documenting the approval process for a new feature (something his boss asked for last quarter). Lunch is usually a sad desk salad while he reviews a junior admin's work. Afternoon is filled with meetings: first with engineering to coordinate the actual deploy, then with sales to review new reports. He leaves the office around 7:30 PM, having spent the last 30 minutes setting up automated validation rules in Salesforce. On his way home, he stops for biryani at a local joint—his one indulgence. The evening is spent either catching up on YouTube tutorials or, if he's particularly stressed, playing badminton with a coworker at a nearby court.

Lifestyle

Adhrit rents a compact apartment near Koramangala because it's a 15-minute bike ride to work. His mornings start at 6:30 AM with chai and a quick scroll through Twitter for Salesforce news. He walks to work when the weather's decent, otherwise takes the office scooter pool (his company has three shared scooters for employees). His weekends are split between debugging Salesforce permission sets and playing badminton with coworkers at a nearby court. He's frugal with discretionary spending but splurges on good headphones for conference calls. His biggest money stress is saving for a down payment on a home in Bengaluru—rental prices have him worried. Socially, he's close with a small group of tech professionals who meet for occasional brewery visits or weekend hikes in the Ramapura Agrahara Forest.

Work life

Adhrit leads Salesforce operations at a fast-growing SaaS company where releases used to be weekly nightmares. He now coordinates bi-weekly releases between engineers, admins, and sales teams, using a hybrid of GitHub for metadata and spreadsheets for approvals (he knows it's messy but it works for now). His team of four includes one engineer who's great but always overcommitted, a junior admin who asks too many questions, and two others who are still learning. His biggest daily frustration is getting marketing to finalize copy before the deploy window. He spends 40% of his time unblocking others, 30% on documentation, and 30% fighting fires—usually around data validation rules. Lately, he's been pushing to eliminate spreadsheets entirely but leadership wants to see a cost justification. He keeps a whiteboard in his cubicle covered in release timelines and dependency maps.

Relationships

Adhrit is the youngest child of a retired school teacher and a small business owner from Ahmedabad. They visit him twice a year, and while they're proud of his career, they don't fully understand what he does. His older sister works in corporate HR and constantly tries to set him up with colleagues from Mumbai. His closest friends are all from the Bengaluru tech scene—people he met through Salesforce user groups or at startup happy hours. He's particularly close with a former coworker who now works at a competitor, and they have an unspoken rule not to discuss proprietary information. For professional advice, he follows a few Salesforce MVPs on Twitter but mostly learns by doing and breaking things. His romantic life is currently on hold—between long hours and weekend work, dating apps feel like another project he can't take on right now.

How they decide

Adhrit researches thoroughly before making decisions but knows when to trust his gut. He'll spend hours evaluating tools but ultimately goes with what his team can adopt quickly. He makes small decisions independently but consults his manager for anything that might affect budgets or headcount. He's heavily influenced by peer recommendations (especially those from similar-sized companies) and will test any promising solution internally before committing. He's cautious about vendor relationships but will take calculated risks if it means saving his team time.

How they sound

Adhrit speaks quickly in paragraphs when he's excited but becomes measured and precise when explaining technical concepts. He uses Bangalore slang casually ('chill na', 'let's just fix this') but switches to more formal English in meetings with executives. You'll never hear him say 'That's not my job' though he does say 'I don't own that workflow' when deflecting. He uses jokes to defuse tension but avoids sarcasm—he's seen how that plays out in Slack threads. When frustrated, his Gujarati swear words slip out briefly before he switches back to English. He's meticulous about email etiquette but uses Slack gifs for everyday communication.

Personality traits

  • Tactfully pushy with stakeholders who delay approvals
  • Secretly judges people who don't document workflows
  • Can geek out on GitHub pull request workflows but hates unnecessary meetings
  • Buys coffee for his team but won't pay for premium SaaS tools without ROI proof
  • Keeps a personal kanban board for household tasks
  • Knows 37 Salesforce keyboard shortcuts but forgets his mom's birthday sometimes
  • Prefers async communication but will yell at Slack when a release goes sideways
  • Reads DevOps blogs during lunch but skips the gym to finish a metadata review

Goals

  • Be promoted to Director of Revenue Systems within 18 months
  • Build a fully automated Salesforce deployment pipeline by Q3
  • Buy a small apartment in Bangalore within 3 years (current high rents are killing him)
  • Start a YouTube channel about Salesforce for non-technical users (he's recorded 2 episodes so far)
  • Find a way to reduce his team's 40% manual approval work without hiring more people

Problems & frictions

  • Spreadsheets for approval tracking are causing version control nightmares
  • Marketing always misses content deadlines, delaying releases
  • Engineering treats Salesforce changes as low priority compared to product work
  • His boss wants everything documented but doesn't allocate time for it
  • Finding talent for his team is harder than he expected (good admins are scarce in Bangalore)
  • Feels like he's constantly firefighting instead of building scalable processes

Values

  • Speed and efficiency in operations
  • Pragmatism over perfectionism
  • Team coordination with minimal friction
  • Ownership of workflows
  • Continuous improvement without over-engineering

Interests

  • Salesforce DevOps automation
  • B2B SaaS revenue systems
  • GitHub workflows for non-engineering teams
  • Workflow automation (Zapier, Make, etc.)
  • Bengaluru startup ecosystem

Media habits

  • Twitter (X) for ops/sales tech trends
  • LinkedIn for professional networking
  • X (formerly Twitter) for real-time Salesforce release discussions
  • YouTube for Salesforce configuration walkthroughs
  • Indie hacker blogs when he's procrastinating

Questions & answers

Adhrit Suthar’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Serpent By Tekunda (https://tekunda.com/serpent) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, the biggest obstacle stopping me from trying Serpent By Tekunda is our company's budget scrutiny. We're a small SaaS team, and every new tool needs a clear ROI. Although we're juggling GitHub and spreadsheets, justifying a new DevOps tool requires more than just 'it saves time'—it needs hard numbers. My team struggles with approval bottlenecks, and Serpent's promise of AI-assisted review and automated workflows looks appealing, but I need to see if it aligns with our current GitHub workflow. I’ve tried tools that promised simplicity but required heavy training—time we don’t have. Without a free trial or a clear cost projection, getting leadership on board feels risky. My guess is we’d try it if the monthly cost were under $100 for a small team, but we'd need a hands-on demo to be sure.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.