Questions Clients Always Ask Me (Answered) | WP & Shopify

After four years of freelance WordPress and Shopify development — working with clients across the US, Canada, Australia, and the GCC — I have answered the same handful of questions more times than I can count. Every new client conversation follows a similar pattern, and the questions are almost always reasonable. Most people hiring a developer for the first time simply do not know what they do not know.

This post collects the questions I get asked most often — honestly answered, the way I actually answer them in a discovery call. If you are considering hiring a WordPress or Shopify developer, this is the conversation we would have anyway, just written down.

“Should I build my site on WordPress or Shopify?”

This is the single most common question I get, and the honest answer is: it depends entirely on what you are selling and how.

Choose Shopify if your primary business is selling physical or digital products online. Shopify handles payments, inventory, shipping, tax, and checkout out of the box, at a level of polish and reliability that takes significant custom development to match on WordPress. If ecommerce is your core business model, Shopify removes a huge amount of operational complexity.

Choose WordPress if your site is primarily content-driven — a blog, a service business, a portfolio, a publication — or if ecommerce is only one part of a broader site with content, membership features, or custom functionality that goes well beyond a storefront. WordPress also wins when you want complete ownership and zero recurring platform fees on revenue.

I work across both platforms specifically because I see this question constantly, and giving an honest platform-agnostic answer serves the client better than pushing whichever platform I personally prefer to build on.

“How much will this cost?”

I cannot give an honest number without understanding the scope first — and I am upfront about that on every discovery call. What I can give is the framework I use to think about pricing, which helps clients understand why the range is what it is.

• A basic WordPress site or Shopify store using a pre-built theme with content entry and light customisation typically takes a few days to two weeks of work.
• Custom theme development — bespoke design, custom templates, ACF or Liquid architecture — typically takes three to six weeks depending on complexity.
• Complex projects involving custom plugin or app development, platform migrations, or Shopify Plus implementations can take two to four months or longer.

I quote based on defined scope and deliverables, not hourly guesswork. If a client cannot yet define the scope — which is genuinely common — the first step is a short paid discovery phase to nail that down before any commitment to a final number.

“How long will my site take to build?”

Timeline and cost are tied together, but the question deserves its own honest answer because clients often have expectations shaped by ads promising a “website in 48 hours.”

A realistic timeline depends on three things: the complexity of the build, how quickly the client provides content and feedback, and how many revision rounds are built into the process. The single biggest timeline killer on every project I have worked on is not development time — it is waiting on content, images, and feedback from the client side. I now build buffer time into every quote specifically to account for this, and I am direct about it upfront so nobody is surprised later.

“Will I be able to update the site myself after launch?”

Yes — and this is something I design for from the very start of every project, not something I retrofit at the end.

On WordPress, this means building with the block editor or Elementor, using ACF fields with clear labels for any custom content, and structuring the site so that adding a blog post, updating a product, or changing a homepage image does not require touching code. On Shopify, this means using the native theme editor’s sections and blocks properly so the merchant can update content, swap images, and add new products without ever opening Liquid code.

I also record a short screen-recorded walkthrough at handover showing exactly how to do the most common day-to-day tasks — adding a post, updating a product, changing a banner image. This single habit eliminates the majority of “how do I do this” messages I used to get in the weeks after launch.

“What happens if I want to switch developers later?”

This question comes up more than people expect, usually from clients who have had a bad experience with a previous developer who held their site hostage in some way — withholding admin access, using a personal hosting account, or building with undocumented custom code nobody else can maintain.

My answer is simple: you own everything. You get full admin access to WordPress or Shopify, your domain stays registered in your name, your hosting account is yours, and any custom code I write is documented with comments explaining what it does and why. If you want to move to a different developer six months from now, you can do that without me, and without losing anything.

I genuinely believe that making it easy for a client to leave is what makes them want to stay.

“Do I need a maintenance plan, or can I just leave the site alone after launch?”

For WordPress specifically, the honest answer is no — you cannot just leave it alone. WordPress core, themes, and plugins need regular updates, and skipping them is one of the most common causes of sites getting hacked. Plugins account for the vast majority of WordPress security vulnerabilities, and an outdated plugin left unpatched for months is exactly the kind of weakness automated bots scan for constantly.

For Shopify, the platform itself handles core security and updates automatically — but apps, theme customisations, and third-party integrations still need periodic review to make sure nothing has broken silently after a Shopify platform update.

I offer a monthly maintenance retainer for exactly this reason — covering updates, backups, uptime monitoring, and a small number of monthly support hours for content changes or quick fixes. Not every client needs it, but every WordPress site genuinely benefits from it.

“Can you just clone [competitor’s] website?”

I get this question more often than I expected, usually framed innocently — “can you make it look like this site, but for us?” The honest answer has two parts.

I cannot and will not copy another site’s code, content, or original design elements directly — that is a copyright problem waiting to happen, and it puts the client at legal risk, not just me. What I can do is study what works about the layout, structure, and user flow of a site you admire, and build something original that achieves the same effect — a similar navigation pattern, a similar content hierarchy, a similar visual energy — without lifting anything directly.

This distinction matters and most clients appreciate having it explained clearly rather than just being told “no” without context.

“Why does this feature cost extra if it’s ‘just a small plugin’?”

This question usually comes from a good place — clients see “WordPress has 60,000 free plugins” and reasonably ask why a specific feature is not just a quick install. The honest answer is that sometimes it is exactly that simple, and I tell clients when it is.

But often the request is for something genuinely custom — a feature tied to their specific data, their specific workflow, or their specific integration needs — where no plugin does the job cleanly. In those cases, installing a generic plugin that approximates the requirement usually creates more problems than it solves: bloated page weight, conflicting scripts, and a feature that almost but not quite does what was asked for.

I run every feature request through a simple framework — does a well-maintained plugin already solve this reliably, or is this specific enough to the business that custom code is the better long-term choice. I explain which path a request falls into and why, rather than just quoting a number.

“What if something breaks after you finish the project?”

Every project I deliver includes a defined post-launch support window — typically two to four weeks depending on project size — during which any bugs or issues directly related to the work delivered are fixed at no extra charge. This is not the same as ongoing maintenance or new feature requests, and I am clear about that distinction upfront so nobody is surprised by where the line sits.

Beyond that window, clients on a maintenance retainer have ongoing support built in. Clients without one can always reach out for a one-off fix, billed for the time it actually takes.

“Can you also do my SEO / social media / branding?”

I am honest about where my expertise starts and ends. I build sites with strong SEO fundamentals baked in from day one — clean code, fast load times, proper heading structure, schema markup where relevant, and a technically sound foundation that an SEO specialist can build on. What I do not do is ongoing content marketing, link building, or social media management — those are different specialisms, and I would rather tell a client that honestly and point them toward the right kind of specialist than stretch myself thin trying to be everything.

What I can and do offer is SEO-optimised blog content as part of an ongoing relationship, since content and development genuinely overlap on most sites I build.

“Do you work with international clients / different time zones?”

Yes — the majority of my client base is international, across the US, Canada, Australia, and the GCC. Time zone differences are manageable with the right communication habits: clear written updates instead of relying purely on calls, asynchronous project management through a shared tool, and defined response-time expectations set upfront rather than assumed.

The work itself — WordPress and Shopify development — does not require real-time presence the way some other services do. What matters more is clarity in written communication and predictable delivery against agreed milestones.

“Is my data and customer information safe?”

This question has become more common as data privacy awareness has grown globally, and it deserves a direct answer rather than a vague reassurance.

On WordPress, I implement the security fundamentals on every project — forced HTTPS, strong admin credentials, login attempt limiting, a security plugin with firewall protection, and regular backups stored off-site. On Shopify, payment data never touches my code at all — Shopify handles PCI compliance and payment processing entirely on their own secure infrastructure, which is one of the platform’s genuine strengths for merchants who do not want to think about payment security themselves.

For any site collecting customer data beyond payments — email addresses, account details, form submissions — I make sure data is handled according to relevant privacy regulations for the markets the client operates in, and that nothing is stored or transmitted insecurely.

“Why does my site need to be fast? Mine looks fine to me.”

This question usually comes from a client testing their own site on fast office WiFi and a powerful laptop — which is a completely different experience from a customer on a mid-range phone on mobile data. The honest answer is that site speed directly affects three things that matter to every business: Google search rankings, because page speed is a confirmed ranking factor; bounce rate, because a slow-loading site loses visitors before they ever see the content; and conversion rate, because every additional second of load time measurably reduces the percentage of visitors who complete a purchase or contact form.

I usually show clients their own site’s PageSpeed Insights score during the discovery call — the numbers make the case far more convincingly than I ever could in words alone.

What These Questions Have in Common

Looking back across four years of these conversations, almost every question boils down to the same underlying concern: clients want to know they are not about to make an expensive mistake, lose control of something they are paying for, or get locked into a relationship they cannot easily exit.

The honest answer to almost every version of this concern is the same: build with ownership, transparency, and documentation as defaults — not as upsells. A client who fully understands what they are getting, what it costs, and what happens if the relationship ends is a client who trusts the process enough to actually move forward.

Have a Question That Isn’t Covered Here?

If you are considering a WordPress or Shopify project and have a question that did not make this list, I would genuinely rather answer it honestly before you commit to anything than have you find out the hard way after the project starts.

At ArshadWebStudio, every new client conversation starts with exactly this kind of honest groundwork — platform choice, realistic timelines, transparent pricing, and clear ownership from day one. If you have a project in mind, get in touch and let’s talk through it properly.

About the Author

Arshad Shah is a freelance WordPress and Shopify developer at arshadwebstudio.com with over four years of experience building custom websites and online stores for clients across the US, Canada, Australia, and the GCC. He believes in honest pricing, full client ownership, and building sites clients can genuinely manage themselves after launch.