Platform Politics: Seven Questions That Expose What Your Agency Really Thinks About Your CMS

Here's something most agency pitch decks will not mention: by the time your redesign conversation starts, the platform decision may already be made. Not by you, and not based on your requirements—but by the agency's partner certifications, the developers currently on payroll, and the margin structure baked into their delivery model.

This isn't necessarily corruption. It's incentives. Agencies get referral commissions and listing placement from certain platforms. Rebuilding a team's expertise in a new CMS costs real money. And a shop that has shipped fifty WordPress sites will genuinely believe WordPress is right for you—familiarity feels a lot like objectivity from the inside. The trouble starts when a client's actual needs diverge from the agency's comfortable answer.

Seven questions will tell you which kind of agency you're talking to.

1. "What platforms did your last five builds use, and why?"

Red flag: All five were the same CMS, and the reasoning is generic—"it's the most flexible" or "it's what we recommend." Uniformity plus vague justification means the platform drives the recommendation, not the reverse.

Strong answer: A genuine mix, with platform-by-platform reasoning tied to client specifics—content velocity, team size, e-commerce complexity. Shops with real range can articulate why each project landed where it did.

2. "Are you a certified partner with any CMS vendor? What does that relationship include?"

Red flag: "No partnerships" is fine; evasion is not. If they dodge the question about referral fees or partner-tier benefits, assume the answer costs them something.

Strong answer: Direct disclosure. "We're a Webflow Premium partner and yes, we receive referral benefits—here's how we account for that in recommendations." Disclosure doesn't eliminate bias, but it invites scrutiny, which is the point.

3. "If we chose a platform you don't typically build on, what would happen?"

Red flag: A immediate list of reasons your choice is risky, delivered with unusual speed and no questions about your requirements. That's not analysis; it's defense of the home turf.

Strong answer: An honest accounting—"we'd need to bring in a contractor or upskill, which adds cost and timeline, and here's the tradeoff." Every agency has a comfort zone. The good ones will tell you where it is and what crossing it costs.

4. "Who owns the CMS account, the hosting, and the code?"

Red flag: Anything involving the agency's own proprietary platform, or "we'll handle all of that." Proprietary builds turn every future change into a negotiation with your current vendor.

Strong answer: You own everything—accounts, code repository, hosting—in your name, from day one. Full stop.

5. "What happens to our total cost of ownership in year three?"

Red flag: The conversation only covers launch. Platform economics diverge sharply over time: plugin licensing and maintenance sprawl on WordPress, per-seat and traffic-based costs on some SaaS platforms, and ongoing dev hours on custom builds. An agency that hasn't modeled year three hasn't done the work.

Strong answer: A cost projection covering licensing, hosting, maintenance, and typical content-editor hours, with the assumptions spelled out.

6. "Who on your team would actually build this, and what's their experience with this specific platform?"

Red flag: The pitch was led by a platform expert; the delivery team is not that person. Platform expertise at the agency level means nothing if it isn't on your project.

Strong answer: Named people, with shipped work on that exact CMS, who will still be there at launch.

7. "Under what conditions would you tell us not to use your recommended platform?"

Red flag: No conditions, or a pause while they construct one. Every platform has a failure mode—WordPress under complex transactional logic, Shopify when content-heavy publishing dominates, custom builds when budgets are lean. An agency that can't name the failure mode hasn't stress-tested its own recommendation.

Strong answer: An immediate, specific scenario: "If your team needed to publish twenty articles a week with complex taxonomies, I'd steer you away from X because..."

What This Means for Your Next Redesign

None of this means WordPress, Webflow, Shopify, or custom builds are wrong—they're each excellent within their lanes. It means the recommendation should be downstream of your requirements, not upstream of the agency's business model. Ask the seven questions, listen for specificity over fluency, and weight heavily the one answer almost no biased agency can fake: a clear, unprompted description of when their preferred platform is the wrong choice.