Case Story Tips for Partners
Here are some guidelines/tips for creating a good story that other manufacturers/end customers can relate to.
Why are case stories great:
Case stories are highly relatable for other end customers and manufacturers. They show that the solution you offer is working at companies similar to themselves. Getting proof that they are not risking their business by going into robotics. The uncertainty about how an automation solution will work is a major barrier for end customers looking into robotics. Case stories can help to break that barrier.
The goal:
The goal for you should never be creating a professional case story, as it is not necessary. We recommend your goal should be to create a trustworthy story with as little effort as possible. I hope the following tips can help you to reach that goal.
What do you need?
3–5 pictures of the solution
Preferably the solution in production
Pictures from installation or workshop can also be used but do not create the same trust
Don’t need to be professional quality (a smartphone is great)
1 video (30–90 seconds) of the solution palletizing in real-time
Doesn’t have to be fancy
Smartphone video is more than good enough
The solution doesn’t need to do anything special, mainly potential customers just want to see it working
If there’s something special about the installation (gripping multiple boxes, shim paper, custom movements), they can also be nice to show. But should be in the context that the solution does its job of putting boxes onto a pallet
1 picture + quote from engineer/decision-maker about why this solution has been beneficial to their business
This is very important. The picture creates a lot of trust, and the quote even more so.
Potentially get two quotes:
Why did they decide to go into automation?
Are they satisfied with the solution (and why)?
The quote is usually also a good starting point for the article
That’s all you need to get started!
The story:
Inspiration for how you can put an effective angle on the story:
Find an angle that showcases how the solution solved a problem for the end customer.
Fx. labor shortage in this story: https://rocketfarm.no/case-stories/cobot-palletizer-solving-labor-struggles/
Efficiency and costs here: https://rocketfarm.no/case-stories/the-ur-cobots-makes-no-mistakes/
Futureproofing the end-of-line: https://rocketfarm.no/case-stories/how-pally-increased-palletizing-performance-with-30-at-nortura/
The stories don’t need to be long and windy. Short and precise is better. 300–500 words should generally be good for the story, but any length is good as long as it’s relevant.
Include a quote from the end customer and a quote from yourself (including a photo). (Your quote should support the story)
Tips:
Align with the end-user during the sales process if you can be allowed to take photos, videos and use their case in your marketing (it is well worth it, even if they want a discount).
Don’t be afraid to write end-customer quotes that support the story you want to tell. Just be sure to get their approval beforehand. Usually, they’ll agree.
Rocketfarm help
If you have the content (the pictures and quotes) and you have permission, we would be happy to help you finalize your case story.
We can help with a thorough review, finding the right angle to the story, or help with the actual writing. We would only want to also publish the story on our webpage and through our channels.
Please reach out directly to martin@rocketfarm.no if you would like our help with a potential case story.
Â