For the purposes of this document, a customization is defined as one or more of the following:
All customizations have lifecycle considerations. A future update to WordPress, an associated plugin, or even the underlying server operating system, could require additional development effort to maintain customization compatibility and/or desired behavior.
While we make every effort to utilize stable APIs and vendor-approved extension mechanisms, from time to time these platforms do change in ways that render some customizations incompatible with the latest software environment.
All customizations are therefore warrantied against underlying platform changes for a period of 180 days from the date of completion. If compatibility issues are discovered or introduced during this period, we will address them at no additional cost, provided there is an equivalent underlying mechanism to achieve the same result in the latest software. In rare cases[1], some customizations may become permanently inoperable.
The largest and/or most sophisticated software teams in the world cannot produce defect-free software, and even the simplest software can have dozens or hundreds of logical paths, only a portion of which can be fully evaluated during the software development process. A Quality Assurance process is part of every customization request, but defects can and do still happen.
All customizations are warrantied against defects for a period of 90 days from the date of completion. The vast majority of defects are discovered well within this period, and if they are, we will correct them at no additional cost.
[1] A good example of this was when Facebook made massive API changes in the wake of the Cambridge Analytica data scandal, rendering tens of thousands of applications temporarily or permanently inoperable. If your software relied on one of the APIs that was removed entirely, you were simply out of luck. Fortunately these types of incidents are uncommon, and in most cases substantial advance notice is provided.