Your Umbraco Gold
Partner in the UK & Dubai.

Recognised Umbraco expertise — Cold Banana is an Umbraco Gold Partner. Our work spans new platforms, integrations and ongoing support, with published projects across the Middle East and the UK.

A clear brief before a build — Bring your marketing, operations and technology teams into the conversation early. We help turn their needs into a shared scope, with visible decisions about content, integrations and delivery.

A team you can work with — Agree responsibilities, review points and how decisions will be made. Whether we work alongside your internal developers or lead the build, the project should have clear ownership.

A roadmap for what comes next — Launch is one milestone. Plan for platform maintenance, content changes and the improvements your customer data reveals, with support shaped around your business.

A considered agency handover — Review source code, hosting, deployment access and integrations before taking responsibility. Capture outstanding problems and the information your team needs to run the platform confidently.

Maintenance with a clear priority — Assess updates, bugs and dependencies against their effect on your business. Agree response arrangements, scheduled maintenance and a release process as part of your support plan.

Connected systems that stay connected — Investigate lead journeys, booking flows and the movement of business data. Use monitoring and clear diagnostics to make integration problems easier to identify.

Improvement alongside support — Turn recurring requests into a manageable roadmap. That might mean a better landing page builder, faster content journeys or a more useful reporting setup.

Understand the starting point — Review the current Umbraco version, custom code, packages and hosting. Establish which parts can be retained and which need rebuilding before choosing a target release.

Give content a clear destination — Inventory pages, media, languages and structured data. Map them to the new content model, run trial migrations and let editors check real examples before cutover.

Plan for search continuity — Create a redirect map, review canonical URLs and metadata, and check key landing pages. Monitor the change after launch; a migration should include a plan for search as well as content.

Rehearse the release — Test integrations, forms and critical customer journeys in a separate environment. Agree content freeze, backups, responsibilities and rollback criteria before the release window.

What is Umbraco Cloud? — Umbraco Cloud is a managed platform for running Umbraco CMS on Microsoft Azure, with tools for deployment, content synchronisation and project management.

Plan the right environment — Review hosting regions, traffic, integrations and recovery needs with your team before choosing a plan. Include the applications connected to the CMS in that discussion.

Make releases repeatable — Agree how developers test changes and how editors prepare content. Set out the release steps and responsibilities so the team knows what moves between environments.

What is Umbraco Engage? — Umbraco Engage brings analytics, visitor profiling, personalisation and A/B testing into the Umbraco backoffice. Capabilities depend on the selected plan.

Start with a specific decision — Choose an enquiry journey, campaign or important content page. Agree the question, the audience and the measure of success before creating variants or rules.

Build a practical testing programme — Plan data collection, audience rules and reporting alongside your content. Review traffic levels, consent requirements and the time needed to learn before scheduling tests.

What is Umbraco Workflow? — Umbraco Workflow adds structured, multi-stage content approvals to the CMS, with review ownership, tasks and notifications in the backoffice.

Map the real approval process — Define who reviews each type of content, how translated pages are handled and who covers an absent approver. Keep the process proportionate to the content being published.

Give editors a workable process — Configure and test everyday scenarios with the team. Include a rejected change, a revised draft and a time-sensitive update so the process is understood before rollout.