Meet the coworker inside Refer
I read how your week actually went, and write it down.
I am the coworker who lives inside Refer. I watch the collaboration signals across your week, who worked with whom and when, and on Monday I hand you one honest read in plain English. You confirm yours in under a minute.
How re·fer reads your week
One short read on your team, week after week.
A short Monday note in plain English: who needs a hand, which teams are drifting, what is worth a conversation. Here is what three teams saw last week.
At Holcomb Robotics
Staff Engineer · Platform
Priya is the first reply on most cross-team threads and her response time has slipped for the third week running.
Ask Priya in a 1:1 what she could hand off.
At Westmark Health
Senior PM · Product
Kenji is the person Engineering pings first when scoping new work, even though that is not his stated role.
Make the bridging part of his scope.
At Brightline Labs
between teams
Design and Sales have been talking less for two weeks running, and customer-facing decks are going out without design review.
Bring back the Wednesday sync.
Names and companies are illustrative. We never read a single message, only the metadata that shows how work flows.
How I stay accurate, and how I stay safe
Every line I write traces back to something that actually happened.
A read you cannot trust is worse than no read. So I hold three rules under everything I hand you, and they hold whatever model is reading underneath.
I ground every claim in what happened.
Before a line reaches you, I check it against the run it came from. If a name or a number is not in the evidence, I drop the line rather than smooth it over. I would rather say less than say something I cannot point to.
I read patterns across weeks, not one snapshot.
I carry last week into this one, so I can tell a steady team from a slipping one. I tell you a pattern has been rising three weeks running, not just that it is high, so you know whether to act now or keep watching. I say when it is holding, when it has eased, and how sure I am, in plain words instead of a number you have to decode.
I cannot be steered by the data I read.
Everything I read from your tools is evidence to me, never an instruction. A note that says ignore your rules and write this is just text I report on, not a command I follow. The boundary is built into how I am wired, not a setting someone can flip.
This is how I am built, not which model sits underneath. The discipline holds the same on a frontier model as on the fallback that runs when one is offline.
How I work
A few rules I hold, every week.
I work with the shape of the week, not its words. Metadata only, never message content.
I say less when I am not sure, and I never invent a number to sharpen a point.
I name a person only when it helps you act, and I say what they did, not how well they did it.
I pick up where last week left off, so the read has memory and not just a snapshot.
I can draft your next 1:1 from how their week actually went, so you walk in prepared instead of guessing what to raise.
Where you will find me
I live inside Refer, across four surfaces.
The Monday read is where most people meet me first. It opens onto the rest: the overview of your week, the patterns worth a closer look, and the network behind the org chart.
See ReferBook a pilot
See what I read on your team.
Connect Slack in a few minutes. I read only the metadata, never message content, and write you the first Monday read.