Skip to main content

What are profiles?

A profile keeps what your work needs to know about one client or one product, so you don't paste the same voice rules or product facts into every task. In the words of the Profiles page: "What your work is for, kept once. Tasks that name a profile follow it on every run, and their checks read it."

This page explains the two kinds of profile, what each one holds and what a profile changes in a task.

Where to find profiles​

Click Profiles in the left rail, between Tasks and Agents. The page shows all your profiles in one list, most recently updated first:

  • Filter the list with All, Client profiles or Product profiles.
  • Each card names its kind and shows its version, how many tasks use it (for example "Used by 2 tasks", or "Not used by a task yet") and when it was last updated. Click a card to open the profile.
  • Start a task with this profile on each card opens the task templates with that profile already selected. See Use a profile in a task.
  • AI drafts at the top lists profiles that AI is drafting for you, until you save or remove them.
  • New profile at the top right creates a profile. See Create a profile.
  • The compass button, Show profiles guide, shows the short introduction again.

Two kinds of profile​

Client profileProduct profile
What it keeps"A client's voice, words, facts and off-limits topics""A product's facts, claims and positioning"
Good forWriting in a client's voice, or in your ownLaunch copy, release notes and directory listings for your product
Templates that need oneThis week's posts for a client, Second version from client notesLaunch announcement for your product, Release notes from what shipped, Directory listing for your product

What a client profile holds​

A client profile works for your own voice too. The welcome page describes it as being "For your own or a client's writing voice, wording and requirements."

  • About the client: Name, Who they are, Who reads them, Channels and Language. "Every run gets this."
  • Voice and notes: how they write, such as voice rules and format, in free text.
  • Words: Words and phrases they use and Words and phrases to avoid, one per line. "Runs follow them, and checks read them."
  • Off-limits topics: one per line. "Runs keep away from them."
  • Facts and stories you can use: each Fact or story with Where it comes from. Runs may use only the experiences, numbers and stories listed here or in their own material.
  • Rules from client notes: rules you added from a run's suggestions, or by hand. Each one shows the run it came from.
  • Approved samples: up to 5 posts your client approved, as a voice reference. "Their facts count only when they are listed above."

What a product profile holds​

  • Product: Product name, Website, Stage (Idea, Prototype, Beta, Live or Relaunch) and Type (for example Software, Service, or Newsletter or podcast).
  • Pitch: Tagline, Short description, Long description and Categories. "Directories and launch posts start here."
  • Who it's for: each audience and what they get from it.
  • Features: what the product does. "Tasks mention only what's listed here or in their material."
  • Pricing: plans and prices. Leave it empty if you don't want tasks to mention prices.
  • Claims you can back up: "Statements you can prove, with links to the proof."
  • Private to you: Internal notes, words and phrases to use or avoid, and Claims not to make. This section is never part of the product's public facts. Tasks use it as context only.

What a profile changes in a task​

When a task uses a profile:

  • Every run follows it. The run gets the profile's current version as context. A product task "writes only what this profile says about the product."
  • The checks read it. The run's checks read the same version of the profile, and its facts count as allowed sources. A check such as "Follows the client's profile" is judged against it.
  • The run records which version it used, for example "Written with Brightside Bakery's profile · version 2".
  • One change reaches every task. "Change a client's preference once here and every task that uses the profile follows it", from each task's next run.

The details are in Use a profile in a task.

Versions​

Every save creates a new version, for example "Saved as version 3. Tasks that use it follow it from their next run." The History card on a profile's page lists each version and how it came about (Created, Edited, Saved from a run, Rules added from a run or Restored). Click View to see an earlier version, and Restore to bring it back. Restoring saves it as a new version, so history is never rewritten.

Runs that already finished keep the version they used, so checking such a run again judges it against the same profile text.

Limits to know​

  • A profile is context for your tasks. Checks give evidence, not proof: a run that passes followed the profile as far as the checks could tell, which doesn't mean every fact in it is right.
  • If a profile is too long to be read in full, AI checks mark the affected items as needs review rather than passing them.
  • Chats and agents don't use profiles. A task you save from a chat starts without one; add it in the task's settings.
  • Rules suggested by runs go to client profiles only.
  • Tasks that use a profile prepare drafts. You send or publish them yourself.

Next steps​