When we started building Wenya, we kept getting the same advice: build a booking page. "Just make it clean and fast. Good UX, one link, done." We thought about it. And then we said no. Here's why — and what we built instead.

The problem everyone was describing wrong

There is no shortage of scheduling tools. Calendly, Cal.com, Acuity, Doodle, Microsoft Bookings — the category is crowded, well-funded, and well-designed. And yet, the problem persists. People still send WhatsApp messages that trail off without a confirmed time. Freelancers still lose warm conversations at the booking step. Group coordinators still manage 30-message threads to lock in a tennis court.

We spent a long time asking why. The tools were good. The tools were not working. The answer, eventually, was obvious: the tools were in the wrong place. Every scheduling product ever built asks you to leave the conversation to book the meeting. That exit is the problem. Not the destination. The exit itself.

The insight that became a patent

We asked a different question: what if scheduling never required you to leave the conversation at all? Not a bot. Not a reply button. A keyboard — living inside the same keyboard tray you already use, on every chat app you already have.

You tap Wenya. You pick a time. It generates a structured scheduling proposal, directly inside your message, inside WhatsApp or iMessage or Telegram. The other person confirms in one tap. The meeting is booked. The conversation continues. No app switch. No form. No link. No context loss.

That mechanism — scheduling via a keyboard layer, inside any chat interface — is what we filed for a US Utility Patent on. Not because we wanted legal complexity. Because we genuinely believe it's a new category, and first-mover IP protection matters when you're sitting at the infrastructure layer.

Why infrastructure, not app

We describe Wenya as scheduling infrastructure, not a scheduling app. The distinction matters. Apps compete for attention. You download them, open them, choose to use them. Infrastructure is ambient — it's just there, part of the environment, working when you need it.

Autocorrect doesn't ask you to open a new app. Predictive text doesn't send you a link. They're inside the keyboard because that's where text happens. Scheduling, for most people, happens in chat. So that's where Wenya lives. The ambition is to become the scheduling layer that other tools route through — not to compete with Calendly or Google Calendar, but to sit beneath them, in the place where the conversation actually starts.