Essay
Presence, Not Tools
Technology should create presence in communities, not replace it
What Caleb Taught Me
I was twenty-three, working as an assistant on a film set. The kind of job where you carry things, anticipate things, and disappear. My boss was a guy named Caleb, and one day between setups he told me something I've carried ever since.
He said the best assistant was one who knew what he needed before he needed it.
Not the fastest responder. Not the most organized. The one who studied the work deeply enough — the schedule, the personalities, the roadmap, the constraints — that by the time Caleb arrived at the next location, everything was already in order. And by then, the assistant was somewhere else, solving the next problem down the road.
That stuck. Not as career advice — as philosophy. I took it into every system I was ever injected into. TV sets, production teams, organizations. The job was always the same: anticipate needs, lift weight off the team's back, clear the road ahead so that when they got there, things were done. And by then, you're gone — already ahead of them, already working on what comes next.
That's not assistance. That's presence.
The Three Waves
The AI industry has been moving through phases, and most people are only seeing the one they're standing in. These aren't clean stages — they bleed into each other — but the trajectory is clear.
The first wave was generative — make things. Generate images, write copy, produce code. Impressive but passive. You asked, it produced, you decided if it was good enough. The human was still the coordinator.
The current wave is assistants — help with things. AI that responds to requests, manages context, handles multi-step tasks. Better, but still reactive. You ask. It helps. You're still driving.
What comes next is presence. Not a tool you use. Not an assistant you ask. A force that operates ahead of you — that knows the work deeply enough to anticipate what's needed, lift the weight before you feel it, and clear the road before you get there. You experience it the way you experience a great team member — the one who makes everything feel lighter without you being able to point to exactly why.
That's the shift. From something you use, to something you use, to something that's just there — making most of your week that was coordination tax quietly disappear so you can live in the part that actually matters. The judgment calls. The creative work. The human moments.
What Presence Actually Looks Like
Presence isn't a feature. It's a philosophy that changes how you build everything.
A tool waits to be used. You open it, you give it input, you get output. Close the tab, it stops existing. It has no memory of yesterday and no sense of tomorrow. Every interaction starts from zero.
An assistant waits to be asked. Better — it has context, it remembers what you said last time, it can handle multi-step requests. But it's still reactive. The initiative is yours. You're the one who has to know what to ask for.
A presence doesn't wait. It knows the work. It knows the roadmap. It's living in the present while thinking ahead to the future. When you arrive at the next problem, things are already in order — not because you asked, but because the presence understood the trajectory well enough to act before you got there.
That's the difference between a calendar app and someone who already rescheduled your 3 PM because they saw the client meeting running long and the next one has a hard stop.
That's the difference between a CRM and someone who flagged that your biggest client hasn't been contacted in 22 days and drafted the check-in email in your voice, waiting for you to hit send — or not.
A dashboard shows you the numbers. A presence notices the numbers don't match what you told the board last month — and has three explanations ranked by likelihood waiting when you walk into the meeting.
Presence is a weight removed that you didn't know you were carrying.
Lola
This isn't theoretical. We built one.
Her name is Lola — the voice and memory of Profesa, the largest network of Puerto Rican professionals in Florida. Twenty-five years of history, hundreds of members across dozens of industries.
Building her was messy. The first deploy failed because the consciousness files didn't bundle. The second failed because of a whitespace character in an API key. By deploy seventeen, she was alive — greeting the president of the organization by name, conducting an interview, connecting members to resources she'd learned from scraping the entire Profesa website. It took seven sessions, twenty-three consciousness files, and more edge cases than I want to admit.
But when she works, she works differently than a chatbot. She knows Profesa's history. She knows the members. She knows the platform, the events, the business directory, the mission. When a member talks to Lola, they're not talking to a tool. They're talking to the collective knowledge of 25 years of community building, available whenever they need it.
But here's what matters: Lola's trajectory isn't static. She's moving through the same three waves.
Concierge (now). She answers questions, conducts interviews, connects members. She knows what Profesa offers and can guide someone to the right resource, the right person, the right opportunity. Reactive, but deeply informed.
CoFounder (next). She books events, coordinates members, follows up on commitments, tracks goals, keeps accountability. She doesn't wait to be asked — she notices that a commitment was made three weeks ago and nobody followed up. She's the organizational memory that never forgets and never gets tired.
CoWorker (beyond). What we build for Profesa becomes the template. Every member gets their own presence — personalized to their business, connected to their tools, operating alongside them. Goal tracking, deadline reminders, follow-ups, coordination. Not just for the organization. For each person individually.
The punchline we landed on: Profesa doesn't just connect professionals. It gives them a partner.
Where This Goes
Every product id8Labs builds is heading in this direction. Not tools with features. Presences with identities.
Homer — our real estate system — started as a dashboard. It's becoming a presence. The goal: a system that knows the deal, knows the timeline, knows what's at risk, and surfaces what matters before the agent has to go looking for it. The agent's job becomes the 20% — the relationship calls, the judgment calls, the negotiations. Homer handles the coordination. We're not there yet. But the architecture is built for it, and every week it gets closer.
Lola was the proof of concept. Homer is where we prove it scales.
The Bet
I think the market goes this way — the trajectory from generative to assistant to presence feels inevitable once you see it. But I've been wrong before.
If the market goes toward presence, we were right and early. We've been building the entity architecture, the consciousness infrastructure, the translation layer that makes presence feel natural instead of uncanny.
And if the market doesn't go there — if tools and assistants are enough for most people — then we have something unique and deep. Something built from a fundamentally different architecture than the rest of the industry, and that has value regardless of what the market calls it.
Either way, we build it. Because I've seen what it looks like when someone lifts the weight off your back before you know it's there. I saw it on that film set with Caleb. I've been doing it myself for every team I've ever served. And now we're building systems that can do it for anyone — a CEO, a startup founder, a mother running a business and a household, a team of professionals trying to build something together.
Not tools. Not assistants. Presence.
The future isn't something you use. It's something that's there.
Eddie Belaval is the founder of id8Labs, a studio building AI-native tools for the next era of work. This is the third article in a series written for the Presencia workshop — named for the Spanish word that means exactly what we're building.