Clone Support

Sample prompts by job

Advanced, field-tested prompts for sales, support, marketing, operations and finance. Each one names the skills it uses.

Team Studio · Studio Max
⬇ Download all (15)
Sales: account research briefEverything you need before a first call, in one page, with a tailored opener.
Research [COMPANY] ([WEBSITE]) before my first call with [NAME, TITLE] on [DATE].

Give me one page with:
1. What they do, who they sell to, size and recent news (last 6 months), with sources
2. Likely priorities for someone in [TITLE]'s role right now
3. Where our [PRODUCT / SERVICE] fits, using what you know from our knowledge
4. Anything in our CRM or email history with them
5. A 2-sentence opener and 3 discovery questions

Flag anything you couldn't confirm.
Download v1
Sales: weekly pipeline clean-upFind stalled deals, missing next steps and stale close dates, with follow-ups drafted.
Review my open opportunities in the CRM. List:
- deals with no activity in 14+ days
- deals with a close date in the past
- deals with no next step recorded

For each, suggest the next step and draft a short, specific follow-up email (don't send). Then give me a 3-line summary of pipeline health for my Monday meeting.
Download v1
Sales: proposal from call notesTurn messy call notes into a clean proposal draft in your own format.
Using my notes from today's call with [COMPANY] (below) and our proposal format from your knowledge, draft a proposal:
- their situation and goals, in their words
- what we recommend, and why
- scope, timeline and next steps
- leave pricing as [PRICING TBD] for me to fill in

Notes:
[PASTE NOTES]
Download v1
Support: answer a customer from your knowledgeA clear, accurate reply grounded in your docs, with the sources listed for you.
A customer wrote in (below). Search your knowledge for the answer and draft a reply:
- answer the actual question first, in plain language
- numbered steps if there is a process
- link the relevant help article if we have one
- warm, short, no jargon

Below the draft, list which knowledge documents you used, and tell me if anything in the question is NOT covered so I can add it.

Customer message:
[PASTE MESSAGE]
Download v1
Support: escalation hand-offSummarize a messy case into a clean hand-off for engineering.
Summarize this support case for an engineer who has never seen it:
- the customer, their plan, and which product they use
- what they expected vs what happened (exact error text)
- steps to reproduce, if we know them
- what has already been tried
- urgency and business impact

Keep it factual, under 200 words.

Case:
[PASTE CASE OR CASE NUMBER]
Download v1
Marketing: one idea, five formatsTurn a blog post or video into a LinkedIn post, an email, social captions and an image.
Take [LINK TO BLOG POST / VIDEO / DOCUMENT] and repurpose it:
1. A LinkedIn post (under 200 words, a strong first line, no hashtag spam)
2. A newsletter section (headline + 120 words + call to action)
3. Three short social captions with different angles
4. One image for the LinkedIn post (use Image Operator, our brand colors, 1:1)

Keep claims to what the source actually says.
Download v1
Marketing: competitive landscape deckA designed, sourced slide deck on your market, made with Research Report.
Use Research Report to make a medium-length slide deck on the competitive landscape for [OUR CATEGORY] in [REGION].

Audience: our sales team. Cover the main competitors and how they position themselves, pricing models (public information only), strengths and weaknesses, where we win, and 3 objection-handling talking points.

Modern theme. Send it to [EMAIL].
Download v2
Marketing: how-to videoA narrated how-to video from a few steps, with review stops before rendering.
Use Clone Automated Video to make a How-To/Tutorial video.

Topic: [WHAT THE VIEWER WILL LEARN]
Key steps: 1) [STEP] 2) [STEP] 3) [STEP] 4) [STEP]
Duration: 1-2 minutes
Aspect ratio: 16:9
Visual style: Photorealistic
Language: English
Send the finished video to: [EMAIL]

I want to review the script and storyboard before anything is rendered.
Download v2
Operations: write an SOPTurn a rough description or a recorded walkthrough into a clean standard operating procedure.
Write a standard operating procedure for [PROCESS] from my description below (or the attached transcript).

Format:
- purpose and when to use it
- who owns it
- numbered steps, one action each
- common mistakes and how to avoid them
- a checklist version at the end

Then suggest which knowledge base it should live in.

My description:
[PASTE]
Download v1
Operations: build a tool for a weekly choreHave Clone Code build a script or mini-app for a repetitive spreadsheet task.
Every week someone on my team [DESCRIBE THE CHORE, e.g. copies numbers from three exports into one summary sheet]. Use Clone Code to build something that does it for us.

Here are example files: [LINKS]
The output should be [a clean CSV / a one-page summary / a simple web page with a table and chart].
Explain how to run it in plain English.
Download v1
Operations: compare vendorsA side-by-side comparison with a recommendation, from public information.
Compare [VENDOR A], [VENDOR B] and [VENDOR C] for [WHAT WE NEED].

Make a table covering: the core features we care about ([LIST]), integrations with [OUR TOOLS], support options, contract terms and public pricing, plus security and compliance notes. Use public sources and link them.

Finish with a recommendation for a company like ours, and the 3 questions I should ask each vendor.
Download v1
Finance: month-end close checklistA tailored close checklist with owners and due dates, ready to schedule.
Build a month-end close checklist for a company like ours ([SIZE], [INDUSTRY], using [ACCOUNTING TOOL]).

For each task: what it is, who usually owns it, which business day of the close it's due, and what "done" looks like. Group by stage (pre-close, close, review, reporting).

Then offer to set up scheduled reminders for each owner.
Download v1
Finance: overdue invoice follow-upsPolite, firm reminders for overdue invoices, tiered by how late they are.
Here is our list of overdue invoices (below). Draft a reminder email for each customer:
- 1-15 days late: a friendly nudge
- 16-45 days late: firmer, with the amount and invoice number up front
- 45+ days late: firm, offering a call to agree on a payment plan

Use the contact names provided. Show me all drafts before sending anything.

Invoices:
[PASTE TABLE: customer, contact, email, invoice #, amount, due date]
Download v1
Finance: explain a budget variancePlain-English commentary on budget vs actual, ready for a leadership update.
Here's our budget vs actual for [MONTH] (attached or pasted below). Write the commentary for our leadership update:
- the 3 biggest variances and the likely reasons
- what's a timing difference vs a real change
- risks and opportunities for next month
- one chart idea that would make it clear

Plain English, no more than 250 words. Ask me about anything you can't explain from the data.
Download v1