Kasha Google Workspace Marketplace

Full integration · Gmail · Sheets · Calendar · Chat · Drive · Luma AI · SEO backlinks
3B+
Gmail Users
10M+
Workspace Orgs
155K+
QuickBooks Installs
1M+
Streak CRM Installs
717K+
Copper CRM Installs

The Opportunity: Meet Clients Where They Already Work

Small business owners and finance operators live in Google Workspace. They receive client emails in Gmail, track finances in Sheets, schedule meetings in Calendar, coordinate with teams in Chat, and store documents in Drive. Every time they switch to a separate business tool, they lose context and momentum.

The Google Workspace Marketplace is where 10M+ organizations discover business tools that embed directly into their existing workflow. Finance and accounting apps rank among the highest-install categories, with established players reaching 155K–1M+ installs. But every competitor is a point solution — FreshBooks does invoicing, Streak does CRM, Calendly does booking. Nobody delivers the full stack.

Kasha ships the complete business management suite — invoicing, CRM, booking, AI assistant, payment tracking, ledger, and notifications — across all five Workspace surfaces (Gmail, Sheets, Calendar, Chat, Drive) as a single integrated add-on.

Strategic Value: Beyond Traditional GTM

This listing is not primarily a marketing exercise. It serves two strategic objectives that compound over time:

1. SEO Backlinks

A public listing on the Google Workspace Marketplace creates high-authority backlinks from Google's own domain (workspace.google.com) to kasha.io. These are among the highest domain-authority links available — more valuable than any link-building campaign.

  • Marketplace listing page → kasha.io (direct link)
  • Privacy policy page → kasha.io/privacy
  • Terms of service → kasha.io/terms
  • Support page → kasha.io/support
  • "Works with" surface discovery links

Every install, review, and interaction strengthens the listing's authority, which in turn strengthens the backlink profile.

2. Client Discovery

The Marketplace is a high-intent acquisition channel. Users searching for "invoice", "CRM", "booking", or "payment" in the Marketplace are actively looking for a solution — they've already decided to buy, they're choosing who from.

  • Keyword-rich listing surfaces in Marketplace search
  • "Works with Gmail/Sheets/Calendar" filter discovery
  • Category browsing in "Accounting & finance"
  • Admin-pushed installs for enterprise orgs
  • Cross-listing from Google search results

This is where SMB and enterprise clients already live — we bring Kasha to them, not the other way around.

Core strategy: Ship a full-blown, no-compromise Kasha integration across all Workspace surfaces. The listing becomes a permanent, self-reinforcing asset: high-authority backlinks improve SEO, better SEO drives more installs, more installs generate reviews, reviews improve listing rank, and the cycle compounds. Meanwhile, the add-on itself delivers genuine value by embedding Kasha into the tools clients already use every day.

Product Thesis

Why Google Workspace

Full integration, not an MVP

This is not a minimal viable product or a phased rollout. Kasha ships the complete integration from day one across all five Workspace surfaces. The platform already has every backend service needed — the work is connecting them to the Workspace add-on frontend. No reason to cut corners when the APIs already exist.

Integration Surfaces

SurfaceKasha FeatureValue proposition
Gmail (sidebar + compose) Invoicing, CRM, Booking, Luma AI, Payment Tracking Full business management sidebar. Create invoices, view CRM profiles, manage bookings, see AI suggestions, track payments — all contextual to the current email.
Sheets (side panel) Kasha Ledger Live finance console. Sync invoices, aging analysis, reconciliation, custom reports. Revenue by client, service, month.
Calendar (context trigger) Time-to-Invoice, Booking sync Convert calendar events into billable items. Auto-calculate hours × rate. Kasha bookings appear as Calendar events.
Chat (app cards) Approvals & Notifications "Invoice approved", "Payment received", "Booking confirmed". Quick action cards for team workflows and approval chains.
Drive (file management) PDF Storage & Templates Auto-store invoice PDFs in Drive. Manage invoice templates. Client document folders.

Marketplace Positioning

Category

Accounting & finance (primary)

Aligns with invoice/payment wedge. Higher intent category for billing decisions.

Listing Title

"Kasha — Invoicing, CRM & Booking for Gmail"

Short, outcome-oriented. Covers core Gmail surfaces.

Keyword cluster (baked into description)

invoice, invoicing, payment request, accounts receivable, billing, CRM, booking, appointment, client management, get paid, PDF invoice, payment link, follow-up, reminder, aging, reconciliation

Required marketplace assets

AssetSpecStatus
App icon (large)128 × 128pxTo create
App icon (small)32 × 32pxTo create
Card banner220 × 140pxTo create
Screenshots (5)1280 × 800pxTo create
Promo videoYouTube, 30–60sTo create
Privacy policyPublic URLTo create
Terms of servicePublic URLExisting
Support pagePublic URLExisting

Gmail: Full Business Sidebar

The primary user flow — the "hero path" that the Marketplace listing, screenshots, and demo video will all showcase:

User opens a client email → Kasha sidebar appears with CRM profile + outstanding invoices + Luma suggestions clicks "Create Invoice" recipient, line items, tax auto-populated "Generate PDF & Payment Link" Gmail compose draft created with PDF attached and payment link in body review and send.

Gmail entry points

Screenshot narrative arc (5 screens)

  1. CRM context: Open a client email → sidebar shows contact profile, lifetime value, last booking, outstanding balance.
  2. Create invoice: Click "Create Invoice" → line items, tax, due date pre-filled from context.
  3. Send with payment link: PDF generated, draft email created with attachment and payment link.
  4. Payment tracking: Invoice status (sent / viewed / paid / overdue) visible in sidebar for any client email.
  5. Luma AI suggestions: "Client hasn't booked in 30 days", "Invoice #1042 overdue — send follow-up?", "Upsell: offer package deal."

CRM Sidebar: Client Intelligence at a Glance

When a user opens any email, Kasha matches the sender/recipient to the CRM database and renders a rich contact card:

Contact Card

  • Name, email, phone, company
  • Tags and custom fields
  • Notes and activity timeline
  • Quick actions: edit, add note, create task

Financial Summary

  • Lifetime revenue
  • Outstanding balance
  • Recent invoices (status badges)
  • Payment history trend

Booking History

  • Last booking date and service
  • Upcoming appointments
  • Booking frequency (weekly/monthly)
  • Quick re-book action

Luma Insights

  • Churn risk indicator
  • Upsell/cross-sell suggestions
  • Recommended follow-up action
  • Revenue prediction

New contact handling: If the email address doesn't match an existing CRM record, the sidebar offers "Add to Kasha CRM" with name/email pre-filled from the message metadata.

Booking Integration

Kasha's booking engine powers salon/wellness appointment scheduling, service consultations, and paid sessions. In Gmail:

Luma AI Assistant

Luma is Kasha's conversational AI assistant. In the Gmail sidebar, Luma powers proactive business intelligence that no competitor offers:

Differentiator: FreshBooks can create an invoice from Gmail. Zoho can show CRM data. Nobody proactively tells you "This client is at risk of churning" or "You could upsell a package deal based on their booking history" — that's Luma.

Luma suggestion types

SuggestionTriggerAction
Follow-up reminder Invoice overdue > 7 days "Send follow-up email" (pre-drafts a polite reminder)
Re-booking nudge No booking in 30+ days for regular client "Send re-booking offer" with suggested service and time
Upsell opportunity Client consistently books same service "Offer package deal" with recommended pricing
Churn risk Activity decline + payment delays "This client may be at risk — reach out with a personal note"
Revenue insight End of week/month "Your revenue this week is up 12% vs last week" (homepage card)
Smart invoice amount Creating invoice for repeat client Pre-suggest line items based on booking history and past invoices

Payment Status Tracking

When viewing any email from a known client, the sidebar shows real-time payment status for all associated invoices:

Draft

Invoice created but not sent

Sent

Email delivered to client

Viewed

Client opened payment link

Paid

Payment confirmed via Adyen

Overdue

Past due date, unpaid

Partial

Partial payment received

Quick actions from payment cards: "Copy payment link", "Send reminder", "Mark as paid (manual)", "View in Kasha".

Kasha Ledger for Sheets

A side-panel add-on for Google Sheets that turns a spreadsheet into a live finance console:

This mirrors the G-Accon/Xero pattern that drives 127K+ installs, but with native Kasha data rather than requiring a third-party connector.

Calendar → Invoice

Convert time spent into billable items:

Google Chat: Approvals & Notifications

Team-oriented workflows delivered as interactive Chat app cards:

Chat integration is particularly valuable for Enterprise (one-to-many) clients where multiple team members need visibility into financial and booking activity.

Google Drive: PDF Storage & Templates

Automated document management integrated with Drive:

One App to Rule Them All

Kasha ships as a single Google Workspace add-on that spans all five surfaces. One manifest, one install, one listing, one set of OAuth scopes. The user installs once and Kasha appears everywhere they work.

Architecture decision: One Workspace add-on, not five separate listings. The Google Workspace add-on framework natively supports multi-surface deployment — a single appsscript.json manifest declares triggers for Gmail, Sheets, Calendar, Chat, and Drive. This is how the framework was designed to be used.

Why one app, not multiple listings

FactorOne app (all surfaces)Multiple listings (per surface)
User experience Install once, Kasha everywhere × Install 5 times, 5 consent screens
Install count Consolidated — bigger number, more trust × Fragmented across listings
Reviews All reviews on one page, compounds × Split, each looks weaker
Discovery "Works with" shows all 5 surfaces = Each listing shows 1 surface
Maintenance One codebase, one deploy, one review × 5 review cycles, 5 sets of screenshots
OAuth One consent screen, all scopes × Multiple consents, user fatigue
Backlinks 1 listing = ~6 backlinks from Google 5 listings = ~30 backlinks from Google

The only advantage of multiple listings is more backlinks. But the right way to multiply backlinks is to list on different marketplaces (Google, Shopify, Zapier, Microsoft, Xero, QBO) — not to fragment the same product into separate listings on a single marketplace. Each external marketplace is a new domain, a new audience, and a new set of high-authority links.

Single manifest structure

appsscript.json ├── addOns │ ├── gmail │ │ ├── contextualTriggers → onGmailMessage() │ │ ├── composeTriggers → onGmailCompose() │ │ └── homepageTrigger → onGmailHomepage() │ ├── sheets │ │ └── homepageTrigger → onSheetsHomepage() │ ├── calendar │ │ ├── eventOpenTrigger → onCalendarEventOpen() │ │ └── homepageTrigger → onCalendarHomepage() │ └── drive │ └── homepageTrigger → onDriveHomepage() ├── chat → Kasha Chat Bot (notifications + approvals) └── oauthScopes → [all scopes, one consent]

Every trigger function calls the same kasha-middleware-gws-connector backend. The Apps Script layer is a thin UI shell — all intelligence lives in NestJS.

Hybrid Architecture: Apps Script + NestJS

Decision (confirmed): Hybrid approach — Apps Script handles Card UI rendering and Google API interactions (Card Service, triggers, compose actions). NestJS HTTP endpoints handle all business logic (invoice creation, CRM lookups, booking management, Luma AI, payment status).

Why hybrid?

LayerTechnologyRationale
UI Layer Apps Script (Card Service) Native card rendering, built-in trigger handling, OAuth token management for Google APIs. Fast to iterate on card layouts.
Business Logic NestJS HTTP endpoints Reuses existing Kasha Platform services. Multi-tenant, battle-tested. Same APIs that power the web app.
AI Layer Luma service (NestJS) Luma suggestions computed server-side, returned as card JSON data to Apps Script for rendering.

Request flow

Gmail opens email | v Apps Script: onGmailMessage trigger fires | v Apps Script extracts: sender email, thread ID, message metadata | v UrlFetchApp.fetch("https://api.kasha.io/workspace/context") POST { email, threadId, userId, orgId } | v NestJS Middleware Connector: ├── CRM Service → contact profile, lifetime value ├── Invoice Service → outstanding invoices, payment status ├── Booking Service → upcoming/past bookings └── Luma Service → AI suggestions for this contact | v Returns JSON: { contact, invoices, bookings, suggestions, cards } | v Apps Script renders Card UI from JSON response | v User sees: CRM card + invoices + bookings + Luma suggestions

Middleware Connector Pattern (ADR-005)

The Google Workspace add-on backend follows the Middleware Connector Pattern established with the KYC proof of concept:

Three-repo structure

@kasha/workspace-addon-service
↓ shared library
kasha-middleware-gws-connector
↓ HTTP endpoints
Apps Script Add-on
Kasha Platform
RepositoryTypePurpose
@kasha/workspace-addon-service Shared library (ADR-006) Provider-agnostic business logic: card data assembly, context resolution, suggestion engine interface, OAuth token management.
kasha-middleware-gws-connector NestJS REST API (ADR-005) Standalone gateway. Receives requests from Apps Script, orchestrates CRM/Invoice/Booking/Luma services, returns card-ready JSON.
Apps Script project Google Apps Script Thin UI layer. Handles triggers, calls the connector, renders Card JSON. Minimal logic — all intelligence server-side.

Data Flow & Service Integration

The middleware connector aggregates data from multiple Kasha Platform microservices:

ServiceData providedEndpoints used
lr-crm-service Contact profile, tags, notes, activity timeline GET /contacts/by-email, GET /contacts/:id/activity
lr-invoicing-service Invoices, payment status, PDF generation POST /invoices, GET /invoices/by-contact, GET /invoices/:id/status
lr-booking-service Appointments, availability, services catalog GET /bookings/by-contact, POST /bookings, GET /availability
lr-payment-service Payment status, payment links, transaction history GET /payments/by-invoice, POST /payment-links
Luma AI service Suggestions, risk scores, revenue predictions POST /luma/suggestions { contactId, context }
lr-auth-service User/org auth, Google account linking POST /auth/google-link, GET /auth/workspace-user

OAuth Scopes & Security Strategy

Full scope set (all surfaces at launch)

ScopeSurfacePurposeClassification
gmail.addons.current.action.compose Gmail Manage drafts/send emails when user interacts with add-on Non-sensitive
gmail.addons.current.message.metadata Gmail View email metadata (sender, recipients, subject) for CRM matching Non-sensitive
gmail.addons.current.message.readonly Gmail Full message context for Luma AI smart suggestions and invoice parsing Sensitive
calendar.addons.execute Calendar Calendar event context for time-to-invoice and booking sync Non-sensitive
drive.file Drive Store invoice PDFs, templates, and receipts in user's Drive Sensitive
openid Auth Google identity for account linking Non-sensitive
email Auth User's email for Kasha account matching Non-sensitive
profile Auth User's name for display and personalization Non-sensitive

Scope strategy: Request all scopes at launch since we're shipping the full integration. The sensitive scopes (message.readonly, drive.file) require OAuth verification and may trigger a security assessment. Budget for this upfront — it's the cost of doing the full integration properly. CASA Tier 3 assessment unlocks the security badge, which accelerates enterprise trust.

Security posture

CASA security badge

Since we're requesting sensitive scopes (message.readonly, drive.file) and exchanging data with Kasha servers, a CASA security assessment is required. Target Tier 3 directly to unlock the security badge — a visible trust signal on the Marketplace listing that accelerates enterprise adoption. Badge takes ~3 weeks to propagate after passing. Budget: low five-figure annual line item for assessor fees + remediation engineering.

Competitor Landscape

AppInstallsWorks withInvoicingCRMBookingAISecurity Badge
QuickBooks (Intuit) 155K+ Gmail, Calendar × × × ×
FreshBooks (Gmail) 11K+ Gmail × × × ×
Zoho CRM 242K+ Gmail × × × ×
Streak CRM 1M+ Gmail, Calendar × × × ×
Copper CRM (Sheets) 717K+ Sheets × × ×
G-Accon for Xero 127K+ Sheets (via Xero) × × × ×
Kasha Gmail, Sheets, Calendar, Chat, Drive (CASA Tier 3)

Kasha Differentiation: Why We Win

1. All-in-one sidebar

No competitor offers invoicing + CRM + booking in a single Gmail sidebar. Users currently need FreshBooks + Streak + Calendly — three tools, three subscriptions, three logins.

2. Luma AI intelligence

Proactive suggestions based on cross-domain data (invoices + bookings + CRM). "This client is at risk" is impossible when your tools are siloed.

3. Payment tracking built-in

See invoice status directly in the sidebar when viewing any client email. No need to open a separate dashboard to check if a payment arrived.

4. Multi-market, multi-currency

CHF, BRL, GBP, EUR, CAD. QR-bill (CH), Pix (BR), TWINT. No competitor on the Marketplace handles this breadth with local payment methods.

Two Types of Marketplace: Kasha-Run vs 3rd Party SaaS

The word "marketplace" means two completely different things in the Kasha context. This distinction is critical for strategy, positioning, and resource allocation.

Kasha-Run Marketplaces

What it is: A product feature inside Kasha where merchants list their products and services for consumers to discover, book, and buy.

Kasha's role: Platform operator. Kasha owns the marketplace, sets the rules, earns commission on transactions.

Revenue model: Transaction commission (8%/6%/4.5%/3.5% tiered), listing fees, promoted placement.

Examples:

  • Brazil: merchant product catalog, service marketplace, beauty & wellness directory
  • Switzerland: SMB service directory, booking marketplace, product storefronts

Audience: End consumers discovering and buying from Kasha merchants.

Status: Part of Kasha Platform product roadmap. Documented in Brazil and Switzerland GTMs.

3rd Party SaaS Marketplaces

What it is: External app stores and integration directories where Kasha is listed as a tool that extends other platforms.

Kasha's role: App publisher. Kasha is a listed product on someone else's marketplace.

Revenue model: No direct revenue from listings. Value is SEO backlinks + client discovery + trust signals.

Examples:

  • Google Workspace Marketplace (this document)
  • Shopify App Store
  • Zapier / Make integration directories
  • Microsoft AppSource
  • Xero App Store, QuickBooks App Store

Audience: SMBs and enterprises searching for business tools within platforms they already use.

Status: Google Workspace is the first listing. Others follow as backlink multiplication play.

Key distinction: Kasha-run marketplaces are a revenue-generating product feature (Kasha earns commission). 3rd party SaaS marketplace listings are a distribution and SEO strategy (Kasha earns no marketplace revenue, but gains high-authority backlinks, client discovery, and trust signals). Both are called "marketplace" but they serve entirely different strategic purposes.

3rd Party SaaS Marketplace Map

Each external marketplace listing creates a new set of backlinks from a different high-authority domain, plus a new client discovery channel. The same middleware connector architecture (ADR-005) serves all of them — each marketplace just needs a different UI layer.

MarketplaceDomain AuthorityAudienceKasha IntegrationBacklinksPriority
Google Workspace Marketplace workspace.google.com (DA 100) 10M+ orgs, Gmail/Sheets/Calendar users Full add-on: Gmail sidebar, Sheets ledger, Calendar, Chat, Drive ~6 links Now
Shopify App Store apps.shopify.com (DA 90+) 4.8M+ stores, e-commerce merchants Order sync, invoice auto-generation, CRM enrichment from Shopify customers ~5 links Next
Zapier / Make zapier.com (DA 90+) Automation users, workflow builders Triggers (invoice created, payment received, booking confirmed) + actions (create invoice, create contact) ~4 links Next
Microsoft AppSource appsource.microsoft.com (DA 95+) Microsoft 365 / Teams / Outlook users Outlook add-in (mirror of Gmail sidebar), Teams bot (mirror of Chat) ~5 links Later
Xero App Store apps.xero.com (DA 85+) Xero accounting users (3.95M subscribers) Two-way invoice sync, bank reconciliation, contact mapping ~4 links Later
QuickBooks App Store apps.intuit.com (DA 90+) QuickBooks users (7M+ customers) Invoice sync, payment matching, expense categorization ~4 links Later
HubSpot App Marketplace ecosystem.hubspot.com (DA 90+) HubSpot CRM users Contact sync, deal-to-invoice, payment tracking in HubSpot timeline ~4 links Later
Slack App Directory slack.com/apps (DA 95+) Slack workspace users Notifications + actions (mirror of Google Chat integration) ~4 links Later

Backlink multiplication: 8 marketplace listings × ~4–6 backlinks each = ~35–48 high-authority backlinks from 8 different top-tier domains. Each listing also opens a new discovery channel with its own audience. The middleware connector pattern (ADR-005) means the backend work is done once — each new marketplace only needs a thin UI adapter.

Architectural reuse across marketplaces

@kasha/workspace-addon-service
↓ shared library (reused across all marketplaces)
kasha-middleware-gws-connector
↓ same business logic, different UI adapters
Google Workspace
Shopify
Zapier/Make
Microsoft
Xero
QBO

SMB → Enterprise Expansion

The Marketplace listing is one listing branded as Kasha. Feature differentiation happens based on the connected Kasha account tier:

FeatureKasha SMB (Free/Starter)Kasha Enterprise
Gmail sidebar (CRM + invoicing)
Booking integration
Luma AI suggestions (+ team insights)
Payment tracking
Sheets Ledger
Mass payouts from Sheets ×
Team approval workflows (Chat) ×
Admin domain install ×
Audit logging & compliance Basic Full (export, retention policies)
API rate limits Standard Elevated

The Marketplace listing generates permanent, compounding SEO value for kasha.io:

Backlink sources from a single listing

Backlink sourceDomain authorityTarget URL
Marketplace listing page (direct link) workspace.google.com (DA 100) kasha.io
Privacy policy link (required) workspace.google.com kasha.io/privacy
Terms of service link (required) workspace.google.com kasha.io/terms
Support page link (required) workspace.google.com kasha.io/support
Admin setup / config link (optional) workspace.google.com kasha.io/workspace-setup
YouTube promo video (optional) youtube.com (DA 100) kasha.io (video description)

Each of these links is a do-follow link from a Google-owned domain with maximum domain authority. This is more valuable than months of traditional link-building campaigns.

SEO reinforcement loop

Listing published → backlinks indexed by Google → kasha.io domain authority increases → kasha.io ranks higher in organic search → more users discover Kasha → more installs → more reviews → listing ranks higher in Marketplace search → more installs → cycle compounds.

Keyword-rich listing as SEO content

The Marketplace listing description itself is indexable content. By embedding keywords naturally (invoice, payment, CRM, booking, AI assistant, multi-currency, CHF, BRL, GBP), we create an additional high-authority page that ranks for these terms and drives organic traffic.

3rd party SaaS marketplaces as backlink multipliers

Google Workspace is the first listing. Each additional 3rd party SaaS marketplace listing (see 3rd Party SaaS Map) adds ~4–6 high-authority backlinks from a different domain. This is not to be confused with Kasha-run marketplaces (see Kasha vs 3rd Party), which are a product feature, not a distribution channel.

Google Workspace Listing Strategy

Listing copy (draft)

Title: Kasha — Invoicing, CRM & Booking for Gmail

Short description: Create invoices, track payments, manage clients, and book appointments — all from your Gmail sidebar. AI-powered suggestions help you get paid faster and keep clients coming back.

Long description (draft)

Kasha brings your entire business toolkit into Gmail — no more switching between tabs to invoice a client, check a payment, or schedule an appointment.

HOW IT WORKS

  1. Open a client email → see their CRM profile, invoices, and bookings in the sidebar
  2. Click "Create Invoice" → line items, tax, and due date auto-populated
  3. "Generate PDF & Payment Link" → attached to a draft email, ready to send
  4. Track payment status (sent / viewed / paid) without leaving Gmail

KEY FEATURES

RECOMMENDED FOR

SETUP
Install the add-on, then sign in to your Kasha account to connect. Admins: see our Admin Setup guide for domain-wide rollout.

Pricing label

"Free of charge with paid features" — Marketplace install is free. Premium features gated by Kasha subscription tier (Starter, Pro, Business, Enterprise). Kasha handles billing via Stripe, not Google licensing.

Growth Strategy & KPIs

North-star metric

Weekly Active Invoice Creators / Total Installs
Activation efficiency

Funnel KPIs

StageMetricTarget (Month 3)
InstallTotal installs500+
ActivationInstall → first sidebar open>60%
First valueFirst invoice created>30% of activations
ConversionInvoice sent (draft → send)>70% of created
Time-to-valueMedian minutes: install → first invoice sent<10 min
RetentionWAU/MAU>40%
ExpansionFree → paid conversion>8%

Growth experiments (post-launch)

Risk Mitigation

RiskSeverityMitigation
OAuth consent misconfigured (Internal vs External) High Use "External" user type for public app. Complete OAuth verification before submission.
Sensitive scopes require security assessment High Engage CASA assessor in week 1, parallel to development. Budget 2–4 weeks for assessment + remediation. Required for message.readonly and drive.file.
Listing mismatch (screenshots vs actual behavior) Medium Screenshots from real UI only. Update listing when features change. No mockups.
Policy violation (Google trademark misuse) High Follow Marketplace branding guidelines. No "Gmail" in app title. Use "for Gmail" only as permitted.
Apps Script quota exhaustion Medium Minimal Apps Script logic; all heavy work in NestJS. Cache Service for repeated lookups. UrlFetch budget managed.
CASA assessment timeline risk Medium Assessor availability varies. Start early, have all security documentation prepared. Badge propagation takes ~3 weeks post-assessment.
Google review rejection Medium Pre-flight checklist: working privacy URL, accurate listing, functional OAuth. Budget 2 review cycles.
Slow sidebar loading Medium Connector returns full context in single request (<500ms target). Progressive card rendering.

Roadmap

This is a single, comprehensive build — not a phased rollout. All five Workspace surfaces ship together.

StreamTimelineDeliverables
Backend Weeks 1–4
  • @kasha/workspace-addon-service shared library (ADR-006 pattern)
  • kasha-middleware-gws-connector NestJS gateway (ADR-005 pattern)
  • Context aggregation endpoint: CRM + Invoice + Booking + Payment + Luma in single call
  • Card JSON serialization layer (translates Kasha data into Google Card format)
  • Google account linking / OAuth token management
  • Webhook endpoints for Chat notifications
  • Drive file management endpoints
Frontend Weeks 2–5
  • Apps Script project: Gmail sidebar (CRM card, invoice creation, booking, payment status, Luma suggestions)
  • Gmail compose actions: insert invoice, payment link, booking link
  • Gmail homepage: today's overdue invoices, upcoming bookings, Luma insights
  • Sheets side panel: Kasha Ledger (sync, aging, reconciliation, reports)
  • Calendar context trigger: time-to-invoice, booking sync
  • Chat app: approval cards, notifications, daily digest
  • Drive: auto-store PDFs, template management
Security & Compliance Weeks 1–6
  • Privacy policy page (workspace-specific data handling)
  • Limited Use disclosure (Google API Services User Data Policy)
  • OAuth verification package (sensitive scopes: message.readonly, drive.file)
  • CASA Tier 3 security assessment (engage assessor early)
  • Data retention policy, deletion API, audit logging
Listing & Assets Weeks 4–6
  • Marketplace listing copy (title, short description, long description, keywords)
  • Icons (128×128, 32×32), card banner (220×140)
  • 5 screenshots (1280×800) from real UI
  • 30–60s YouTube promo video (real screen capture, not mockups)
  • Admin setup documentation
Pilot & Launch Weeks 6–8
  • Pilot with 5–20 B2B client domains + internal
  • Performance optimization (<500ms sidebar load target)
  • Submit to Google Workspace Marketplace (public listing)
  • Google review cycle (budget 1–2 iterations)
  • Launch: "Works with Gmail" badge on kasha.io, email campaign, SEO backlinks active
Post-Launch Weeks 9+
  • Review velocity: prompt early adopters for ratings
  • Listing optimization: A/B test descriptions, update screenshots as product evolves
  • Next 3rd party SaaS listings: Shopify App Store, Zapier/Make, Microsoft AppSource, Xero/QBO app stores
  • Each additional listing = ~4–6 new high-authority backlinks + new discovery channel (see 3rd Party SaaS Map)

Cost & Resource Estimates

ItemEstimateNotes
Shared library (@kasha/workspace-addon-service) 1–2 weeks engineering ADR-006 pattern. DTOs, interfaces, orchestrator, card data assembly.
NestJS middleware connector (all endpoints) 3–4 weeks engineering Context aggregation, card JSON serialization, Chat webhooks, Drive management. Reuses existing Platform APIs.
Apps Script add-on (all 5 surfaces) 3–4 weeks engineering Gmail sidebar + compose, Sheets side panel, Calendar context, Chat app, Drive triggers. Card Service UI across all surfaces.
OAuth verification (sensitive scopes) 2–6 weeks (Google process) Sensitive scopes (message.readonly, drive.file) require full verification. Start in parallel with development.
CASA Tier 3 security assessment $5K–$15K/year Required for sensitive scopes + data exchange. Unlocks security badge. Annual renewal. Engage assessor in week 1.
Marketplace listing assets 1 week design Icons (128×128, 32×32), banner (220×140), 5 screenshots (1280×800), YouTube promo video.
Google Cloud project $0 (Marketplace SDK) No listing fee. Cloud project needed for OAuth + APIs.

Open Decisions

#DecisionOptionsPriority
1 Listing branding: "Kasha" vs "Kasha Invoicing, CRM & Booking" vs "Kasha for Gmail" Trade-off: broader brand recognition vs search keyword optimization vs Marketplace naming conventions P1
2 Account linking: create Kasha account from add-on, or require existing account? In-addon signup maximizes conversion from Marketplace installs. Requiring existing account limits to current users. P1
3 Luma AI: full ML-based suggestions from day one, or start with rule-based and layer ML? ML is the differentiator and worth doing properly. Rule-based can supplement while ML models warm up on user data. P1
4 Market-specific features: auto-detect from org/user locale or manual configuration? QR-bill (CH), Pix (BR), TWINT, local payment methods — should be contextual to the user's market P1
5 Enterprise mass payout from Sheets: structured Kasha template or flexible custom Sheet format? Template is safer and reduces support; custom Sheet is more flexible for power users P2
6 Chat notification granularity: per-event or daily digest or user-configurable? Over-notification kills adoption. Per-event for critical items (payments), digest for everything else. P2
7 Next 3rd party SaaS marketplace listings after Google Workspace Shopify, Zapier/Make, Microsoft AppSource, Xero/QBO — each listing = ~4–6 new backlinks from a different DA 85+ domain. Priority by audience size + engineering effort. P2

Related documents: Brazil SMB GTM · Switzerland SMB GTM · Middleware Connector Pattern (ADR-005) · Licensing & Routing Framework