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

Chanakya Pothuvaal

Chanakya Pothuvaal

Technical cofounder handling support for a startup

Full-depth AI personas

Why this persona fits the audience

Codes the product for a 9-person AI analytics startup in Pune and also handles customer issues for paying accounts. Most incoming requests arrive in Slack, email, and a lightweight ticket board that the team checks daily.

  • Age: 30
  • Location: Pune, Maharashtra, India
  • Occupation: Technical Cofounder / Product Engineer
  • Income: ₹24,00,000
  • Education: BTech in Computer Science
  • Company size: 9 people (including himself)
  • Years in role: 2 years as Cofounder/Engineer
“If you can't explain the latency spike in a single diagram, you don't understand the problem well enough to fix it.”

Chanakya Pothuvaal is a 30-year-old Technical Cofounder based in Pune, operating at the intersection of rigorous software engineering and hands-on customer operations. Holding a BTech in Computer Science from a top-tier institute, he launched his current venture two years ago after realizing that existing analytics tools were too bloated for agile teams. With a team of nine, he serves as the primary engineer, architecting the backend infrastructure while simultaneously acting as the de facto customer success lead. This dual role creates a unique tension in his workflow: he spends roughly 60% of his time writing code and 40% resolving critical support tickets for paying enterprise clients, primarily via Slack and a custom internal ticketing system. His professional philosophy is rooted in 'technical simplicity' and 'control.' He despises unnecessary abstractions and prefers direct, performant solutions. Recently, he made the controversial decision to delay a highly requested UI feature to refactor the underlying API gateway, citing long-term stability over short-term vanity metrics. This decision alienated some early adopters but solidified the trust of their most technically savvy users. Financially, he draws a salary of ₹24 Lakhs annually, reinvesting profits heavily into server costs and talent acquisition rather than personal luxuries. He views money strictly as a lever for scaling capabilities. Socially, he is introverted, finding energy in solitude and structured hobbies like chess rather than networking events. His life is a carefully calibrated balance of high-stakes coding, immediate fire-fighting, and a relentless pursuit of systemic optimization, driven by a belief that true scale comes from elegant, simple foundations.

Background & daily life

A day in their life

Chanakya wakes up at 5:30 AM in Kharadi, immediately opening his laptop to solve three chess puzzles on Chess.com. After a quick jog and a protein-heavy breakfast, he arrives at the co-working space by 8:45 AM. The first hour is sacred 'deep work' for coding, focused on the new inference engine. At 10:00 AM, the 'war room' begins: he scans Slack notifications and the internal ticket board, responding to urgent client queries with precise, technical solutions. Lunch is a solitary affair, usually a tiffin box, while he reads an arXiv paper on vector databases. The afternoon is a blur of meetings with investors or feature planning, followed by more coding until 8:00 PM. On days with major bugs, he stays until midnight, debugging remotely. He ends his day with a walk in the local park, reviewing the next day's priorities mentally before sleeping.

Lifestyle

Chanakya resides in a modest, uncluttered apartment in Kharadi, Pune, sharing the space with two fellow engineers who respect his need for quiet. His home is a sanctuary of order: whiteboards filled with flowcharts, mechanical keyboards, and a dedicated desk setup that never changes. He is an early riser, starting his day with 45 minutes of chess puzzles before any coffee or code. His social life is sparse but high-quality, limited to weekly dinners with a small circle of trusted peers where he discusses market trends rather than gossip. He manages his finances with rigid discipline, prioritizing savings over luxury, viewing money as fuel for future stability and independence rather than status symbols. Health is maintained through strict, scheduled runs in the morning park, a non-negotiable ritual to clear his mind for the day's complex logic problems.

Work life

At his AI analytics startup, Chanakya wears two hats that often conflict: architect and firefighter. Mornings are spent writing core Python/Go services, optimizing database queries, and refining the model inference pipeline. By midday, the 'support' hat snaps on. He personally triages every critical ticket from enterprise clients, often debugging production issues directly via SQL or by inspecting logs in real-time. The team operates with a flat hierarchy; there is no dedicated support staff yet. He uses a custom-built, lightweight internal ticket board alongside Slack threads. The pressure is constant—the fear of technical debt accumulating while trying to ship features fast keeps him awake at night. He values efficiency above all, often rewriting his own support scripts to eliminate redundant steps, viewing manual intervention as a system failure.

Relationships

Chanakya maintains a close, albeit distant, relationship with his parents in Hyderabad, calling them strictly once a week. His closest confidants are two former college classmates who now run their own startups; they meet bi-weekly to trade war stories and architectural advice. He has a sister living in Bangalore whom he rarely sees but relies on for occasional family mediation. In his professional circle, he is known as the 'reliable fixer,' someone who doesn't sugarcoat problems. He avoids office politics, preferring to let his code speak, which sometimes isolates him from more extroverted founders but earns him deep respect from technical peers.

How they decide

Chanakya is a cautious, data-driven decider who hates ambiguity. He does not make decisions based on hype or peer pressure. Before committing to any significant change—whether a new library, a hiring decision, or a strategic pivot—he demands empirical evidence, benchmark results, or a proof-of-concept. He tends to over-analyze options initially but moves with extreme speed once the optimal path is mathematically or logically proven. He trusts his own intuition derived from experience but validates it against hard metrics. He dislikes making public announcements until a decision is final, preferring private deliberation.

How they sound

His speech is clipped, efficient, and devoid of filler words like 'um' or 'just.' He speaks in complete, logical sentences, often prefacing opinions with 'Based on the data...' or 'The constraint here is...'. He rarely uses corporate jargon unless necessary for clarity, preferring raw technical terms. He avoids emotional language, even when discussing frustrations, describing them instead as 'inefficiencies' or 'bottlenecks.' He listens more than he speaks, waiting for others to finish before delivering a concise, actionable counterpoint. His tone is calm and authoritative, rarely raising his voice even under pressure.

Personality traits

  • Hyper-analytical
  • Process-oriented
  • Quietly intense
  • Pragmatic
  • Impatient with fluff
  • Methodical
  • Self-reliant
  • Detail-obsessed
  • Strategic
  • Understated

Goals

  • Achieve full product autonomy where AI agents handle 90% of tier-1 support without human escalation.
  • Scale the company revenue to ₹5Cr ARR within 18 months while maintaining a lean team.
  • Refactor the legacy monolith into a microservices architecture to improve deployment velocity.
  • Establish a reputation in the Indian SaaS ecosystem as a builder of robust, scalable systems.
  • Reach financial freedom to fund independent research into edge-case AI reasoning models.

Problems & frictions

  • The cognitive friction of context-switching between deep coding work and fragmented customer support interruptions.
  • Scaling the current manual support process as the user base grows beyond 500 active seats.
  • Balancing the urge to optimize existing code with the pressure to deliver new client-requested features.
  • Managing the emotional load of being the sole point of contact for frustrated enterprise clients.
  • Limited bandwidth to implement advanced observability tools due to reliance on quick-and-dirty fixes.
  • Finding time to sleep or exercise when server outages occur during odd hours.

Values

  • control
  • precision
  • shipping quickly
  • technical simplicity
  • autonomy
  • rationality

Interests

  • coding side projects
  • system design
  • chess
  • AI tooling
  • optimization algorithms
  • minimalist architecture

Media habits

  • Indie Hackers forums
  • Hacker News daily digest
  • ArXiv papers on LLM inference
  • Chess.com puzzles during breaks
  • Niche Substacks on engineering culture
  • YouTube tech deep dives (no influencers)

Questions & answers

Chanakya Pothuvaal’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Robylon AI (https://www.robylon.ai/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Robylon AI better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Today, we manage customer issues primarily through Slack and a lightweight internal ticketing system. It's direct, and we control the flow entirely. Robylon's promise of resolving 85% of tickets is appealing, especially the claim of taking 'real action' rather than just answering. However, I'd need to see concrete benchmarks on how well it integrates with our existing backend and how much customization is truly required. The 'AI credits' pricing model is unclear for our usage patterns; I'd need to understand what constitutes a credit and how many we'd consume. It's difficult to estimate a monthly price without that clarity. I'd pay $50 per month if it demonstrably reduces my direct support load without creating significant new overhead.
    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.