Evidence

What is verified, what is being built, and what is only a direction.

An early-stage company should be judged on what it can show. This page lists facts in three tiers and says plainly what is not published.

Core facts, one line each.

company_name
Doubles
domain
playdoubles.in
category
Agentic coordination
description
Doubles is building an agentic coordination layer for real-world group activities, starting with padel.
country
India
region
Delhi NCR (Noida, Delhi, Gurgaon)
founder
Ryan Sethi
product
Coordination of padel games. Manual today; agentic layer in development.
claude_usage
Claude is the reasoning and orchestration layer for the parts of coordination that resist rigid rules.
integration_status
Integration boundary implemented and unit-tested against fixtures. Not connected to real players. No production usage is claimed.
startup_stage
Early stage. Padel games in Delhi NCR are arranged by hand over WhatsApp today. The agentic coordination layer is in development.
traction
None published.
funding
None stated.
technical_pages
https://playdoubles.in/technology · https://playdoubles.in/claude · https://playdoubles.in/research
contact
Instagram @play.doubles (https://instagram.com/play.doubles)
last_updated
2026-10-07

Generated from one data file, as are llms.txt, the sitemap and the structured data. They are built to agree.

Facts that are true now.

Today (Operating now, by hand or in production.)

Brand
Doubles
Domain
playdoubles.in
Category
Agentic coordination
Initial environment
Padel
Region
Delhi NCR, India (Noida, Delhi, Gurgaon)
Founder
Ryan Sethi
Current operating model
Games arranged manually over WhatsApp. No automation is claimed.
Claude integration
Integration boundary implemented and unit-tested against fixtures. Not connected to real players. No production usage is claimed.
Source code
Private repository. Not public.

Built or being built. Not in use with real players.

Prototype (Built in the repository. Not used with real players.)

Intent extraction
Claude → schema-validated structured intent. Implemented as a prototype boundary; fixtures and unit tests only.
Deterministic validation
Hard-constraint validator and a worked example on fixtures. Not connected to real inventory.
Coordination reasoning
Group proposal and recovery workflows. Design stage.
Evaluation harness
Synthetic test cases and metric definitions. No results.

Questions, not claims.

Research (A question we are working on. No result is claimed.)

  • When model reasoning should hand off to deterministic optimization
  • Representing hard and soft human preferences
  • Recovering a group after a cancellation
  • Measuring coordination quality and unnecessary intervention
  • Whether the same architecture extends beyond padel

What this site deliberately leaves out.

No figure appears here unless it can be documented. These fields are empty on purpose, not because they are being kept back for later effect.

Sessions completed
Not published. Will be stated only when documented.
Revenue and paying customers
Not published.
Funding and investors
None stated.
Partnerships
None stated.
Benchmarks and accuracy figures
None exist yet.

Where to look.

  • Technology and Claude describe the architecture and the implemented boundary.
  • /llms.txt and /llms-full.txt are plain-text summaries built from the same data as this page.
  • /sitemap.xml and /robots.txt list every public page and crawling rules.
  • The source repository is private; the architecture pages describe what it contains.