Getting a customer ready by Monday
Sound: music only, no speech
Illustrative trailer; interface and timing simplified, with some approvals omitted. Fernhill Freight and its workspace, command and SSO setup are fictional examples. The Linux and multi-machine setup is not included in the current one-Mac customer offer. Contract checks are AI assistance, not lawyer review.
The film in text
The soundtrack is music only, with no speech. Everything the trailer says is on screen. It is an illustrated, shortened example made up for the film: getting Fernhill Freight, an invented customer, ready to start on Monday. The desks in it are AI agents with roles, not Patch employees, a managed operations team or licensed professionals, and the story’s timing is not a promised result.
On Friday at 5:40 PM a consult question from Chase’s sales desk reaches Olivia’s desk, the operations desk:
Fernhill Freight signed. 40 seats, SSO. They start Monday.
Olivia’s answer is a checklist, “Six things before Monday.”: Workspace, Single sign-on, Signed terms, First invoice, Welcome pack and Check-in schedule. A note added by the film, set apart from Patch’s own screens, then reads:
Handoff answered. Onboarding starts in a new turn.
On the agent map Olivia’s desk shows “idle · just now” and the map reads “Nothing running”: the answered turn is over. Then her desk turns to working, a new turn that starts the onboarding, before any work goes out. What the film shortens: in Patch, a desk answering a consult cannot pass it on to more desks, and the film leaves out the setup and some of the steps in between.
The map shows a hub, agent-hub-hetzner, and three machines: linux, with the operations project and Olivia’s desk; a MacBook Pro, with the sales project and the desks of Chase (sales), Michael (finance), Saul (legal) and Sedrick (writer); and mac-studio, with the patch project and the desks of Arthur (architecture) and Paul (PM). The Linux and multi-machine setup is not included in the current one-Mac customer offer. The hub’s name is a label, not a hosting service Patch offers, and the film does not offer more machines, or Patch on a phone, as something to buy.
From Olivia’s desk the work goes out through the hub, one label at a time: “First invoice · 40 seats” to Michael’s desk, “Signed terms against ours” to Saul’s desk and “Welcome pack” to Sedrick’s desk. Arthur’s desk gets “SAML or OIDC for Fernhill?”, and its answer comes back: “SAML. Their provider is supported.”
What the film shortens: these consults rely on consult switches and permissions set up beforehand. A consult with no approval card, as here, is not Patch’s default; it takes a saved approval or an opt-in made in advance, and those still stop at Patch’s hard limits.
Olivia’s desk starts a worker, “Create the workspace”: “Setting up the workspace Fernhill Freight starts in on Monday.”, with a progress bar for “Workspace fernhill-freight · 40 seats · SSO: SAML”. The worker stops, waiting on you, on Patch’s card for running a listed command: “Run a listed command”, the command “workspace create fernhill-freight --seats 40 --sso saml”, “Matched workspace create.” and “In operations on linux.”, with the choices “Run it once” and “Don’t run it”. The person presses “Run it once”, the card reads “Ran once”, and the worker lands.
The workspace command, the customer’s 40 seats and its single sign-on are an invented customer system: Patch does not ship that command, or a single sign-on or provisioning connection, and the 40 seats are the customer’s, not a count of Patch licences. Real work depends on your own tools, access and settings. “Run it once” allowed this one listed command, once; it approves no later command, and it does not approve the rest of the onboarding. The progress bar, the worker’s card and the checklist simplify Patch’s screens.
Saul’s desk, the legal desk, returns one line to Olivia’s desk, “Clause 9 changed: data kept 90 days”, and the bell lights. In Alerts, under Questions, Olivia’s desk asks:
Fernhill changed data retention from 30 days to 90. Accept it?
The choices are “Accept for this customer (Recommended)”, “Send it back to legal” and an optional Other. The person picks the first and presses Submit, and the question moves to Resolved, marked answered: “Accept for this customer”.
The legal desk is AI assistance, comparing the example’s signed terms with the standard ones and flagging a changed clause for a person to decide; no lawyer reviewed them, and “Recommended” is the example desk’s suggestion for this one customer, not advice. The answer is the owner’s business instruction in the story: it certifies nothing, amends no contract and changes no retention setting by itself, and the 90 days belong to the example contract, not to Patch.
A click on Scheduled opens Tasks. A new task is at the top, under linux: “Fernhill Freight check-in · first 4 weeks”, Mondays, next run “Mon 9:00 AM”, last run “Not run yet”, in operations. Below it are two tasks already there, “Review sales notes” under MacBook Pro and “Nightly backup” under mac-studio, each daily. A second note added by the film, outside the table, reads:
Schedule approved separately; approval step not shown.
An agent proposed the check-in, and its approval is left out of this shortened story. Neither the workspace command nor the contract answer approved it. In Patch an agent’s proposed task waits for your approval, unless you turn on a separate setting that approves eligible agent jobs, and this example is read as approved the ordinary way. The task has not run and has delivered nothing, and “first 4 weeks” is part of its name, not a setting that stops it after four runs. “Review sales notes” reviews notes kept as files, not email.
On Monday at 8:00 AM Olivia’s checklist has every row ticked, beside a screen of the customer’s workspace: “Fernhill Freight”, “40 seats · SSO on”, “ready”. One line stays yellow:
Welcome pack is drafted. Send it when you’re ready.
The first invoice and the welcome pack are prepared drafts. The film shows nothing sent, posted, charged or invoiced through a connector, and no customer record updated.
Every desk sends one last streak to the middle, the Patch mark forms, and the trailer closes on one line, with the address patchcove.com:
Ready by Monday.
That is this story’s ending, not a service level or a promise that work finishes over a weekend. Fernhill Freight, its workspace, command, single sign-on, contract, invoice and welcome pack are an example.
More trailers
- 01Building Patch with Patch One message, a new agent map layout: four lanes build and test it, two reviewers and a designer sign off, one approval releases it.
- 02Making a game with Patch A phone game from brief to store listing: desks tune a cat’s jump, draw its run cycle and playtest its levels, and the calls are yours.
- 03Building a marketing team Ask for a marketing team: four AI profiles are tested, an example site’s titles are fixed, emails and posts are drafted, and you approve the page’s deploy.
- 04Getting a customer ready by Monday An illustrated AI operations team prepares a fictional customer’s onboarding, bringing a workspace command and a contract question to the owner for approval.