Create a campaign landing page with Claude Cowork

Turn a campaign folder into a useful brief

Claude Cowork is useful when the ingredients for a landing page already exist across documents: a service description, approved logo, old presentation, and notes from customer calls. The first job is to reconcile those materials into one offer. A polished page assembled from contradictory documents still makes a confusing campaign.

This guide describes a desktop folder workflow based on current documentation. It does not report a hands-on Cowork-to-Pageree account test. Check that your own client exposes the required tools before relying on this publishing route.

Create a dedicated folder containing only the materials for this campaign. Add a short offer.md that says which document takes precedence when prices, dates, or claims differ. For local file access, Anthropic’s current instructions require the desktop app to be available; access to Cowork and individual capabilities depends on your account and workspace. See Cowork’s getting-started guide.

Ask for an inventory before a page

Imagine a small workshop business preparing a team-training campaign. Its folder might contain a current workshop outline, an old sales deck, facilitator photographs, and approved customer quotes. Have Cowork distinguish current facts from reference material:

Review the files in this campaign folder for a landing page about our team workshop.
Use offer.md as the source of truth. Make a table of audience, deliverables,
format, location, price, availability, proof, and approved images.
For each fact, name its source file. Flag contradictions and missing information.
Do not turn a customer note into a testimonial or reuse an old price automatically.
Propose one primary action: request workshop details. Do not publish anything.

Review the table yourself. An old presentation can provide a useful visual direction without being a reliable source for this month’s availability. Use the brief worksheet to settle the offer before layout work begins.

Connect the publishing tools

Add Pageree as a remote connector using https://mcp.pageree.com/ and complete the account authorization. Use the maintained connection instructions for the steps available in your client. Anthropic documents remote custom connectors for Cowork; these connections are brokered through the Claude account, whereas local Desktop MCP configuration is a separate mechanism. See remote connector setup.

In the actual Cowork session, ask it to read your Pageree account and list existing pages. Proceed only after a tool response identifies the account. If Pageree is unavailable in that session, Cowork can still prepare the approved brief and compatible HTML for a supported Claude publishing conversation. A file handoff is a valid next step; a claimed publication without a returned URL is not evidence of hosting.

Build from approved materials

Use the approved campaign facts to create a Pageree landing page for our workshop.
Explain who it suits, what participants work on, what the engagement includes,
and what happens after an enquiry. Ask for any missing factual details.
Use only authorized images and quotes. Do not invent customer results.
Follow Pageree's current page, asset, form, privacy, and publishing skills.
Create one HTML document with inline CSS and JavaScript and hosted image URLs.
The form should request name, email, team size, and the workshop challenge.
Ask me for the destination inbox and desired page address.
Save a private preview and retain its page ID. Wait for my review before publishing.

Ask Cowork to retain a campaign handoff containing the approved facts, source filenames, page ID, and remaining checks. Keep credentials out of this document. That small record prevents the next session from rediscovering old files and choosing a different offer.

Review the campaign as a visitor

Check that the headline names the workshop’s practical outcome, the images match the service, and the enquiry does not imply a confirmed booking. A team-size field should help you prepare a reply; it should not silently quote an unapproved price. Test the mobile layout, keyboard navigation, and form validation in the actual preview.

After you approve the preview, ask for publication. Open the resulting public URL and send a clearly marked enquiry using an address you control. Confirm receipt in the configured destination. Draft forms use email delivery and do not prove a live CRM workflow; the email-delivery guide explains the distinction.

Save the public URL alongside the campaign brief. When the workshop changes, update that same page through its stored identity rather than creating a new page from the original folder every time.