pages.useCasesFirst30Days.heroHeadline
pages.useCasesFirst30Days.heroLede
Four phases. Each one does a different kind of work on the team.
Turning it on
The silent installation.
Only one person needs to auth the integration in Slack/Teams.
StandIn sits silently in channels. It does not interrupt.
Your pilot team (one project) posts their first end-of-day wraps.
Learning the rules
Friction establishes the protocol.
Someone will ask a private/gossip question. StandIn will refuse to answer. This builds trust.
Most wraps arrive pre-filled from the day's work. The habit isn't writing — it's reviewing and hitting publish. When someone skips it, the next morning a question goes unanswered. They won't skip again.
When StandIn refuses to answer a gossip question or a privacy-violating query, something important happens: the team sees the boundary is real. Not a policy. Not a promise. An architectural constraint the system enforced in front of everyone. That moment builds more trust in 10 seconds than a month of privacy policy reading. The refusal is the proof.
Turning it on
The silent installation.
Wraps start as auto-drafted bullet points from actual work output. By Week 2, people learn to add the context that tools can't capture — handoff notes, blockers that need explaining, decisions that happened in a call.
Instead of "Any updates?", queries become "Did Sarah merge the auth fix?". Precision increases.
Learning the rules
Friction establishes the protocol.
The notification volume after 6 PM drops by ~80%. People stop checking Slack "just in case".
The "morning archaeology" of reading 400 messages is replaced by a single query to StandIn.
What does not happen
pages.useCasesFirst30Days.notHappenIntro
No Surveillance
Managers never get a "who is working" dashboard. Activity metrics are never exposed.
No Surveillance
Managers never get a "who is working" dashboard. Activity metrics are never exposed.
No Surveillance
Managers never get a "who is working" dashboard. Activity metrics are never exposed.
New hires ramp faster with Project Representatives
Instead of scheduling six intro meetings in the first week, new engineers query the Project Representative. "What's the status of the payments migration?" returns sourced answers from three teams. "Who owns the auth service?" returns a name and a timestamp.
New hires build context at their own pace, from what the team actually published, without waiting for someone to be available. By week two, they're asking better questions. By week four, they're publishing wraps that answer other people's questions.
How Representatives work