Disqualify & Close the Loop (Scripts)
When to use this page
Use these talk tracks when you need to disqualify cleanly or close the loop (next steps or breakup) while keeping Ribbn’s narrative consistent:
- You uncovered a mismatch (wrong persona, wrong motion, no urgency, no omnichannel need, etc.).
- The prospect is “interested” but can’t meet the meeting bar (stakeholders missing, no pain, no commitment).
- Pricing / packaging questions show up early and you need guardrails.
- You need a crisp close: book, park, or break up.
Ribbn “core value narrative” (the sentence you return to)
Use this as your anchor when closing or disqualifying:
- Ribbn is a resale commerce platform that runs the end-to-end workflow: seller sourcing → intake/listing → inventory lifecycle → in-store checkout → payouts, and can sync products to Shopify while Ribbn stays the system of record.
- Seller intake typically starts with Sell Requests (review, price, accept/decline), and the seller is notified when the store clicks Confirm Selection.
- In-store: Ribbn supports mobile app checkout and Web POS options; Web POS supports scanning and payment via a Stripe WiFi-based reader in supported setups.
Meeting bar (book vs disqualify)
Book an AE/SE meeting when you confirm 2+ of the following (and can name the workflow pain):
- Seller sourcing + intake complexity (Sell Requests, review, notification cadence).
- Item lifecycle control matters (draft → QC → listed → sold → payout; bulk updates).
- Omnichannel execution (in-store checkout + online selling; Shopify ecosystem fit).
- Commission/payout complexity (manual payout steps, or seller self pay in supported flows).
Disqualify (or park) when:
- They want only a generic webshop and don’t have resale workflows (seller-linked inventory, commissions, payout steps).
- No one owns the workflow (no ops lead/store manager/ecom owner available).
- They can’t articulate a “why now” (no intake backlog, no inventory accuracy pain, no in-store queue issues, no Shopify migration/sync need).
Disqualify scripts (clean exits that still feel helpful)
1) Not a resale/consignment workflow (wrong motion)
When to use: They don’t manage seller-linked inventory, commissions, or payout steps.
Script:
“Based on what you shared, it sounds like you’re not really running the seller-linked resale workflow—intake from sellers, commissions, and the sold-to-payout steps. Ribbn is purpose-built for that end-to-end resale operation. If your main need is a general ecommerce storefront, we’re probably not the right first step. If you ever start (or expand) consignment/resale workflows, I’m happy to reconnect.”
Quick confirm question (optional):
- “Just to sanity-check—do you ever need to link items to sellers and manage commissions/payout steps after a sale?”
2) They already have the workflow solved (no pain / no urgency)
When to use: “Everything works fine” + no clear friction.
Script:
“Makes sense. Ribbn tends to be highest impact when teams feel operational strain—like intake speed, listing quality control, inventory accuracy, in-store checkout flow, or keeping Shopify aligned while Ribbn remains the system of record. If none of that is a priority right now, it’s probably not worth pulling you into a full meeting.”
Park with permission:
“Would it be helpful if I checked back in 90 days, in case priorities shift?”
3) Can’t reach the right owner / stakeholder
When to use: You’re speaking to someone who can’t confirm workflow reality.
Script:
“I want to be respectful of your time—Ribbn touches the day-to-day workflow from sell requests to listing to POS and payout steps, so these conversations go best when we have whoever owns ops/inventory and whoever owns ecommerce/Shopify decisions. Who’s the best person for those pieces—and should we bring them into a 25-minute working session?”
If they can’t introduce:
“No worries—without that, we’d be guessing. Let’s pause here. If you get me connected to the ops owner, I’ll gladly pick it back up.”
4) They want detailed implementation/project planning (out of scope for SDR)
When to use: They push for step-by-step admin detail.
Script:
“I can give a high-level view of how the workflow works, but the step-by-step configuration is something our AE/SE team handles in a proper working session. If we confirm you’re a fit on workflow and volume first, we can bring in the right team to go deep.”
5) Compliance / legal / payout guarantees (disqualify or escalate)
When to use: They want guarantees beyond product behavior (tax/VAT compliance, legal assurances).
Script:
“I can share how Ribbn behaves operationally—statuses, payout steps, return-window gating—but I can’t make legal or compliance guarantees. If that’s a hard requirement, we should bring in an AE/SE to confirm what Ribbn explicitly supports in your market.”
Close-the-loop scripts (book the right meeting, with the right promise)
1) Close for next step (qualified meeting)
When to use: You confirmed 2+ meeting-bar signals.
Script:
“This sounds like a strong fit for Ribbn: seller intake + item lifecycle control, plus omnichannel selling. The next best step is a working session with an AE (and sometimes an SE) to map your workflow—sell requests → intake/QC → listed → in-store checkout → payout steps—and confirm how Shopify fits with Ribbn as the system of record.”
Calendar close:
“Does it make sense to book 25 minutes this week? If you can bring your ops lead and whoever owns Shopify/ecom, we can make it concrete.”
2) Close with a recap (make the prospect feel understood)
Use this format:
- Current state
- Pain
- Ribbn mapping
- Next step
Script template:
“Let me make sure I captured it. Today you’re doing [current state], and the biggest friction is [pain]. Ribbn helps by [workflow mapping]—especially around [status lifecycle / sell requests / payout clarity / Shopify system-of-record]. Next step: I’ll set up a session with an AE to walk through your workflow and confirm fit.”
3) Close for “not now” (park, don’t chase)
When to use: Fit exists but timing doesn’t.
Script:
“You’re in Ribbn’s wheelhouse, but it sounds like timing is the blocker. Rather than forcing a meeting, let’s do this: I’ll send a short recap of what Ribbn would cover (sell requests → lifecycle → POS → payout steps + Shopify sync), and we’ll reconnect in [60/90] days.”
First-line objection handling (bridge → qualify → close)
“We already use Shopify.”
Bridge + clarify the model:
“Totally—Ribbn often complements Shopify. The model is: Ribbn stays the system of record for one-of-a-kind resale inventory and seller mapping, then you sync/publish to Shopify for the storefront. Edits belong in Ribbn first; Shopify edits don’t sync back.”
Qualify:
- “What are you using today as the source of truth for resale inventory and seller-linked items?”
Close:
- “If Shopify is staying, a working session is still useful—so we can map Ribbn → Shopify responsibilities and confirm the workflow.”
“Payouts are a pain.”
Bridge:
“That’s a common one. Ribbn supports clear post-sale payout steps, typically after a return window, and in supported flows sellers can cash out via seller self payouts—which reduces admin work. Your policy is still your choice, but Ribbn gives you an operational workflow.”
Qualify:
- “Do you pay out manually today after a return period, or do you offer store credit options?”
“We’re worried items will get stuck / missed.”
Bridge:
“Ribbn is built around lifecycle status management, and teams can bulk update items to keep operations clean—especially when moving lots of items through QC/listing stages.”
Operational trust detail (optional, if relevant):
“One example: in the sell request flow, it’s important to click Confirm Selection so sellers get the consolidated notification—otherwise things can look ‘stuck’ from the seller’s perspective.”
Pricing & packaging guardrails (SDR-safe)
Quick pricing table (what you can say out loud)
| Plan | Monthly price (as shown) | Transaction fees (as shown) | Included users (as shown) |
|---|---|---|---|
| Starter | $70 / month | +1.5% on physical store sales | 2 |
| Business | $329 / $295 per month | +1.5 on store sales, 0% online sales | 4 |
| Commercial | $724 / $595 per month | +1% on store sales, 0% online sales | 6 |
Add-ons (mention only if asked)
| Add-on | Price / notes (as shown) |
|---|---|
| Tradera integration | $100 / month |
| Extra mobile terminal | $80 / month per terminal |
| Remove backgrounds | $100 / month per 500 images |
| QR codes for checkout (1000 yearly) | $30 / month |
| RFID gun | $100 / month (min subscription 24 months or pay remaining cost; original price $2500) |
| RFID tags | $0.5 / tag |
| Fortnox integration | TBD |
Pricing objection script: “Can you give me pricing?”
If they’re qualified:
“Yes—there are three plans, and pricing depends on which checkout/integration setup you need. If it’s helpful, I can share the plan ranges now, and the AE will confirm exact fit and totals with any add-ons.”
If they’re not qualified yet:
“Happy to cover pricing, but to make it accurate: are you selling in-store, online, or both—and is Shopify part of your stack? Ribbn is often the system of record with Shopify as the storefront.”
Shopify vs checkout bundling (talk track)
“You can choose between Shopify integration or mobile app checkout depending on your needs—or run both for an extra $49/month.”
“Close the loop” follow-up templates (email/LinkedIn)
1) Post-call recap + meeting ask
Subject: Ribbn — next step?
Quick recap from today:
- Current workflow: [sell requests/intake + listing + POS + payouts + Shopify]
- Pain: [slow intake | inventory accuracy | stuck requests | payout admin | omnichannel sync]
- Why Ribbn: system of record for resale inventory + seller-linked items, with POS + Shopify sync
Next step: want to book 25 minutes with [AE name] to map your workflow and confirm fit?
If helpful, please invite whoever owns ops/inventory + Shopify/ecom.
2) Park it (timing isn’t right)
Subject: Ribbn — circle back?
Sounds like Ribbn fits your resale workflow, but timing isn’t right.
Want me to follow up in [60/90] days?
If priorities change sooner (intake volume, lifecycle control, POS throughput, Shopify sync), just reply “bump” and I’ll re-open it.
3) Breakup (no response)
Subject: Closing the loop
I haven’t been able to connect with you, so I’m going to close this out on my side.
If you ever want a workflow walkthrough for seller intake → lifecycle statuses → POS sale → payout steps (and how Shopify fits with Ribbn as system of record), reply here and I’ll reopen.
Quick “product truth” reminders (so your close stays accurate)
- Sell Requests: Accept/Decline changes state, but seller notification happens when the store clicks Confirm Selection.
- Shopify model: Ribbn is the source of truth; create/edit in Ribbn first; Shopify edits don’t sync back.
- Bulk ops: Teams can bulk edit items (statuses, commission, price, etc.) from All Products to keep inventory moving.
- Payout framing: Ribbn supports post-sale payout steps (often after a return window) and seller self payouts in supported flows—avoid guarantees beyond workflow support.