Talk about your next project
Scratchpad case study

The lesson

Put the customer's tech stack and use cases in a strip under the headline so a buyer can check fit before reading the story.

The move

The headline states the outcome, followed by two paragraphs on what Memfault builds and how the Nordic Semiconductor acquisition made its sales process more complex. A three-column strip follows: 'INSIGHTS FROM' with Oliver Levin's photo and role, 'USE CASES' and 'TECH STACK'. The body moves through 'The challenge: manual CRM work was stealing time from selling', 'Key pain points before Scratchpad', 'What Scratchpad powers for Memfault' and 'After Scratchpad: from admin burden to execution engine', with a boxed Levin quote after most sections and dark product image blocks between them. It closes on a bolded 'Results' list and 'Advice for other sales teams', then a grid of 'More customer stories'.

Why it works

  • Our readThe tech stack column naming Salesforce, Slack, GSuite and Gong tells a buyer whether the setup matches their own before they read any copy.
  • Our readThe challenge is tied to a concrete change, selling hardware alongside software, so the CRM pain reads as a consequence of the business rather than a generic complaint.
  • Our readThe pain points list and the Results list use the same bolded lead-in format, so a skimmer can match each problem to what changed.

What not to copy

Don't copy Memfault's hardware and chipset details, the MEDDPICC framing, or the Monday Slack digest specifics. Keep the outcome headline, the profile strip of speaker, use cases and tech stack, the before-and-after sections with a quote after each, a bolded results list and a closing advice quote.

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.