The Presence Layer

There is a venue in Shoreditch on a Tuesday night. Two hundred people. Six conversations.

The lighting is good. The music is right. The bar is staffed. The operator has done everything the operator can do. And still, the room sits inside itself. Strangers next to strangers. Phones in hands. Sixty percent of the people in that room came alone or came in pairs that have run out of things to say.

This is not a venue failure. The venue is doing its job. The room is full. The drinks are pouring. The lights and the music and the bar staff are all where they should be.

What the room does not have is a way to know itself.

It does not know who in it would like to meet someone. It does not know who is open and who is closed. It does not know which two strangers, three metres apart, would have found each other instantly in a smaller, slower century. The room is a database with no query layer. It contains every connection the operator paid to host. None of them can find each other.

This is the problem the next decade of consumer social will solve. Not because anybody asked it to. Because the cost of leaving it unsolved has finally come due.

For twenty years, the assumption running underneath consumer social has been that connection is a profile problem. Build a richer profile, run a smarter algorithm against it, surface the right faces. The platform that learns the most about you brings you the most relevant people. That is the swipe-app paradigm, the LinkedIn paradigm, the dating-app paradigm, the conference-app paradigm. Different verticals, identical premise: connection is downstream of declared identity, and the platform's job is to match declarations.

It worked, commercially. It did not work, humanly.

The product of that paradigm is a generation that can describe its preferences in eight bullet points and cannot say hello to the person sitting next to it. We have built the most thorough self-description tooling in human history, and we have built it on top of an environment, the smartphone, that systematically removes the conditions under which strangers used to meet. The trade was supposed to make us more connected. The trade made us more inventoried.

Loneliness is now the loudest public health story of the decade. The UK government has appointed a minister for it. The US Surgeon General has called it an epidemic. The data is unambiguous: 16 to 24 year olds in England are the loneliest age cohort, and they are also the most digitally connected. The two facts are not in tension. The two facts are the same fact.

The profile-matching paradigm did not fail because the algorithms were bad. The algorithms got very good. It failed because it was solving the wrong problem. The problem was never which stranger is statistically most compatible. The problem was always which of the strangers I am already near is open.

That is a different question. It requires a different category of software.

We are calling that category the Presence Layer.

A Presence Layer is a class of social software that activates on physical co-presence rather than on declared interest. It triggers when two people are in the same place at the same time and both opt in. It does nothing when they are not. It produces no inventory, no profile, no permanent record. It is not a network. It is a layer that sits on top of a room.

The Presence Layer is not a feature inside an existing product category. It is a new category. It cannot be reached by adding presence-detection to a dating app, by bolting AI matchmaking onto a conference platform, or by giving a ticketing tool a chat function. Those are all retrofits inside the profile-matching paradigm. They preserve the assumption that the platform's job is to inventory people, and they add a location filter on top.

The Presence Layer inverts the assumption. The room is the unit. The room knows who is in it and who is open. The platform is the protocol the room uses to introduce its own occupants to each other. The user is not a profile inside a global graph. The user is a participant in a specific place at a specific time, and when they leave, the layer goes with them.

Profile-matching software answers who out there might I like. Presence Layer software answers who in here is open.

These are not two flavours of the same product. They are different categories of infrastructure, built on different primitives, optimised for different outcomes, and they sit in different lines of a venue operator's budget.

A Presence Layer is defined by three primitives. Any product that has all three is in the category. Any product missing one of them is in a neighbouring category, regardless of what it calls itself.

These three primitives are non-negotiable. A platform with two of them is interesting but not in the category. A platform with all three is in the category whether it calls itself a Presence Layer or not. We expect peers. We hope for them. The category is larger than any one product.

Category creation only works if the boundaries are explicit. So here are the boundaries.

The Presence Layer is not a dating app. Dating apps are global, profile-matched, persistent, and approach-by-default. They optimise for the swipe. The Presence Layer is local, presence-triggered, ephemeral, and consent-gated. It optimises for the room.

The Presence Layer is not a ticketing platform. Ticketing platforms exist to move a person across the door. Their job ends at the scan. The Presence Layer begins where ticketing ends. We sit on top of the ticketing stack, not inside it.

The Presence Layer is not an event networking tool. Event networking tools, whether they call themselves intentional networking or AI matchmaking or attendee-to-attendee, are profile-matching software with a conference badge. They run the same paradigm we are arguing against. They are not in this category. They are in the category we are leaving behind.

The Presence Layer is not a social network. Social networks are persistent, profile-based, and globally addressable. Their job is to maintain a graph. Our job is to make a room legible to itself for a few hours and then disappear.

The Presence Layer is not a feature. It is not something a venue can switch on inside the software it already has, because the software it already has was built on the opposite assumption. It is a separate layer. That is what the word means.

The Presence Layer is not a clever idea waiting for permission. It is the inevitable response to four forces that have now converged.

The first is the loneliness data, which has reached the point where public institutions are treating it as infrastructure failure rather than personal misfortune. When loneliness becomes a policy problem, the tools to address it become procurement categories.

The second is the venue economics. Independent venues across the UK are closing at the fastest rate on record. The operators still standing are looking for differentiation that is not price and not music policy. A venue that knows itself, that produces measurable social outcomes for the people inside it, is a venue with a story it can sell. The Presence Layer is that story.

The third is the privacy shift. A decade of data scandals has retrained consumers to read the small print. Architectures that promise privacy through settings are now correctly distrusted. Architectures that deliver privacy through ephemerality, through never collecting the data in the first place, are the only credible move forward. The Presence Layer is built on the second architecture by design.

The fourth is the protocol moment. The technical conditions for consent-first, geofence-bounded, ephemeral social software did not exist five years ago. They exist now. Real-time location, on-device cryptography, mobile compute, and end-to-end messaging are commodity primitives in 2026. The hard part is no longer the engineering. The hard part is the category courage to build something that is deliberately less sticky, deliberately less inventoried, and deliberately less optimisable than its incumbents.

Category courage is what this manifesto is about.

To venue operators, organisers, residential building managers, campus welfare offices, and anyone who runs a physical space where strangers gather: you are sitting on a layer of value that you cannot currently capture. Every event you run produces a social graph. Every event you run discards it at the door. The Presence Layer is how you stop discarding it. Not by surveilling your guests. By giving your guests a tool to find each other while they are inside your space, and letting them leave with the connections rather than the data trail.

To the press and the analysts: the Event Networking and Matchmaking category that G2 has been tracking for the last five years is mature, profitable, and structurally incapable of solving the problem its incumbents claim to solve. The next move in this space is not a better matchmaking algorithm. It is a different category. Cover it as a different category.

To peers building in this space: the category is bigger than any of us. If you are building something with all three primitives, you are a peer. We will name you, link to you, and defend the category alongside you. If you are building something with two of them, you are a fast follower in an old category, and we will compete with you on those terms. The thing that gets us all somewhere is the boundary being clear.

To the people who will use it: this is not another app for your screen. This is the app that gets you off your screen for the duration of a night, a conference, a festival, a residency. It activates when you arrive somewhere. It goes quiet when you leave. It introduces you to people who are physically in the same room as you, who have signalled they are open, and whose openness you have signalled back to. It does the smallest possible thing that the swipe paradigm cannot do. It hands you back the room.

FirstMove is building the first Presence Layer for live venues and events. We are not the only company that will build in this category, and we should not be. A category with one product in it is not a category. It is a niche.

What we are committing to, publicly, with this document, is the work of naming the category, defending its boundaries, and seeding the vocabulary that lets the rest of the work happen. The three primitives, geofence, consent, ephemerality, are the criteria. The Presence Layer is the name. The argument is that profile-matching has reached the end of what it can do for human connection, and the next twenty years belong to a different paradigm entirely.

We are putting this in writing because manifestos are how categories get named, and because the room is full, and because the cost of leaving it unsolved has finally come due.