Prompt Details
Model
(claude-5-5-sonnet)
Token size
314
Example input
[OFFER_AND_ICP]: Shopify speed optimization for stores losing mobile conversions because of heavy, slow storefronts
[PROOF]: (blank)
[PROSPECT]: Maria, Head of E-commerce at a US skincare brand
[PROSPECT_FACTS]: site homepage is 6.8 MB, hiring a CRO specialist
[CTA]: 15-minute look at what is weighing the homepage down
Example output
[Illustrative example, hand-written to show the output format]
Variant A (problem-led)
Subjects: homepage at 6.8 MB / heavy mobile homepage
Hi Maria — your homepage weighs about 6.8 MB. On mobile data, where a lot of skincare shopping happens, that kind of weight often means a slow first paint and shoppers who leave before they ever reach the product page. I saw you are hiring a CRO specialist. The tests they run will be more trustworthy if the storefront is lighter first. I optimize Shopify images, apps, and theme code without a redesign, and I can show you what is adding the weight. Open to a 15-minute look?
Variant B (insight-led)
Subjects: before the CRO hire / CRO tests need a lighter store
Hi Maria — you are hiring a CRO specialist, which usually means you already care about conversion data. One thing that hire will likely flag early is a 6.8 MB homepage, because heavy pages make test results noisier and slower to read. I work on Shopify speed (images, apps, theme code) so the storefront is lighter before those tests start, with no redesign. If useful, I can walk through what is adding the weight in 15 minutes. Open to that look?
Variant C (curiosity-led; no proof provided)
Subjects: 6.8 MB on mobile / what the 6.8 MB is
Hi Maria — I was looking at the public homepage size, about 6.8 MB, and I am curious how much of that is images, apps, or theme code. On a skincare store, that number often surprises people because it rarely looks heavy in the office. I optimize Shopify storefronts and can spend 15 minutes showing what is contributing to that weight. If it is already on your list for the CRO hire, happy to compare notes. Open to a 15-minute look?
Why each could work
A: leads with the verifiable 6.8 MB problem and ties it to mobile shoppers, then uses the CRO hire only as context.
B: starts from the hiring signal and treats homepage weight as something that hire will run into.
C: stays curious about the same public number and does not invent results, since no proof was provided.
Follow-up #1 (day 3)
Hi Maria — just circling back on the 6.8 MB homepage and the 15-minute look. If the CRO hire is already covering speed, no need to add another call. If not, I am happy to show what is adding the weight.
Follow-up #2 (day 8, polite breakup)
Hi Maria — I will close the loop here so I am not taking more of your time. If a 15-minute look at the homepage weight would still help later, I am easy to reach.
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-5-SONNET
Write short, specific B2B cold emails that sound human. Provide your offer and a prospect's public info; get 3 variants (problem-led, insight-led, social-proof-led), subject lines, and a 2-step follow-up sequence, under 120 words each, no fake familiarity, no hype. Built for founders, freelancers, agencies and SDR agents.
...more
Added 15 hours ago
