💼 Business

HoneyBook Project Client Map from Pipeline Inventory (No Invented Revenue Totals)

Turn a HoneyBook pipeline inventory into a project client map only. No invented revenue totals, booking percents, or pipeline scores beyond the inventory.

0.0
0Reviews
P
September 24, 2026

Prompt

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.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

HoneyBook Project Client Map from Pipeline Inventory (No Invented Revenue Totals) - Result

Examples

Example Input

Inventory: project Harbor Quay Dock Wedding as pasted client cue Quay Couple as pasted pipeline notes inquiry as pasted; project River Ops River Brand as pasted client cue Quay Studio as pasted. Revenue invent NONE. Booking invent NONE.
Version: HoneyBook as pasted (do not invent unreleased AI pipeline pack)
Workspace: Harbor Quay studio desk as pasted
SpecNames: Dock Wedding project map as pasted; River Brand project map as pasted. Pipeline scores UNKNOWN.
ProjectCues: Dock Wedding as pasted; River Brand as pasted. Retainer UNKNOWN.
ClientCues: Quay Couple as pasted; Quay Studio as pasted. VIP UNKNOWN.
PipelineNotes: inquiry as pasted. Revenue VALUES NOT IN INPUTS.
Banned: guaranteed bookings, revenue invent, booking invent, pipeline invent
Never: invent revenue totals, invent booking percents, invent pipeline scores, invent billing secrets
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: project Harbor Quay Dock Wedding as pasted client cue Quay Couple as pasted pipeline notes inquiry as pasted; project River Ops River Brand as pasted client cue Quay Studio as pasted. Revenue invent NONE. Booking invent NONE. Version HoneyBook as pasted. Workspace Harbor Quay studio desk. SpecNames Dock Wedding project map as pasted; River Brand project map as pasted. Pipeline scores UNKNOWN. ProjectCues Dock Wedding as pasted; River Brand as pasted. Retainer UNKNOWN. ClientCues Quay Couple as pasted; Quay Studio as pasted. VIP UNKNOWN. PipelineNotes inquiry as pasted. Revenue VALUES NOT IN INPUTS. Lang English. Banner: not a HoneyBook brand-kit generator; not a sales guarantee. Forbidden: invented revenue totals, booking percents, pipeline scores, billing secrets, guaranteed bookings, revenue invent, booking invent, pipeline invent.

2. Project client map.
1. Harbor Quay Dock Wedding | ProjectCues Dock Wedding as pasted | ClientCues Quay Couple as pasted | PipelineNotes inquiry as pasted | revenue VALUES NONE | booking NONE | HoneyBook project client map only.
2. River Ops River Brand | ProjectCues River Brand as pasted | ClientCues Quay Studio as pasted | PipelineNotes beyond inquiry NOT IN INPUTS | revenue VALUES NONE | booking NONE.
Pipeline scores UNKNOWN so write pipeline-score VALUES NOT IN INPUTS. Retainer not invented beyond ProjectCues.

3. Spec name set. Dock Wedding project map as pasted; River Brand project map as pasted as SpecNames. Unnamed rows NOT IN INPUTS. Never invent pipeline-score VALUES.

4. Version lock. HoneyBook as pasted as pasted. Refuse unreleased AI pipeline pack.

5. Refuse list. inventing revenue totals; inventing booking percents; inventing pipeline scores; inventing billing secrets.

6. Compliance. Quoted Banned: guaranteed bookings, revenue invent, booking invent, pipeline invent. Cut. Quoted Never: invent revenue totals, invent booking percents, invent pipeline scores, invent billing secrets. Cut. Format ledger + table + specs + version + refuse + compliance.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...