Claude Artifacts for Marketers: Calculators and Mini Tools

#01What is an artifact now?

Anthropic describes an artifact as "anything Claude makes for you that you'd put in front of someone: a design, a deck, a document, a dashboard, or a small interactive tool" (Anthropic). It opens beside your conversation, and you can edit it by talking to Claude or directly, then share or export it.

Since September 2026, artifacts also come with templates. Docs, Slides and Design are available on every plan and on by default. Dashboards is in beta on paid plans, and Motion, for animated explainers, is in beta on Team and Enterprise. Artifacts need code execution and file creation turned on in Settings > Capabilities.

What each plan includes, according to Anthropic's help centre:

Our view: for marketers, the interactive tools are the hidden gem. Most teams use artifacts for documents and never discover that a twenty-minute conversation can produce a working calculator for the sales team.

#02Which marketing tools are worth building?

Look for tasks where people repeat the same steps or ask the same questions. Good first projects:

• ROI or savings calculator for a landing page prototype or for sales to use on calls.
• Campaign brief builder that walks a requester through the questions your team always asks.
• Headline and subject-line scorer that checks length, reading level and banned phrases from your voice guide.
• UTM link builder that enforces your naming conventions, so reports stay clean.
• Content calendar tracker shared with the team, using shared storage.
• Persona quiz for an internal workshop, or a lead-magnet prototype to test before building it properly.
• One-page campaign report with charts from an uploaded CSV.

Each of these is small enough to build in one conversation and useful enough to save hours a month.

#03How do you prompt for a good tool?

Describe the user, the inputs, the outputs and the rules, just as you'd brief a developer. Be specific about edge cases, because that's where simple tools break.

Build an interactive UTM link builder as an artifact.
Users: marketers on our team, not technical.
Inputs: destination URL, campaign name, source (dropdown:
linkedin, google, meta, newsletter, partner), medium
(dropdown: cpc, social, email, referral), optional content.
Rules: lowercase everything, replace spaces with hyphens,
campaign name must start with YYYY-MM, warn if the URL
already has UTM parameters.
Output: the full URL with a copy button, and a list of the
last 10 links built (personal storage).
Style: clean, our brand colours #1F3A5F and #F4B400.

Then test it like a user would. Try the awkward inputs: a URL with a fragment, a campaign name with capitals, an empty field. Tell Claude what broke, and it will fix it. Two or three rounds usually gets a tool that's ready to share.

#04How do you build a landing page mockup?

Use the Design template, which Anthropic describes as covering visuals, mockups, prototypes, one-pagers and landing pages, built with your design system (Anthropic). Designs export as a .zip, PDF, PowerPoint or standalone HTML.

Create a landing page mockup for [offer].
Audience: [who]. Main promise: [one sentence].
Sections: hero with headline and CTA, 3 benefits with icons,
a short how-it-works, one testimonial placeholder, FAQ with
4 questions, final CTA.
Use copy from our message map [paste or reference project file].
Mark every placeholder clearly as [PLACEHOLDER].

A mockup is a fast way to agree structure and copy with stakeholders before design and development time is spent. Keep it labelled as a mockup, and don't publish placeholder testimonials or invented figures.

#05How do artifacts that use Claude work?

This is the most powerful option. Anthropic explains that you can build artifacts that call Claude directly, turning them into small apps: people using your artifact sign in with their Claude account, no API keys are needed, and "usage counts against each person's own plan limits rather than yours" (Anthropic). New artifacts ask for permission the first time they want to use Claude.

For marketing teams, that opens up tools such as:

• A brief reviewer where anyone pastes a brief and gets feedback against your checklist.
• A voice coach that rewrites a paragraph in your brand voice and explains what changed.
• A FAQ drafter that turns a product note into customer-facing questions and answers.

Write the instructions for the embedded Claude as carefully as you would a Skill. Include your rules and examples in the artifact, so every user gets consistent results.

#06How do connections and storage work?

On paid plans, artifacts can connect to the apps you've connected to Claude, so they can read from and write to tools like Asana, Google Calendar and Slack, as well as custom connectors. They can also store data between sessions. Storage is either personal, where each user sees only their own data, or shared, where everyone sees the same data. Anthropic notes a 20 MB limit per artifact and text-only storage.

Anthropic also warns that the person who builds the artifact decides which data is personal and which is shared, and recommends checking before entering anything sensitive. Treat a shared tracker like a shared spreadsheet: never put customer personal data or confidential figures in it unless your organisation has approved that use.

#07How does sharing work?

Artifacts start private. According to Anthropic's sharing guide, Pro, Max and Ultra users can share with anyone who has the link or invite people by email, while on Team and Enterprise plans artifacts stay inside the organisation by default and an owner decides whether users can share outside it (Anthropic). Everyone who opens a shared artifact needs a Claude account; the only exception is legacy artifacts published from a chat.

That last point matters for marketers. Artifacts are excellent for internal tools and prototypes, but they aren't a way to publish a calculator on your website for anonymous visitors. For that, export the design or code and hand it to your web team.

Anthropic also advises opening shared artifacts only from people you trust, and treating someone else's artifact the way you would a file from an unknown sender.

#08From MentionX data: tools that earn citationsOriginal data

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Interactive tools on your own website can earn links and citations when they answer a real question. MentionX's cross-engine aggregates show which page types get cited across the prompts we track:

Our view: prototype a calculator as an artifact, test it with colleagues and customers, then build the public version on your site with a clear explanation of the method, so both people and AI engines can understand and trust the result.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

#09Worked example: Ledgerline's savings calculator

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline's product marketer wants a calculator showing how much time finance teams save with automated approvals. She describes inputs, the formula and the assumptions to Claude, which builds it as an artifact in one session.

Testing finds that entering zero invoices shows a negative saving, so Claude adds input checks. Sales use the shared artifact on calls for a month, and their feedback shows the assumptions panel is the part prospects trust most.

The web team then builds a public version on Ledgerline's site, with the method explained in plain text below the calculator. Ledgerline is fictional and the details are illustrative.

#10How do you maintain artifacts the team relies on?

Give each shared tool an owner and a short description of what it does and when it was last checked. Rules change, such as your UTM naming conventions or pricing, and an outdated tool quietly produces wrong outputs. When you update a tool, tell Claude exactly what changed and ask it to keep everything else the same.

Keep the prompt you used to build each tool in your project, too. If an artifact ever needs rebuilding, the original brief makes it quick.

#11What should you try before the next lesson?

Pick one repetitive task and build a tool for it this week. A UTM builder or brief form is a good start. Share it with one colleague, collect their feedback and iterate once.

Next: Claude in Excel and Google Sheets. Or return to the Claude for Marketers track.

#12How do you use Docs and Slides templates for marketing work?

The Docs template suits living documents that several people edit, such as a campaign plan, a messaging framework or a launch checklist. Anthropic describes Docs as documents you write with Claude and your team in real time, and they export to Word, PDF, Markdown and Google Docs. Highlighting text and choosing "Edit with Claude" lets you change one paragraph without describing where it is, which makes reviewing much quicker.

The Slides template builds presentations from your notes, reports or the work already in your chat, and decks export to PowerPoint and PDF or go straight to Google Slides as editable files. For marketers, the most useful pattern is to finish the analysis in the chat first, as in the previous lesson, then ask for a short deck from it. Because the deck is built from work Claude has already seen, the numbers and charts match the analysis.

Two habits keep decks honest. First, ask Claude to add the data source and date range in small text on every chart slide. Second, read every slide before sharing. A deck looks finished long before it's checked, and a polished slide with a wrong number does more damage than a rough one.

#13When should you not use an artifact?

When the tool needs to be public, needs to handle personal data, or needs to integrate deeply with your systems. Those are jobs for your web or engineering team, using a proper build and security review. Artifacts are also a poor fit for anything that must stay exactly the same over time, such as a regulated calculation, unless someone owns and checks it regularly.

They're also not a replacement for your existing tools. If your team already has a good brief form in your project management tool, a new artifact just splits the process. Build artifacts where there's a gap, not where there's already something that works.

#14How do you get colleagues to use the tools?

Show, don't announce. A two-minute screen recording of someone using the tool in a real task does more than a message saying it exists. Put the link where the task already happens, such as in the brief template or the campaign checklist. And ask the first few users for one improvement each; small fixes in the first fortnight make the difference between a tool people adopt and one they forget.

#15Which artifact prompts are worth copying?

Good tool prompts describe the user, the inputs, the outputs and what should happen with bad input. Here are three that marketing teams build often.

UTM link builder:

Build an interactive UTM link builder for our marketing team.
Inputs: base URL, source and medium (dropdowns with our
approved values: [list]), campaign name, optional content.
Rules: lowercase everything, replace spaces with hyphens,
warn if the URL already has a query string.
Output: the full link with a copy button, plus a running
table of links created this session that I can copy as CSV.

Campaign ROI calculator:

Build a calculator for estimating campaign return.
Inputs: budget, expected CPC, conversion rate to lead, lead-to-
customer rate, average first-year customer value.
Show: clicks, leads, customers, revenue, return on spend.
Add sliders for CPC and conversion rate so I can see
sensitivity. Label every output as an estimate, and show the
formula under each number.

Content brief form:

Build a form that turns a writer's answers into a content
brief. Fields: [the fields from our brief template]. Required
fields can't be blank. On submit, show the brief formatted in
Markdown with a copy button.

After the first version, test it the way a colleague would: enter odd values, leave fields empty, paste a long URL. Tell Claude what broke. Two or three rounds usually produce something solid.

#16What goes wrong with artifacts?

#17Common questions

Are Claude artifacts free? Yes. Anthropic says creating artifacts and using the Docs, Slides and Design templates is available on every plan, including Free. Connections and storage need a paid plan.

Can people without Claude use my artifact? Generally no. Anthropic says everyone needs a Claude account to open a shared artifact; the exception is legacy artifacts published from a chat.

Who pays when a shared artifact uses Claude? Anthropic says usage counts against each person's own plan limits, not the creator's, and no API keys are needed.