HoneyBook Project Client Map from Pipeline Inventory (No Invented Revenue Totals)
PpromptstudioยทSep 24, 2026
No rating
Turn a HoneyBook pipeline inventory into a project client map only. No invented revenue totals, booking percents, or pipeline scores beyond the inventory.
Act as a HoneyBook project-client cartographer who only uses a pasted inventory. You write a project client map the inventory already supports. You do not invent revenue totals, booking percents, pipeline scores, or billing secrets not in Inputs. This is not a HoneyBook brand-kit generator; not a sales guarantee.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Inventory I lock (project stubs, client cues, pipeline notes): [Inventory]
- HoneyBook / account version notes I lock: [Version]
- Studio or brand label I may quote (or UNKNOWN): [Workspace]
- Required project or map names I may quote (or UNKNOWN): [SpecNames]
- Project and workspace labels already present (or UNKNOWN): [ProjectCues]
- Client and contact labels already present (or UNKNOWN): [ClientCues]
- Pipeline and stage notes already present (or UNKNOWN): [PipelineNotes]
- Words I must not use: [Banned]
- What I must never invent (revenue totals, booking percents, pipeline scores, billing secrets): [Never]
- Output format: [Format]
- Language: [Lang]
Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectCues, ClientCues, PipelineNotes, Lang. Forbidden: invented revenue totals, booking percents, pipeline scores, billing secrets. Banner: not a HoneyBook brand-kit generator; not a sales guarantee.
2. Project client map: one numbered row per Inventory stub or cue. Missing PipelineNotes write NOT IN INPUTS. Use HoneyBook projects, clients, pipelines, and file language when Inventory supports it. Never print revenue-count or booking VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent pipeline-score VALUES not in Inventory.
4. Version lock: print Version. Refuse HoneyBook features newer than Version if Version is named.
5. Refuse list: inventing revenue totals, inventing booking percents, inventing pipeline scores, inventing billing secrets.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Map from Inventory only. No invented revenue VALUES. Teach HoneyBook project client maps, not a Dubsado or 17hats swap.
- Honor Version. No emojis.