Our Mission

About StandIn

We build infrastructure for continuity, not surveillance.

Why StandIn Exists

The modern distributed team is broken. We have successfully distributed talent across the globe, but we have failed to distribute the context they need to work.

When time zones shift, context resets. London wakes up and spends hours figuring out what New York did. San Francisco stays online until midnight to answer questions from Tokyo.

Most organizations try to fix this with more meetings ("syncs") or by demanding "responsiveness" that destroys work-life balance. Existing tools force a trade-off: either total silence (blocking work) or total noise (Slack chaos).

We built StandIn because we believe you shouldn't have to choose between sleep and continuity.

The Insight

Ambient context is missing

Physical offices worked because context was ambient. You saw who was talking to whom. You heard decisions being made. You knew when someone left for the day.

Distributed teams lose this by default. In a remote environment, if it isn't written down, it doesn't exist. But writing documentation is heavy, slow, and often ignored.

StandIn creates a third way: Structured, Declared Continuity. We don't try to recreate the office. We build a mechanism for handing off the baton of work explicitly, so the next runner can start at full speed.

Our Approach

01

Declared, not Observed

We reject the "surveillance" model of AI. We do not infer what you are doing by watching your mouse or reading your private DMs. We only know what you explicitly tell us via a Wrap or a commit.

02

Humans as Authors of Record

AI should transport context, not invent it. When StandIn answers a question, it cites the human who provided the answer. Accountability remains with people.

03

Refusal is a Feature

A system that guesses is a liability. If the answer isn't in the declared record, StandIn stays silent. We prioritize trust over being "helpful" at the cost of accuracy.

What StandIn Is Not

Not a Monitoring Tool

We do not track activity, presence, or "time online".

Not an "AI Manager"

We do not score productivity or evaluate performance.

Not a Magic Box

We do not "figure things out" from unstructured noise. We require structure.

Not a Spy

We never ingest private messages or DMs.

Who StandIn Is For

  • International teams spread across non-overlapping time zones (e.g., NY/London, SF/Tokyo).
  • Engineering, Product, and Operations organizations that manage complex state.
  • Companies that value deep work and want to protect their employees' off-hours.

Who It Is Not For

  • Teams that require real-time, synchronous availability (e.g., L1 Incident Response rooms).
  • Leaders looking for surveillance or activity tracking software.
  • Organizations unwilling to adopt the discipline of publishing end-of-day context.

"We believe that work should stay at work.
By building better boundaries, we build better teams."