This is Crew One, running someone else’s company.
Northwind Robotics is an example company — a 14-person B2B robotics company. The interface below is the product’s own, over their data. Filter the trace, approve something, see what the crews are doing.
What happened overnight
Since 18:00 yesterday. Two contracts moved, one needs your signature, and the pipeline forecast slipped.
- 1Signal
Usage on the Halden Systems account fell 34% month on month, and the renewal is 21 days out.
- 2Evidence
Pulled from the CRM, the last three support threads, and the account’s usage history — each cited back to its source.
- 3Observation
A renewal at risk, with the drop concentrated in the two features their team used most.
- 4Recommendation
Reach out before the renewal window opens, referencing the drop and offering a call this week.
- 5ApprovalYou decide
The draft stops here. It is an external message, so it waits for a human — that is the rule you set, not a judgement the crew makes.
- 6Action
On approval the email sends, the CRM updates, and a follow-up is booked for the reply.
- 7Learning
The outcome is recorded against the decision. What you approved, edited or rejected becomes precedent the next renewal risk is judged against.
What stops for a human
Money leaving the company and messages going to customers wait here. Approve or reject one — this workspace resolves it locally, and nothing is sent.
Finance.Approve Invoice
Pay Ardent Logistics invoice #AL-2291 — £31,400.00
Gtm.Send Email
Send renewal-risk outreach to Halden Systems
Who is working, and on what
The Chief of Staff and eight specialist crews, as Northwind Robotics runs them. The two holding an approval are the two with a row in the queue.