Launch Studio Walkthrough
Takeda · SeeEOE · one SEO/GEO fix, from the first scan to Done · 28 screens · 25 September 2026, 10:29 to 13:42
Human in the loop
A person acts on ten of the twenty-eight screens. The rest is the agents working or reporting back. The ten have a violet dot in the filmstrip.
- 02 Read through the scan and picked the missing
<article>finding to follow. - 06 Picked the impact levels, named the plan, sent 15 issues across.
- 12 Opened a chat on the task and created the branch
feature/SEO-GEO_fix. - 13 Typed Can we work on Task 4? and sent it.
- 14 Answered Flight's question with Build it.
- 21 Read the Dev Agent's summary as the assigned reviewer.
- 22 Asked for a QA pass.
- 24 Did the visual QA in the Universal Editor and checked the markup and source, because the preview was locked for MLR review and the QA agent had no way in.
- 25 Approved the change and moved TASK-4 to Done.
- 28 Asked how long the rest of the branch would take unattended.
All told, about ten short actions over two hours, most of them under a minute. The long gaps, 11:03 to 11:23 and 11:59 to 12:34, are the agents working.
What came out of it
- 15 issues turned into 19 tasks. There's a Fix task per issue and a QA task per scoring group, and every one has a Definition of Done tied back to the rule id.
- One task took 133 agent steps, 22 minutes and three files, at about $3.18. With the QA spin-up the session came to about $7.48.
- The QA agent never finished. The preview is locked down at the client's request while the site is in MLR review, so the visual and source check happened by hand in the Universal Editor and TASK-4 was approved on that basis. The automated re-scan that would confirm
content-no-articleis gone is still open. - Flight's own estimate for the other three fix tasks plus QA is 75 to 105 minutes of unattended run time.
One fix, two ways
The article wrapper from scan to live, conventional stack estimated against Launch Studio as recorded. Conventional means Profound plus a crawler audit, GitHub, a developer driving Claude Code, and Edge Delivery.
| Conventional stack | Launch Studio | Note | |
|---|---|---|---|
| People involved | 5 to 7 | 1 operator + 2 agents | The client approver is the same person in both columns. |
| Hands-on time | 7 to 12 h | about 40 min | Ten short actions by one operator, most under a minute. |
| Elapsed time | 1 to 3 weeks | about 2 h | Both columns still wait on the client for approval. The site is in MLR review, and the preview stays locked until it clears. |
| Tools in the chain | 9 or 10 | 1, then EDS | Edge Delivery is the shared endpoint. Everything before it is one tool. |
| Cost | $575 to $985 | about $55 | Staffing chart rates, blended $94 an hour. Launch Studio is 40 min of operator time at the Tech Lead rate plus $7.48 of agent spend, including the QA Agent's attempt while the preview was locked for MLR review. |
| Monthly licensing | $1,280 to $4,770 | quoted | The conventional chain before Edge Delivery, list prices at September 2026, eight seats. Profound is 40 to 60 percent of it. Launch Studio is one subscription, priced per engagement. |