Home  /  Who we are

The collective

Who we are

Independent specialists, each running their own practice. One address to write to, and an introduction by name once we know what the work is.

Not an agency, and not a marketplace

An agency sells you its bench and gives you whoever is free that month. A marketplace sells you a search box and leaves the judgement to you. dot-connectors is the thing in between, and the difference is the routing.

Everyone here runs their own practice. Nobody is on a salary, nobody has utilisation targets to hit, and nobody is incentivised to stretch a two-week job into a retainer. What holds it together is that we have worked on the same broken stacks for long enough to know who is genuinely good at which part of them.

The obvious question

Why there are no names on this page

Because the people here are independent practitioners with their own clients, and their names are not marketing material. Publishing a roster would put them in a shop window for anyone who felt like approaching them directly, or reading their client list, and none of them signed up for that.

So the sequence runs the other way round. You tell us what is broken. We work out whether it is real work and which discipline it belongs to. Only then do we introduce the specific person, by name, with their own company behind them, and you decide whether you want to work with them. Nobody is exposed before there is something to be exposed for.

The trade is deliberate and it costs us something. You cannot vet us from the sofa, and we know that asks more of you than a page of headshots would. What you get in exchange is that when a name does arrive, it is the right one, and that person is accountable under their own business rather than shielded by an agency logo.

How a request travels

What happens to your email

There is one address. What happens behind it is deliberately short.

  • A person reads it. Not a router, not a form parser, not a chatbot. Someone who has built this kind of system reads what you wrote.
  • They work out what it actually is. A server-side tagging problem and a Shopify fulfilment problem are not the same discipline, and we do not pretend one person is excellent at both.
  • You are introduced to that specialist by name. With their company, their background, and a direct line to them.
  • They quote and invoice under their own business. You always know exactly who you are contracting with before anything starts.
  • If nobody here is right for it, we say so. That answer costs you one email. It is also why we can afford to be honest, because there is no bench to keep busy.

Illustrative, not client work

The kind of thing that lands here

These are worked examples of the problems this collective exists to solve, written to show how we think rather than to claim a past client. Real references come with the introduction, once we know what we are working on.

The revenue that does not reconcile

Analytics reports one revenue figure, the shop platform reports another, and the gap is big enough that nobody trusts either. The usual causes are unremarkable: a purchase event firing twice on a thank-you page that reloads, refunds never written back, and consent bolted on afterwards so a slice of traffic is invisible. The work is a written measurement plan, one implementation, and a reconciliation against finance rather than against a second dashboard.

Two teams, two versions of the truth

Marketing reports leads, sales reports opportunities, and the two never meet. The same company exists several times under different spellings, and a form field one team depends on was renamed by the other. The fix is not a new tool. It is an object model both teams sign off, deduplication rules that actually hold, validation on every form feeding the CRM, and a written definition of each pipeline stage.

The integration that quietly stopped

A platform pushed an update, a form stopped posting to the CRM, and nobody noticed until a monthly report looked thin. Weeks of enquiries are sitting in an inbox nobody owns. The work is short: find the break, repair it, then put monitoring on the connection so the next failure announces itself instead of being discovered.

The honest part

What this model is bad at

Worth knowing before you write. A distributed collective is slower to mobilise a large team than an agency with a bench, so a twelve-person launch in three weeks is not our shape. We do not do brand strategy, creative campaigns or media buying. There are people far better at those, and we will name them if that is what you need. And because everyone has their own clients, we schedule work in defined blocks with fixed dates rather than being permanently on call.

What it is good at is the thing agencies quietly subcontract anyway: the connective work between systems, done by someone who has done that exact integration before.

Start with the gap

Tell us where the chain breaks.

One reply from a person, then an introduction to the specialist it belongs to.

Get in touch