How to Use Mutiny to Build 1:1 ABM Pages for Target Accounts

The short answer: on Mutiny's free plan each seat gets 5 credits a day and 30 a month, and a simple page costs about 1.5 credits, so a 20-account tier fits inside one seat's month before you pay anything (pricing, credits guide, checked on 5 November 2026); the job is to check the brand Mutiny imported, fill the Library, save a template, hand the agent your account list as a CSV or a CRM query, review the pages inside one project, publish them on your own subdomain, let the reps send them, and read which accounts came back.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

A 1:1 page is the account's name on the door. Mutiny's blueprint lists the parts: a header with your logo beside theirs, a logo bar of peers from their industry, a feature spotlight mapped to their use case, two or three resources picked for their stage, a next-step block and one call to action (1:1 ABM blueprint). What Mutiny is now, and what it stopped being, is in the Mutiny glossary entry.

Before you start:

1. The credit sum. For example, 25 accounts x 1.5 credits = 37.5 credits, more than one Free seat's 30 a month, so split the list over two seats or take Business at $50 for a 50-credit pool (credits guide, pricing).
2. The list you already have. Export the tier with owner, industry and the initiative you know about; the agent uses every column it gets, and an owner column puts that rep in the page's meeting banner (1:1 at scale guide).
3. The number. Identified visitors from each target account in the 14 days after the rep sends the link, against the same 14 days for accounts that got a plain email.

1. Check what Mutiny read from your site

Mutiny imports a brand from your website at signup: colours, fonts, typography, three button styles and visual guidelines the design agent follows (brand guide). Open Settings, then Brand, and correct what it guessed; a brand change propagates to every asset that uses it.

2. Fill the Library

The Library holds what the agent may pull into a page: case studies, product pages, PDFs, decks, images and video up to 2 GB, scraped from your site at signup and added by URL or upload afterwards (library guide). Only Owners, Admins and Content Managers can add or delete there, which is the governance point: reps build pages, marketing decides what pages may contain.

3. Connect the CRM, reading only

HubSpot connects through a Pipedream modal without a Pipedream account, and you choose per tool when the agent may use it; the read tools fetch companies, contacts, deals and owners, the write tools create and update records (HubSpot guide). Salesforce connects by OAuth and the agent runs SOQL queries from account to contacts to opportunities (Salesforce guide); the pricing page lists it under Enterprise (pricing). For this job leave every write tool off.

4. Save a template from the blueprint

Templates sit in columns by deal stage, and where a stage has none Mutiny suggests blueprints; build the 1:1 ABM page once with the agent, open the three-dot menu and choose Save as template (templates guide). The guide's line is worth keeping: templates handle the design, Skills handle the instructions the agent follows when a template is used. Deleted templates cannot be recovered, so archive instead.

5. Create one page per account

From the Home tab start a thread, attach the CSV with the plus button and write the prompt the guide gives, "Create a personalized asset for each account in the attached list", or ask the agent to search the connected CRM for accounts matching your criteria (1:1 at scale guide). Have it create a project first; the guide calls that highly recommended, because a project keeps every page and thread for one goal together. The agent asks clarifying questions before it builds, and those cost no credits (credits guide).

6. Review in the project, change in bulk

Inside a project the agent holds every asset in context, so one message changes all of them, "change the call to action to Book a meeting", and a second limits it to named pages (projects guide). The logo bar is where it goes wrong: one peer logo the account would laugh at undoes the rest.

7. Publish on your own subdomain

Every asset lives by default on a Mutiny-branded domain. A custom subdomain needs a name used for nothing else, two CNAME records from the Assets tab in Settings, and between a few minutes and 48 hours for DNS to settle before you press Activate (subdomain guide); the pricing page lists it under Business (pricing). Publish each page from Share Externally, set its slug and use Copy Link for the reps; Archive from the card menu takes it down (publishing guide).

So on Free the first account to open a page reads Mutiny's name in the address bar before it reads yours, and the subdomain that fixes that is the Business feature: that is the upgrade the free tier is built to produce.

8. Decide consent before the first EU visitor

Mutiny's analytics identify visitors, which is why its guide prefers opt-out tracking with a call to window.mutiny.client.optOut when someone declines; for opt-in, tick Disable Default Cookie Opt-in under Assets and call optIn from your consent tool, and the guide warns that the box without the call leaves tracking severely impeded (cookie consent guide). Replays and time on page still record for opted-out visitors, with form inputs redacted. Article 5(3) of the ePrivacy Directive is what your counsel reads first for Dutch and other EU accounts.

9. Hand the next batch to Claude, and keep publish in your hands

Mutiny runs an MCP server at https://mcp.mutinyhq.com/mcp. In Claude Code the command is claude mcp add --transport http mutiny https://mcp.mutinyhq.com/mcp; on claude.ai it is a custom connector under Settings, Customize, Connectors, with an OAuth window to approve (Claude guide). The server exposes 12 tools, among them create an asset, send refinement messages to its agent, publish, list approved templates and manage Library content (MCP overview). Blueprints are not reachable over MCP, so the template from step 4 is what you name in the prompt (creating assets guide).

The agent drafts, a person publishes. Ask Claude for "a 1:1 page for Account X from the ABM template, using the deal notes above", read the draft in the chat, refine by message, and only then say publish, because that call pushes the page to production and returns the live URL. Only tool requests and their results cross the connection; Mutiny says it does not receive or log your prompts, and the token can be revoked under Account settings, Authorized Applications (data handling guide).

10. Read who came back

Asset analytics show visits over time with a source breakdown, total clicks and engaged time, and a visits table in three views, Identified, Engaged and All, filterable by the account's domain and exportable (analytics guide). Add your Google Tag Manager snippet to assets and UTM parameters to the links the reps send, and the pages appear in GA4 under Pages and screens by hostname (GA4 guide).

What the guides warn about

• Deleted templates are gone for good; archive them (templates guide).
• Deleting a Library resource does not remove it from pages already using it (library guide).
• Opt-in mode without the optIn call leaves the analytics nearly empty (cookie consent guide).

FAQ

Does the account have to be in my CRM?

No. A CSV with the account name and whatever you know is enough; the CRM only adds fields the agent can read, such as deal stage, amount and owner (1:1 at scale guide).

What does one page cost in credits?

About 1.5 credits for a simple page, about 3 for a larger interactive asset and about 8 per account for a data-heavy automation that builds several, all in Max mode; Balanced mode costs around half (credits guide).

Can reps build these pages themselves?

Yes, that is the pitch, and the controls stay with marketing: only Owners, Admins and Content Managers change the Library (library guide).