Key Takeaways:

• As a marketer using Kentico, the tasks I handle myself include building campaign pages, publishing blog posts, updating team bios, sending email campaigns, and scheduling content.
• The page builder is the part I use most. Dragging components onto a page and filling in the content fields takes minutes, not hours, and I can preview exactly how it looks before it goes live.
• I still involve the developer for new design components, integration work, and anything structural. But the content side is mine.
• The biggest change from our previous setup: I stopped raising tickets. That alone changed how fast we can move on campaigns.

I want to be upfront about what I am: a marketer, not a developer. I understand enough about websites to be dangerous but not enough to edit a template file without sweating. So when our team moved onto Kentico Xperience, my main concern was whether I would actually be able to do my job without constantly pulling in the developer. Here is what I found.

Monday morning: updating last week's campaign

We ran a lead generation campaign the previous week. Now I need to update the landing page with the new offer, swap the hero image, and change the CTA button text. On our old setup, this was a ticket. It would sit in the queue for a day or two, the developer would make the changes, and by then the moment had passed.

In Kentico, I open the page in the page builder. The hero section is a widget with three fields: headline, supporting text, and image. I update the text, click the image field, pick a new image from the media library (which I have already uploaded from the brief), and save. The CTA button text is another field. I change it, hit preview, check how it looks on mobile, and publish. Elapsed time: about 15 minutes.

WHAT CHANGED

Before Kentico: raise a ticket, wait 1-2 days, review the change, request a tweak, wait again, sign off, deploy. Turnaround: 3-4 days minimum.  With Kentico: open the page, make the change, preview, publish. Turnaround: 15 minutes.  For a campaign with a short window, that difference is the campaign either working or missing the moment entirely.

Publishing a blog post (the full workflow)

We publish articles regularly as part of our content strategy. The workflow in Kentico goes like this: I write the article in a Word document first (old habit), then bring it into Kentico. In the content editor, I paste in the text, format the headings using the toolbar, add the featured image, fill in the SEO title and meta description fields, and set the article category and tags.

Before it goes live, the article sits in draft and goes to the approver in our workflow. They get a notification, they review it in Kentico's preview mode, and they either approve it or send it back with a comment. Once approved, I either publish immediately or set a scheduled publish time. For our Friday articles, I write and schedule them on Wednesday and forget about it.

The honest summary

Kentico is not the simplest tool I have ever used. The first week involved a learning curve, and the developer walked me through the page builder and the content workflow before I was confident. But within a fortnight I was operating independently on content tasks.

The practical test of a CMS for a marketer is simple: does it get out of the way and let you do your job? For the content tasks that make up most of my week, Kentico does. I am publishing more content, running more campaigns, and moving faster than I was before. That is the answer that matters.

Talk to Dapth about Kentico for your marketing team

About Dapth

Dapth helps organisations “unlock business advantage” by connecting customer, employee and operational systems into scalable digital ecosystems. Built on understanding, knowledge and collaboration delivering ROI through efficiency and/or revenue.