CONNECTED TEAM
Connected is for keeping the people you meet. The workstreams do not stop at the moment cards are swapped — they carry through to remembering, and getting back in touch.
WHO IT IS FOR
The person swapping cards, the company that wants it managed, and the developer wiring it into something else.
Anyone who meets people and wants to keep the thread.
Workstreams serving them13
Organisations that want those contacts to outlive one person.
Workstreams serving them9
The people connecting it to a CRM or an internal system.
Workstreams serving them1
THE ROSTER
One workstream, one objective. What follows is not a snapshot of who is busy today — it is the set of workstreams this product needs.
5
Hand it over, take theirs in, and be able to find them again later.
Digital business cards
Hand over a card by QR code or link, in the moment.
Individuals
Reading paper cards
Photograph a paper card and be done — no typing.
Individuals
Who sees what
Let someone choose, per connection, what is visible.
Individuals
Organising connections
Keep when and where you met attached, so the person is findable months later.
Individuals Teams
Sharing across a team
Let a company's connections survive the person who made them.
Teams
2
Handing a card over and photographing one both happen on the spot, so the phone is where this has to feel right.
iOS development
Hand it over and take theirs in, right there, on iPhone.
Individuals
Android development
Deliver the same on Android, without the handset adding steps.
Individuals
2
Meeting people starts with an event, so this covers the whole day: the invitation, the door, and the desk.
Event management app
Run the day — sending the schedule out, checking people in, QR cards at the desk.
Teams Individuals
White-label apps
Ship it under someone else's name and look, for one particular event.
Teams
1
What the screens can do should be reachable from outside tools and AI agents too.
MCP / API
Let outside tools and AI agents work with Connected's features and data.
Developers
3
Building it is not enough. These carry someone from never having heard of it to using it.
SEO and content
Be findable, and say what it does before anyone has to ask.
Individuals Teams
PR / SNS
Keep saying, outside, what this is actually for.
Individuals
Sales
Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.
Teams
2
Nobody gets stuck after they start, and what they tell us turns into a fix.
Help content
Let people solve it themselves instead of waiting for support.
Individuals
CS / QA
Answer what comes in, and turn it into a fault that cannot happen twice.
Individuals
1
The workstream that runs before anything is built: what was asked for, read against how it is used.
Feature requests
Gather what users ask for and what usage shows is missing, and decide what gets built next.
Individuals Teams
3
It stays up, it stays protected, and the billing adds up.
Server watch / log analytics
Find errors and slowness first, so nobody meets them mid-task.
Security
Check on every change that what must be protected still is.
Individuals Teams
Billing
Bill what was used, correctly and on time.
Teams
THE LOOP
Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.
See the eight stepsAn individual or the company running the event — who it gets better for, and how. People decide that.
One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.
Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.
Did anyone get back in touch afterwards? Cards handed out on the day is not the measure.
ONE AT A TIME
The workstreams do not all run at once — one moves at a time. Everyday card swapping and the day of an event both fit because one conversation only ever holds one workstream.
Work on reading paper cards does not queue behind check-in at an event. Each moves on its own objective.
Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.
Decisions accumulate inside each workstream, so picking it up again does not start from zero.
When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.
Many small changes rather than one large one — each inside a range we can roll back.
STILL OURS
More agents does not move the responsibility. That stays with people.
We can do more than before. That is exactly why the decisions worth our time are the ones to decline.
Dates, estimates, quality. A company promises those, and a company is people.
Review and merge. A person presses the last button.
LET'S TALK
The way we run Connected is the way we run the work clients bring us. Tell us what you need moved first.
Talk to us