Services and capability

WordPress engineeringLink

Potential scope includes technically led builds, rebuilds, custom functionality, justified themes or plugins, integrations and migrations. Check standard features and maintained products before commissioning custom code. Deliver agreed requirements, implementation, proportionate checks, deployment notes and handover. Complex commerce, headless and unusual integrations need separate capability approval.

Technical care and improvementLink

Potential scope includes planned updates, issue assessment, maintenance decisions, small enhancements and an evolving technical record. Start with a site inventory and prioritized work list. Assign hosting, monitoring, backups, restore checks and license responsibilities explicitly. Care does not imply continuous availability or responsibility for all external services.

Rescue and performanceLink

Assess inherited sites, diagnose faults, plan recovery or migration, and make controlled repairs and measured improvements. Confirm authorized access and a recovery path before intervention. Deliver findings, baseline, priorities, change records and limitations. Security incidents and malware recovery require demonstrated skill or an agreed specialist. Never promise a universal score, permanent protection or recovery of nonexistent data.

Technical consultingLink

Review architecture, platform and plugin choices, proposed builds or difficult sites. Deliver a decision brief with options, dependencies, risks and a recommended next step. Implementation is a separate scope choice. Recommending against WordPress or against proceeding can be a valid outcome.

Capability gateLink

For each public claim, record one state: proven through inspectable work; deliverable with a named and available specialist; or not yet offered. Record the evidence, limitations and reviewer in Decisions and evidence. Confirm specialist availability before a client commitment.

The four pillars organize expertise. The three buying formats in Buying formats explain how clients pay. Avoid a separate package for every task or a public service list wider than actual capability.