How a Fractional CMO Runs AI Sales Across 3 Countries With One Scheduling System

As a fractional CMO working across a US SaaS company, a Japanese D2C brand, and a Korean startup, I maintained five Google accounts and used three different AI SDR tools: Apollo for US outreach, Smartlead for Japan, and manual sequences for Korea. Each tool had its own booking link pointing to its own calendar. None of them knew the others existed.

• 5 Google accounts across 3 companies • 30+ AI-generated emails sent per week • 3 double-bookings per month on average • 2 hours per week manually checking calendars for conflicts • 1 missed meeting per month due to timezone confusion across accounts Double-bookings were not just inconvenient — they damaged credibility with prospects who received last-minute reschedules. For a fractional executive selling trust, this was unacceptable.

I searched for a scheduling tool that could do two things simultaneously: (1) let me create separate booking links per company, each writing to that company's calendar, and (2) check availability across ALL my Google accounts before showing slots to guests. Calendly couldn't do it — one account per subscription. Cal.com couldn't do it — one calendar source per instance. No tool on the market combined company-level link separation with cross-account availability aggregation. So I built Tenbin.

Each AI SDR pastes its designated link. Guests see only available time slots. No guest ever learns about the other companies. FreeBusy ensures no event details cross account boundaries.

• Double-bookings: 3/month → 0 • Manual calendar checking: 2 hours/week → 0 • Missed meetings: 1/month → 0 • Time from AI SDR reply to booked meeting: reduced by 40% (no back-and-forth rescheduling) • CRM attribution accuracy: 100% (each booking page triggers its own webhook)

The key insight was using Google's FreeBusy API instead of calendar sync. Traditional scheduling tools sync calendars — copying event data between accounts. This creates privacy issues (Company A sees Company B's meeting titles) and complexity (sync conflicts, permission management). FreeBusy asks a simpler question: "Is this person busy between 2pm and 3pm?" The answer is yes or no. No event titles, descriptions, or attendees are shared. This means: • No calendar sharing permissions to manage • No data leakage between client companies • No sync delays — availability is real-time • No setup per account beyond OAuth connection