Representatives — the feature that makes StandIn different

## The problem we kept seeing Every distributed team we talked to had the same pattern. Someone goes offline. Someone else has a question. The question waits until morning, or worse, it gets answered with a guess. The tools they had — Slack, standup bots, shared docs — moved information around. But none of them made that information queryable after the person logged off. The information existed, but nobody could find it without pinging the person who wrote it. ## What a Representative actually is A Representative is the queryable version of what someone published in their wrap. When Sarah publishes her end-of-day handoff at 17:00, her Personal Representative goes live. For the rest of the evening, anyone on her team can ask it a question and get a sourced answer from what she wrote. Not a summary. Not a guess. A sourced answer, citing Sarah's wrap and the timestamp she published it. When the answer is not in her wrap, the Representative says so. That refusal is not a limitation. It is the feature. Because when a Representative does answer, you know the answer came from a human, you know when they wrote it, and you can trace it back. ## Three types, same rules **Personal Representatives** speak from what one person published. Sarah's Personal Representative answers questions about her work — her blockers, her decisions, her handoff notes. **Team Representatives** roll up wraps from every engineer on a team. Ask the Amsterdam Team Representative what shipped overnight and get a sourced answer from six engineers' wraps. **Project Representatives** span teams and timelines. Ask the Payments Project Representative what's blocked and get answers from three teams in two time zones. All three types follow the same rules: sourced answers or silence. No guessing. No inference. No reading between the lines. ## Why refusal matters Most AI tools are optimized to answer every question. StandIn's Representatives are optimized to be right. The difference shows up at 2am when someone asks whether the API migration is done and the Representative says "blocked on ticket LIN-482, waiting on Dave's review" instead of "looks on track." The 10% of questions a Representative refuses are what make the other 90% worth believing. ## What Representatives replace The 45-minute morning catch-up meeting. The "quick question" that pulls someone out of deep work. The onboarding marathon where new hires sit through six 1:1s to get context. The status roll-up meeting that exists only because the information is not queryable. Representatives don't add a new meeting or a new process. They make the information that already exists available to the people who need it, when they need it. ## Try it We walk through a live Representative in every demo. An engineer goes offline, their Representative answers a question, and you see exactly where the answer came from. [Book a walkthrough](/request-access) to see it for yourself.