CMS Implementations Deck

Obviously, if you picked the last one, you wouldn’t be talking to Blend at all.

Blend most often worked under the first one. Most of Blend’s clients had no internal development capacity.

Building a new, content-managed website is an enormous amount of work. Do you have significant people sitting around with nothing to do? If not, then you’re just never going to get this done internally.

Over and over, we would organizations that insisted they were going to do part of the development themselves. Or sometimes they were doing all of the development, and Blend was just consulting.

I can count on one hand the number of times this actually worked out.

“Agile” is the most over-used word in development. No one agrees on what it means other than, “we won’t wait until things are perfect to show them to you.”

Back in 2000, long before Blend, I built the website for an NFL football team. I worked on it non-stop for six months. The team’s marketing group didn’t see the site until three days before launch. That is an example of what not to do. (Thankfully they liked it, because this was 2000, and the bar for a good website was very low.)

That last point sounds snarky, and I don’t mean it to, but Blend launches 20-30 web projects a year. Most organizations will do one every three years, at most.

Experience matters.

Some organizations try to save money by doing front-end internally. It never works. They don’t do a good job at it, and the integrator has to mess around with the artifacts so much that it would have been faster to do them from scratch.

If you’re working with an integrator using a CMS that they know well, then I promise they have front-end skills that they have honed around that particular CMS, and they will have efficiencies and conventions that you can never duplicate.