Unified Workspace: Bridging Google and Microsoft Ecosystems
A full-stack productivity platform that unifies Google Cloud and Microsoft Graph APIs into a single workspace, built end-to-end by one engineer.
The Problem
A Dubai-based startup had a fragmented productivity stack. Their teams used a mix of Google Workspace and Microsoft 365, and the tools didn't talk to each other. Calendars, files, emails, and contacts lived in separate ecosystems, creating friction for users who worked across both.
They needed a single platform that unified both ecosystems: one interface where users could access Google and Microsoft services without friction, without switching between apps or managing separate logins.
What We Built
A full-stack productivity integration platform:
- Unified dashboard: single interface surfacing calendars, files, emails, and contacts from both Google and Microsoft
- OAuth2 integration: users connect their Google and Microsoft accounts once, then access everything through the platform
- Cross-platform actions: schedule a meeting that syncs to both Google Calendar and Outlook, share files across ecosystems
- API orchestration layer: backend that abstracts Google Cloud APIs and Microsoft Graph API behind a unified API surface
Tech Stack
- Vite + React SPA: fast, responsive frontend for the unified workspace
- Express.js: API layer orchestrating between Google and Microsoft APIs
- PostgreSQL (Prisma): user accounts, preferences, and cross-platform mappings
- JWT + OAuth2: secure authentication with both Google and Microsoft identity providers
- Docker on GCP Cloud Run: containerized deployment, same infrastructure pattern we use across projects
How We Worked
This project had a unique structure: one engineer owned the entire build end-to-end. No team of five. No handoffs. One person, backend, frontend, API integrations, deployment, and ongoing maintenance.
The engagement started as a 1-month trial. The client wanted to validate whether a small team could deliver the full scope before committing to a longer engagement. After the trial, they renewed for 3 additional months.
Why this matters: A single engineer delivering a full-stack platform that integrates two major cloud ecosystems demonstrates the caliber of our team. This isn't about headcount, it's about engineering depth per person.
The Result
The client renewed after the 1-month trial for 3 additional months of development, extending the platform's capabilities and coverage. The product is in active development with a Dubai-based team.
Want something like this built?
Tell us the problem. We'll tell you what 72 hours can produce.
Tuesday Build Notes · 3-min read
One engineering tradeoff, every Tuesday.
From the engineers actually shipping. What we tried, what broke, what we'd do differently. Zero "5 AI trends to watch." Unsubscribe in one click.
Issue #1 lands the moment you subscribe: how we cut a client's LLM bill 60% without losing quality. The 3 model-routing rules we now use on every project.
✓ You're in. Issue #1 is on its way to your inbox.
Something went wrong. Email dharini@kalviumlabs.ai and we'll add you manually.