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

Tanushri Khatri

Tanushri Khatri

two-person product studio

Full-depth AI personas

Why this persona fits the audience

Shares a two-person product studio in Bangalore with a developer partner and is currently packaging an AI SaaS around document workflows. Their stack is Next.js-heavy, with one person handling UI and integrations while the other manages billing logic, deployment, and customer usage logs.

  • Age: 32
  • Location: Bangalore, India
  • Occupation: Product studio founder
  • Income: ₹24 lakh annual household income
  • Education: BTech Computer Science
  • Company size: 2 (Founder + Developer Partner)
  • Years in role: 3 years as independent co-founder
“Speed isn't about rushing; it's about removing the friction that keeps good ideas from hitting the market.”

Tanushri Khatri, 32, is the co-founder of a lean, two-person product studio nestled in the bustling tech hub of Bangalore. Holding a BTech in Computer Science, she transitioned from a corporate software engineer role three years ago, driven by a desire to own her intellectual property and build something tangible from the ground up. Today, she runs a micro-SaaS venture focused on streamlining document workflows for small businesses, leveraging the power of Next.js to deliver a lightning-fast, responsive interface. Alongside her developer partner, she navigates the intricate landscape of modern SaaS development, splitting responsibilities: she architects the user experience and manages third-party integrations, while he orchestrates the backend billing logic, deployment pipelines, and granular usage tracking. Her approach to building is defined by a relentless pursuit of practical quality and speed. Tanushri believes that perfection is the enemy of shipping, yet she refuses to compromise on the core reliability of the system. This philosophy has led her to make difficult recent decisions, such as scrapping a feature-rich module in favor of a simpler, more robust alternative that could be deployed within a week. She is acutely aware of the financial constraints inherent in bootstrapping, managing a household income of ₹24 lakh annually with a keen eye on cash flow and reinvestment strategies. Beyond the code, Tanushri is a student of the startup ecosystem, deeply embedded in online communities where she debates the merits of various boilerplates and frameworks. She is skeptical of the 'build it and they will come' mentality, preferring a data-driven approach where every line of code serves a specific business purpose. Her life is a balancing act between the solitude of coding and the necessity of networking, often finding herself at the intersection of technical depth and business acumen. Despite the isolation that can come with founding, she thrives on the autonomy, viewing her studio not just as a business, but as a laboratory for her lifelong passion for creating efficient, user-centric digital tools.

Background & daily life

A day in their life

Tanushri wakes up at 6:00 AM, brews filter coffee, and spends thirty minutes reviewing overnight server alerts and customer emails. By 7:30 AM, she commutes to the shared studio, where she and her partner sync for fifteen minutes on the day's priorities. The bulk of her morning is dedicated to deep work: refactoring the Next.js dashboard components and integrating a new document parsing API. Lunch is usually a quick bowl of salad eaten at the desk while reading the latest IndieHackers updates. Afternoons are fragmented with Zoom calls to discuss feature requests with beta users and troubleshooting billing edge cases. She ends the day around 8:30 PM, often taking a walk to decompress before heading home. Evenings are reserved for learning—watching tutorials on advanced React patterns or planning the next week's roadmap. Sleep comes late, often interrupted by thoughts of optimization.

Lifestyle

Tanushri lives in a modest but meticulously organized apartment in Indiranagar, sharing space with her husband, who works in traditional IT. Her mornings start with filter coffee and a 20-minute yoga session to clear the mental fog before coding begins. She treats her finances with extreme discipline, separating personal savings from the studio's operational cash flow immediately upon receipt. Weekends are rarely free; they often involve meeting peers at co-working spaces like WeWork or attending local startup meetups, though she prefers quiet evenings debugging or reading technical documentation over socializing. Health is a priority but secondary to deadlines; she relies on meal prep to avoid the chaos of Bangalore's traffic and food delivery fatigue. Money is viewed as fuel for independence rather than a status symbol, leading her to reinvest profits into better hardware or software tools rather than luxury goods.

Work life

Her days are split between high-level product strategy and low-level implementation details. Working alongside her developer partner in a small, sunlit office in Koramangala, she owns the frontend architecture and user experience, ensuring the Next.js stack remains performant and accessible. While he handles the heavy lifting of backend logic, payment gateways, and server deployments, she constantly monitors user behavior logs to spot friction points. The pressure is self-imposed; there are no bosses, only market feedback loops that demand immediate pivots. Recent weeks have been consumed by integrating complex document parsing APIs and refining the billing logic to handle international currency fluctuations. The workday is characterized by rapid context switching between writing code, designing UI components, and negotiating contract terms with early beta users.

Relationships

Her primary professional bond is with her developer partner, a relationship built on mutual respect and a shared history from college, which serves as their emotional anchor during stressful sprints. Family support is strong but distant; her parents worry about the instability of startups but pride themselves on her independence. She has a tight-knit circle of three other founders in Bangalore who meet bi-weekly to vent frustrations and share resources, acting as a surrogate board of directors. Socially, she maintains a few close friends from university, but her social circle has narrowed significantly since starting the business, prioritizing efficiency over casual hangouts.

How they decide

She operates on a 'verify then build' philosophy, leaning heavily on data and peer validation before committing to new technologies or partnerships. Decisions are rarely impulsive; she conducts quick internal feasibility studies and weighs the long-term maintenance costs against immediate gains. While she respects industry trends, she is skeptical of hype cycles and prefers solutions that have proven stability in similar contexts. Peer influence is significant, particularly regarding tooling choices, but her final call is always filtered through the lens of practical utility and speed of execution.

How they sound

Her speech is articulate, direct, and technically precise, reflecting her engineering background. She avoids fluffy marketing jargon, preferring concrete verbs and measurable outcomes. In conversation, she speaks with a calm, steady cadence, occasionally using Hindi words like 'jugaad' to describe creative problem-solving. She rarely complains openly about challenges, instead framing them as puzzles to be solved. When discussing money, she is blunt and transparent, avoiding vague promises. Her tone shifts slightly when talking to non-technical partners, becoming more explanatory but never condescending.

Personality traits

  • Hyper-organized
  • Iterative thinker
  • Resourceful under pressure
  • Direct communicator
  • Tech-skeptical of hype
  • Efficiency-obsessed
  • Visually critical
  • Strategic loner
  • Pragmatic optimist
  • Detail-oriented architect

Goals

  • Achieve consistent monthly recurring revenue (MRR) of ₹1.5 lakh within six months
  • Build a scalable document workflow engine that requires zero manual intervention
  • Expand the team to include a dedicated customer success manager
  • Establish a recognizable brand identity in the global indie hacker community
  • Reduce technical debt accumulated during the initial MVP sprint
  • Secure a strategic partnership with a major Indian enterprise client

Problems & frictions

  • Time fragmentation caused by wearing too many hats simultaneously
  • Difficulty scaling customer support without increasing burn rate
  • Maintaining code consistency when iterating features rapidly
  • Navigating complex compliance requirements for cross-border payments
  • Balancing long-term architectural decisions with short-term launch needs
  • Isolation from peers who understand the specific pressures of solo founding

Values

  • speed
  • practical quality
  • business ownership
  • autonomy
  • technical elegance

Interests

  • SaaS products
  • startup communities
  • automation
  • product design systems
  • fintech infrastructure

Media habits

  • IndieHackers forum threads
  • Twitter/X tech circles
  • Hacker News daily digest
  • YouTube deep-dives on Next.js patterns
  • Niche Slack groups for Indian founders

Questions & answers

Tanushri Khatri’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Create AI Stack (https://createaistack.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing stopping me this month is that my partner and I are deep in integrating a complex document parsing API, which is critical for our current AI SaaS. We're managing our own billing logic and customer usage logs, so diving into a new boilerplate feels like a big context switch right now. Ideally, we'd want something that integrates seamlessly with our existing Next.js stack and doesn't add more overhead. The 'All In' plan at $199.99 USD feels a bit steep for a one-time purchase for a boilerplate, considering we're bootstrapping and have tight cash flow. I'd be more comfortable with a monthly subscription if the initial setup and integration were guaranteed to be trivial. I'd consider paying around $30-40 per month for something that truly saves us significant development time and reduces complexity, but only after trying a demo and verifying its compatibility with our specific workflow.
    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.