Build · Transform · Writing & Content
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
Example
A sample of what this play produces. Your result is generated for your inputs.
- Prospect
- Northwind Trailcraft (fictional example prospect)
Source ids
- call-2026-07-28-disco
- call-2026-08-04-demo
- email-2026-08-06-pricing-thread
- email-2026-08-11-security-questions
- ticket-2026-08-12-trial-support
Objections
- Objection id
- OBJ-1
- Statement
- We already pay for a general-purpose AI chat assistant, so another AI tool line item feels like paying twice for the same model.
- Category
- price
- Occurrence count
- 3
- Source refs
- call-2026-07-28-disco
- email-2026-08-06-pricing-thread
- call-2026-08-04-demo
- Rebuttal
- The chat assistant is the blank prompt STUD replaces: every session starts from zero and someone still has to know what to ask. STUD is a living system, it holds what the business knows, runs ready-made plays from a short intake, and every result feeds the next run. Plays run on prepaid credits: a 500-credit pack is $20, most plays cost 500 credits ($20), purchased credits never expire, and credits are spent only on an accepted run, so a finished, structured deliverable costs less than the hours reps spend re-prompting.
- Objection id
- OBJ-2
- Statement
- Our team is mid-quarter on a product launch, so evaluating a new workspace tool has to wait until next quarter.
- Category
- timing
- Occurrence count
- 2
- Source refs
- call-2026-07-28-disco
- email-2026-08-06-pricing-thread
- Rebuttal
- A launch is exactly when STUD earns its keep: the catalog has 265 ready-made plays across 14 playbooks, the intake fills itself from workspace facts, and results land structured, so the launch work itself becomes the pilot. Starting mid-quarter means the system already knows the business by the time next quarter's planning begins.
- Objection id
- OBJ-3
- Statement
- The founder likes it, but the ops lead owns the tooling budget and has not seen it yet.
- Category
- authority
- Occurrence count
- 1
- Source refs
- call-2026-08-04-demo
- Rebuttal
- Offer a 20-minute walkthrough for the ops lead built around their own workspace: state a fact once and it flows into every run. Prepaid credit packs start at $20 for 500 credits and purchased credits never expire, so the budget conversation is small; the decision is really about whether the venture's knowledge should compound.
- Objection id
- OBJ-4
- Statement
- A freelance marketplace already gives us a human for the same deliverables when we need one.
- Category
- competitor
- Occurrence count
- 2
- Source refs
- call-2026-08-04-demo
- email-2026-08-11-security-questions
- Rebuttal
- A marketplace hire starts from a blank brief every time and takes their context with them when the gig ends. In STUD the context stays: the workspace holds what the business knows, plays run from a short intake in minutes, and every deliverable passes its play's acceptance check before it counts. Use freelancers for bespoke work; use STUD for the recurring knowledge work that should compound.
- Objection id
- OBJ-5
- Statement
- We are a hardware-adjacent shop, so a catalog built for software startups may not fit our workflows.
- Category
- fit
- Occurrence count
- 2
- Source refs
- call-2026-07-28-disco
- ticket-2026-08-12-trial-support
- Rebuttal
- The plays cover marketing, finance, product, and engineering work every small team does regardless of what it sells: pricing registers, competitor teardowns, financial models, launch copy. The intake carries their facts, not a software template. Point the trial at one real deliverable they owe this week and let the result argue the fit.
- Objection id
- OBJ-6
- Statement
- STUD is pre-seed and pre-revenue, so betting a workflow on it feels risky if the product goes away.
- Category
- risk
- Occurrence count
- 2
- Source refs
- email-2026-08-11-security-questions
- ticket-2026-08-12-trial-support
- Rebuttal
- Fair concern, and worth answering plainly: STUD is a pre-seed soft launch, and the deliverables are the hedge. Every result lands as a structured artifact the buyer owns and can export, so nothing is locked in the tool. Credits are prepaid one pack at a time, held when a run is commissioned and spent only on an accepted run, and the workspace facts are the buyer's data throughout.
Summary
- Objection count
- 6
- Total occurrences
- 12
Opens soon
Cost50 credits
ProtectionSpent when the run starts · returned only if STUD is at fault
STUD opens runs for everyone soon, on every play at once.
Get early access to STUD the day it goes live.