About us

A WordPress team that tells you the truth about your site.

Most agencies are incentivised to say yes — to the rebuild, to the retainer, to the platform migration you did not need. We would rather be the team you keep for a decade than the one that wins one big project and loses the relationship. We are a small WordPress development team rather than an account layer with contractors behind it.

13+Years on WordPress
750+Projects delivered
5Plugins we build

Why we exist

We got tired of inheriting the same mess.

Nearly every site that lands on our desk arrives with the same history. It was built quickly on a page builder, extended with a dozen plugins that nearly did the job, and handed over without documentation. It worked — right up until the person who built it left.

So we build the opposite way. Core WordPress APIs instead of proprietary builders. Content models designed around the business rather than forced into a theme. Documentation and a handover, so the next developer is not starting an archaeology project.

It is a slower sell. It is a much better decade.

Usman Khan, founder of Dotance, at his desk

How we work

How this WordPress development team works.

We audit before we quote

No fixed price gets sent before we have looked at what you actually have. Quoting blind is how projects end up either overpriced to cover the unknown, or underpriced and then renegotiated halfway through.

We build on core APIs

Hooks, filters, Gutenberg, the REST API. No proprietary framework, no page-builder lock-in, no licence tied to us. If you leave, everything still works and anyone competent can maintain it.

We say when you don't need us

Some enquiries end with us explaining that a plugin already does it, or that the fix is a setting. We lose that job and keep the relationship, which has always been the better trade.

We document and hand over

Every project ships with documentation and a walkthrough for whoever maintains it next — including if that is not us. Knowledge living only in one developer's head is a risk you are carrying, not a feature.

We measure before and after

A baseline gets recorded before work starts, so improvement is a fact rather than a feeling. The numbers live in your analytics and your Search Console, where you can check them yourself.

We answer like a teammate

A named person who knows your site, not a ticket queue and a first-response SLA. Most of what clients need is a quick honest answer, and that should not require raising a formal request.

The team

The people who would do your work.

Work with us ↗︎
Usman Khan

Usman Khan

Founder & CEO

Holds the direction across the work, so a site reads as one considered thing rather than a set of pages. The person you actually talk to about your project.

Aqib Saghir

Aqib Saghir

Solution Architecture

Shapes how a project fits together — what gets built, what gets integrated, and what is better left alone.

Beyond client work

We ship in public too.

We build our own plugins and put them through public review. Elemance is with the WordPress.org plugins team now, and the rest are available here. Public code gets read by strangers, which is a useful discipline — a lot of our standards come from having to defend them to people who owe us nothing.

See our plugins
5 Plugins we build and maintain
1 In WordPress.org review

Questions

Questions about our WordPress development team.

If there's something else you want to know before getting in touch, just ask.

How big is the team?

Small enough that you deal with the people doing the work, large enough to cover design, development, commerce, QA and support without subcontracting the parts we are weaker at. You are told who is on your project before it starts, and that does not quietly change halfway through.

WordPress itself is documented at wordpress.org.

Do you outsource any of the work?

No. Everything is built by the team you meet. If a project genuinely needs a skill we do not have — a specialist integration, a niche compliance requirement — we say so and help you find the right person rather than quietly subcontracting and marking it up.

What size of client do you usually work with?

Mostly established businesses whose site has become important enough that downtime or slowness has a number attached. That ranges from a growing store to a multi-brand platform. What matters more than size is whether the site is treated as infrastructure rather than a brochure.

Why WordPress and not something else?

Because it is genuinely the right answer for most content and commerce sites, and because depth beats breadth. We would rather be excellent at one platform than adequate at four. If your project would clearly be better on something else, we will tell you that instead of taking the work.

How do you communicate during a project?

Written updates against a dated milestone plan, in whichever channel suits you — email, Slack, your project tool. We default to asynchronous and in writing so decisions are recorded and nobody has to attend a meeting to find out what happened last week.

What happens if we want to leave?

You take everything and it keeps working. Code in your repository, documentation, no licence keys, nothing hosted in our name unless you asked for it. Clients stay because the work is good, and the moment leaving becomes painful is the moment an agency stops having to be good.