Commonly asked questions
Answers to what clients most often ask before starting a WordPress, PHP, or Moodle project, browse by category below.
WordPress theme and plugin builds, WooCommerce stores, Moodle/LMS sites, and general PHP development from single-page fixes and bug hunts to full builds from scratch.
Yes. I take on white-label and subcontract work for agencies that need extra WordPress or PHP capacity, alongside project work for direct clients.
Yes, Moodle theme and plugin development is one of my core specialties, alongside WordPress, so LMS sites and course platforms are very much in scope.
Yes, from store setup and theme customization to plugin integrations, checkout fixes, and performance tuning for existing WooCommerce stores.
PHP, MySQL, WooCommerce, and Moodle form the core of my stack, alongside the front-end tools needed to build and customize themes and plugins.
Yes, alongside freelance and contract projects, I'm open to full-time remote roles as well as long-term contracts.
Reach out through the contact page with a short description of your project. I'll follow up with a few questions and a clear, no-obligation quote.
It depends on scope, but most theme or plugin builds run from a couple of weeks to a couple of months. Ongoing retainers run for as long as you need support.
Yes, I regularly take over, extend, and fix existing WordPress themes and plugins rather than insisting on rebuilding everything from zero.
Yes, see the Support & Maintenance page for the kinds of ongoing work I cover once a site or plugin is live.
Regular check-ins over email or your preferred tool, plus a shared task or project board for larger builds so you can see progress as it happens.
We'll revisit the quote together and agree on the adjusted timeline and cost before any extra work continues.
Client code, credentials, and project details are treated as confidential and are not shared, reused, or shown to other clients without permission.
Yes, I'm happy to sign a client's NDA or confidentiality agreement before reviewing sensitive project details or credentials.
Only what's needed for agreed-upon support or maintenance work, and only with the client's knowledge, nothing is kept or reused beyond that.
No, custom work built specifically for a client stays that client's, unless we agree otherwise upfront.
See this site's Privacy Policy page for the details on what, if anything, is collected when you browse.
Only me, unless you explicitly bring in another collaborator or approve read access for someone else on your team.
For most engagements, yes, typically a partial upfront deposit with the balance due on agreed milestones or delivery. Exact terms are confirmed before work starts.
Yes, a simple written agreement covering scope, timeline, and payment terms is used for paid engagements to keep expectations clear on both sides.
Once final payment is received, ownership of the custom code delivered transfers to the client.
Yes, retainer arrangements can be paused or ended with reasonable notice as agreed at the start of the engagement.
We'll go through the agreed revision rounds together to get the work to where it needs to be before calling the project complete.
See the Terms & Conditions page linked in the site footer for the complete details.
Let's scope a package that fits your budget and goals
Tell me about your project and I'll follow up with a clear, custom quote, no obligation.
-
Free, no-obligation quote
-
Response within 1-2 business days