M
Maria Sweeney
Guest
Find a familiar name in Forrester’s “The Content Management Systems Landscape, Q3 2026.”
Progress Software, the company behind Progress Sitefinity CMS and trusted provider of AI-powered digital experience and infrastructure software, is recognized among 30 notable vendors in Forrester’s The Content Management Systems Landscape, Q3 2026.¹ We’re pleased to be included as enterprises consider how their content platforms should support their next stage of growth.
For teams evaluating a CMS, AI brings some practical questions into that decision. How will customers find and use your content? Where could AI improve the work of your marketing team? And how will you manage the information and processes behind those experiences?
Our view is that enterprises need a practical way to build on their existing content, systems and governance. A new capability has to earn its place through the value it delivers to customers and the people running the website.
Forrester describes CMS platforms as delivering digital experiences and structured content to both human and machine audiences.¹
That gives marketing teams another reason to look closely at the information they publish. A product description needs to make sense on the website, but also when it is retrieved as part of an answer to a specific question. Clear language, consistent facts and identifiable sources all deserve attention.
Consider a manufacturer maintaining product specifications, technical documentation and support articles across several websites. A customer trying to establish whether a component is suitable for a particular application may need information from all three. If the specifications conflict or the documentation is out of date, the customer has to resolve the uncertainty.
Before adding an AI experience, the manufacturer needs to know which information is authoritative, who maintains it and how updates are handled. Those decisions are part of content management and they influence how useful the resulting experience can be.
For discoverability, the CMS should also help teams describe their content consistently. Sitefinity CMS supports Schema.org markup for pages and supported content types, with content fields mapped to machine-readable properties such as author, publication date and description.
That gives teams a way to maintain descriptive markup alongside their content. The editorial work remains just as important: answering the customer’s question clearly and keeping the answer up to date.
The report identifies organizational challenges as the biggest obstacles to operationalizing AI in CMS environments.¹
For a digital team, those challenges become familiar questions. Who approves an AI-assisted update? Which sources should an assistant use? Who needs to act when information changes? What happens when a process crosses from marketing into product management or customer support?
These questions deserve a place in the evaluation. A demonstration becomes much more useful when the people responsible for the work can see how their role would change.
Take content review. If editors regularly send work back for search optimization, there may be an opportunity to address those issues earlier. The Sitefinity CMS SEO Agent provides suggestions within the editing experience. Editors can preview, apply or dismiss them.
The practical test is whether that assistance improves the review process. Does it reduce repeated corrections? Does the editor spend less time preparing an item for publication? Is the reviewer satisfied with the result?
Approval responsibilities also need to remain clear. Sitefinity CMS supports configurable, automated approval workflows by site, language, content type and pages, with users or roles assigned to review stages. A regional event update and a change to a financial product page can follow processes appropriate to their requirements.
There is also an opportunity to help customers use the information an organization has already invested in creating.
Sitefinity CMS connects with Progress Agentic RAG to make selected content available for AI-powered retrieval and answers. Retrieval-augmented generation (RAG) uses retrieved source material to inform a generated response. Administrators can select the sites and content types included in the connection.
For the manufacturer, a possible application is helping customers find answers across product information and technical documentation. The team can define the source material, test representative questions and assess whether the responses help customers complete their research.
Search and answers are one application. Another is adapting the page experience to what a visitor is trying to accomplish.
The Sitefinity CMS Dynamically Generated Experience capability uses a visitor’s expressed intent to retrieve relevant CMS content and assemble page sections in real time. Editors define the layouts and presentation formats, such as summaries, FAQs or content cards. Available with a Sitefinity AI subscription for supported ASP.NET Core and Next.js implementations, it provides a way to create hyper-personalized experiences within the website.
A manufacturer could, for example, use that approach to present relevant information in response to a visitor’s description of an application. The implementation would need testing against actual customer questions and product information, with a clear view of what a useful response should contain.
The business objective gives each of these capabilities a purpose: helping someone find the information they need to make a decision or take the next step.
A CMS investment also has to account for the websites, campaigns and business systems already in use. Teams need to understand how content will move, which connections must be maintained and who will own the work after launch.
For Sitefinity Cloud customers, the Sitefinity Integration Hub, built on Workato, supports connections and automated workflows with other business applications through a visual designer, which is one option for addressing processes that extend beyond the CMS.
During an evaluation, it is worth following a real update through those systems. Where does the information originate? Who can change it? How does it reach the website? Who is responsible if the process fails?
These details affect the team’s workload and the ongoing cost of running the platform. They should be part of the business case alongside the customer experience you want to deliver.
A useful next step is to choose a problem your organization can describe and measure. Customers may struggle to find technical answers. Regional teams may duplicate content work. Editors may spend too much time coordinating reviews.
Bring that problem, a sample of the content and the people responsible for it into the demonstration. Ask to see the sources, the editor’s work and the controls behind the experience. Agree on what improvement would look like, whether that is a higher rate of completed customer tasks, less rework or a shorter publishing cycle.
That gives everyone a concrete basis for assessing the investment. It is also the conversation we want to have with organizations considering Sitefinity CMS.
If you want to explore how these capabilities could address your content and customer experience needs.
Request a Sitefinity CMS Demo
¹ The Content Management Systems Landscape, Q3 2026, Forrester Research, Inc., Chuck Gahun with Fiona Swerdlow, Sarah Morana and Nicole Lesperance, September 14, 2026.
Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change. This report is part of a broader collection of Forrester resources, including interactive models, frameworks, tools, data, and access to analyst guidance. For more information, read about Forrester’s objectivity here.
Continue reading...
Progress Software, the company behind Progress Sitefinity CMS and trusted provider of AI-powered digital experience and infrastructure software, is recognized among 30 notable vendors in Forrester’s The Content Management Systems Landscape, Q3 2026.¹ We’re pleased to be included as enterprises consider how their content platforms should support their next stage of growth.
For teams evaluating a CMS, AI brings some practical questions into that decision. How will customers find and use your content? Where could AI improve the work of your marketing team? And how will you manage the information and processes behind those experiences?
Our view is that enterprises need a practical way to build on their existing content, systems and governance. A new capability has to earn its place through the value it delivers to customers and the people running the website.
Enterprise Content Now Serves People and AI Systems
Forrester describes CMS platforms as delivering digital experiences and structured content to both human and machine audiences.¹
That gives marketing teams another reason to look closely at the information they publish. A product description needs to make sense on the website, but also when it is retrieved as part of an answer to a specific question. Clear language, consistent facts and identifiable sources all deserve attention.
Consider a manufacturer maintaining product specifications, technical documentation and support articles across several websites. A customer trying to establish whether a component is suitable for a particular application may need information from all three. If the specifications conflict or the documentation is out of date, the customer has to resolve the uncertainty.
Before adding an AI experience, the manufacturer needs to know which information is authoritative, who maintains it and how updates are handled. Those decisions are part of content management and they influence how useful the resulting experience can be.
For discoverability, the CMS should also help teams describe their content consistently. Sitefinity CMS supports Schema.org markup for pages and supported content types, with content fields mapped to machine-readable properties such as author, publication date and description.
That gives teams a way to maintain descriptive markup alongside their content. The editorial work remains just as important: answering the customer’s question clearly and keeping the answer up to date.
Putting AI to Work Starts with the Team’s Responsibilities
The report identifies organizational challenges as the biggest obstacles to operationalizing AI in CMS environments.¹
For a digital team, those challenges become familiar questions. Who approves an AI-assisted update? Which sources should an assistant use? Who needs to act when information changes? What happens when a process crosses from marketing into product management or customer support?
These questions deserve a place in the evaluation. A demonstration becomes much more useful when the people responsible for the work can see how their role would change.
Take content review. If editors regularly send work back for search optimization, there may be an opportunity to address those issues earlier. The Sitefinity CMS SEO Agent provides suggestions within the editing experience. Editors can preview, apply or dismiss them.
The practical test is whether that assistance improves the review process. Does it reduce repeated corrections? Does the editor spend less time preparing an item for publication? Is the reviewer satisfied with the result?
Approval responsibilities also need to remain clear. Sitefinity CMS supports configurable, automated approval workflows by site, language, content type and pages, with users or roles assigned to review stages. A regional event update and a change to a financial product page can follow processes appropriate to their requirements.
Making Enterprise Content More Useful with Sitefinity CMS
There is also an opportunity to help customers use the information an organization has already invested in creating.
Sitefinity CMS connects with Progress Agentic RAG to make selected content available for AI-powered retrieval and answers. Retrieval-augmented generation (RAG) uses retrieved source material to inform a generated response. Administrators can select the sites and content types included in the connection.
For the manufacturer, a possible application is helping customers find answers across product information and technical documentation. The team can define the source material, test representative questions and assess whether the responses help customers complete their research.
Search and answers are one application. Another is adapting the page experience to what a visitor is trying to accomplish.
The Sitefinity CMS Dynamically Generated Experience capability uses a visitor’s expressed intent to retrieve relevant CMS content and assemble page sections in real time. Editors define the layouts and presentation formats, such as summaries, FAQs or content cards. Available with a Sitefinity AI subscription for supported ASP.NET Core and Next.js implementations, it provides a way to create hyper-personalized experiences within the website.
A manufacturer could, for example, use that approach to present relevant information in response to a visitor’s description of an application. The implementation would need testing against actual customer questions and product information, with a clear view of what a useful response should contain.
The business objective gives each of these capabilities a purpose: helping someone find the information they need to make a decision or take the next step.
Introducing New Capabilities into an Existing Operation
A CMS investment also has to account for the websites, campaigns and business systems already in use. Teams need to understand how content will move, which connections must be maintained and who will own the work after launch.
For Sitefinity Cloud customers, the Sitefinity Integration Hub, built on Workato, supports connections and automated workflows with other business applications through a visual designer, which is one option for addressing processes that extend beyond the CMS.
During an evaluation, it is worth following a real update through those systems. Where does the information originate? Who can change it? How does it reach the website? Who is responsible if the process fails?
These details affect the team’s workload and the ongoing cost of running the platform. They should be part of the business case alongside the customer experience you want to deliver.
Bring a Business Problem into the Demonstration
A useful next step is to choose a problem your organization can describe and measure. Customers may struggle to find technical answers. Regional teams may duplicate content work. Editors may spend too much time coordinating reviews.
Bring that problem, a sample of the content and the people responsible for it into the demonstration. Ask to see the sources, the editor’s work and the controls behind the experience. Agree on what improvement would look like, whether that is a higher rate of completed customer tasks, less rework or a shorter publishing cycle.
That gives everyone a concrete basis for assessing the investment. It is also the conversation we want to have with organizations considering Sitefinity CMS.
If you want to explore how these capabilities could address your content and customer experience needs.
Request a Sitefinity CMS Demo
¹ The Content Management Systems Landscape, Q3 2026, Forrester Research, Inc., Chuck Gahun with Fiona Swerdlow, Sarah Morana and Nicole Lesperance, September 14, 2026.
Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change. This report is part of a broader collection of Forrester resources, including interactive models, frameworks, tools, data, and access to analyst guidance. For more information, read about Forrester’s objectivity here.
Continue reading...