Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the it-l10n-ithemes-security-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-layout-styles domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-uploads domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the it-l10n-ithemes-security-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-history domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131 Showcasing OmniIndex’s AI, web3 and blockchain expertise - Case Study | Spreckley
We are experts at telling your story.
Connecting clients with their customers through integrated public relations, content marketing and media relations campaigns.
Showcasing OmniIndex’s AI, web3 and blockchain expertise
The client
OmniIndex is a web3 and blockchain powered data platform that uses AI and patented fully homomorphic encryption technology to ensure data is secure, whilst remaining available to analytics. OmniIndex’s solution allows users to be confident they can use their most sensitive and confidential data when and where they want it, with no risk of exposure.
The goals
At the start of our partnership OmniIndex had no media profile whatsoever, meaning the Spreckley team had to start from the ground up.
The OmniIndex team set out to launch their consumer blockchain product Dropblock within the first two months of working together and needed to follow it with partnership announcements, customer wins and regular commentary on key issues relating to AI, web3 and blockchain to maintain a healthy share of voice.
The solution
Spreckley delivered exceptional coverage across the board within the first 12 months working together. By first raising the profile of OmniIndex’s CEO through reactive opportunities, it allowed the OmniIndex team to build key media relationships to deliver proactive announcements about product launches and partnerships.
Alongside this, Spreckley also maintained a proactive approach to commentary opportunities, responding to the news agenda.
The achievement
Spreckley drafted press releases announcing OmniIndex’s new customer wins and partnerships and launched its new products.
The team also produced a steady stream of thought leadership content and proactively pitched to secure interviews in the likes of Yahoo Finance, The Daily Mail, The Times and more.
