Please ensure Javascript is enabled for purposes of website accessibility

Six Things a CIO Should Sign Off Before Choosing a CMS

headline for Six Things a CIO Should Sign Off Before Choosing a CMS

The public website tends to reach the CIO as a platform question. Marketing wants a redesign, the current CMS is due for an upgrade, and someone asks IT to choose between WordPress, a headless stack or whatever the last vendor recommended. The platform gets chosen in a few meetings, and everything that actually determines whether the project works gets decided later, by default. 

A replatform is an operating decision before it is a technology decision. It sets who can publish what, which systems the site talks to, what it costs to run, and what happens to years of search visibility. Those are IT’s questions as much as marketing’s, and they are far cheaper to answer before a vendor is chosen than after. 

At Crafted we design and build websites and platforms for universities, nonprofits and brands, and the platform is one of the last things we settle. These are the six decisions we ask a technology leader to own first. 

Key Takeaways

  • A replatform is primarily an operational decision, determining ownership, integrations, and budget before selecting a technology vendor.
  • Decide ownership of content creation and approvals to prevent chaotic site management after launch.
  • Identify all necessary integrations upfront; this drives platform choice and informs the budget for custom development.
  • Include measurable standards in contracts, such as accessibility and performance metrics, to ensure accountability and prevent future issues.
  • Plan for ongoing costs and support beyond launch, securing a service level agreement to manage performance and updates effectively.

1. Decide who owns what after launch 

person giving 5 stars from cms

Most website arguments are ownership arguments. Marketing owns the message. IT owns the platform, the security and the uptime. Neither team usually owns the space between them: who can create a new type of page, who approves a new integration, who decides when a plugin or package gets added. 

Write that down before the build. A simple model works: editors can build any page from an approved set of components; a new component requires a design review and a technical review; anything that touches personal data or authentication goes through IT. When we build, every page is assembled from custom blocks designed for that brand, so editors get real freedom inside limits that protect the design, the performance and the security. The governance is built into the tool rather than enforced by email. 

If no one can say who approves a new component, the site will slowly fill with one off pages, unreviewed scripts and plugins nobody remembers installing. 

2. Count the integrations before the platform 

The CMS is rarely the hard part. The connections are. List every system the site has to touch: CRM, marketing automation, single sign on, ERP or product data, search, analytics, consent management, payments, and any internal tools that feed content in. Then note which direction the data flows, who owns each system, and what happens when one of them is down. 

That list should drive the platform choice and the budget, and it often decides whether you need custom web development or can work with what a standard platform already supports. 

Two examples from our own work show how specific this gets. For The New York Times corporate subscriptions page, the visitor’s journey through the page was tracked and tied to a dynamic phone number, so when a prospect called, sales already knew what they had told the site. For Syracuse University’s online programs, we designed and built landing pages as templates for Wagtail, the university’s own Django based CMS, with every form feeding Slate, their admissions CRM, and every page tagged in Google Tag Manager. The templates were handed to the university’s developers to deploy. In both cases the integration was the brief, not a detail added at the end. 

3. Decide whether you run one site or a portfolio 

Many organizations do not have a website. They have several: a corporate site, brand or product sites, regional sites, microsites from old campaigns, each with its own templates, logins and hosting bill. A replatform is the moment to decide whether that portfolio should become one platform. 

BioZyme, an animal nutrition company, came to us with seven brands, each on its own WordPress build. We moved the corporate site and every brand onto one headless Craft CMS platform where the brands share components, product data and publishing tools. Content is published once and assigned to a brand, and deployment runs from GitHub. Each brand keeps its own color, mark and voice; IT maintains one codebase instead of seven. 

Consolidation is not always right, and neither is headless. We recommend headless when content has to feed several channels, when the front end team already works in React, or when performance demands it. Plenty of organizations go headless for a gain a well built custom theme would have delivered at lower cost. The decision belongs in the requirements, not in a vendor’s pitch. 

4. Put the standards in the contract as numbers 

“Fast”, “accessible” and “secure” are not requirements. Numbers are. Before the build, agree on the standards the site will be accepted against and put them in the statement of work: 

  • Accessibility to WCAG 2.1 AA, which universities, government bodies and nonprofits increasingly need to demonstrate. 
  • A performance budget, such as Largest Contentful Paint under 2.5 seconds and Cumulative Layout Shift under 0.1, tested on a mid range phone rather than a developer’s laptop. 
  • A security baseline: patching cadence, who holds administrator access, how dependencies are reviewed, and where the site is hosted. 

These give IT a way to accept or reject the work on evidence. They also stop the slow erosion that happens after launch, when every new script or embed adds a little weight and nobody is measuring. 

5. Protect what search engines and users already know 

A replatform changes URLs, page structures and tracking. Handled carelessly, it can wipe out years of search visibility and break every bookmark, printed QR code and link from a partner site. 

Treat the old site as an asset to migrate, not a building to demolish. Inventory every URL that earns traffic or links, map each one to its new home before launch, and test the redirects as part of acceptance rather than as cleanup. On the BioZyme platform, every legacy URL across the brand sites was mapped before launch. Do the same for analytics: decide which events and conversions must survive the move, and confirm they report correctly on day one. 

If the site serves several countries, the language model belongs in this decision too. For Tishman Speyer’s global site, every country had its own language, which shapes the URL structure, the editorial workflow and who approves translated content. 

6. Budget for year two before signing year one 

Launch is the midpoint of a website’s cost, not the end. The site will need security patches, dependency updates, new components as the business changes, and someone watching performance and search after the agency has moved on. 

Every engagement we take on includes support backed by a service level agreement: monthly performance reviews, security patching, training for the content team and a quarterly review of the roadmap. Whoever you work with, the questions are the same. Who patches the site? Who answers when the CRM integration fails at nine on a Monday? Who is accountable for the performance budget twelve months from now? If the answers are vague, the total cost of the project is unknown. 

Read Next

A few related pieces worth your time:

What to sign 

Before the platform is chosen, a CIO should be able to sign one page that answers six questions: who owns what, what the site connects to, how many sites it replaces, which standards it will be accepted against, how existing URLs and data will move, and who runs it in year two. 

With that page signed, choosing the CMS becomes a short conversation, because the requirements have already made most of the decision. Without it, the platform will be chosen on preference, and the real decisions will be made one at a time, under deadline, by whoever happens to be in the room. 

Peter Mendez is the founder of Crafted, a design and development agency that builds websites and platforms for universities, nonprofits and brands. 

Subscribe

* indicates required
Previous articleElastic Earnings Beat Estimates, but Guidance Sinks the Stock
Bailey 'Bails' Thomas
Bailey Thomas is a data scientist using large databases, visualization platforms and analytical tools for predictive modeling. He has experience working for Fortune 500 and other private companies. Bailey was also a professional eSports player who played Starcraft 2 competitively across the globe. He was ranked #1 of millions of players in North and South America. He travelled across North America and Europe for notable tournaments, to include DreamHack, MLG, Red Bull Battlegrounds. Bailey has a Bachelor’s degree, where he double-majored in Business Analytics and Finance from the University of Kansas.