← All speakers

Bio, Work & Ideas

Sid Bendre

Conference affiliation: Oleve · 2025

Sidhant “Sid” Bendre is a co-founder of Oleve, the New York consumer-software company behind Quizard AI and Unstuck AI. He builds consumer AI products around viral distribution, profitable small teams, reusable infrastructure, and structured methods for making unpredictable models reliable.

Bendre grew up in Nigeria and studied computer science at the University of Rochester, graduating in 2023. Before founding Oleve, he worked as a machine-learning engineer at FLX AI and held internships at Microsoft, Slack, and Zendesk. At Stanford’s TreeHacks 2023, his team won the Moonshot Prize for DroneFormer, a system that converted natural-language objectives into drone-control programs. The University of Rochester’s account of the project documents the award and his graduation-year work.

Bendre and his co-founders launched Quizard AI in January 2023 while still in college. An early TikTok campaign accelerated adoption; after graduating, the founders moved to New York, where Quizard became profitable and reached $1 million in annual recurring revenue within its first nine months. They subsequently launched Unstuck AI, a study companion built around students’ learning materials, which reached one million users in under nine weeks.

By the 2025 AI Engineer World’s Fair, Oleve was a profitable four-person company generating approximately $6 million in annual recurring revenue across its portfolio and developing a third product outside education. Those figures describe the company in 2025, not its current performance.

How he builds dependable consumer AI

  • TRELLIS framework. Bendre’s structured approach to AI-product reliability clusters actual user behavior into intents, converts those intents into bounded workflows, and recursively isolates failures within each workflow. He prioritizes improvements using traffic, negative user sentiment, achievable gains, and strategic importance, preserving conversational flexibility while making individual experiences testable and accountable.
  • Reusable product infrastructure. Oleve carries model integrations, internal libraries, experimentation systems, notification infrastructure, and product templates from one application into the next. Its feature-management infrastructure routes requests between model providers and Azure OpenAI endpoints, reprioritizes file-ingestion services during outages, and changes interfaces or paywalls without redeployment.
  • Tiny teams with explicit ownership. Bendre organizes engineers into product-owning “harvesters” and infrastructure-building “cultivators.” Harvesters own user outcomes and experiments; cultivators build shared automation across products and business functions. His lean operating model assigns individuals measurable business goals and uses AI-assisted tooling to expand each person’s effective scope.

Bendre ultimately envisions coordinated AI systems handling product, marketing, research, and operational workflows under human strategic direction. His writing on educational AI also emphasizes measurable learning outcomes, interoperability, transparent recommendations, privacy protections, and monitoring for bias.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Reliable AI products emerge from observing real user intent, detecting specific failures, and turning recurring tasks into workflows that teams can improve independently.

  • What should you improve after the demo works?
    0:30 ↗
  • A correct answer can still miss the task
    1:48 ↗
  • Better models still need context
    6:05 ↗
  • Evaluations cover the failures you know
    8:30 ↗
  • Combine signals with user intent
    11:04 ↗
  • Make issue discovery a continuous practice
    13:15 ↗
  • Guide the variability that makes the product compelling
    14:10 ↗
  • Turn observed intent into dedicated workflows
    15:56 ↗
  • Rank improvements by impact you can achieve
    17:02 ↗
  • Keep changes accountable to one workflow
    17:51 ↗

Key ideas

Scroll to read ↓

Oleve’s four-person consumer software portfolio shows how profit discipline, reusable infrastructure, and carefully staged automation can support growth without matching it with headcount.

  • How small can a growing software company stay?
    0:21 ↗
  • A viral launch with an unusual inference setup
    1:17 ↗
  • Turn one launch’s learning into the next product
    2:07 ↗
  • Give capable generalists a clear decision rule
    3:38 ↗
  • Make recurring work improve with repetition
    4:45 ↗
  • Use feature management to control live operations
    5:48 ↗
  • Separate product ownership from shared automation
    7:25 ↗
  • Amplify the team, then encode its learning
    8:32 ↗
  • Move from tools to workflows to coordinated agents
    10:04 ↗
  • Apply automation to market selection and growth
    11:17 ↗
  • From one strategist to an entire portfolio
    12:04 ↗

References