<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[AmazeRealise - Medium]]></title>
        <description><![CDATA[AmazeRealise is an award-winning end-to-end experience agency headquartered in the UK with offices in London, Edinburgh, Manchester, Liverpool and Chicago. A member of the Kin + Carta plc connective we seek to create connected experiences that transform businesses. - Medium]]></description>
        <link>https://medium.com/amazerealise?source=rss----f2c67dcc9270---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>AmazeRealise - Medium</title>
            <link>https://medium.com/amazerealise?source=rss----f2c67dcc9270---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:38:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/amazerealise" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why we love Contentful (and you should too…)]]></title>
            <link>https://medium.com/amazerealise/why-we-love-contentful-and-you-should-too-d3b319627fc4?source=rss----f2c67dcc9270---4</link>
            <guid isPermaLink="false">https://medium.com/p/d3b319627fc4</guid>
            <category><![CDATA[headless]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[contentful]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Martin Paton]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 15:30:45 GMT</pubDate>
            <atom:updated>2019-01-08T15:27:41.747Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are AmazeRealise, we’re big fans of Contentful, the content infrastructure provider for modern digital experiences, and to get the shameless plug out of the way, we’re immensely proud to be working with them and our clients as a leading partner with certified developers.</p><p>Contentful is an attempt to provide a cure for the “one size fits all” path that CMS/CXM vendors have travelled over the last 5 years, strip back to basics, and place the control back into the hands of the developers and content authors who are the primary “actors” in any such system, and well it does it rather well.</p><p>Here I attempt to break down how I see Contentful addresses some key challenges you may find with more traditional CMS platforms.</p><h3>You can get started immediately</h3><p>Contentful is a true self-service, SaaS product, with low number of moving parts that need any sort of configuration. Billing details and API key generation is about where it ends.</p><p>This means you can get started building and populating your content model in minutes. This has a significant positive impact to your overheads and time to value unlike other systems which claim to be SaaS, but in reality require days or even weeks of configuration by the vendor before you can begin.</p><p>As Contentful uses a standard JSON data model, developers can even begin mocking the data even before you have signed up and created the actual production model.</p><h3>Laser sharp focus: Content creation and delivery</h3><p>What very often happens when organisations procure a CMS/CXM system, is that a lot of domain functionality outside the core CMS is procured as part of the sales deal, but then ignored in favour of a much more specialist product, or one which the organisation has been using for some time — for example CRM, DAM, Personalisation, Search, Commerce, etc,</p><p>By focusing on creating and delivering content only through standards compliant APIs, and remaining integration-neutral, the freedom of choice of integrations to and from your core applications remains solely yours in the shape and style of your choice.</p><p>Some examples</p><ul><li>Pushing content to social channels</li><li>Generation of automated, personalised landing pages using VWO or Optimizely</li><li>Generate personalised newsletter content based on customer profile preferences from SalesForce</li><li>Pushing product details to an ERP such as SAP B1</li><li>Leveraging IBM Watson to automate and create content meta-tags</li></ul><p>All the above would nearly always require the procurement of a third-party tool, additional licensing, significant specialist development resource with other platforms and may be akin to the sledgehammer/nut analogy. With Contentful, development is still required, but it is much more on-point to the use case.</p><h3>Omni-channel is the default behaviour</h3><p>The sole objective of Contentful is to allow you to use your content anywhere with as many obstacles removed from the process as possible. If you can think of a “channel” and it can consume an API, you can use it to deliver content from Contentful.</p><h3>You are not constrained or locked-in by vendor proprietary technology</h3><p>This is the big one for architects and developers.</p><p>Most CMS platforms impose some sort of specific architecture, deployment process, proprietary backend technology, ways of working that means you need extremely experienced, hard to find (read: costly contractors) people to run your projects — this creates budget challenges, creates vendor lock-in, and makes it difficult to leverage new technologies that can add value to your business and may lead to a large replatforming exercise down the line when the promised roadmap fails to materialise.</p><p>Contentful is almost 100% un-opinionated on how you develop your application, save that you can consume a JSON API.</p><ul><li>Want to create a standard MVC website? Check.</li><li>Want to create a complex React, Redux driven SPA? Check.</li><li>Want to adopt the latest in static site generators using serverless technologies? Check.</li><li>Want to deploy a private iOS intranet application inside your firewall? Check.</li><li>Moving to a containerised application strategy with K8s? Check.</li></ul><p>You get the picture.</p><p><em>Want to talk more about this? Want to hear how AmazeRealise has helped some of the leading organisations get back the freedom to innovate? Maybe you already have Contentful and and just want to chat about best practices? Contact me at </em><strong><em>martin.paton@amazerealise.com</em></strong><em> or head over to my LinkedIn profile for a chat — </em><a href="https://www.linkedin.com/in/martinpaton/">https://www.linkedin.com/in/martinpaton</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3b319627fc4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazerealise/why-we-love-contentful-and-you-should-too-d3b319627fc4">Why we love Contentful (and you should too…)</a> was originally published in <a href="https://medium.com/amazerealise">AmazeRealise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing new CMS/CXM this year? Here’s 4 points to consider.]]></title>
            <link>https://medium.com/amazerealise/implementing-new-cms-cxm-this-year-heres-4-points-to-consider-8c2918a68691?source=rss----f2c67dcc9270---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c2918a68691</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[requirement-analysis]]></category>
            <category><![CDATA[outcomes]]></category>
            <dc:creator><![CDATA[Martin Paton]]></dc:creator>
            <pubDate>Tue, 08 Jan 2019 15:19:38 GMT</pubDate>
            <atom:updated>2019-01-08T15:19:38.086Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been travelling the world helping organisations implement CMS/CXM platforms in some way for the best part of 15 years now and with the landscape as diverse and complex as ever, I hope the following will help guide you towards a successful CMS/CXM implementation in 2019.</p><h3>Focus on highest-value, measurable outcomes not lists of features the platform should support</h3><p>Working in an agency, I have personally been on the receiving end of unending lists of MOSCOW prioritised requirements a platform <em>must</em>, <em>should</em> or <em>could </em>have which are often just lists of features with no qualitative or quantitative measures that prove implementing the feature will have a positive effect on the user.</p><p>By way of a bad example:</p><blockquote>The platform must support WYSIWYG</blockquote><p>Great! We can put a tick-box against this one and move on, completely missing the point of <em>why</em> one would like the platform to support WYSIWYG and why one thinks including it would add a positive business benefit:</p><p>A slightly better outcome-driven example of the same requirement</p><blockquote><em>We believe implementing a visual editor will allow authors to create a page with fewer defects during the approval process which should reduce the overall time to create a page meaning our editors can create more pages per day at a higher, more consistent quality. Success will be measured as an increase in the number of pages published per day with a downward trend in the number of defects at approval</em></blockquote><p>Now we can at least attempt to prove that the addition of WYSIWYG is a beneficial thing to have. Of course, in an ideal world we’d have historical datasets and a control, but we need to start somewhere.</p><p>Broken down this translates to</p><p><em>[hypothesis] — [desired outcome] — [how it will be measured]</em></p><p>Thinking in an outcome driven way over lists of features will sharpen your thinking towards developing and prioritising hopefully fewer backlog items that can be measured correctly and add genuine positive benefit rather than be a waste of time and money.</p><h3>Don’t rely on the sales demo</h3><p>Sales demos have been very carefully tailored to artificial scenarios over a long period of time. They will undoubtedly look impressive, but may be gloss over hidden issues that surface at time of implementation which in the worst case could leave you high and dry.</p><p>Focusing on outcomes over features again plays a key role in avoiding this pitfall. Work the vendor and ask for a tailored demonstration and gain proof that the implementation will support your desired outcome. If this proof requires development that is beyond fair investment by the vendor it may be worth setting aside a small budget to allow for your implementation expert partner to create spikes or more involved POCs.</p><p>This approach will almost always pay off in the long run — it will significantly reduce the risk of a failed project and also allow you to see in more detail how the vendor works and where any issues or concerns may arise so you can head these off before getting into the meat of the project delivery.</p><h3>Cost everything out in detail</h3><p>Implementing a platform has many cost facets. It’s tempting to focus purely on the ticket price of the platform plus the agency implementation cost.</p><p>However there are a lot of hidden costs that will need to be budgeted and set off against any ROI predictions — items like staff costs, lost opportunity costs, staff reassignment, data cleansing, migration, business process re-engineering, retraining and staff ramp-up, new ways of working alignment, etc. All must be accounted to give as much accuracy and visibility to the C-suite. Plus with modern platforms being almost entirely SaaS, you need to play the black magic game and predict your usage sensibly to both avoid over-specifying on one side, and a hefty bill on the other.</p><h3>Work out a realistic implementation roadmap and don’t underestimate the implementation itself</h3><p>Todays platforms come bursting with promises of “out of the box” end-to-end marketing automation, personalisation, AI, etc. Whilst the power this places into the hands of the marketing and development team is undeniably immense, it doesn’t all happen from day one and the phrase “out of the box” should be treated with extreme caution. It may well be in the box, but the implementation that fits your business ambition almost certainly won’t be.</p><p>Be realistic about what you can achieve in the first 6–12 months.</p><p>Getting the architecture right is crucial to allow scalability and avoid cul-de-sacs. Capturing enough data to make AI systems effective is constrained mostly by time and optimising your CX will require much manual experimentation before you can unleash automated AB optimisations. Don’t be afraid to change things that obviously aren’t working but do allow time for the platform to bed in so you can start to see trends emerging against your outcomes, and finally remember to get your measures in a dashboard that are transparent to all stakeholders.</p><p><em>Martin Paton is CTO of AmazeRealise, ranked as the EConsultancy #1 B2B D&amp;B agency 2018 and part of the Kin+Carta global connective where by combining strategy, innovation, and communication we help you create and market the digital products and services your customers demand by delivering specialist when and where you need it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c2918a68691" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazerealise/implementing-new-cms-cxm-this-year-heres-4-points-to-consider-8c2918a68691">Implementing new CMS/CXM this year? Here’s 4 points to consider.</a> was originally published in <a href="https://medium.com/amazerealise">AmazeRealise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>