The Prototypes connector lets you ask Claude for a real web page — a dashboard, a report, a mockup — and get back a link on portcast.team you can share with anyone at Portcast. You edit it by chatting. No code, no files, nothing to install.
“Create a prototype called ‘Pipeline Review’ with my open HubSpot deals by stage…” The better the brief, the better the first version.
Claude replies with a live portcast.team URL in ~10 seconds (the page finishes publishing ~30s later). Private by default — only @portcast.io accounts can open it.
“Make the headline bigger.” “Add a churn column.” Same link updates in ~20 seconds. Full history, undo anytime, and teammates can edit the same page too.
Artifacts are great in a chat, but the moment you want to hand it to the team, you want this instead:
Real workflows from our own Slack, Notion, ClickUp and HubSpot — each card has a prompt you can copy into Claude and make your own.
Open deals from HubSpot by stage with totals and aging — the Monday pipeline call starts from the same page, already up to date.
Create a prototype called "Pipeline Review". Pull my open deals from HubSpot (stage, amount, close date, owner), group them by stage with totals, and flag anything with no activity in 14+ days. Dense dashboard style. Then implement daily sync. Keep it private.
One page per active trial: goals, KPIs, weekly progress, open issues. Keep it private while you work — flip it public for the prospect call.
Create a prototype called "Trial Scorecard — [prospect]". Sections: trial goals & KPIs (I'll paste them from our Notion trials table), weekly usage summary, open issues, next milestones. Clean and customer-presentable. Private for now — I'll make it public when we share it.
The approved answers we keep rewriting — security, data sources, integrations, SLAs — on one searchable page, each answer copyable.
Create a prototype called "RFP Answer Library". A searchable page of our standard RFI/RFP answers grouped by topic (security, data coverage, integrations, SLAs). I'll paste the approved answers; add a filter box and make each answer easy to copy. Private.
New MQLs from HubSpot with company, source and status, plus a week-over-week summary. The page stays fresh on its own.
Create a prototype called "Inbound Leads — Weekly". From HubSpot, list contacts that became Marketing Qualified Leads in the last 7 days with company, source and current status, plus a summary row comparing to the week before. Then implement daily sync. Private.
Sree’s data-backed sections — top congested ports and 3-month transit trends — as a page the team reviews before each issue goes out.
Create a prototype called "Newsletter Data Preview — [month]". Two sections to review with the team: top congested ports this month, and 3-month transit-time trends for our key lanes. I'll paste the data; chart it simply with a one-line takeaway per chart. Private.
The digest project from the marketing backlog: per-competitor news, product changes and pricing signals — with a “so what for us” line each.
Create a prototype called "Competitor Intel — Weekly". One section per competitor: notable news, product changes, pricing signals, each with a short "so what for us". I'll paste this week's findings; lay it out as a scannable brief with a summary on top. Private.
Every account in the HubSpot onboarding pipeline at its stage, with days-in-stage and owner — stuck accounts flagged automatically.
Create a prototype called "Onboarding Tracker". From HubSpot's onboarding pipeline, show each account at its current stage with days-in-stage and owner; flag anything stuck more than 14 days. Then implement daily sync. Private.
The weekly trial reports we already assemble — as one live page per prospect, built from the trial’s use cases and KPIs, presentable as-is.
Create a prototype called "Weekly Trial Report — [prospect]". Use the trial's use cases, KPIs and report requirements (I'll paste them from Notion), this week's tracking stats, and an exceptions section to discuss. Customer-presentable. Private until we send it.
Per tier-1 account: onboarding milestones from ClickUp, open issues, usage notes, renewal and QBR dates — updated by chat as things change.
Create a prototype called "Account Health — [customer]". Sections: onboarding milestones (from our ClickUp Customer Success folder), open issues, weekly usage notes, upcoming renewal and QBR dates. One page I'll keep updating by chat. Private.
Take a roadmap item — say, Alerting — and put a working-feeling mockup in front of a customer the same afternoon.
Create a prototype called "Alerting — Concept v1". A clickable mockup: an alert list with severity filters, an alert-detail drawer, and a settings panel for thresholds. Use realistic shipment data. Private — when it's ready for a customer test I'll ask you to make it public.
Epics from the ClickUp Product folder on a quarter-by-quarter board with a “shipped recently” strip — the answer to “what’s the status of…?”
Create a prototype called "Product Roadmap — Live". Pull epics from our ClickUp Product folder (status, target month) into a quarter-by-quarter board, with a "shipped recently" strip at the top. Then implement daily sync. Private.
A page variant to react to — new positioning, a pricing tier, a feature framing — before anything touches the real site.
Create a prototype called "Pricing Page — Experiment". Hero with new positioning, a three-tier pricing table with realistic features, and an FAQ. I'll paste our current copy as the starting point; propose one bolder variant of the headline. Private.
Customer-impacting issues, sprint progress and bug counts from the ClickUp ETA space — standup starts from the same page every day.
Create a prototype called "Sprint Health — ETA". From ClickUp's ETA space: open Customer Impacting Issues, current sprint progress, and bugs by status. Then implement daily sync so standup starts from this page. Private.
Turn a one-off analysis (port congestion, transit times, carrier performance) into a clean page with charts and a methodology note.
Create a prototype called "Port Congestion — [port]". I'll paste the query output; chart daily vessel traffic and weekly waiting times (mean/median/p90) for the last 3 months, with a short methodology note. Clean, customer-presentable. Private.
The Notion agents catalog as a live page: each agent’s status, maintainer, hours/month and cost — tracked against the 180 h/month target.
Create a prototype called "AI Agents — Status Board". From our Notion agents catalog: each agent with status, maintainer, hours/month and token cost, plus total hours against the 180 h/month target. Then implement daily sync. Private.
Application → screen → interview → offer with counts, conversion and days-open per role — one link for every hiring sync.
Create a prototype called "Hiring Funnel — Live". Stages from application to offer with counts and conversion rates, plus open roles and days-open. I'll paste this month's numbers; lay it out like a recruiting dashboard. Private.
A friendly one-pager: first-week checklist, who’s who, tools to set up, FAQs — easier to keep current than a buried doc.
Create a prototype called "New Joiner Guide". A friendly one-pager: first-week checklist, who's who (roles, not photos), tools to set up, and FAQs. I'll paste our existing onboarding doc; make it skimmable with anchors. Private.
Offsite options, policy changes, budget proposals — laid out as a page people can actually discuss in the meeting.
Create a prototype called "Offsite 2027 — Proposal". Three location options as comparison cards (cost per person, travel time, vibe), a recommended option with rationale, and an open-questions section. I'll paste the research. Private.
MRR, run-rate and net-new from the invoicing sheet, refreshed daily through connectors. Not a concept — it’s running now.
Open the Company Health Live prototype and tell me: which data on this page is kept fresh, who keeps it fresh, and when it was last checked?
Yesterday’s pipeline movement, customer flags from the tier channels, and the day’s focus — one page that’s ready before you are.
Create a prototype called "Daily Brief". Sections: pipeline deals that moved stage yesterday (HubSpot), customer flags worth knowing (I'll describe which Slack channels matter), and top 3 focus items for today. Then implement daily sync. Private.
The quarter on one page — growth, retention, pipeline, costs — with an honest chip on every section saying exactly how fresh it is.
Create a prototype called "QBR One-Pager — Q2". Four sections: growth, retention, pipeline, costs. I'll paste the numbers and tell you the source and as-of date for each — label every section with its source chip. Private.
Any data section can refresh itself every day. You say “implement daily sync” — Claude sets up the whole thing in the chat, using the connectors you already use. Every section then wears an honest label:
https://portcast-prototype-mcp-502842186904.asia-southeast1.run.app/mcp