Claude Code publishes an AI-coaching booking page
Schaber reports launching an AI-coaching service page by transferring Cowork’s positioning into Claude Code, applying a saved webpage skill and embedding Google Calendar booking in Elementor.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Use our approved coaching offer and webpage skill to create the service page. Ground the copy in the workspace, embed the supplied Google Calendar booking code, and show me the finished HTML for wording review before I publish it in Elementor.
Reach people exploring AI agents
See placements →What happened
Schaber reports launching an AI-coaching service page by transferring Cowork’s positioning into Claude Code, applying a saved webpage skill and embedding Google Calendar booking in Elementor.
Reported by Patrick SchaberHow the agent did it
- Develop the coaching offer and positioning in the business workspace.
- Have Cowork prepare a handoff instruction for Claude Code.
- Apply the saved webpage skill and review the generated HTML copy.
Where a person stepped in
Schaber defines the service, reviews wording and performs the final Elementor publication. The article does not establish launch conversions or revenue.
Patrick Schaber develops a one-to-one AI-coaching offer after a business owner asks why a useful demonstration call is not a paid service. He works through the positioning in Claude Cowork, then transfers the resulting instructions into Claude Code inside his existing business workspace.
A saved webpage-creation skill carries his format and strategy. Claude Code creates an HTML file in the workspace’s output folder, and Schaber adjusts selected text through the preview interface. He supplies a Google Calendar booking-page embed, which the agent adds to the page.
The finished HTML is copied into an Elementor HTML block on his existing WordPress site. This is a completed published service page, not a claim that the agent independently deploys or sells the offering. Schaber chooses the offer, supplies business context, reviews copy and performs the final WordPress handoff.
The useful pattern is carrying approved messaging from one task into the production environment, with a reusable skill defining the page structure. A working booking embed connects the marketing artifact to an actual scheduling path. The source describes supporting slide and outreach drafts too, but does not document a conversion or revenue result from this launch. Its publication also promotes the author’s coaching business, so speed and quality remain personal assessments rather than an independent benchmark.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Patrick Schaber
Frequently asked questions
How did messaging reach Claude Code?
Cowork prepared a prompt after the positioning work, which Schaber transferred into the same business workspace.
How was the page published?
Schaber copied the finished HTML into an Elementor HTML block on his WordPress website.
Did the account prove the launch won clients?
No. It documents the service page and supporting drafts, without a measured sales result.
More details
Remaining steps
- Add the supplied Google Calendar booking-page embed.
- Copy the finished HTML into the WordPress Elementor page and inspect it live.
About this account
Claude Code uses the business workspace and webpage skill to build a branded HTML service page, revise selected copy and integrate a supplied booking embed.
Firsthand account by Patrick Schaber; original publication date verified against Original Substack byline Apr19,2026. Outcomes are the author’s reports, not independently reproduced. Suggested prompt written by Agents In Use; not the author’s original prompt.
Credit: Patrick Schaber
Source published 19 Apr 2026
Source checked 14 Oct 2026
Tools and topics
Claude Cowork · Claude Code · patOS workspace · Webpage skill · Google Calendar booking · WordPress · Elementor
Positioning-to-page handoff · Service booking embed · Reviewed HTML publication
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.