Agency Value Brief: Scoping a Parsley Engagement

How GTM agencies scope and price a Parsley implementation. The deliverables, suggested fee bands, and what sits inside a recurring optimisation retainer.

This brief is written for agencies scoping a Parsley engagement. It explains why Parsley shows up in your tech stack as a billable implementation rather than a referred subscription, what the configurable surface buys you in client conversations, and a rough fee-band you can anchor to. Adapt freely; the goal is to give you something to walk into a client meeting with.

The implementation-services wedge

What an agency gets out of bed for is the setup fee. The pattern across credible vendor partner programmes in B2B SaaS is the same: the platform belongs to the vendor, the implementation belongs to the agency. For tools in this price band, setup engagements typically run from a single intensive day to an eight-to-twelve week phased deployment, and the fee scales accordingly. The setup fee is what makes the platform stick: a configured, documented system the client owns and the agency can return to optimise.

Parsley is built around this assumption. Everything below is configuration that the client could in principle do alone, and that in practice the client will pay an agency to do once, well, and as a documented system. Parsley's own pricing is a separate conversation - point clients at /pricing when they ask.

What you actually deliver

The canonical chatbot-implementation deliverables checklist (use-case definition, knowledge ingestion, intent taxonomy, conversation mapping, lead routing, CRM field mapping, tech-stack integration, custom playbooks, QA, analytics, training, ongoing optimisation) maps almost exactly to what Parsley exposes. Per client, an agency configures:

Knowledge corpus. 8-12 documents, 5,000-15,000 words, structured as the chatbot's training set. Q&A format, pricing context, objection handling. The most leveraged work in the engagement.
Topic taxonomy. Parsley ships 15 fixed topics. The agency reviews them against the client's actual prospect questions and flags any that need a custom topic for the client's vertical. Custom per-organisation topics are on the near-term roadmap; until then, vertical specifics surface in the per-conversation theme that already lands on every CRM record.
Welcome flow + suggested questions. Three to five suggested questions framed in the prospect's voice, a two-sentence welcome, off-topic handling tone.
Lead-capture rules. Which topics trigger capture, custom capture message, minimum-exchange threshold, MEDDIC overlay configuration.
CRM field mapping. Connect Attio / HubSpot / Salesflare / Folk / Twenty / Copper. Ensure the topic chips, the free-text theme, the MEDDIC signals, and the lead quality score all land on the contact record. Verify the client's reps can filter their CRM by parsley_topics as a list-builder operation.
Branding. Logo, colours, fonts, button styles, and hiding the Parsley mark on any retainer engagement.
QA. Three test conversations per topic group; verify CRM contact accuracy; spot-check question theme specificity.
Handoff. A 30-minute walkthrough with the client's rep and CRM admin. Document the configuration so the client knows what was set up and what changing it costs.

The deliverable artifact is a configured Parsley card plus a written configuration document plus a 30-day post-launch retainer slot. That is what justifies a four-figure setup fee.

Suggested fee bands

These are anchors, not prescriptions. Adapt to the client's procurement appetite, the agency's operator rate, and the engagement complexity.

Tier	Fee range	What's in scope
Low-touch	$1,000	Single rep, generic B2B SaaS taxonomy, OAuth into one CRM, default welcome and lead capture, light branding (logo + primary colour). 3-5 hour engagement. Right for a client testing the surface before committing.
Standard	$3,000-$5,000	Single rep or small team, knowledge corpus tuned to the client's vocabulary, custom welcome and suggested questions, lead-capture thresholds tuned to funnel shape, full CRM field mapping with workflow review, full branding pass. 1-2 week engagement.
Vertical specialisation	$7,500-$15,000+	Vertical-specific knowledge corpus (health-tech, fintech, regulated industries), custom topic taxonomy once available, conversation playbooks per persona, rep training session, 30-day post-launch retainer included. 4-8 week phased deployment.

A 30-day post-launch optimisation retainer (weekly question-theme review, knowledge corpus updates, lead-capture threshold tuning, CRM workflow review) typically runs $500-$2,000 a month flat, and converts to a longer monthly retainer if the client is happy.

What you are competing against

When you walk into a client meeting offering Parsley setup, you are not competing on Parsley's own pricing - that's a separate conversation the client can have with us directly via /pricing. You are competing on the value of having a live first-party intent-capture surface running in 1-2 weeks, configured by an agency the client trusts, plumbed into the CRM the client already lives in.

The configuration surface above is a sufficient artifact to charge for. Knowledge corpus tuning alone is a chargeable line item; agencies have built entire practices around chatbot training. Topic taxonomy review is a chargeable line item. CRM field mapping plus workflow design is a chargeable line item. Bundled with the platform decision, the engagement reads as a system, which is what clients buy.

Practical operator notes

Use a client-owned email at signup. Agency-owned signup creates a transfer step later. Avoid the friction.
Run signup the same day as your first working session. The 14-day Business trial starts on signup, not on first knowledge upload.
Assume the client wants the Parsley mark hidden. On Business tier this is a single toggle. Default to hide-mark for any agency engagement; the deliverable should look like the client's, not Parsley's.
Build a knowledge corpus template for the agency. Health-tech, fintech, dev-tools, agency, RevOps. Reuse aggressively across clients in the same vertical; this is where setup time compresses on the second and subsequent deployments.
Parsley will surface vertical-specific configuration needs back to product. If three or more clients in the same vertical ask for the same custom topic, that is a signal we want to act on - email peter@parsley.id with the pattern and the agency moves up the priority list when the custom-topic surface ships.

On the near-term roadmap

Custom topics per organisation. Vertical-specific taxonomies on top of the standard 15 topics. The org-admin surface lands when the first agency partner is ready to deploy with a custom taxonomy.
Multi-tenant agency console. One dashboard managing several client accounts from a single login. Sequenced behind partner demand.
Certification badge. Worth building once the agency cohort is large enough for the badge to mean something. Revisited as the partner roster grows.

If any of these is the unlock for a specific deal, flag it directly. Partner-driven asks move first.

Want to talk through a specific client

Email peter@parsley.id. Useful in the email: the client's domain, the vertical, the rough engagement size you're scoping, any custom-topic vocabulary you've already identified.

Agency conversations land directly with product, so the feedback loop is short.