Let’s Connect
( ← Back )

Why a hexagon: what the Agneya logo means

Illustration: a hexagon with five sides drawn in white, labelled think, build, solve, secure and deliver, and a sixth side in teal labelled you, the client, closing the shape

Our logo is a hexagon. It has six sides, and we only claim five of them. People occasionally point this out as though it were an oversight. It was the entire idea.

The Agneya hexagon stands for how we run a project. Five sides are what we bring. The sixth side is the client, drawn into the structure rather than left outside it. The shape only closes when both are there.

That sounds like a line from a pitch deck. It isn’t, because it has costs, and some of them land on you. We’ll get to those.

What does a hexagon symbolize?

Strength without waste. Regular hexagons tile a flat surface with no gaps, and they do it with less edge than any alternative. The mathematician Thomas Hales proved in 1999 that any way of dividing a plane into regions of equal area has a perimeter at least that of the regular hexagonal honeycomb. Bees didn’t choose it for decoration.

That’s a reasonable thing for a technology company to put on its business card. But it isn’t why we chose it.

Five sides we can draw ourselves

Five of the sides are what we bring to every project: we think, we build, we solve, we secure, we deliver. Each one is real work that holds its own weight. Draw those five and you have something that already looks close to finished.

It isn’t finished. Five sides of a hexagon is an open shape. It can’t enclose anything, it can’t bear load, and the gap isn’t subtle. Anyone looking at it can see exactly what’s missing.

The sixth side is the client. Not outside the structure. Part of it.

What the sixth side means in practice

It would be easy to leave that as a nice line in a deck. It describes a specific way of running a project, and it has costs we accept on purpose.

You’re in the room, not on the distribution list. There’s no account manager translating between you and the people writing the code. When an engineer hits a decision that changes what the product does, you hear about it that day, from them, in plain language. A small team is what makes this possible. It’s also why we’ve stayed one.

You see the work while it’s still ugly. Showing you a finished thing at the end is safer for us and worse for you. Feedback at week two is a conversation. The same feedback at week nine is a rebuild, and someone has to pay for it.

We tell you when you’re wrong, and we expect the same. A structural member that can’t take load isn’t doing its job. If a feature you’re attached to is going to cost more than it returns, saying so is part of the work, not a breach of politeness.

The uncomfortable half

A shape that depends on the sixth side depends on the sixth side. This only works if you actually show up. The two things that most reliably slow a project down are late content and late feedback, and neither is something a development team can fix on your behalf.

So we’re direct about it at the start. We agree who owns decisions, who owns content and how quickly review happens, before anyone writes a line of code. That isn’t bureaucracy. It’s the sixth side agreeing to be a side.

Who this isn’t for

If you’d rather hand over a brief and see the result at the end, this way of working will feel like more of your time than you wanted to give. That’s a fair preference, and a team built around a hand-off will suit it better.

Why it’s worth saying out loud

Plenty of agencies call the client a partner. Too often it means a payer who’s kept comfortable. The difference shows up in small moments: whether you’re told about a problem or told about it afterwards, whether a bad idea gets pushed back on or quietly built.

We put it in the logo because a mark you look at every day is harder to quietly stop meaning than a line on a website. Five sides are ours. The sixth is yours. The shape only holds when both are there.

One client. One team.
Because the best work is built together.

If that sounds like the way you’d rather work, tell us what you’re building.

Sources

  1. Thomas C. Hales, “The Honeycomb Conjecture”, arXiv, 8 June 1999.

More from the blog