Akia Consulting
Field notes for owners and operators
Zero messages to book a meeting
It used to take Nenad four days and five messages to land on a meeting time, and the lead still showed up at the wrong hour. Here's what changed when he started sending a link instead of a reply.
In short
- A manual back-and-forth to book one meeting routinely costs four or more messages and several days, and every extra step is a place a lead can go cold or misread a time zone.
- Ritmo replaces that exchange with one shareable link: the invitee sees real availability already checked against Google Calendar, converted to their own time zone, no math or guessing required.
- Booking, rescheduling, and cancellation all happen without either side touching a calendar by hand, and Google Calendar stays in sync automatically in both directions.
- Paid event types run through Stripe Checkout with webhook-confirmed payment status and automatic refunds on cancellation. This runs in test mode today; live payment collection is a separate, scoped step, not a flag to flip.
- The same booking link speaks English or Serbian Latin to each visitor automatically, dashboard, public page, and every confirmation email included, with nothing extra to configure per lead.
Nenad runs a small consulting practice. Three people, a full calendar, and - until recently - a booking process held together entirely by memory and goodwill.
Here's what booking a call with him actually looked like.
A lead fills out his contact form. He sees it Tuesday morning, between two client calls. He replies: "Happy to chat - does Thursday afternoon work?" She writes back: "Thursday's tough, what about Friday morning?" He checks his calendar. Friday morning has a client session he forgot to block off. He counter-offers Friday at 2pm. She's in a different time zone. She thinks he means 2pm her time. He meant his.
Four days and five messages after the first contact, they finally land on a time. She shows up at the wrong hour. He's mid-call with someone else. She leaves. He never hears from her again.
What one booking used to cost
Multiply that by every lead, every referral, every 'let's find 30 minutes.' The thing eating a consultant's week usually isn't the work. It's the scheduling around the work.
A colleague sends him a link instead of a reply. No email back-and-forth. No "does this work for you." Just a page: pick a time, add your details, done. Confirmed instantly, on both calendars, in both time zones, correctly. He asks what it is. The answer is Ritmo.
What Thursday looks like now
A new lead lands in his inbox. Instead of typing "when works for you," he pastes one link. The lead opens it and sees Nenad's actual availability - not a guess, not a stale calendar screenshot, his real open slots, already checked against his Google Calendar so nothing double-books. The times are shown in her time zone automatically. She doesn't do the math. She doesn't need to.
She picks Thursday at 10am, answers one quick question he added to the form - "What are you hoping to get out of this call?" - and confirms. She gets an email immediately. So does he. Both calendars update themselves.
The old way
- A reply chain to find a time both sides can actually do
- Manual time-zone math, done wrong at least once
- A calendar event somebody has to remember to create
- A no-show risk baked into every step of the exchange
With a Ritmo link
- One link shows real, already-checked availability
- Time zone converted automatically for the person booking
- Google Calendar event created the moment it's confirmed
- Confirmation email sent to both sides immediately, no manual step
Thursday at 10am, she shows up. He's ready, and he already knows what she wants to talk about, because her answer was sitting in his dashboard since Tuesday.
When plans change
Wednesday evening, something comes up and she needs to move the call. She doesn't email him. She clicks the link from her own confirmation email, picks a new time, and it's done. He gets notified. His calendar updates. He never has to touch a keyboard.
If the meeting had come with a price tag - a paid consultation, a strategy session - the same thing happens automatically on cancellation: she's refunded without either of them chasing it down. That part runs through Stripe, with the payment and the refund both confirmed by webhook rather than a hope that the browser redirect worked. It's worth being precise here: Ritmo's payment flow is fully built and live-tested, but it currently runs in test mode only. Turning on real transactions is its own scoped, audited step, not a setting anyone flips by accident.
The part Nenad didn't expect
He works with clients across Serbia and abroad. Some of his leads are far more comfortable booking in Serbian than in English. With most tools, that means a second, clunkier version of the process, or none at all.
With Ritmo, it's the same link. It's the same page. It just speaks to each visitor in their own language - the confirmation email, the reschedule page, all of it - with nothing extra for him to set up per lead. He flips a toggle once for his own dashboard; his leads never even see a toggle, it just already matches them.
A booking link that reflects the calendar you actually have
Google Calendar free/busy is checked before a slot is ever offered publicly, so nothing gets double-booked on Nenad's side.
Zero-math time zones
Every visitor sees availability converted to their own local time automatically, on both the booking page and the confirmation email.
Self-service changes
A secure link in every confirmation email lets the invitee reschedule or cancel their own booking, no account and no email required.
One workspace, your own brand
Accent color, logo, and profile image carry across the public booking page, so it reads as Nenad's practice, not a third-party widget.
Why this works
None of this is about doing something new. It's about removing the five steps that used to sit between someone wanting to talk to Nenad and actually talking to him. Every one of those steps was a place a lead could go cold, misread a time zone, or just quietly give up and book with someone else who made it easier.
Ritmo doesn't add a feature to Nenad's business. It removes the friction that was costing him leads before the first real conversation even happened.
That's the whole pitch: find your rhythm, get booked - and let the calendar handle the part that was never really about the work anyway. Ritmo is real and shipped, running in production today. It isn't a shared multi-tenant product yet - each client gets their own dedicated, isolated deployment - and payments stay in test mode until turning them on becomes its own scoped project. Both of those are deliberate choices, not gaps waiting to be discovered later.
FAQ
Common questions, answered directly- What is Ritmo?
- A scheduling and booking platform: a branded public link your leads use to pick a time themselves, checked live against your Google Calendar, converted to their own time zone, and confirmed by email on both sides with zero back-and-forth.
- Is Ritmo actually live, or a concept?
- It's real and shipped, running in production today, handling live bookings, calendar sync, and transactional email for a real client.
- Can it take payments?
- It has a full Stripe Checkout integration for paid event types, with webhook-confirmed status and automatic refunds on cancellation. It currently runs in test mode only; enabling live transactions is treated as its own scoped, audited project phase.
- Do we get our own instance, or a shared account?
- Each client gets a dedicated, isolated deployment: their own server, database, and domain or subdomain. It's not a shared multi-tenant platform today.
- Does it handle Serbian-speaking clients?
- Yes, natively. The same link automatically shows English or Serbian Latin to each visitor, including every confirmation and reschedule email, with nothing extra to set up per lead.
Talk about your case
Describe the process costing you the most. In a short call, we tell you whether it is worth automating and what that would actually look like.