Magic Library⌘K, and launch the skill by name. Everything these skills produce is a draft for the sales owner — nothing money-facing leaves the building on its own.
Quote the deal
When a client asks “what would this cost?”, don’t start from a blank spreadsheet. Run Quote Preparation on the ticket. It:- reads the request and the client’s sizing context (users, sites) from tickets,
- confirms the option axis with you — term (1-year vs 3-year), tiers (good/better/best), or delivery model (managed vs one-off) — capped at two or three options so it reads as a quote, not a menu,
- builds each option with the same structure so they compare cleanly, and
- writes the assumptions every price depends on underneath, plus a one-line recommendation.
Scope project-shaped work
If the deal is a project — a migration, an office move, a rollout — price the scope, not a guess. Run SOW Drafting on the ticket describing the work. It drafts five plain-language sections:1
Objective
One paragraph in the client’s own words — the outcome they asked for.
2
Deliverables
Numbered and verifiable (“X configured and tested,” not “assist with X”).
3
Assumptions
Every unverified fact the effort estimate depends on — access, counts, business-hours work. This list doubles as the sales owner’s verification checklist.
4
Exclusions
The adjacent work this SOW does not cover — the usual scope-creep vectors (end-user training, legacy cleanup, third-party licensing, out-of-hours cutover).
5
Engagement model
A reasoned T&M-vs-fixed recommendation: T&M when discovery is incomplete, fixed when deliverables and counts are verified.
Find the deals already sitting in your tickets
Some of your best pipeline is buried in support work nobody flagged. Before a renewal or QBR, run Tickets to Opportunities on the client (or a portfolio). It sweeps recent tickets for buying signals:
Each candidate comes back with evidence (ticket refs + a quoted line), so you walk into the renewal knowing exactly where the expansion is — not guessing.
Every opportunity is evidence-backed by design: one grumble isn’t a signal. The report requires repetition or explicit client language before it lists anything, and a capped sweep is labeled a sample, not a census. Signals from a client’s frustration are framed as service improvements, never “upsell targets.”
Route the won deal into delivery
A “support” ticket that’s really a purchase, renewal, or pricing question shouldn’t die on the service board. Run Sales Handoff Routing on it. The skill:- confirms the ticket is genuinely a sales conversation (not a support issue with a purchase side-mention — mixed tickets stay in support, with the sales portion flagged),
- writes a plain-text handoff summary — who’s asking, what they want in their own words, environment facts, urgency or renewal dates, and anything already promised to the client,
- on your confirmation, moves the ticket to the sales board and puts the account owner on it, and
- drafts the heads-up email to that owner (as an Outlook draft if the connector is set up, else as text) for you to send.
Next
That’s the full sales cycle in Thread — pitch, quote, scope, and route. Head back to the hub for your starter kit and deal-cycle ritual, or browse every skill built for your role.Back to the Sales course
Your starter kit, deal-cycle ritual, and FAQ.
All Sales & Quoting skills
The full Super Magic skill set for quoting and hand-off.