Why connect Productised to Claude
When it makes sense to drive Productised from Claude, when it doesn't, and how it changes the way you build.
You can build, ship, and run a complete AI product business inside Productised without ever opening Claude. The platform is designed to stand on its own — the canvas, Brain, the Create-with-AI flow, themes, branding, analytics, and lead pipeline all work from a browser.
The Claude Connector is for the people who already live inside Claude — coaches, consultants, founders, and operators who treat Claude as their primary thinking surface — and want their Productised workspace to be a first-class citizen there.
Three ways people use the connector
1. As a faster way to build
You describe the product in plain English ("a leadership readiness scorecard for first-time executive coaches"). Claude plans it, builds it, configures the agent, applies a default result template, and gives you a live demo URL. In one message.
You can keep iterating in the same conversation: "make it more direct", "add a question about team size", "switch the result to a radar chart". Each tweak is a real, persistent change with an immediately-previewable result.
2. As a design partner for result pages
Result pages are where Productised products shine — a personalised, branded outcome that feels like it was made for one person. The connector turns Claude into the designer.
Ask Claude to design the result page in conversation. It writes the HTML, the connector validates that every {{ object:* }} token matches a field your AI agent produces, suggests any missing fields, and saves the page. You get a live URL back.
Then iterate: "make the gauge bigger", "add a 'critical gap' callout in red", "I want a dark mode version", "swap the CTA copy". Claude reads the current HTML, tweaks it, saves it back.
3. As your daily lead pipeline cockpit
If you already start your day in Claude, you can keep it as your single surface: morning briefing, hot leads, recent activity, segment breakdowns, tagging, status changes — all conversational, all logged.
"Give me my morning briefing." "Tag Sarah at Acme as a hot lead and mark her contacted." "What products are converting best this month?"
When it makes sense
- You already work in Claude every day. The connector means you stop context-switching.
- You want to design and iterate fast. Talking through changes is faster than clicking through panels — especially for result-page HTML.
- You build for many clients. A single conversation can configure branding, swap themes, set a custom domain, update SEO, and publish — for one client product at a time, in series.
- You like working from a description. Plain-English specs become real products in one round-trip.
When the canvas is still better
- Visual graph thinking. When you want to see how nodes connect, the canvas is unbeatable.
- First-time exploration. Newer users tend to learn the platform faster by clicking around than by talking to it.
- Big multi-node products. When you're wiring up scoring, multiple agents, and branching outcomes, the canvas's spatial layout helps you reason about the flow.
Most people end up using both — building on the canvas, then editing via Claude once the structure is set.
What the connector cannot do
- Delete products, pages, or responses. Destructive operations stay in the dashboard.
- Authenticate as you. OAuth 2.0 — you sign in to Productised in a popup, click Authorise, and revoke at any time from either side.
- Change billing or subscription state. No financial actions through the connector.
- Read or send personal email/messages. It operates on your Productised workspace only.