How the work is approached
Three principles decide almost every decision here.
- Diagnose before changing. Confident guessing creates avoidable damage; careful diagnosis creates most of the value.
- Say what cannot be done. A clear no is more useful than an optimistic yes that fails later.
- Leave a record. You should never depend on one person’s memory of what happened to your site.
What that looks like in practice
In an incident, the first move is to preserve evidence rather than to start fixing. For example, a one-click restore can overwrite newer orders, and deleting a suspicious file can take a site down while leaving the backdoor untouched.
Therefore the sequence is fixed: establish the fault, agree the change and the way back, verify the result, then write it down. The full sequence is published under how the work runs.
Who is behind it
DuePress is built by Renzo Johnson, the credit carried in the footer of every page on this site.
Beyond that attribution, this page deliberately publishes no staff list, no photographs and no biographies. Inventing a team is a common pattern on service sites and it is worth nothing to you. If it matters who will actually handle your site, ask before you commit, and expect a straight answer.
What DuePress deliberately does not claim
You will not find a response-time promise, a guarantee, a certification badge, or a customer count anywhere on this site. Each of those is easy to print and hard to honour, and none of them is currently measured here.
Similarly, no page quotes a price. Instead, how pricing works explains how a number is reached and what moves it, because incident work is not a shelf product.
Common questions about DuePress
Is this an agency or one person? This page does not claim a team, and you should treat any service site that does so without names as unverified. Ask directly before you commit.
Why is there no case-study page? Client work is confidential unless a client has agreed otherwise, and none has been published here. Invented case studies are worse than none.
What happens if you cannot fix it? You still receive the written findings. That is the point of paying for diagnosis rather than for an attempt.
Remote, and national in reach
The work is done remotely, because WordPress problems are remote problems. Consequently there is no office to visit and no local service area; a site in another country is no harder to diagnose than one down the road.
Where to go next
If something is broken, start at WordPress support, or hacked site recovery for a compromise. Store owners should read WooCommerce support. If nothing is on fire, see maintenance plans and security services. The service scope lists what is declined, and the WordPress troubleshooting documentation is a reasonable place to start on your own.