Open-ended discovery calls with delivery leads at boutique consulting firms to surface the most painful recurring delivery tasks and validate the client delivery bottleneck thesis.
Four prospects classified Pilot Now: Ewen Finser, Uzair Chutani, Nitin Jain, Vagmita Sharma. Each has a problem statement and a meeting summary.
13 of 30 interviews logged so far. Four prospects met the bar on both ICP fit and urgency and have been classified Pilot Now — they are the focus of EXP-002 pilot scoping. The remaining nine calls are kept as reference but are not in active pursuit. See the full scoring rubric and rationale →
Each card below opens the full scoring detail, including a meeting summary describing how the call went.
Ewen Finser, founder of a Reddit and AI-search marketing agency serving 75+ clients, faces a recurring delay producing monthly client reports. Even after automating data extraction, the strategic framing — translating performance into client-specific narrative — still consumes meaningful team hours and runs 3–4 days behind month-end. The delay cascades into invoicing, leaving the agency carrying receivables it shouldn't have to. Framing depends on each client's situation, channel mix, and history, which is why it resists templatization. The bottleneck happens every month, every client, and grows with each new account. If reports closed within a day of month-end, invoicing would tighten, cash flow would improve, and the team could shift attention to forward strategy instead of backward assembly.
Uzair Chutani, co-founder of a 22-person performance marketing agency, has every delivery team member writing a 3–4 page client update every week, for every account. The writeups consume 25–30% of team capacity and cap accounts-per-head at 5–8 when the realistic ceiling without notes would be 7–10. That translates to roughly $45–60k of unrealized capacity per delivery head per year. The writeups are required because clients expect them, and the narrative reflects each account's specific performance — generic templates don't substitute. Every account, every week, every person. If the writeups could be produced without consuming strategy hours, account capacity would expand by 25–40%, the agency could scale revenue without scaling headcount, and the team would shift focus from assembly to account growth.
Nitin Jain, partner at Barrington Consulting, watches his delivery consultants get pulled off billable engagements to write proposals — roughly 2 a day, 4 hours each. The hours come from evenings and weekends, costing about $1,200/day in stolen billable time, or ~$20k a month. A Copilot agent gets consultants 80% of the way there, but produces robotic language that partner QA spots and rejects, forcing rework. The voice of the firm — implicit knowledge held in partners' heads — doesn't transfer to generic output. The bottleneck recurs every working day. If proposals could be produced on-voice without pulling consultants off billable work, ~$20k/month would return, after-hours burnout would ease, and Barrington could absorb current proposal volume without delivery erosion.
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.
Below the Pilot Now threshold but on file. Click any row for the full scoring detail.
| Prospect | Firm | Verdict | Score |
|---|---|---|---|
| Mike Nesselbeck | Demand Path | Warm | 12/20 |
| Spencer Wixom | The Brooks Group | Warm | 11/20 |
| Sofiane Benyouci | Innovitech | Warm | 11/20 |
| Chris Bryce | Dotfusion | Insight Only | 10/20 |
| Sarah Mittiga | scaliify | Insight Only | 10/20 |
| Jason Lee (call 2) | New Wave Associates | Insight Only | 9/20 |
| Jason Lee | New Wave Associates | Insight Only | 8/20 |
| Carolyn Crewe | Best Kind Consulting | Insight Only | 7/20 |
| Amy Aitman | Venture4th Media | Disqualify | 3/20 |
Enter each call with one premise locked: client delivery is a bottleneck. Everything else is open. Walk them through their current delivery process and find where they get stuck. The goal is to hear them describe a recurring pain in their own words — not to validate a solution.
Do not ask what they would hand off to AI. Their answer will reflect their perception of what AI can do, not the real problem. Instead, ask about past behavior: what have they already tried to solve this, why haven’t they solved it yet, what would need to be true for them to feel confident handing it off to anyone.
If a strong pain signal emerges organically and matches something Gia can solve, offer a pilot on the spot.
Each open-ended question below is designed to elicit answers to one or more of these underlying assumptions without leading the witness.
| # | Assumption |
|---|---|
| A1 | Client delivery is the most painful workstream — more than biz-dev or content |
| A2 | There are recurring delivery tasks that consume meaningful time |
| A3 | Those tasks are bottlenecking growth, not just annoyances |
| A4 | Firms have already tried to solve this and failed (or haven't tried) |
| A5 | There's a willingness to hand work off — to a human OR AI — if conditions are met |
| A6 | The pain has a quantifiable monetary cost they can articulate |
| A7 | The delivery lead (not founder) is the one who feels this most |
| A8 | The pattern is consistent across firms with judgment-heavy delivery |
Run in this order. Use the question verbatim where possible — the wording is doing real work to keep the interview unbiased.
| Question | Tests |
|---|---|
| “Before we dig in — tell me about your role and how you're personally involved in client delivery work.” | v1.3 ICP fit, A7 |
| “Walk me through how you deliver a client engagement, end to end.” | A2, A8 |
| “Where in that process do you and your team spend the most time?” | A2 |
| “Of those time-heavy pieces, which one is most likely to slow you down when you try to take on more clients?” | A3 |
| “Tell me about the last time that bottleneck cost you something — a client, a deadline, a deal.” | A6 |
| “What have you tried to make that work easier?” | A4 |
| “Why do you think those attempts didn't fully solve it?” | A4 |
| “If that bottleneck no longer existed, what would change for the business?” | A5, A6 |
| “What would have to be true for you to feel confident handing that work over to someone or something else?” | A5 |
| “Have you tried any AI tools for this? Tell me what happened — or why you haven't.” | A5 (AI specifically, only after pain is established) |
| If speaking with a founder: “Who on your team feels this most directly day-to-day?” | A7 — reroutes to the right person |
Two principles from Matt: (1) Past behavior > future intent. Ask what they've already tried, not what they would hypothetically do. (2) Don't prescribe AI. The minute you describe a solution, you've collapsed their answer to your frame.
| Pool | Approach |
|---|---|
| Net new outreach | Cold outreach to delivery roles at 3–50 person consulting firms. Research-ask framing, not a product pitch. 70% strict ICP (delivery roles), 30% adjacent firms with strategy component. |
| Existing customers | Existing Gia customers in 3–50 range. Speak to the delivery lead — not just the founder. Use the same open-ended interview frame. |
| Inbound leads | Gap selling approach. “Why did you make time for this call?” Let them name their pain first, then position Gia’s delivery capability in that lens. |
A consistent pain pattern emerges across interviews — a specific recurring delivery task that multiple contacts describe independently. Bonus: one or more contacts accept an offer to pilot a solution on the call. This data feeds ICP v1.4 and directly scopes EXP-002.
| Execution | Bailey Darling (outreach + calls), Tukan Das (calls) |
|---|---|
| Advisor | Matt Cooper (interview questions, weekly check-in on pace) |
| North Star | 15 calls by May 15, 30 by May 31 — only calls with ICP-qualified delivery leads count |