Clio Websites

Mentioned, not specified.

The site answers the 'how long until launch' part in detail but is silent on current availability and how soon work could start after an inquiry. Launch timelines: 'Most projects take 4–8 weeks from kickoff to launch' for a standard five-page brochure site; a 10–20 page business site runs 4–12 weeks; anything over 20 pages or with custom functionality, plus e-commerce builds, runs 8–16 weeks. The eCommerce FAQ confirms 'Our projects usually take between 4-8 weeks to complete. From start to launch!' These ranges assume content is ready before kickoff — 'A site with content ready on day one and fast feedback lands at the bottom of its range,' while late content and piecemeal feedback push toward or past the upper end. However, no chunk states whether Clio Websites is currently taking on new projects, whether there is a waitlist or booking queue, or how quickly a kickoff could happen after reaching out this week. The closest adjacent guidance is 'Start planning before you need the finished site,' which implies projects benefit from lead time rather than promising immediate starts. A buyer would need to contact the agency directly (the site links to a Contact Us page) to learn current availability and start dates.

Mentioned, not specified.

Partially. Clio's site contains a 'Real Calgary Business Case Studies: ROI Results You Can Expect' section inside its blog article on Calgary website design ROI, which describes anonymized client outcomes — e.g., 'a specialty food retailer with a physical location in Calgary added an online store' and 'by month eight, after consistent SEO work and email marketing integration with the website, online revenue accounted for 22 percent of total sales,' plus a note that service-business clients are 'typically worth $2,500 or more per year.' However, these case studies name no clients and include no screenshots or links to the actual websites that were launched. None of the retrieved chunks — including the site's sitemap and llms.txt post listings, which enumerate dozens of blog guides and service pages — show a dedicated portfolio page where you could view real sites Clio has built. So a buyer can read about results for Calgary businesses similar to theirs, but cannot actually see examples of launched websites from the site content available.

Mentioned, not specified.

Partially answerable — Clio Websites builds on WordPress and Webflow, and specializes in WooCommerce (not Shopify or Wix) for eCommerce: - WordPress: Yes — their core platform. The site links to a dedicated WordPress Development service (cliowebsites.com/services/wordpress-development/) and publishes multiple WordPress-focused guides (e.g., for accountants and contractors in Calgary). - Webflow: Yes — there is a dedicated 'Calgary Webflow Development' service page explaining why they build with Webflow (responsive design, CMS capabilities, e-commerce, integrated hosting, SEO). - Shopify: No — the eCommerce FAQ states 'We specialize in WooCommerce websites,' explicitly noting WooCommerce means 'you are not locked in by a single vendor, like Shopify.' They publish a Shopify vs WordPress (WooCommerce) comparison to help buyers decide, but do not advertise Shopify builds. - Wix: Not advertised as a build platform — there is no Wix service page. The site offers a 'Wix vs WordPress: An Agency's Honest Comparison' guide and blog posts describing Wix's limitations (restricted SEO control, generic templates, migration difficulty), but it never explicitly states whether they would build a client site on Wix. Net: they are a multi-platform shop for WordPress + Webflow with WordPress/WooCommerce as the stated specialty — not a single-platform agency — but the site does not directly confirm or deny taking on Wix or Shopify client builds.

Mentioned, not specified.

Clio's website never states its own response-time commitment for maintenance-plan emergencies, so it doesn't answer whether a downed or hacked site gets same-day or next-business-day attention. The site has a dedicated page on maintenance SLAs (cliowebsites.com/website-maintenance-sla), but it is educational rather than a statement of Clio's plan terms: it recommends classifying issues by severity, with a sample framework where Critical issues ('site completely offline, checkout unavailable, major security incident') get 'immediate acknowledgement and active investigation' and Normal issues get 'same-day or next-business-day review' — explicitly framed as what a framework 'might look like,' not what Clio guarantees. The same page clarifies that response time means acknowledgement or start of investigation, not a guaranteed fix, and that a guaranteed 15-minute acknowledgement 'tells you very little by itself.' Descriptions of what Clio's maintenance plans include mention uptime monitoring, daily automated offsite backups, and security scanning, but give no response-time figure for incidents. To get an actual answer, you would need to contact Clio or review their maintenance agreement.

Mentioned, not specified.

Partly yes — files and design are explicitly yours, but domain and hosting control are not explicitly promised. Clio's 'How we handle it' section states: 'You own the design, the content we produced for you, and the site files outright once final payment clears,' and 'If you ever leave, we'll provide a full export and answer reasonable questions from your next developer during a handover window.' Two carve-outs are disclosed: they retain the right to display the work in their portfolio/case studies (unless you ask them not to), and they do not hand over their internal reusable code libraries and site-build framework. However, the site never states its own practice for domain registration or hosting accounts — its FAQ says 'Ownership needs to be explicit for the domain, hosting, content, and code separately. Paying the invoice doesn't automatically transfer everything unless your contract says so,' and its other pages treat domain registrar control, hosting account ownership, and WordPress administrator access as items you must confirm contractually before signing. So: design, content, and site files — yes, owned outright on final payment with a full export if you part ways; full admin control of the domain and hosting — not guaranteed on the site, and per Clio's own guidance depends on what your contract specifies.

Mentioned, not specified.

Partially. (1) Monthly retainer: yes — the site states twice that 'Clio Websites currently publishes Calgary SEO plans at $1,500, $3,000, and $6,000 CAD per month,' confirming SEO is sold as a monthly engagement. (2) Minimum commitment: not stated anywhere in the retrieved content. The site never specifies a minimum contract length or term; it only cautions generally that 'a focused audit followed by a prioritized implementation plan can be more economical than committing immediately to a long-term retainer,' without stating Clio's own commitment terms. (3) Monthly deliverables: no itemized per-tier deliverable list is published. The site's own example of a monthly scope — 'a $2,500 monthly proposal might include technical monitoring, improvements to selected service pages, two researched supporting articles, AI visibility sampling, and a monthly review' — is explicitly labeled 'a hypothetical scope, not a standard package.' The pricing guide describes in general terms what a package 'should' include (technical SEO such as crawl/indexing checks, redirects, sitemaps and structured data; on-page work on titles, headings, internal links and CTAs; authority building via local SEO and credible links; and reporting tied to clicks, impressions, queries and conversions), but frames these as questions buyers should ask, not as Clio's guaranteed monthly deliverables at each price tier.

Mentioned, not specified.

The site never states a default split of content responsibilities, but it strongly implies Clio offers copywriting as a service and can supply imagery. The copywriting guide closes with a direct service pitch: 'If you are ready to improve your messaging... Clio Websites can help. Book your free consultation with Clio Websites and let's build a website message that works for your Calgary audience.' The ownership article also frames agency-produced content as a normal option: 'If your agency wrote your copy or supplied stock photography, check whether that's licensed to you specifically or to the agency's account.' However, nowhere do the retrieved pages explicitly say whether copywriting and image/photography sourcing are included in a Clio website build by default or billed separately — and the site's own planning guides repeatedly push that clarification onto the buyer ('Clarify whether your agency or internal team is responsible for writing content, sourcing images'; 'Does your company provide final copy?... Who sources photography?'; 'who will supply the final content'). Image sourcing as a Clio service is not addressed anywhere; only copywriting has service-flavored coverage, via a blog article rather than a services page.

Mentioned, not specified.

Yes on WCAG, partially on cost, and AODA is never mentioned. Clio's site says it 'offers WordPress development and accessibility support for Calgary businesses ready to meet modern web standards' and recommends WCAG 2.1 Level AA as the build target: 'For the vast majority of Calgary businesses, WCAG 2.1 Level AA is the appropriate target. This is the level referenced in most Canadian legislation and procurement standards.' It also describes building accessibility in from the start of a project. On cost, the site is only qualitative: 'building in accessibility from the start is significantly cheaper than retrofitting it later under legal pressure,' and its RFP guidance tells buyers to 'identify the standard you expect the agency to design and test against' when requesting quotes — but it never states whether accessibility adds to the price of a build, by how much, or whether it's included in standard quotes. AODA (Accessibility for Ontarians with Disabilities Act) is not named anywhere; the site references WCAG 2.1, the Accessible Canada Act, and Alberta's accessibility legislation, and cautions that 'a website build should not be assumed to create legal compliance automatically.'