Oogle

BUILD

WordPress built properly, not assembled from plugins.

Custom themes, custom plugins, block editor work and integrations. Built so your team can run the site without calling anyone.

IF YOUR SITE IS BROKEN RIGHT NOW

Building something new? Read on. If WordPress is throwing a critical error, showing a white screen or refusing to let you log in, go to WordPress support instead.

What we build in WordPress.

Custom themes

Built for your content rather than bought and bent into shape.

Custom plugins

Functionality kept in a plugin so it survives a theme change, follows WordPress conventions, and can be read by the next developer.

Block editor work

Custom blocks, patterns and editor styles, so editing matches the design and the site can't be broken by accident.

Custom post types and fields

Real content models rather than a pile of pages.

Multisite

Networks of related sites sharing a codebase, with the shared and per-site parts decided up front.

Integrations

Your CRM, your payment provider, your email platform, your accounting system.

  • Custom themes
  • Custom plugins
  • Block editor
  • theme.json
  • ACF
  • Custom post types
  • WP-CLI
  • REST API
  • Multisite
  • WooCommerce
  • Composer
  • Git
  • Object caching
  • Core Web Vitals

Why WordPress sites go bad.

The plugin pile

WordPress makes it easy to solve a problem by installing something. Do that for three years and you have forty plugins, six that overlap, two that are abandoned, and one that's why the admin takes nine seconds to load.

Page builders cost you later

A heavy visual builder gets a site launched quickly and then charges rent forever: bloated markup, poor Core Web Vitals, content locked into shortcodes, and a migration that means rebuilding every page by hand.

What to expect

  1. We model the content first
  2. We decide what's theme and what's plugin
  3. We choose plugins carefully

It depends on how many templates and content types there are, how much is custom, what has to be migrated and what it connects to.

How we bill

WordPress build questions.

Can you improve the WordPress site we already have?

Often that's the better spend. We audit what's there, cut what isn't earning its keep, replace the risky parts, fix the performance problems and leave you with something maintainable.

Do you use a page builder?

Not on new builds. We use the block editor with custom blocks, which keeps content portable and pages light.

Will our team be able to update it?

That's the point. We set the editor up so the common changes are obvious, and we'll walk your team through it before launch.

Quoted Services

Custom themes and plugins are quoted against a written scope.

Quoted

Quoted after we look. One-off or monthly.

Not what you need? See all three ways we work

Building something on WordPress?

Tell us what it has to do, and what your team needs to change without asking anybody.