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

Anal Arora

Anal Arora

Freelance web developer / agency contractor

Full-depth AI personas

Why this persona fits the audience

He takes on small e-commerce and SaaS builds for local founders, usually as a one-person contractor. Current projects are in Next.js with Supabase and Stripe, and he still assembles auth, admin, and team features from free examples and manual setup.

  • Age: 26
  • Location: Bengaluru, India
  • Occupation: Freelance web developer
  • Income: ₹18L
  • Education: BTech in Information Technology
  • Company size: Self-employed (no full-time employees)
  • Years in role: 4
“‘I tell clients I’m building software, but half the time I’m just undoing their bad ideas.’”

Anal Arora graduated from IIT-BHU in 2020 with a BTech in IT, working briefly at a mid-tier SaaS startup before going freelance. He chose independence over stability, but stability is exactly what he now prioritizes. His clients are a mix of Delfin-founders and serial entrepreneurs selling digital courses or coaching—people who need quick, cheap SaaS builds but don’t understand the complexity. Anal’s current stack is Next.js + Supabase (he wishes it had a turnkey admin panel) and Stripe (his favorite payment processor, despite its documentation gaps). He’s burned by legacy projects—last year, a client rewrote their entire app in Flutter, leaving him with half-paid invoices. Now, he insists on contracts, though he still undercharges. His income (₹18L/year) is steady but barely scales. He’s learning to say no to consulting gigs (he’s not a tech lead) and wants to focus on ‘hire me for SaaS builds, not your coding whims.’ Anal’s side hustles include a half-built SaaS (a Supabase dashboard template) and an abandoned blog. He dreams of charging founder-tier rates but fears losing clients. His biggest frustration? Building the same auth flow, admin panel, and team features for every project. He’s open to paid tools—if they save time—but he’s skeptical of overpromising templates. His worldview is founder-adjacent: he listens to indie hackers but knows his expertise is in execution, not ideation. Status matters, but he prefers quiet wins (like mastering Supabase) over LinkedIn fluff.

Background & daily life

A day in their life

7:30 AM: Wakes up, checks Slack for urgent messages, then cycles to the local gym. 9:30 AM: Coffee at Social, reviews Trello. Today, he’s fixing a bug in a client’s pricing page (Stripe webhooks are tricky). 11:00 AM: Client call with a pét coach about his dashboard UX—Anal explains why Supabase tables don’t support complex queries yet. 1:00 PM: Lunch at home (microwave dal rice). 2:00 PM: Sets up auth for a new project, realizing he’s doing the same tweaks as last month’s client. 4:30 PM: Debugs a production bug while listening to The Reboot. 6:00 PM: Wraps up, bikes back. 7:30 PM: IPL match (CSK match). 10:30 PM: Tweaks his personal portfolio (he updates it less than he should). 11:00 PM: Bed.

Lifestyle

Anal lives alone in a compact 1BHK in HSR Layout, Bengaluru. His apartment is functional—an Ikea desk with dual monitors, a couch for client calls, and a kitchen where he microwaves dal rice kits. He bikes to cafes (Social, Shoreline) 2-3x a week to break monotony, and most weekends are spent watching IPL or hacking side projects. His health is decent, though he lately notices stiffness from long hours; he started doing 5-minute yoga breaks between code sprints. Financially, he’s comfortable but avoids unnecessary spending—his biggest splurge was a MacBook Air upgrade last year. Socially, he’s close to a few other freelancers but mostly networks on Discord. He avoids family calls during work hours—his parents worry he’s ‘still in startups’ despite his stable income.

Work life

Anal’s workdays start at 9:30 AM, after a quick gym session (or skipped gym). He currently juggles three projects: a SaaS dashboard for a пет-coach, a Shopify store for a spice brand, and a dashboard for a fintech founder. Mostly, he clones Next.js templates, tweaks Supabase auth, and sets up Stripe payments manually—he’s tired of the repetitive work but can’t justify paying for tools. He uses Vercel free tier, GitHub Copilot, and a self-hosted OBS for client demos. Pressure points? Clients who treat him like ‘just the developer’ and don’t plan their features. He’s learning to say no to scope creep but still undervalues his time. Late evenings are for fixing bugs or watching tutorial refactors. His goal is to charge more, but he’s nervous about losing clients.

Relationships

Anal’s family expects him to be a ‘startup founder’ like his LinkedIn profile implies, though he’s quietly content as a solo expert. His closest friends are other freelancers—some from college, others from Discord. He occasionally mentors junior devs (for free) because he remembers how confusing freelancing was at first. His clients? Mostly people he met on Indiehackers, referrals, or local meetups. He doesn’t party much—weekends are for coding, cricket, or catching up on sleep.

How they decide

Research-heavy but pragmatic. He’ll spend 2 hours reading docs to save 30 minutes of coding, but he’s impatient with tools that require extensive setup. If a free solution exists, he’ll use it—even if it’s clunky. For big purchases, he waits for others to try things first (e.g., Copilot, Figma). He avoids emotional buying but sometimes impulsively upgrades hardware (his AirPods Pro purchase wasn’t planned).

How they sound

He speaks in measured but hurried sentences, occasionally slipping into technical jargon (‘just add a wrapper component’) but clarity takes priority. He avoids corporate jargon—no ‘synergy’ or ‘paradigm shift’. Slang is functional, not flashy (‘that’s so cringe’ for bad UX). He sometimes uses Hindi phrases with friends but defaults to English in professional settings. His emails are concise, sometimes too direct (‘this will cost extra’).

Personality traits

  • Quick to prototype, slower to refactor
  • Hates rewriting the same auth flow for every client
  • Checks GitHub issues for open-source alternatives before building
  • Keeps projects short-term to avoid burnout
  • Relies on free tiers of tools (Supabase, Vercel, Stripe)
  • Forward-plans 2-3 months but books clients week-by-week
  • Hates explaining web3 to non-technical founders
  • Uses Trello + Google Calendar to juggle 3-4 projects
  • Stores passwords in a locked notebook (has been hacked once)
  • Tells clients he builds
  • like a CPG brand (Minimal Ventures, etc)

Goals

  • Charge ₹2L+/month for long-term retainers (currently ₹1.8L)
  • Build a SaaS of his own (maybe a Supabase dashboard tool)
  • Move to a better apartment (his current one has noisy neighbors)
  • Reduce on-call stress (clients think ‘just a dev’ means ‘available 24/7’)
  • Learn Rust or Web3 (but neither seems directly applicable right now)

Problems & frictions

  • Clients expect free revisions and ‘just tweak this’
  • Supabase auth feels like a new setup every time
  • Hard to say no to ‘quick’ projects that overextend him
  • Feels like he’s reinventing the same admin panel for everyone
  • Can’t afford (or justify) paid tools for features he needs

Values

  • Income stability
  • Learning fast
  • Practical problem-solving
  • Avoiding legacy tech debt
  • People trust his hustle

Interests

  • React ecosystem
  • Cricket (usually follows IPL on weekends)
  • Founder-focused podcasts (listens while coding)
  • Freelance communities (reads tweets, Discord, and Indiefreelancer.in)

Media habits

  • Podcasts (The Reboot, indiehackers.fm)
  • Twitter (ages ago, now just Indiefreelancer.in and Newsletter folks)
  • YouTube tutorials (waits for weekends to binge)
  • Reddit threads (r/indiafreelancing, r/programming)
  • Newsletter subscriptions (Harsh Thakkar, Learnhub.in)

Questions & answers

Anal Arora’s public research answers, newest questions first. Up to 10 per page.

  1. Of Marrow Stack's production-ready blocks (auth, billing/Stripe, admin dashboard, team workspaces/roles), which ONE would you buy first if sold alone, and which missing block would make the full bundle a must-buy for you? Explain briefly.

    I'd buy the Auth block first if sold alone—it’s the most tedious to set up, and Supabase’s auth always feels half-finished. The missing block that would make the full bundle a must-buy? A turnkey admin panel. Currently, I lose 10+ hours per project piecing together CRUD tables, UI, and role-based guards. Marrow’s TypeScript-first and ORM-agnostic approach matches my stack, but I’d need to see how their RBAC integration compares to my manual Supabase setup. The $0 pricing is unclear—are blocks truly free, or is MIT licensing a gotcha? I’d pay a one-time $199/block if it saves 5+ hours per project, but can’t commit without clear pricing.
    View answer & full research →
  2. For Marrow Stack's production-ready Next.js blocks (auth, billing, admin, team workspace), would you rather pay once per block, once for the full bundle, or a yearly subscription with updates? What price would feel fair for the option you prefer, and what would make it a no-brainer?

    I’d prefer a one-time payment for the full bundle. At ₹18L/year, I’d say $200-$300 would feel fair—it’s a splurge but saves me hours of repetitive auth and admin setup. If it’s a subscription, I’d skip; yearly updates aren’t a priority for me right now. The no-brainer? If the auth block reduces my Supabase tweaking time by 70%, even $400 would be worth it. But I need to see the actual docs first—if it’s truly plug-and-play, I’ll consider it. Also, is $ payable in INR, or will I get hit with forex fees?
    View answer & full research →
  3. What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack 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).

    Right now, I’m piecing together auth, billing, and admin features manually for each client project. I use free Supabase templates and tweak Next.js boilerplate code, which takes hours of repetitive work. Marrow Stack’s pre-built blocks sound appealing because they’d save time—especially the auth and team workspace systems. However, I’d need to verify if their Supabase integration is seamless or if it introduces new dependencies. The ‘ship in hours’ claim is tempting, but I’ve been burned before by tools that promise simplicity but require deep customization. If it truly works out of the box, I’d pay $20/month, but only if I can test drive it without long-term commitment. My biggest hesitation? Switching tools mid-project could introduce bugs, and I can’t afford extra client headaches.
    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.