Workspace 01 — Flagship

Win the pharma & med-tech GCC market, account by account.

India hosts 150+ life-sciences GCCs — pharma R&D hubs, med-tech engineering centers, CRO data factories and payer tech campuses. This workspace turns that landscape into a system: build your ICP, map the buying center inside each account, and run persona-true outreach that lands meetings with site heads and function leaders.

Penetration dashboard

Live view of your GCC motion — computed from the shared account & contact base used across every workspace.

The starter list is directional, public-knowledge research on India GCC presence (entries marked “verify” especially). Always verify site, leadership and scope before outreach — this is a research aid, not a verified database.
Pipeline by stage

Click any card to open the account drawer — edit stage, notes and contacts. Cards move across the board as you update the stage.

Ideal Customer Profile — GCC edition

Define who you win with inside the India life-sciences GCC universe. Everything you save here feeds every generator in this workspace — account plans, persona playbooks, sequences, landscape briefs.

Write it the way you'd say it to a GCC site head in 20 seconds.
ICP scorecard

A live summary of your saved ICP — this exact context is injected into every AI generator in this workspace.

Account map

Your target GCC universe — shared with every workspace on this platform. Open an account to map stakeholders and generate a penetration plan.

How GCC buying really works

A GCC deal is never one signature. The India site leader owns the P&L optics, the function head owns the problem, global HQ owns the process standard, procurement owns the commercials, and InfoSec/Quality own the veto. Deals die when one of these five is discovered late. Map all of them, deliberately, for every account you pursue.

◆ Economic Buyer

Who in a GCC: Site Head / Center Head for India-funded scope; the global functional VP (HQ) when budget sits with the process owner. Ask early: “whose budget line does this touch?”
Cares about: Center scorecard — cost per FTE, productivity, attrition, and the story they tell HQ each quarter about moving “up the value chain.”
How to engage: Frame outcomes in their scorecard language. One page, one number, one risk removed. Never sell features here.
Classic mistake: Treating the India site head as a rubber stamp when they actually control vendor onboarding — or vice versa.

◆ Champion

Who in a GCC: Usually the function head (Head PV, Head Clinical Data, Head Engineering) whose team feels the pain daily and who gains career capital from fixing it.
Cares about: Their function's KPIs, audit posture, and being seen by HQ as an innovator — not just a cost center operator.
How to engage: Arm them to sell internally: a 3-slide business case, a de-risked pilot design, references they can forward. Your champion does 70% of the selling when you're not in the room.
Classic mistake: Confusing an enthusiastic manager with a champion who actually has access to the economic buyer.

◆ Technical Evaluator

Who in a GCC: Head of Digital & IT, enterprise architects, and — in pharma — CSV/Quality IT who will assess validation impact (GxP, 21 CFR Part 11, Annex 11).
Cares about: Integration with the global stack (Veeva, Argus, SAP, LIMS), security review outcomes, and not inheriting an unsupported orphan system.
How to engage: Bring an architecture one-pager, a validation approach note, and your InfoSec pack (SOC 2 / ISO 27001, data-residency answers) before being asked.
Classic mistake: Letting the first technical conversation happen inside a procurement-run RFP where you can't shape the criteria.

◆ Procurement & Vendor Management

Who in a GCC: India sourcing lead executing against a global category strategy; larger GCCs run formal vendor-management offices with preferred-supplier lists.
Cares about: Rate benchmarks vs the big SIs, contract paper (MSA/SOW), payment terms, and whether onboarding you is worth the empanelment effort.
How to engage: Get sponsored in by the business, then make yourself easy: clean paper, insurance certs ready, and a pilot small enough to ride a PO instead of a full MSA cycle.
Classic mistake: Discovering a 90-day empanelment process after verbal agreement. Ask about the vendor onboarding path in meeting two, not meeting eight.

◆ Gatekeeper

Who in a GCC: InfoSec, Data Privacy (GDPR/DPDP), Legal, and in regulated functions the Quality unit. Also executive assistants controlling site-head calendars.
Cares about: Risk. Patient data, IP leakage, regulatory exposure, sub-processor chains. They can't say yes — but they can absolutely say no.
How to engage: Pre-answer: data-flow diagram, hosting model, breach terms, GxP position. Volunteer the security review early; it signals maturity and removes the slowest dependency.
Classic mistake: Treating security review as an admin step. In life sciences it is a full evaluation gate — budget 4–8 weeks.

◆ End Users

Who in a GCC: The case processors, data managers, engineers and analysts whose daily work your solution touches — often hundreds of people per function.
Cares about: Will this make my day easier or add another tool? Will automation threaten my role? (In GCCs this fear is real — address it, don't dodge it.)
How to engage: Involve 2–3 senior users in the pilot design. Position automation as removing drudge work and creating higher-value roles — the site head needs that narrative too.
Classic mistake: Winning the leadership and losing the floor. Quiet user resistance stalls more GCC rollouts than budget ever does.
Map a buying center

Pick an account, assign each mapped contact to a buying-center role, and watch the gaps. No champion = no deal; no economic buyer = no budget.

Contacts are shared with the whole platform — add them here or in the account drawer.
Persona playbooks — the six people who decide your GCC deal

Field-tested playbooks for the personas that matter in India life-sciences GCCs. Use them verbatim, or hit “Personalize with AI” to fuse a playbook with your ICP and a specific target account.

First-touch pack — pick an account, get the note

Four field-tested first-touch notes, generalized from real wins. Pick an account, a contact and a template — the composer merges your firm profile, the contact, and the account's live “WHY-NOW” trigger straight from its notes (capture one as WHY-NOW (date): trigger [url] in the account drawer).

30-day account motion — first touch to paid pilot, one account
Play builder

A play = one persona × a set of accounts × one goal × a channel mix. Build the play here, then draft its sequence with AI using your ICP and the persona playbook.

Sequence library

Three complete, GCC-tuned sequences with merge fields. Copy any touch, or export a full sequence as DOC for your sales-engagement tool.

Competitor & partner snapshot

Track who else is in your GCC accounts — competitors to displace, partners to ride with, ecosystem players to watch.

GCC ecosystem cheat-sheet — what you're really selling against

Your competition is rarely another boutique. It's these four alternatives. Know the counter for each before the first call.

1 · Do nothing / build with the internal team

Their pitch: “We have 400 engineers on site — why pay a vendor?” GCCs exist to insource; internal build is the default answer and the safest career move for the site head.
Where it breaks: Internal teams carry run-the-business load; strategic builds slip 2–3 quarters, and niche expertise (GxP validation, PV automation, regulatory data models) is thin and expensive to hire.
How a boutique wins: Don't fight insourcing — enable it. Sell “we build it with your team and hand over the keys”: fixed-scope pods, co-delivery, explicit knowledge transfer. You become the fastest route to their insourcing story, not a threat to it.

2 · Big-4 / global system integrators

Their pitch: Incumbency, master agreements already signed, global delivery scale, and a brand nobody gets fired for choosing.
Where it breaks: The A-team shows up for the sales cycle; delivery lands with rotating juniors. Minimum engagement sizes crowd out surgical problems. Change requests price like ransom.
How a boutique wins: Specificity and seniority. Lead with named senior people who stay on the account, a domain artifact the SI can't fake in a deck (your PV accelerator, your validation pack), and a start-small commercial shape the SI can't match. Position as complement: “keep the SI for the platform; use us for the sharp edge.”

3 · Staffing / contract-talent firms

Their pitch: Bodies at ₹X/hour, on-boarded in two weeks, flexible ramp-down. Procurement loves the rate-card simplicity.
Where it breaks: All accountability stays with the client. No method, no IP, no outcome ownership — and attrition on contract staff is brutal, so knowledge walks out quarterly.
How a boutique wins: Refuse the rate-card comparison; sell outcomes with acceptance criteria. “You're not buying five contractors, you're buying a validated case-intake automation in 14 weeks with a warranty.” Make procurement compare cost-per-outcome, not cost-per-hour.

4 · Point SaaS vendors

Their pitch: “The platform already does this — just configure it.” Slick demos, global reference logos, subscription pricing HQ already approved.
Where it breaks: The last mile — integration into the GCC's actual workflows, validation burden, data migration, and the 40% of requirements the configuration can't reach. GCC teams end up building around the tool anyway.
How a boutique wins: Be the last-mile partner, not the platform rival. “Keep the platform; we make it work in your validated environment and wire it to your processes.” Partner with the SaaS vendor where possible — their CS team becomes your referral channel.