Solo Consultant Client Pipeline Assistant

Outreach, call prep, follow-ups, proposals, scope changes, and a client log for solo consultants, with each stage's rules built in.

Salesconsultingclient-pipeline
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Draft a pre-call research brief for an inbound lead”
Beforegeneric AI agent
I can help you prepare a pre-call research brief for your inbound lead. To make sure it's thorough, I'd need some information. What industry is the prospect in, and what's their company size? Do you know anything about their recent news, funding, or challenges? Also, what's your offering, and what problem does it solve for them? I could put together a brief that covers their background, potential pain points, and talking points for your call. Do you have their LinkedIn profile or website I should look at?
Afterwith Solo Consultant Client Pipeline Assistant
PRE-CALL RESEARCH BRIEF

Prospect: Sarah Chen, VP Product @ FinTechStartup Inc
Meeting time: Tuesday 2pm PT (30 minutes)

===== COMPANY INTEL =====

FinTechStartup Inc (Series B, 25M raised, 80 employees)

Industry: Payments infrastructure (B2B SaaS)

Recent news:
• Announced Series B funding (Sequoia, a16z participation) June 2024
• 3 new hires in product team (LinkedIn posts indicate hiring spree)
• New product launch: real-time settlement (Aug 2024)

Website: fintech-startup.com
• Positioning: Real-time payment infrastructure for modern banks
• Core product: API for settlement, liquidity, compliance
• Customers: 15+ regional banks listed as case studies

Growth trajectory:
• Founded 2021
• Series A: 8M (2023)
• Series B: 25M (2024)
→ Implies: 2M+ ARR (Series B typical for FinTech)

===== PROSPECT INTEL =====

Sarah Chen, VP Product
• LinkedIn: 8 years in fintech, previously lead PM at BigBank's innovation lab
• Background: Stanford computer science, 2 years at Google payment team
• Relevant: Experienced buyer, technical understanding of payments

Likely motivation:
• Series B = rapid growth mode (likely pain: engineering capacity)
• New hires = need better processes/tools
• Real-time settlement launch = scalability challenge

===== PAIN POINTS TO PROBE =====

Primary hypothesis: Product team scaling faster than processes
→ Hypothesis from: Hiring spike, rapid launches

Follow-up probes:
• Sarah, I saw you just hired 3 product people. How are you managing communication now?
• With the real-time settlement launch, how is your team tracking feature requests from customers?
• What's your current prioritization process—how do you decide which features come first?

If she mentions:
• Communication chaos → Offer collaboration tool demo
• Feature request overload → Offer roadmap/feedback tool
• Manual prioritization → Offer data-driven prioritization framework

===== COMPETITIVE INTEL =====

Likely competitors already in their mix:
• Notion (roadmapping)
• Jira (engineering tracking)
• Slack (communication)

Your angle: Consolidation opportunity (all your product ops in one place)

===== YOUR VALUE PROP (how to position) =====

For FinTech startups in growth mode:
We help product teams scale without hiring a program manager. Real-time visibility into features, customer requests, and shipping progress.

Specific angle for Sarah:
Your team likely has feature requests scattered across Slack, email, and customer calls. We centralize that, so your 3 new hires can contribute immediately without a 4-week ramp.

===== TALKING POINTS =====

Opening (2 min):
• Thanks for taking the call. I know Series B is busy—congrats on the round.
• I noticed you just expanded your product team. How's that going?
→ Listen for: process friction, growth challenges

Middle (15 min):
• Share 1–2 customer stories (pick FinTech, Series B-like)
• Demo: Show how 1 feature request flows from customer → prioritized → shipped
• Probe: Does this look similar to how you currently track things?

Close (5 min):
• If interested: Could I schedule a 30-minute session with you + 1 engineer to see if it fits your workflow?
• If not: No worries. If things shift with the hiring, happy to revisit.

===== THINGS TO AVOID =====

• Don't lead with features (she cares about outcomes, not checkboxes)
• Don't compare to Jira (it's their engineering tool, not our competitor)
• Don't ask about budget first (let her see value, then talk money)
• Don't pitch for 60 min (she said 30 min; respect that)

===== POST-CALL ACTION =====

If meeting goes well:
→ Send: Short video walkthrough (not a deck)
→ Ask: Interested in a brief pilot with your product team?

If she's lukewarm:
→ Send: 1 relevant case study (FinTech company)
→ Add to retargeting list: Check back in Q2 when hiring slows

If she's not interested:
→ Ask: Is there someone on your team more focused on product ops I should talk to?
→ Don't burn bridge (VC portfolio companies collaborate)

About this skill

The back office for a one-person services business. Tell it what happened with a client and it works out where they are in your pipeline and drafts the right next move.

What it does

  • Places each request in a stage: outreach, call prep, call follow-up, proposal, engagement, or close-out
  • Writes short, trigger-based outreach and same-day call recaps in your voice
  • Builds proposals with in and out of scope, 2-3 priced options, terms, and an expiry date
  • Handles scope creep with a change order or swap instead of silent free work
  • Keeps an append-only client log where every entry has a next action and a date

What you get

Ready-to-send drafts plus the next step and log entry, with placeholders instead of invented names, prices, or results.

Best for

Solo consultants, coaches, freelancers, and corporate trainers managing their own client pipeline.

SKILL.md preview

SKILL.md
---
name: solo-consultant-client-pipeline
description: Run the client side of a solo consulting, coaching, or training business end to end - cold outreach, pre-call research, discovery-call follow-up, proposals and pricing, engagement kickoff and scope changes, and a simple client log - by working out which stage the request is at and applying that stage's rules. Use when the user says "draft outreach to this prospect", "prep me for my call with X", "write the follow-up from today's call", "turn this into a proposal", "the client wants more work for the same price", "log this in my CRM", "should I take this client?", or "what should I send next?".
---

# Solo Consultant Client Pipeline

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More sales skills

View all Sales skills →