PartnerVista · GTM / Program Manager
Vagmita Sharma, project manager at PartnerVista, has to consolidate campaign requirements arriving asynchronously across emails, calls, and client documents — one recent intake took 15 emails to fill 2–3 onboarding-form fields. Once captured, the same context gets reformatted for subcontractor handoff, and any gaps trigger rework downstream. The intake-to-launch lag slows every campaign and limits how many can run concurrently. Workarounds like PV-numbering require client cooperation that doesn't happen. The bottleneck repeats on every campaign launch, with multiple in flight at any time (ServiceNow with six partners, Dell). If requirements were captured cleanly the first time and propagated to subcontractors without rework, launch speed would increase and PartnerVista could run more concurrent campaigns without intake becoming the gating function.
Run the pilot. Pain is real, costed, and the buyer is ready.
Not a discovery call in the classical EXP-001 sense — Vagmita is an active Gia customer, and the session functioned as pilot scoping rather than open-ended discovery. She came prepared with workflow diagrams and walked the team through PartnerVista's presale-to-execution intake process. The team co-designed a two-agent solution live on the call. The standout signal was volunteered, not extracted: "fifteen email exchanges, all just for two or three fields in a form." Sanjeevi and Purvesh contributed engineering questions, which kept the conversation grounded in implementation. Closed concrete: Dell-campaign pilot agreed, weekly 30-min cadence established, Google Drive access to be shared.
Does the firm match ICP v1.3? Boutique consulting, 3–50 employees, judgment-heavy delivery, hands-on buyer, actively scaling.
| Dimension | Read | Score |
|---|---|---|
| Firm type | Partner marketing services firm — judgment-heavy program design + vendor orchestration. | 2/2 |
| Team size | Small team, exact headcount unclear. Founder Rick is hands-on with delivery. | 1/2 |
| Core pain | Intake from fragmented sources (emails, calls, client docs) takes a 15-email thread to populate 2–3 fields. Repeats every campaign. | 2/2 |
| Buyer | Vagmita owns the intake/handoff. Rick (founder) hands-on in delivery decisions. Both at the table. | 2/2 |
| Growth posture | Running multiple concurrent campaigns (ServiceNow with 6 partners). Actively scaling and hiring subcontractors. | 2/2 |
Is the pain live, costed, and ready to act on? Past attempts and trigger events tell us whether they’ll move.
| Dimension | Read | Score |
|---|---|---|
| Pain currency | Live — described a specific 15-email thread for a current campaign. | 2/2 |
| Cost quantified | Time cost implied (multiple days of back-and-forth) but not put to a dollar figure. | 1/2 |
| Failed attempts | PV-numbering scheme and subject-line discipline introduced as workarounds — clients don't follow. | 1/2 |
| Trigger event | Active campaign launch pressure (Dell, ServiceNow). | 1/2 |
| Action commitment | Concrete Dell-campaign pilot agreed. Weekly 30-min cadence established. | 2/2 |
“Fifteen email exchanges — all just for two or three fields in a form.”
“The PV-number system would work if clients actually used it.”