a 35-minute WordCamp Ottawa 2014 talk on the Business Track aimed at WordPress freelancers — covering how to pitch WordPress as a CMS, how to handle the predictable security objection, and how to balance technical, creative, and business goals on a single client engagement.
Where and when
- Event: WordCamp Ottawa 2014
- Date: Saturday, May 3, 2014
- Track: Business
- Duration: 35 minutes
- Session page: ottawa.wordcamp.org · sessions
The premise
From the published WordCamp Ottawa 2014 session listing:
“a 35 minute presentation on how to use WordPress to improve the relationship between designers and clients by empowering the client with a fully fledged content management system. We’ll talk about how to pitch WordPress to people as a successful CMS, how to discuss security and other obstacles, and the most common practices how to balance technical, creative, and business goals to deliver powerful, profitable, and manageable WordPress websites.”
Watch or read
This session was not recorded for WordPress.tv.
The sustained argument (reconstructed)
Reconstructed framework. The published abstract sets up four pillars (pitch, security objections, balance, deliverability). The section below presents the talk as a single sustained argument — what problem freelancers faced in 2014, what core claim the talk likely advanced, the supporting reasoning, and the recap outcome — anchored in documented industry context for that year.
1. The problem freelancers faced in 2014
By 2014, WordPress had unambiguously matured into a real CMS — version 3.9 shipped that april, Customizer was becoming central, custom post types and taxonomies were normal — but a meaningful segment of small-business clients still framed it as “blog software.” Freelancers were caught in the middle: pitching against custom-built CMS quotes that were three to five times the price, defending against off-the-shelf SaaS competitors that promised faster setup, and answering the same security objection on every initial call.
2. The core claim
The abstract’s central move was to reframe WordPress as “a successful CMS” — not a blog, not a website builder, but a content management system that the client themselves can operate confidently after launch. The talk’s argument depends on that reframing. Once the conversation is about CMS suitability, the comparison set changes (custom builds, Drupal, proprietary platforms) and so does the price benchmark.
3. The supporting reasoning
- How to pitch: position WordPress against the client’s actual alternatives, not against the abstract idea of “a website.” Concrete comparison sets (custom CMS quote, headless options, SaaS platforms) make the price-to-value argument do the work.
- How to discuss security: address the predictable objection head-on. WordPress installations get attacked in proportion to their visibility. The honest response is to talk about practices — managed hosting, automatic updates, two-factor authentication, principle-of-least-privilege user roles — not to dismiss the objection.
- How to balance technical, creative, and business goals: every client engagement involves three competing pressures. Freelancers who optimise for one of the three on every project deliver fragile work. The argument is for explicit, named trade-offs across all three on every engagement.
4. The recap outcome
The talk’s framing — pitch as CMS, address security plainly, balance trade-offs explicitly — pointed freelancers at recurring-revenue work over one-shot builds. Maintenance, ongoing content support, and incremental improvements compound on a healthy client relationship in a way that one-and-done builds cannot. The recap is less a list of tactics and more a mindset shift: position yourself as a partner the client trusts to operate the CMS with them, not a contractor who hands off a finished site and disappears.
Related work
- adjacent talks by the same speaker on consulting practice: WordCamp Ottawa 2013 — How to Make a Living with WordPress
- Working with the speaker: WordPress services · Get in touch
