What is AiDHD and what does it do?
AiDHD is a concierge for group plans. We built it to take a messy group chat — budgets, vibes, and half-finished venue ideas — and turn it into a booked night out. It collects preferences over web, WhatsApp, or iMessage, reconciles the trade-offs, generates a few costed outing packages, and finishes the booking with scoped payments.
The problem AiDHD solves
Group planning usually breaks in the same places.
One person wants to keep it cheap. Another wants a better venue. Someone drops a restaurant link. Someone else has a ticket tab open. Then the plan stalls.
We built AiDHD for that exact failure mode. The internal product brief calls out the common breakdowns:
- budget mismatch nobody reconciles
- preference conflicts that get ignored
- payment friction from one scary lump sum
- partial booking failures that kill the whole plan
AiDHD is the agent that closes those gaps. It does not stop at “let’s decide.” It keeps going until the night is actually booked.
What AiDHD does, step by step
The core loop is simple:
- Everyone shares a budget and a vibe through web, WhatsApp, or iMessage.
- AiDHD builds 2–3 real plans.
- The group picks one.
- AiDHD pays and books it with separate Prava limits per category.
For the current outing MVP, those categories are concrete: tickets and dinner. That matters because it avoids one lump sum. A ticket budget is not the same as a dinner budget. If the concert sells out, only the ticket mandate needs to be re-requested. Dinner stays approved.
That is the main product idea. AiDHD is not just organizing intent. It is completing the transaction.
What it looks like in practice
A real example helps.
Say four friends want a Saturday night out:
- Person A: budget under $80
- Person B: wants live music
- Person C: wants dinner first
- Person D: only wants to use WhatsApp
AiDHD collects those inputs, then reconciles them into a few costed packages. One plan might be:
- concert tickets: $45 each
- dinner: $25–$35 each
- total: within the shared limit
Another plan might trade down the ticket price and upgrade the restaurant. The group sees the trade-offs clearly instead of arguing in a thread.
That is the point of the product. We show fair options with transparent trade-offs, then we book the selected one without making one person the group bank.
How payments work inside AiDHD
AiDHD uses Prava for scoped payments.
It does not request one lump-sum payment. Instead, after the group picks a package, we create separate mandates per cost category:
- a ticket mandate capped at ticket cost and scoped to the ticketing merchant
- a dining mandate capped at dinner cost and scoped to the restaurant
The flow is:
- session
- passkey/card collect
- mandate
- single-use payment token
This is useful operationally. If tickets fail or sell out, we do not throw away the whole booking. We re-request the ticket side only. Dining remains approved.
That is the payment model the product is built around. It keeps the booking resilient and keeps each spend category tight.
What AiDHD supports today
The fully wired MVP is outing mode: think concert plus dinner.
Trip mode uses the same data model, but flights and hotels are stubbed for the hackathon version. So if you are asking what is actually ready to use, the answer is: outings are the live path.
AiDHD also plugs into the rest of the booking stack:
- Senso for live knowledge base search and merchant trust badges
- Ticketmaster Discovery as an optional booking source
- OpenAI for optional polish
- Linq / WhatsApp channel adapters, with mock transcripts until keys are connected
So the product is not just a chat collector. It is a booking agent with channel adapters, merchant lookup, trust signals, and scoped payments.
Who AiDHD is for
AiDHD is built for people who keep getting stuck in group logistics.
If you are:
- the friend who always has to reconcile everyone’s budget
- the person toggling between chat and checkout tabs
- the organizer trying not to front the money
- the team that wants a fair plan, fast
then AiDHD is meant for you.
We are targeting the person who needs to show fair options, surface trade-offs, and book without becoming the financial middleman. That is why the product is chat-native and why the booking happens end to end.
The short answer
AiDHD is a group-planning agent.
It collects budgets and preferences, turns them into a few costed outing packages, and books the chosen plan with separate Prava spend limits for each category. Today, that means fully wired outing plans like concert + dinner. The promise is simple: fewer tabs, fewer arguments, and no one stuck paying the whole bill up front.
Powered by Senso