Services

WordPress services that survive contact with production.

Three ways to work with AWP. Start with one and add the others later: the team, the standards and the person who answers are the same.

What we do

  • Plugin development. From discovery to release, including security review, tests and the WordPress.org or Envato submission.
  • Maintenance. Updates on staging, off-site backups, monitoring, incident response and a monthly report.
  • Integrations. REST endpoints, webhooks, OAuth, licence checks and sync with the SaaS tools you already pay for.

How an engagement runs

  1. A 30-minute call. What breaks today and what success looks like.
  2. A written scope. Deliverables, dates and what is out of scope, approved before any code exists.
  3. Build in the open. Short feedback loops against a staging site you can click.
  4. Handover. Code, documentation, tests, release notes and a walkthrough.

Questions we get asked

Do you work with existing codebases?

Yes. We start with a reading pass and a short written assessment of what can be kept, what needs covering with tests and what should be replaced. If the honest answer is that a rewrite is cheaper, we say so before quoting.

Can you take over a site someone else built?

Yes, that is most of our maintenance work. We document what we find before touching anything, and we do not change production without a backup and a staging copy.

Do you sign NDAs and work under procurement?

Yes to NDAs. We are a small team, so we can work with your legal and security templates instead of asking you to accept ours.

Tell us what you need.

A short description is enough to tell you whether we are the right team and what it would take.