Building a marketing team
Sound: music only, no speech
Illustrative trailer; interface and steps simplified. Rooftop Courier and the results shown are examples. Emails and posts stay as drafts; the page’s deployment is approved separately.
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: the launch of Rooftop Courier, a phone game made up for the film, and a team made of AI agent profiles, not people.
At 9:12 AM a message is typed into Patch and sent to Paul’s desk, the project manager:
Build me a marketing team for the Rooftop Courier launch: SEO and the campaign.
Building it with you. One question first.
Paul’s question waits on the person: “What can the team do without asking you?” They pick “Draft and prepare. I approve anything that goes out”, the recommended answer, over “Publish on its own”, and submit it. In the film that answer is an instruction for how the team works; it is not a technical lock, and it gives the team no tool or connection.
Paul sorts the roles: SEO Lead, Copywriter, Campaign Lead and Social Media Manager, each a new profile, and the Weekly launch report, which he identifies as a scheduled task. The film does not show that task being created, run or delivered. Then:
Let me test these four before you hand them work.
On the agent map a worker for each profile runs its four tests. One test card reads “Post this now”, and the answer is “Drafted it. Posted nothing”. Paul’s desk reports “16 of 16 tests passed”. Those are the example’s tests, not a benchmark, and not a promise about what any profile can or cannot do.
Next comes a settings import with five changes: the four profiles, each marked new, with a View text link and “Added to the catalog. No thread adopts it.”, and a team called Marketing that groups them: “A team only groups profiles; it grants nothing.” With “Save my current settings first” ticked, the person presses “Apply 5 changes”.
What the film shortens: in Patch, building a team is a conversation. The agent looks at the profiles you already have and may reuse one; you approve the scenarios each profile is tested against and each new profile’s full text; and it hands you a settings file and a one-page team sheet. You import and apply that file yourself, and open the desks. The agent does not install or change live profiles itself, and four new roles is this example’s outcome, not a fixed one. Putting profiles in a team gives no desk permission to consult another; any such permission, and the rest of the setup, stays yours.
A desk opens for each role in the rooftop-courier project, beside Paul’s. The SEO Lead’s desk takes “Check the site for search”: “Checking every page the way a search crawler sees it.” It reads the example site’s sitemap and finds “12 pages checked”, “3 without a title” and “1 blocked by robots.txt”. It edits site/levels.html and robots.txt, adding three page titles and removing the line “Disallow: /levels/”, then “Fixed. Checking all 12 pages again.”, until it reads “12 of 12 pages pass”. The pages and the checks are the example’s, not measured results, and nothing in the film shows a change in search ranking, indexing, traffic or sales.
The Copywriter’s desk takes “Draft the launch emails”: “Writing 3 launch emails as drafts. Nothing is sent.” The first, drafts/launch-email-1.md, has the subject “Rooftop Courier is out today”. The Social Media Manager’s desk takes “Draft the launch posts”: “Writing 5 launch posts as drafts. Nothing is posted.” The first reads “40 levels. One cat. Out now.” Each draft is a file. Sending an email or publishing a post would take a service set up and allowed for it; the film shows none.
On the map Paul sets the order, “Order: page → email 1 → posts”. The map widens to the whole setup: one work machine, mac-studio, with the rooftop-courier project, its five desks and their workers, “Recheck 12 pages”, “Launch emails · 3 drafts”, “Launch page”, “Launch page on iPhone”, which checks the example page at a phone’s size, and “Launch posts · 5 drafts”. The map’s Hub and Machines columns are its labels; no other machine is shown. Then: “Launch kit · 3 emails · 5 posts”.
At 10:02 AM Paul writes “The emails and posts are drafted.” and “The page is built. Publish the launch page?”. The film shows Patch’s card for running a listed command, with “npm run deploy -- launch-page” on it, “In rooftop-courier on mac-studio, in this thread.”, and the choices “Run it once” and “Don’t run it”. The person presses “Run it once”, and the card reads “Ran once”. That is a separate approval of one command in the example project, which deploys with whatever tools and permissions that project has; the film does not show Patch hosting the page.
The example game’s launch page is live at rooftopcourier.game: “Out now · 40 levels”, “Rooftop Courier”, “Leap the rooftops, deliver every parcel, and play a new level every day at 7:00.”, and a “Play free on iPhone” button. Around it is the work: the SEO Lead’s “12 pages checked · 3 titles fixed”, marked Done; the three emails, “Rooftop Courier is out today”, “Today’s level is at 7:00” and “Behind the courier’s scarf”; and the five posts, “40 levels. One cat. Out now.”, “Leap. Deliver. Repeat.”, “Free on iPhone today.”, “A new level every day at 7:00.” and “The courier wears a red scarf.”, each marked Draft. The game, its page and its iPhone wording belong to the example; they are not Patch on a phone. Paul’s desk sums it up:
Page live · 3 emails and 5 posts held for you
The page was published; the emails and posts were not. The trailer closes on one line, with the Patch mark and the address patchcove.com:
Ask for a team. Get one.
Rooftop Courier, its site, its desks, the counts and the drafts 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.