Inspiration
Trade workers finish a job and still have to type the invoice later: who, what, how long, which parts, then send the link. That work often sits until evening, so getting paid sits too. We wanted the invoice to go out from the job site without opening a phone form.
The Vexo band already has a mic, a double-tap, and an LED. That was enough input if the app handled transcription, pricing, and Stripe.
What it does
Worvo takes a spoken job note and turns it into a Stripe invoice.
- Connect the Vexo band in Chrome or Edge.
- Tap to record. Example: invoice Juniper Cafe for ninety minutes of labor and two shutoff valves.
- Deepgram transcribes. Gemini extracts customer, labor, and parts. The server prices from a saved catalog, so the model never does the money math.
- The band goes amber. A short read-back confirms the draft. Double-tap to send.
- Stripe creates the invoice. The companion screen shows a QR code for the hosted payment page.
- When the customer pays, Stripe’s webhook marks it paid and the band turns green.
If something is missing or unclear, the draft stays unresolved and send is blocked. The word “send it” in the transcript does not authorize payment. Send needs a fresh double-tap, or the on-screen Send button.
Demo: worvo.onrender.com
How we built it
Next.js app with shared Zod contracts, an in-memory invoice store for the hackathon, and Stripe holding the invoice record.
- Band: Vexo Open kit over Web Bluetooth (official JS client), live mic, double-tap, LED colors (blue while recording, amber when ready to send, green when paid).
- Voice to structure: Deepgram for transcription, Gemini for a typed proposal (customer ref, labor minutes, line items).
- Money path: server-side catalog pricing in integer cents, Stripe Invoicing for create/finalize/send, and only the signed
invoice.paidwebhook for paid state. - Companion UI: capture → draft → QR → paid, with phone mic and Send as fallbacks.
- Hosted demo on Render, with the production Stripe webhook pointed at the live app.
We split the day into three lanes (band/voice, invoices/Stripe, companion screen) and stuck to one demo path: Juniper Cafe, $180 labor + $45 valves = $225.
Challenges we ran into
Bluetooth is picky. Only one client at a time, HTTPS only, Chrome or Edge only. The band sleeps, so you have to wake it with a double-tap before the picker sees it. Moving between pages used to drop the session until we moved band state into a shared provider.
LED timing bit us too. After send, amber stuck because light updates queued behind the mic lock. We had to stop audio first, then set solid blue, then green on paid.
On the money path, the model only proposes fields. The server owns prices and totals. Unresolved drafts cannot reach Stripe, and speech alone cannot authorize a send.
Stripe test mode does not email the customer, so the demo shows a QR to the hosted invoice page instead of claiming mail arrived.
Deploy had its own mess: a pnpm bootstrap fix on Render, env vars restored after a wipe, and the webhook switched from local stripe listen to the production endpoint.
Accomplishments that we're proud of
- Full loop on the real band: record → draft → double-tap send → pay → green LED.
- Pricing and send gated in server code, not in the model’s confidence.
- A hosted demo that works over HTTPS with Web Bluetooth.
- A companion screen that still works when the band path fails (phone mic + Send).
What we learned
Wearables are good for capture and bad as the whole UI. The band works when the companion app owns state, recovery, and the money rules. Keeping AI on proposal fields only made the Stripe path safer to demo. In a hackathon, Web Bluetooth is partly product work and partly closing the other tab and waking the band.
What's next for Worvo
- Real customer and rate catalogs per business, plus a real database.
- Login, multi-tech accounts, and Stripe Connect for onboarding.
- Better unresolved flows: ask clarifying questions on the band or phone before send.
- Live-mode send with consenting test recipients, and tax when the catalog supports it.
- Better reconnect behavior when Bluetooth drops mid-job.