STUD
← Plays

Build · Transform · Writing & Content

Build a Sales Objection Handling Register

A register of recurring sales objections surfaced from a fixed document set, each categorized, counted by occurrence, and paired with a suggested rebuttal, so a rep can prep before the next meeting.

You receive: A JSON object {prospect, source_ids:[...], objections:[{objection_id, statement, category, occurrence_count, source_refs:[...], rebuttal}], summary:{objection_count, total_occurrences}}.

Part of Build a Sales Engine

Opens soon

Cost20 credits
ProtectionHeld until verified delivery

This play is verified and ready. It opens soon, once sign-in and payments are live.

Example

A sample of what this play produces. Your result is generated for your inputs.

ProspectHarborline Ops

Source ids

  • call-0710
  • call-0715
  • email-0718
  • ticket-0722

Objections

Objection idobj-price-01
StatementThe $20 monthly plan feels expensive before we have seen a play finish work we would otherwise do ourselves.
Categoryprice
Occurrence count2
Source refs
  • call-0710
  • email-0718
RebuttalStandard is $20/mo for 500 credits, and each play costs 10 to 40 credits ($0.40 to $1.60), so a team runs twelve or more plays a month before it costs more than one freelance hour.
Objection idobj-timing-01
StatementWe would rather wait until next quarter's budget cycle before adding a new subscription line.
Categorytiming
Occurrence count1
Source refs
  • call-0715
RebuttalCredits carry no lock-in term: start on Standard this month, run the plays that matter now, and pause or cancel before the next cycle if it has not earned its place.
Objection idobj-authority-01
StatementOur ops lead can trial it, but procurement has to sign off on any new recurring tool before it is approved.
Categoryauthority
Occurrence count2
Source refs
  • call-0710
  • ticket-0722
RebuttalPoint procurement at the one-time credit pack first: it needs no recurring approval, and the ops lead can show a finished, judge-accepted run before the subscription conversation happens.
Objection idobj-competitor-01
StatementWe already use a general-purpose AI chat assistant for this kind of work, so it is unclear what STUD adds.
Categorycompetitor
Occurrence count2
Source refs
  • call-0715
  • email-0718
RebuttalA chat assistant hands back text you still have to check and rework; STUD freezes the acceptance criteria up front and a platform-owned judge verifies the delivered work against them before payment settles, so the check is built in, not a second job.
Objection idobj-fit-01
StatementOur niche compliance workflow was not one of the plays we saw in the catalog demo.
Categoryfit
Occurrence count1
Source refs
  • ticket-0722
RebuttalThe catalog runs about 265 plays across 14 playbooks today; if a specific workflow is not covered yet, flag it so it can be scoped as a new play rather than forcing the closest existing match.

Summary

Objection count5
Total occurrences8

Get early access to STUD the day it goes live.