One fictional launch, one connected record
Consider the fictional Aster & Rue Solstice rainwear launch. Its operator already knows Journalist J-014 at the fictional Northline Journal and Creator C-008. J-014 has changed desks since the previous campaign; C-008 has sizing notes and a clear no-go for paid deliverables disguised as gifts. Those facts belong to the relationships, not to a disposable campaign tab.
The operator can select those contacts for the Solstice campaign, prepare an Outlook-ready list, record a Mistral jacket send, add a published article or social post as coverage, attach supporting evidence, and freeze a campaign report. The same contact and product references travel through the workflow, so a report row can be traced back to the campaign decision and the evidence entered by the operator.
| Working question | Where the answer lives |
|---|---|
| Who is this person and what changed? | Contact, outlet, role, notes, markets, languages, and history |
| Why were they included? | Campaign audience and selection status |
| What was sent? | Product or pair, send status, dates, and notes |
| What appeared? | Coverage record, URL or stored evidence, quality, and measurement context |
| What did we report? | A dated report snapshot scoped to the campaign |
Built around your list, not a rented directory
cutePR separates people from media outlets. A journalist can move while the relationship history remains attached to the person; an outlet can have several contacts with different roles, topics, and markets. Journalists and creators can live in the same operating memory without pretending their work or consent expectations are identical.
An existing Excel or CSV file enters through a review step. The operator can inspect normalized rows, warnings, skipped rows, and duplicate hints before acceptance. Exact email matches and probable same-name, same-outlet matches are treated differently. Migration assistance in the founding beta begins with an agreed source, record volume, and mapping; unsupported objects or unresolved duplicates stay visible rather than being silently forced into the CRM.
- Keep source and relationship notes beside the contact they describe.
- Use relational markets, languages, topics, campaigns, products, and outlets instead of comma-separated database shortcuts.
- Prepare copy and lists for Outlook or another existing mail tool; sending remains manual.
- Preserve coverage links, screenshots, PDFs, clippings, or manual proof notes for later reporting.
Where the current beta fits
The strongest fit is a solo in-house PR operator, freelance publicist, or boutique practitioner managing an existing set of journalist and creator relationships. The workspace is private per user. It gives one person a calmer operating record across contact care, product seeding, coverage cleanup, and reporting.
The current beta has no shared seats, client partitions, licensed journalist database, native email sending, automatic monitoring, ecommerce fulfillment, carrier feed, creator portal, automatic social capture, or live autonomous AI execution. Agencies that require simultaneous client workspaces and teams that need monitoring or distribution should keep those functions in tools designed for them.
A paid, accompanied founding-customer beta
Founding customers join a working paid beta at a preferential price. The amount and billing cadence are confirmed privately before enrollment; no public price has been decided. The standard price that follows the beta will be announced in advance so each customer can decide whether to continue.
The founder helps move an agreed part of the customer's current PR records into cutePR, with a preview and reconciled counts before acceptance. Customers can share concrete feedback and influence priorities, but participation does not promise that every request will ship or create a guaranteed deadline. The goal is to get one concrete PR workflow running with its limits understood.