Gmail and Calendar cards
Cards that show the matching account, ticket, or deal when an email or event opens.
The Problem
Your Team Copies Data Between Gmail and Your App All Day
It shows up when your product or CRM lives in one tab and your customers' emails live in Gmail. Every reply, meeting, and file means switching tabs and pasting.
01 · Tab switching
Reps switch tabs to look up every sender.
A Gmail card shows the sender's account from your system.
02 · Lost notes
Meeting notes never make it into your CRM.
A Calendar card logs each meeting to the right record.
03 · Loose files
Drive files have no link to the deal.
A Drive card attaches the selected file to the record in one click.
04 · Review delays
Google's OAuth review pushes back your launch date.
Scope reasons, privacy policy, and demo video are ready before submission.
A customer email arrives. Your rep opens a second tab, searches your app for the account, then copies an order number back into the reply. A meeting gets booked in Calendar, and the notes reach your CRM later, if at all. Files sit in Drive with no link to the deal. You searched the Marketplace, but no add-on talks to your system. Your own customers are asking for the same thing in their inbox.
We start with the moments your team switches tabs, then put your system's data on a card beside the open email, event, or file. Reps look up, log, and update records from Gmail's side panel, and compose actions drop the right link into a reply. The data lands in your system, not in someone's clipboard.
Cards beside the open email
Contextual cards show your records the moment a matching email opens in Gmail.
Verification planned from day one
Every OAuth scope is justified up front, so Google's review doesn't surprise you at launch.
Script or your own server
Apps Script for internal tools, or HTTP endpoints in any language for products you sell.
Our Google Workspace Add-on Development Process
From Inbox Workflow to a Published Add-on in Five Clear Steps
You approve every card, trigger, and OAuth scope before code is written, and your team tests the add-on with a small group before it reaches the whole domain.
We watch how your team moves between Gmail, Calendar, Drive, and your system, and list where cards would save the most steps. You get a card plan, a scope list, and a fixed quote. If an existing add-on covers it, we'll tell you before we quote.
What's Included
What You Get With Google Workspace Add-ons Built for Your System
Side panel cards, compose actions, a connection to your API, OAuth verification prep, publishing, and a rollout plan, all scoped to the moments your team switches tabs.
Compare Options
DeveloperLook vs Marketplace Add-on vs Freelancer
An existing Marketplace add-on is quick and cheap when it fits, and a freelancer can be fine for an internal script. This is how they differ on a real add-on.
| Feature | DeveloperLookBest fit | Marketplace add-on | Freelancer |
|---|---|---|---|
| Fit to your system | Cards built around your data | Only the tools it supports | Built from your brief |
| Time to start | 3 to 10 weeks | Installed in minutes | Days to weeks |
| Triggers and cards | Gmail, Calendar, Drive, and editors | Whatever the vendor built | Often Gmail only |
| OAuth verification | Scope reasons and demo prepared | Done by the vendor | Often left to you |
| Testing before rollout | Pilot group in your domain | Vendor tested | Varies by person |
| Data handling | Tokens server side, fewest scopes | Set by the vendor | Varies by person |
| Code and listing | Your code and Cloud project | Depends on the contract | |
| Cost over time | One-time build | Per-user subscription | Hourly fixes |
DeveloperLook
Marketplace add-on
- Fit to your system
- DeveloperLook: Cards built around your dataMarketplace add-on: Only the tools it supports
- Time to start
- DeveloperLook: 3 to 10 weeksMarketplace add-on: Installed in minutes
- Triggers and cards
- DeveloperLook: Gmail, Calendar, Drive, and editorsMarketplace add-on: Whatever the vendor built
- OAuth verification
- DeveloperLook: Scope reasons and demo preparedMarketplace add-on: Done by the vendor
- Testing before rollout
- DeveloperLook: Pilot group in your domainMarketplace add-on: Vendor tested
- Data handling
- DeveloperLook: Tokens server side, fewest scopesMarketplace add-on: Set by the vendor
- Code and listing
- DeveloperLook: Your code and Cloud projectMarketplace add-on:
- Cost over time
- DeveloperLook: One-time buildMarketplace add-on: Per-user subscription
Projects We've Built
SaaS, Recruiting, and Agency Projects We Have Built
SaaS, recruiting, e-learning, and agency sites we designed and built. None is a Workspace add-on, but each serves teams who spend their day in email and calendars.
Staffic.io Marketing Website for a Time Tracking SaaS
- HR & Staffing
- Website
CognifyHR AI Recruitment Website and HR Dashboard
- HR & Staffing
- Technology
- Dashboard
Gradely E-Learning Website Design & Development
- Education
- Dashboard
- Membership Platform
ElevateX Digital Agency Website Design & Development
- Agency
- Website
What Our Clients Say
What Clients Say After Launch
Feedback from teams we have built websites, apps, and integrations for.
We had a pretty specific idea of what we wanted our website to become, but I wasn’t sure how easily we could explain all of it to a development team. There were quite a few moving parts, and we were working toward a deadline, so I expected a few things to get lost along the way. That never really happened. They understood what we were trying to achieve, kept us updated throughout the process, and got everything ready within the agreed timeline. The final site feels much easier to navigate, works beautifully on mobile, and is noticeably smoother for our customers. It was a huge relief seeing the original idea actually turn into the website we had in mind.
The mobile experience is probably my favourite part of the new site. We had spent a lot of time making sure the desktop version looked right, and the team kept pushing us to think about how everything would actually feel on a phone too. They were right. The navigation is clean, the interactions feel natural, and everything we’ve tested so far works exactly as it should. They also went through the links, forms, integrations, and other details more than once before launch, which I really appreciated. And even after going live, we could still reach out when something came up. The whole process felt friendly, organised, and surprisingly straightforward.
What I appreciate most is that the website is actually easy for us to manage now. We can update content ourselves instead of sending a developer a message every time we need to change something small. They also paid attention to the technical SEO side, which mattered to us because we didn’t want a new website to create problems for the traffic we already had. I’ve probably asked more questions than I should have since launch, but every question has been handled patiently and without any fuss. The team is easy to work with, they explain things clearly, and when we need something changed, they focus on getting it done rather than making the process complicated.
1,250+
Projects shipped
10+
Years of experience
Top 3%
Upwork Top Rated Plus
5 stars
Average review score
Want results like these?
Tell us what you are building. You get a reply within 24 hours on business days, then a written estimate.
Work Culture
Why SaaS Teams Trust Us With Their Workspace Add-on
An add-on reads your users' email, events, or files, so these habits decide how it treats their data, their admins, and Google's review.
Fewest scopes that work
We ask for the narrowest Gmail, Calendar, or Drive scopes each card needs. Admins approve smaller lists faster, and Google's review has less to question.
Verification on the plan
OAuth verification is a step in the timeline, not an afterthought. Restricted scopes add an independent security assessment, so we flag that cost before you commit.
Pilot group before the domain
Every build goes to a small test group first. Your whole company only sees it after those users say the cards help.
Script or server, chosen honestly
Apps Script is cheaper for internal add-ons, while a server suits products you sell. We recommend the cheaper one whenever it fits.
One price per card
Your quote prices each card and trigger on its own line. A card you add later is quoted before anyone writes it.
Your Cloud project, your listing
The Google Cloud project, the OAuth client, and the Marketplace listing are created in your account. You can change developers without losing installs.
Overview
Who handles Google Workspace add-on development for SaaS teams?
DeveloperLook handles Google Workspace add-on development for SaaS teams and companies that work in Gmail and Calendar. We build side panel cards, compose actions, connections to your API, OAuth verification prep, and Marketplace or private publishing. Add-ons start from $850, take 3 to 10 weeks, and the code and listing stay yours.
DEVELOPERLOOK
Project facts · Google Workspace Add-on Development
- Service
- Google Workspace add-on development (Gmail and Calendar cards, API connections, Marketplace listing)
- Typical timeline
- 3 to 4 weeks for a private add-on, 6 to 10 weeks for a Marketplace launch
- Platforms
- Gmail, Calendar, Drive, Docs, Sheets, Slides, Meet, and Chat in Google Workspace
- Built with
- Apps Script or HTTP endpoints on Cloud Run, Card service, OAuth 2.0, Marketplace SDK
- Experience
- 10+ years of development experience and 1,250+ shipped projects
- Post-launch support
- 30, 60, or 90 days, depending on plan
- Communication
- Calls in US, UK, and AU business hours
- Starting price
- From $850 USD, fixed scope after a free inbox workflow call
Reviewed 22 Oct 2026 by Saimul Islam
Good fit
SaaS teams whose users live in Gmail
Your customers keep asking for your product inside Gmail, and you want a listing next to the other Google Workspace Marketplace add-ons they already use.
Sales and support teams on a CRM
Your reps copy order numbers and account notes between Gmail and your CRM dozens of times a day, and half the emails never get logged.
Companies with an internal system
Your staff need data from an internal tool beside each email, and the add-on should install only for your own Google Workspace domain.
Teams with an Apps Script prototype
Your Apps Script developer built a prototype that works, and now it needs proper cards, fewer scopes, and a listing customers can trust.
Agencies building for clients
Your agency builds Google Workspace extensions for clients and needs engineers who handle OAuth verification and Marketplace listings under your name.
Not a fit
Spreadsheet automation only
You want scheduled scripts that clean up Sheets, Forms, or Drive, with no side panel. Our Google Apps Script Developer page fits that work better.
Your tool runs in the browser
Your users need your product on any website they visit, not only in Gmail or Docs. Our Chrome Extension Development page covers that.
A Marketplace add-on exists
An existing add-on already connects Gmail to your CRM or helpdesk. Installing it costs less than building one, and we'll tell you so.
Your team uses Microsoft 365
Your team reads email in Outlook and writes in Word or Excel. Our Outlook Add-in Development page covers Office add-ins.
Not sure we're the right fit?
Book a free call or message us. We'll tell you honestly whether we're the right team.
Pricing
Transparent Starting Prices for Google Workspace Add-on Development
These are starting points in USD. Your final price depends on your cards, host apps, and OAuth scopes, and you get a fixed proposal after a free inbox workflow call.
For one company that needs its own data beside every email in Gmail.
$850one-time, USD
- Free inbox workflow call and card plan
- One host app, such as Gmail
- Homepage and contextual cards
- Apps Script or HTTP endpoints
- Private listing for your domain
- 30 days of post-launch support
Recommended
For SaaS products launching a public add-on for their customers.
$2,700one-time, USD
- Everything in Private Add-on
- Gmail plus Calendar or Drive
- HTTP endpoints on Cloud Run calling your API
- OAuth verification for sensitive scopes
- Public Marketplace listing and assets
- 60 days of post-launch support
For add-ons that read mail or files, or reach Chat and the editors.
$5,600one-time, USD
- Everything in Marketplace Add-on
- Restricted Gmail or Drive scopes
- Security assessment prep (assessor fee separate)
- Google Chat app as an add-on
- Docs, Sheets, and Slides cards
- 90 days of post-launch support
For Agencies
White-Label Google Workspace Add-on Development for Agencies
You own the client relationship. We supply the add-on engineering: card design, Apps Script or server code, OAuth verification prep, and Marketplace publishing. Everything ships under your agency's name inside your client's own Google Cloud project.
How the partnership works
White label: your client only ever sees your brand
- Your client
- You, the agency
- DeveloperLook
Share the client brief
Send the client's tools, the tabs their team switches, and their Workspace setup.
- Client needs
- You share the details
- Details received
We scope and staff
Within days you get a card plan, a fixed price, and the engineer's name.
- Scope and plan
- Proposal to resell
- Your quoteYOUR LOGO
Build and hand off
We build, pilot, verify, and publish, then hand over under your brand.
- Done by our team
- Your brand on it
- Handed to your clientDone
Partner with DeveloperLookDelivered under your brand
Stay client-facing
You run the client calls while we build, verify, and publish.
Predictable delivery
A fixed scope per card, with dates that account for Google's review.
Senior Workspace engineers
Engineers who know cards, triggers, quotas, and OAuth verification.
Verification paperwork done
Scope reasons and demo videos prepared for each client's submission.
The Right Technology for Your Project
Technology Stack
The Workspace apps, add-on tools, languages, and Google Cloud services we use to build add-ons that pass review and stay within Google's quotas.
- Gmail
- Google Calendar
- Google Drive
- Google Docs
Google Sheets- Google Chat
- Apps Script
- Card service
- Marketplace SDK
- OAuth 2.0
TypeScript
JavaScript
Node.js
Python
Google Cloud- Cloud Run
Firebase
Docker
FAQ
Frequently Asked Questions
Straight answers on Workspace add-on cost, timelines, the Marketplace, safety, OAuth verification, and Apps Script.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
A private add-on from us starts at $850 for one host app, such as Gmail, with homepage and contextual cards. A public Marketplace add-on calling your API is $2,700, and add-ons with restricted scopes or Chat start at $5,600. The independent assessor's fee for restricted scopes is billed by the assessor, separately.
A private add-on for your own domain takes 3 to 4 weeks and appears as soon as it's published. Public add-ons take 6 to 10 weeks, plus Google's review: listing review typically takes several days, and restricted scopes can add about six weeks of verification.
Google Workspace Marketplace is Google's catalog of apps that work with Workspace: Workspace add-ons, Editor add-ons, Drive apps, and web apps. Users and admins install from it. Older guides call these g suite marketplace apps, from before G Suite became Google Workspace in 2020. Google charges developers no listing fee.
Mostly, with your admin in control. Google's Marketplace team reviews every public app before it's listed, but Google says users stay responsible for what they install. Admins can allowlist apps, install them for chosen groups, and see or revoke the data an app can reach.
A Google Workspace addon shows cards in Gmail's side panel. A homepage card appears when no email is open, and a contextual card appears when a message opens, so it can show that sender's account. Compose triggers add buttons while someone writes a reply. The same add-on can show other cards in Calendar or Drive.
Use Apps Script for internal add-ons, because Google hosts it and it costs nothing to run. Use HTTP endpoints, in any language on Cloud Run or similar, for products that call your own API. Either way, each card callback must finish within 30 seconds, so slow lookups get cached.
Yes, if it's public and uses sensitive or restricted scopes. Restricted Gmail and Drive scopes also need a security assessment by a Google-authorized assessor at least every 12 months when data reaches your servers. Google charges no fee for it. The assessor sets their own price, so we plan scopes to avoid restricted ones where we can.
No, there's no separate Google Apps Script marketplace. Add-ons built in Apps Script are published to the Google Workspace Marketplace through the Marketplace SDK in a Google Cloud project. Pick public or private carefully, because Google won't let you switch after publishing. Private add-ons skip Google's listing review.
Yes. Since July 2025, Google Chat apps can be built as Google Workspace add-ons, so one project can serve Gmail, Calendar, and Chat. That suits alerts or lookups your team wants in a Chat space as well as beside an email. Chat features need their own scopes and testing.
You do. The Google Cloud project, the OAuth client, the code, and the Marketplace listing are all created in your account. Plans include 30 to 90 days of support after launch, and Google's new rules or API changes after that are quoted as fixed updates.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Free 30-min callGoogle Meet
Book a call
Book a free 30-minute call
In 30 minutes on Google Meet we walk you through how we would build it, how long it takes and what it costs. Then you get a written estimate.
Calendar not showing? Book on cal.com or send a brief.