Putting The Tech Meet On The Map

A meetup that only existed if you already knew about it.

The Tech Meet has run monthly at The Muggleton Inn in Maidstone for a year and a half. It grew the way most community events grow, through people telling other people, and it worked well enough that the room kept filling up.

What it did not have was anywhere to point somebody who had not already been told. Somebody in Kent typing tech meetup into Google found nothing. The meetup existed on a listings page and in a WhatsApp group, neither of which turns up when a developer new to the area goes looking for something to go to.

For an event whose entire purpose is bringing people together, being invisible to anyone outside the existing circle is the thing holding it back.

Kent Tech Meetup had outgrown its own name.

The original name did an honest job while the meetup was a Kent thing. It also quietly set a ceiling. People travelling in from London or the wider South East read a county in the title and assumed it was not for them, and the name left no room for the event to grow beyond one place.

We rebranded it to The Tech Meet. The new name says what the thing is rather than where it happens, which keeps the door open to more people without pretending the meetup is something it is not.

That decision drove everything else. A broader name needed an identity that could carry it, and a website that could be found by somebody who had never heard the old one.

A logo for a room full of people.

The mark is a small network: five nodes joined into one connected graph. It stands for the people in the room and the conversations between them, which is the entire product. There is no laptop, no circuit board and no lightbulb, because none of those are the reason anybody turns up.

It was drawn to survive being small. The full lockup pairs the graph with the wordmark, and once that has appeared on a piece the graph stands alone as an avatar or a sticker. The rules are set tightly: no smaller than 18px on screen or 5mm in print, with clearspace equal to the height of the mark on every side.

Dark-first, with one colour doing the talking.

The palette is three colours and no more. Ink, a near-black at #0B0E13, is the default surface everywhere we control: the site, the banners, the decks. Signal, a green at #3DDC97, is the brand voice. Paper, an off-white at #F5F6F4, exists for print and light contexts only.

Dark-first suits an event that happens in a pub on a weeknight, and it gives the photography somewhere to sit. Every pairing clears AAA: white on Ink at 18.5:1, Signal on Ink at 11.2:1, Ink on Paper at 18.1:1. The one prohibition in the guide is that Signal is never body text on Paper, where it falls to 1.6:1 and fails outright. It is a surface and an accent colour rather than a light-mode text colour.

The type runs on three voices. JetBrains Mono at 700 shouts and carries the display lines. Instrument Sans at 400 explains, set between 14 and 16px at 1.6 line height so event details are easy to read on a phone. JetBrains Mono at 500 handles labels, which is why dates and venues read like terminal output rather than marketing. Bricolage Grotesque carries the logotype.

The monospace is doing more than decoration. It tells a developer, in about a second and before they have read a word of it, that this event is for them.

The palette, built to hold up on a phone and on printed signage.

The type system, chosen for legibility at small sizes.

The rules that keep it consistent.

The identity was handed over as a guidelines document rather than a folder of files, because a meetup that anyone might post on behalf of needs rules somebody can follow without asking first.

It covers the voice as tightly as the visuals. Never advertise speakers or agendas, because the conversation is the event. Lead with what somebody gets out of coming rather than how good the event is. Write like a good senior dev explaining something at the bar, plain and warm with no hype. There is even a punctuation rule: no em dashes, semicolons where one would have gone, and no Oxford commas.

It closes on four questions every piece has to answer. Who is this for, what do you do, why should I care and what now. The last one has a single answer, which is signing up for the next meetup, and everything the brand produces points at it.

Built to be found.

The whole point of the site was discoverability, so it was built for that from the first page. Event pages carry proper structured data, so a search engine understands that this is a recurring event at a fixed venue on a known date rather than a page that happens to mention one.

The copy was written around what people actually search for. Not clever phrasing, but the plain terms someone types when they have moved to the area and want to meet people who do the same work as them.

It runs on Devigo Studio, which keeps the pages light and means the listing for next month can be updated in a couple of minutes rather than becoming a job somebody has to remember to ask for.

The site that now answers anybody searching for a tech meetup nearby.

Twenty percent more members in the first month.

The site has taken over sixty clicks from Google Search since it went live, from people who had no other way of finding the meetup. Membership grew by a fifth in the first month, and it is still climbing.

It also now turns up in AI overviews when people ask about tech meetups in the area, which is increasingly where that question gets asked and answered before anybody clicks anything at all.

A meetup that ran for eighteen months on word of mouth is now something a stranger can find, understand and turn up to without knowing anyone first.