Now onboarding design partners · 10 teamsFor distributed engineering teams

Amplify your work.
Don't automate
it away.

Your work stays yours. Your voice stays yours. StandIn just makes it reachable.

standin › gateway-team-rep
Typing
Live demo · click to try
Pieter · Amsterdam · 09:02 CET
Live54wraps in the last 2h
Tokyo8
Sydney5
Bengaluru11
Amsterdam14
New York9
SF7
Early pilot signal · 10 design-partner teams
0min
saved per daily standup
n=10 teams · self-reported · 6-week avg
0%
fewer "what did I miss?" pings
Slack DM volume · pre/post pilot · same teams
0.0x
faster async handoffs, Tokyo→SFO
time-to-unblock · measured on 214 threads
Three principles

We're building the opposite of an agent that does your work for you.

Every other tool is racing to do work for you. We hold your work and make it reachable. Different problem. Different shape.

01
When the answer isn't there.

We say so.

StandIn refuses to guess. "Not in the record" is information. It tells you who to ask.

02
Amplify humans.

Don't replace them.

We hold your work and make it reachable. Your teammates quote your own words, not an AI's guess.

03
Only what you wrote.

Nothing guessed.

No surveillance. No DM reading. No calendar scraping. A representative knows only what its person declared.

From the field
My morning used to be 90 minutes of catch-up. Now it's a couple minutes of reading wraps, and I know more than the standup ever told me.
Eng manager·distributed infrastructure team · 14 engineers across 5 timezones
How it works

Two layers. One ritual.

Wrap_01 · Input

Wraps. The input layer.

Before going offline, each teammate publishes a daily wrap. Auto-drafted from the tools they already use. Under 60 seconds.

80% of your wrap writes itself from the tools you already use.

Wraps capture trade-offs, not just outcomes. Future-you will thank you.

Every unknown has an owner. "Waiting on" becomes a first-class field.

The goal isn't thorough. It's fast. Published daily beats perfect never.

Rep_02 · Output

Representatives.
The output layer.

Every wrap becomes queryable. A Representative answers only from declared content, cites every claim, and refuses when the answer isn't there.

No sentence lands in an answer without a source. Traceable end to end.

When nothing was declared, your rep says so and names who to ask.

One engineer's rep. One team's rep. One launch's rep. Scoped by who declared what.

A rep knows nothing about your activity, DMs, or calendar. By design.

A working day, in data

Representatives represent your work. They don't replace it.

Four things change when context is infrastructure, not tribal knowledge.

01·Global handoff
TYOAMSSFO17:00 JST09:00 CET00:00 PST

A ritual that replaces the meetings.

Catch-ups, status pings, handoff docs. All of it absorbed into a 90-second wrap that auto-drafts from your stack. Tokyo ships, Amsterdam reviews, SF picks it up, without any of them overlapping live.

02·One record
AUTHOR · DECLARATIONCITEDSORAPIETERMARCUSPRIYA·SORADAVEELENAPIETER·MARCUS

Every decision, cited and sourced.

Wraps from every engineer, PM and designer roll into one queryable ledger. Searchable by teammate or by AI, with citations on every claim.

03·Human-first
SOURCE OF CLAIMINFERREDDECLARED70%95%Who decided50%90%When30%88%Why15%82%Trade-offs42%78%Next step10%70%Open Qs

The thinking stays yours.

StandIn never invents a decision you didn't make. It retrieves what you wrote, with your name and timestamp on every line. Judgement doesn't get outsourced.

When Amsterdam logs off

When Amsterdam logs off, the context goes with them.

Decisions, reasoning, blockers. It all lives in one person's head. When they're asleep, your team in San Francisco starts piecing it back together from Slack threads and guesses.

  1. 01The morning catch-up meeting.
  2. 02The 11pm ping across timezones.
  3. 03The four-meeting onboarding marathon.
  4. 04The "where are we on this?" status request.
  5. 05The vacation handoff nobody writes well.
Not an agent. Not a bot. Not a summary.

Agents infer. Representatives declare.

One guesses to fill silence. The other refuses, and the refusal is information.

AI agent
StandIn representative
Source of knowledge
Inferred from logs, calendars, DMs
Declared by the person, in their own words
Inferred claims drift when the signals change. Declared ones persist, carry reasoning, and stay attributable. That is what engineering decisions actually need.
When uncertain
Generates a confident guess
"Not in the record" + names who would know
A confident wrong answer is worse than no answer. Refusal is actionable. You know exactly who to ping, and you stop trusting the tool when it fills gaps.
Citations
Best-effort, often missing
Every claim cited to a wrap, author, timestamp
Auditability matters when answers feed into shipping decisions. Every sentence your rep says should be traceable back to a specific person on a specific date.
Surveillance
Reads everything you do
Knows only what you wrote
Activity monitoring corrodes trust and produces low-signal noise. Declarations are opt-in by definition. Your team chooses what their rep knows.
Trust model
90% true, 10% guessed
Refusal is a feature, not a failure
The 10% guess is why nobody trusts AI for load-bearing engineering work. Removing it, intentionally, is what makes a rep load-bearing.
Employee-first trust

The constraint is what makes the answers trustworthy.

A tool that tells the truth 90% of the time and guesses the other 10% is unusable for anything that matters. So we built one that admits the gap.

No surveillance

Zero activity tracking, calendar access, or DM reading.

No passive monitoring

A representative knows only what its person wrote down.

Declaration-based by design

You opt into what your representative can answer about.

Refusal as a feature

"Not in the record" is the default. Never a confident guess.

Auto-drafted from

We meet your stack where it already is.

Every signal maps to a specific wrap field. The 60-second ritual is a read and confirm. Most of the writing is already done.

Signals in
G
GitHub
commits · PRs · reviews
L
Linear
issues · cycles · status
J
Jira
tickets · sprints
C
Confluence
docs · RFCs
N
Notion
RFCs · wikis
A
Asana
tasks · milestones
D
Discord
channels (opt-in)
M
Monday
workflows · status
mapped to
Wrap fields out
Decisions made
what we chose and why
What shipped
what's in prod or merged
Blockers
what's in the way
Context & reasoning
the thinking behind it
Open questions
what's still unresolved
+ webhooks · REST · MCP · custom adapters on request
Correct refusals

“I don't know” is a feature.

When StandIn doesn't have declared state, it says so. No inference. No hallucination. The refusal tells you what's missing and who to ask next.

data-platform-reprefusal · cited
Q ·
Who approved the shift to Postgres 16 on the data platform?
Not in the record.
No declaration found mentioning "Postgres 16" from any owner on the data platform team in the last 30 days.
Ask Priya (data-platform lead) or check the #platform-changes channel.
gateway-teamrefusal · cited
Q ·
What was the final rate-limit agreed for the public API?
Partially declared.
Dave proposed 120 req/min on 2026-04-12. No follow-up declaration confirms a final value.
Treat as draft. Ping Dave or Elena for a confirming wrap.
gateway-teamrefusal · cited
Q ·
Is the mobile team on track for the June ship?
Cannot answer. Out of scope.
This rep covers gateway-team only. Mobile declarations live on a different rep.
Query mobile-team-rep directly or ask Sora (eng director) for a cross-team roll-up.
I came back from two weeks of leave and didn't have a single "what did I miss" meeting. The record was just there.
Senior engineer · design partner · Series B fintech
Our reps quote the engineers, not a model. When the answer isn't there, they say so. That's what makes it usable.
CTO · pilot · global e-commerce
Pre-seed open · pilots running now

Amplify your work.
Without automating
it away.

Every email to this address is answered by a human, usually within a day. No support queue. No form. Tell me about your team and we'll figure out if StandIn fits.

[email protected]· Amsterdam, NL
Parker
Founder · StandIn