Can I code this? A Timezone Meeting Finder for Remote Teams

Show each teammate's working hours on one shared timeline and highlight where they overlap — genuinely simple once you're honest that pure display, not calendar sync, is the actual goal.

Build it
Effort: an eveningRunning cost: $0/mo to start

Why CanICodeThis says Build it

  • Displaying multiple timezones on a shared horizontal timeline is well-documented date/time-library work
  • Highlighting overlapping working-hours windows across everyone is a straightforward range-intersection calculation
  • Saving a team's members and their timezones is simple CRUD

The parts that'll cause problems

  • Syncing with everyone's actual calendars (not just their general working hours) reintroduces real calendar-integration complexity
  • Daylight saving time transitions need careful, well-tested date-library handling to avoid off-by-one-hour bugs
  • Suggesting an optimal meeting time automatically (not just showing overlap) is a small but real additional feature

How I'd build this

frontendAstro or Next.js
databaseTurso (SQLite)
hostingCloudflare Pages

MVP scope

  • Add team members with their timezone and working hours
  • A shared horizontal timeline showing everyone at once
  • Highlighted overlap windows

Postpone to v2

  • Calendar sync for actual availability, not just general working hours
  • Automatic optimal-time suggestion
  • Shareable public link for scheduling with people outside the team

What it actually costs to build

AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)$0 marginal
AI agent — pay-per-use API, no subscription$16–$27 one-time
Hosting, once it's running$0/mo (free tier)
Domain name, if you want your own~$12/yr

Existing tools solving a similar problem typically run $6.95–$12/mo — see how they compare below.

The build prompt

Build me a timezone overlap finder: add team members with their timezone and typical working hours, show everyone on one shared horizontal timeline, and highlight the windows where everyone's hours overlap. Use a well-tested date/timezone library — don't hand-roll DST handling. SQLite behind a small API.

← try another idea · browse the full register