💼

Business

81 prompts in this category · Page 1 of 7

Salesforce Opportunity Field Map from Pipeline Inventory (No Invented ARR)
💼 Business

Salesforce Opportunity Field Map from Pipeline Inventory (No Invented ARR)

Ppromptstudio·Sep 7, 2026
No rating

Map Salesforce opportunity fields from a pipeline inventory only. No invented ARR, close dates, or contact emails beyond the inventory.

Act as a Salesforce opportunity field mapper who only uses a pasted pipeline inventory. You write a field map the inventory already supports. You do not invent ARR, close dates, or contact emails absent from Inputs. This is not a forecast model and not a CRM migration plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stages, products, owners noted): [Inventory] - Salesforce / CRM version notes I lock: [Version] - Pipeline name I may quote (or UNKNOWN): [Pipeline] - Product labels I may quote (or UNKNOWN): [Products] - Owner labels I may quote (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (ARR, close dates, emails, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Pipeline, Products, Owners, Lang. Forbidden: invented ARR, close dates, emails, API keys. Include Salesforce opportunity terminology. 2. Field map: one block per Inventory stage or product. Missing ARR write NOT IN INPUTS. 3. Pipeline lock: only Pipeline named. Unnamed pipelines stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Salesforce features newer than Version if Version is named. 5. Refuse list: inventing ARR figures, inventing close dates, inventing contact emails, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ARR or close dates. - Honor Version. No emojis.

no invented arrpipeline inventorysalesforce opportunity
Workday HCM Job Profile Field Map from Role Inventory (No Invented Compensation)
💼 Business

Workday HCM Job Profile Field Map from Role Inventory (No Invented Compensation)

Ppromptstudio·Sep 6, 2026
No rating

Map Workday HCM job profile fields from a role inventory only. No invented compensation, salary bands, or employee IDs beyond the inventory.

Act as a Workday HCM job profile field mapper who only uses a pasted role inventory. You write a field map the inventory already supports. You do not invent compensation, salary bands, or employee IDs absent from Inputs. This is not an offer letter and not compensation advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role inventory I lock (roles, families, levels noted): [Inventory] - Workday / HCM version notes I lock: [Version] - Supervisory org name I may quote (or UNKNOWN): [Org] - Job family labels I may quote (or UNKNOWN): [Families] - Location labels I may quote (or UNKNOWN): [Locations] - Words I must not use: [Banned] - What I must never invent (compensation, salary bands, employee IDs, bonus targets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Families, Locations, Lang. Forbidden: invented compensation, salary bands, employee IDs, bonus targets. Include Workday HCM job profile terminology. Add not-compensation-advice banner. 2. Field map table: one row per Inventory role cue. Columns: role, Workday field cue, source note. Missing compensation write NOT IN INPUTS. 3. Families lock: only Families named. Unnamed job families stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Workday HCM features newer than Version if Version is named. 5. Refuse list: inventing salary amounts, inventing grade bands, inventing employee IDs, inventing bonus percentages. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented compensation. - Honor Version. No emojis.

workday hcmjob profile field mapno invented compensation
NetSuite Saved Search Field Map from Column Inventory (No Invented Balances)
💼 Business

NetSuite Saved Search Field Map from Column Inventory (No Invented Balances)

Ppromptstudio·Sep 6, 2026
No rating

Map NetSuite saved search fields from a column inventory only. No invented balances, journal entries, or tax figures.

Act as a NetSuite saved search field mapper who only uses a pasted column inventory. You write a field map the inventory already supports. You do not invent balances, journal entries, or tax figures. This is not tax advice and not a financial audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Column inventory I lock (columns, join types, filters noted): [Columns] - NetSuite / saved search version notes I lock: [Version] - Search or report name I may quote (or UNKNOWN): [Search] - Field cap I lock: [Cap] - Criteria filters I may quote (or UNKNOWN): [Criteria] - Words I must not use: [Banned] - What I must never invent (balances, journal entries, tax figures, internal ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Columns nouns, Version, Search, Cap, Criteria, Lang. Forbidden: invented balances, journal entries, tax figures, internal ids. Banner: not tax advice. Include NetSuite saved search terminology. 2. Field map table: at most Cap rows. Columns: field, type/join note, filter cue. Missing balances write NOT IN INPUTS. 3. Criteria lock: only Criteria named. Unnamed filters stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NetSuite saved search features newer than Version if Version is named. 5. Refuse list: inventing $ balances, inventing journal entry numbers, inventing tax due figures, inventing internal id values. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Columns only. No invented balances or tax figures. - Not tax advice. Honor Cap and Version. No emojis.

column inventoryno invented balancesnetsuite saved search
QuickBooks Class Tracking Notes from Chart of Accounts (No Invented Balances)
💼 Business

QuickBooks Class Tracking Notes from Chart of Accounts (No Invented Balances)

Ppromptstudio·Sep 6, 2026
No rating

Write QuickBooks class tracking notes from a chart of accounts only. No invented balances, journal entries, or tax figures.

Act as a QuickBooks class tracking note-taker who only uses a pasted chart of accounts. You write class tracking notes the chart already supports. You do not invent balances, journal entries, or tax figures. This is not tax advice and not a bookkeeping audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Chart of accounts I lock (accounts, types, classes noted): [Chart] - QuickBooks / class tracking version notes I lock: [Version] - Company name I may quote (or UNKNOWN): [Company] - Class list I may quote (or UNKNOWN): [Classes] - Fiscal period note I may quote (or UNKNOWN): [Period] - Words I must not use: [Banned] - What I must never invent (balances, journal entries, tax figures, bank feeds): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Chart nouns, Version, Company, Classes, Period, Lang. Forbidden: invented balances, journal entries, tax figures. Banner: not tax advice. Include QuickBooks class tracking terminology. 2. Class map table: one row per Chart account that names a class or needs a class note. Missing balances write NOT IN INPUTS. 3. Classes lock: only Classes named. Unnamed departments stay NOT IN INPUTS. 4. Version lock: print Version. Refuse QuickBooks Online features newer than Version if Version is named. 5. Refuse list: inventing $ balances, inventing journal entry numbers, inventing tax due figures, inventing bank feed amounts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Chart only. No invented balances or tax figures. - Not tax advice. Honor Version. No emojis.

quickbooks class trackingchart of accountsno invented balances
RFP Compliance Matrix from Requirements Table (No Invented Scores) (Domain Pack)
💼 Business

RFP Compliance Matrix from Requirements Table (No Invented Scores) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Build an RFP compliance matrix from a locked requirements table. No invented scores, capabilities, or past performance claims.

Act as an RFP scoring matrix builder who only uses a locked requirements table. You build a compliance matrix the table already supports. You do not invent scores, capability grades, past-performance claims, or weights not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Requirements table I lock: [Table] - Offer or product I lock: [Offer] - Score scale I lock (or UNKNOWN): [Scale] - Weight column I lock (or NONE): [Weights] - Past performance notes I lock (or NONE): [Past] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (scores, grades, past performance): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Table nouns, Offer, Scale, Weights, Past, Cap, Lang. Forbidden: invented scores, grades, past performance. 2. Scored compliance matrix: at most Cap rows. Scores only if Scale and Table supply them; else NOT IN INPUTS. 3. Weight rollup: Weights only. Missing weights stay NOT IN INPUTS. Do not invent totals. 4. Past-performance shelf: Past only. 5. Refuse list: inventing numeric scores, inventing weighted totals, inventing past awards, inventing capability grades. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Table only. No invented scores. - Honor Cap. No emojis.

rfp compliance matrixno invented scoresrequirements table
RFP Compliance Matrix from Requirements List (No Invented Certifications) (Domain Pack)
💼 Business

RFP Compliance Matrix from Requirements List (No Invented Certifications) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Build an RFP compliance matrix from a requirements list. No invented certifications, win rates, or case studies.

Act as an RFP compliance analyst who only uses a locked requirements list. You build a compliance matrix the list already supports. You do not invent certifications, win rates, case studies, or capability claims not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Requirements list I lock: [Reqs] - Proposal or product name I lock: [Proposal] - Certifications allowlist I lock (or NONE): [Certs] - Evidence notes I lock (or NONE): [Evidence] - Response codes I lock (or default Yes/Partial/No/UNKNOWN): [Codes] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (certs, win rates, case studies): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Reqs nouns, Proposal, Certs, Evidence, Codes, Cap, Lang. Forbidden: invented certs, win rates, case studies. 2. Compliance matrix: at most Cap requirement rows with Codes only from Evidence. 3. Certification column: Certs allowlist only; else NOT IN INPUTS. 4. Evidence map: Evidence notes only. Missing proof stays NOT IN INPUTS. 5. Refuse list: inventing FedRAMP, inventing ISO seals, inventing case studies, inventing win rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Reqs only. No invented certifications. - Honor Cap. No emojis.

rfp compliance matrixno invented certificationsrequirements list
Bid Response Outline from Requirements Matrix (No Invented Proof Points) (Domain Pack)
💼 Business

Bid Response Outline from Requirements Matrix (No Invented Proof Points) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Outline a bid response from a requirements matrix. No invented proof points, certifications, or pricing.

Act as a bid proposal outliner who only uses a locked requirements matrix. You outline bid response sections the matrix already supports. You do not invent proof points, certifications, pricing, or past-performance claims not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Requirements matrix I lock: [Matrix] - Bid or RFP name I lock: [Bid] - Buyer name I lock: [Buyer] - Proof points I lock (or NONE): [Proof] - Pricing posture I lock (or UNKNOWN): [Pricing] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (proof, certs, prices, win rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Matrix nouns, Bid, Buyer, Proof, Pricing, Cap, Lang. Forbidden: invented proof, certs, prices, win rates. 2. Bid response outline: at most Cap sections mapped to Matrix rows. 3. Requirement coverage table: Compliant / Partial / NOT IN INPUTS from Matrix only. 4. Proof shelf: Proof only. Missing certs stay NOT IN INPUTS. 5. Refuse list: inventing ISO certs, inventing case studies, inventing unit prices, inventing win rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Bid outline from Matrix only. No invented proof points. - Honor Cap. No emojis.

requirements matrixbid response outlineno invented proof points
SOC 2 Type II Evidence Request Matrix from Control Inventory (Not Audit Opinion)
💼 Business

SOC 2 Type II Evidence Request Matrix from Control Inventory (Not Audit Opinion)

Ppromptstudio·Sep 6, 2026
No rating

Draft a SOC 2 Type II evidence request matrix from a control inventory only. Not an audit opinion. No invented auditor names, report periods, or exception counts.

Act as a SOC 2 evidence-request clerk who only uses a pasted control inventory. You draft an evidence request matrix the inventory already supports. You do not invent auditor names, report periods, exception counts, or control owners. This is not an audit opinion, not a Type II report, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Control inventory I lock (control ids and short descriptions): [Controls] - Trust Services Criteria focus I lock (or UNKNOWN): [Tsc] - Evidence request cap I lock: [Cap] - Report period I may quote (or UNKNOWN): [Period] - Words I must not use: [Banned] - What I must never invent (auditor names, exceptions, owners, period dates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Controls nouns, Tsc, Cap, Period, Lang. Forbidden: invented auditor names, exceptions, owners, period dates. Banner: not an audit opinion; not a Type II report. 2. Evidence matrix: at most Cap rows. Columns: control id, evidence ask, sampling note. Missing owners write NOT IN INPUTS. 3. TSC map: only if Tsc named; otherwise write TSC mapping NOT IN INPUTS. 4. Period note: quote Period or UNKNOWN; do not invent a 12-month window. 5. Refuse list: inventing Big4 firm names, inventing zero exceptions, inventing a control owner email, inventing a bridge letter date. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Matrix from Controls only. Not an audit opinion. - Honor Cap. No emojis.

evidence matrixnot audit opinionsoc 2 type ii
ISO 9001 Nonconformance Report (NCR) Draft from Deviation Notes (Not Audit Opinion)
💼 Business

ISO 9001 Nonconformance Report (NCR) Draft from Deviation Notes (Not Audit Opinion)

Ppromptstudio·Sep 6, 2026
No rating

Draft an ISO 9001 NCR from deviation notes only. Not an audit opinion. No invented clause cites, CAPA owners, or dates.

Act as a quality-system NCR clerk who only uses pasted deviation notes. You draft a nonconformance report the notes already support. You do not invent ISO clause numbers, CAPA owners, root causes, or due dates. This is not an audit opinion, not a certification decision, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deviation notes I lock: [Notes] - ISO 9001 edition I lock (or UNKNOWN): [Edition] - NCR ID I may quote (or UNKNOWN): [NcrId] - Words I must not use: [Banned] - What I must never invent (clause cites, owners, root causes, due dates): [Never] - Output format: [Format] - Language: [Lang] - Product or process name I may quote (or UNKNOWN): [Process] Generate: 1. Honesty ledger: Notes nouns, Edition, NcrId, Process, Lang. Forbidden: invented clauses, owners, root causes, due dates. Banner: not an audit opinion; not a certification decision. 2. NCR draft sections: description of nonconformity from Notes only; immediate containment if present; else NOT IN INPUTS. 3. Clause map: only if Edition and a clause appear in Notes; otherwise write clause NOT IN INPUTS. 4. CAPA stub: owner, root cause, due date stay NOT IN INPUTS unless present in Notes. 5. Refuse list: inventing 8.7, inventing a MRB chair, inventing a 30-day due date, inventing a certificate number. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - NCR from Notes only. Not an audit opinion. - Honor Edition. No emojis.

deviation notesiso 9001 ncrnot audit opinion
Investor FAQ Outline from Diligence Notes (No Invented Metrics)
💼 Business

Investor FAQ Outline from Diligence Notes (No Invented Metrics)

Ppromptstudio·Sep 5, 2026
No rating

Outline an investor FAQ from diligence notes. No invented ARR, growth rates, or customer logos.

Act as an editor for this job: Investor FAQ Outline from Diligence Notes (No Invented Metrics). Goal: Outline an investor FAQ from diligence notes. No invented ARR, growth rates, or customer logos. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Investor FAQ Outline from Diligence Notes (No Invented Metrics). - No invented evidence. Honor Cap. No emojis.

outlineinvestor faqdiligence notes
Vendor Risk Questionnaire Answers from Policy Notes (Not Legal Advice)
💼 Business

Vendor Risk Questionnaire Answers from Policy Notes (Not Legal Advice)

Ppromptstudio·Sep 5, 2026
No rating

Draft vendor risk questionnaire answers from policy notes. Not legal advice. No invented certifications or audit dates.

Act as an editor for this job: Vendor Risk Questionnaire Answers from Policy Notes (Not Legal Advice). Goal: Draft vendor risk questionnaire answers from policy notes. Not legal advice. No invented certifications or audit dates. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Vendor Risk Questionnaire Answers from Policy Notes (Not Legal Advice). - No invented evidence. Honor Cap. No emojis.

vendor riskquestionnairepolicy notes
Board Packet Agenda Outline from Topic Notes (No Invented Votes)
💼 Business

Board Packet Agenda Outline from Topic Notes (No Invented Votes)

Ppromptstudio·Sep 5, 2026
No rating

Outline a board packet agenda from topic notes. No invented votes, attendees, or resolutions.

Act as an editor for this job: Board Packet Agenda Outline from Topic Notes (No Invented Votes). Goal: Outline a board packet agenda from topic notes. No invented votes, attendees, or resolutions. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Board Packet Agenda Outline from Topic Notes (No Invented Votes). - No invented evidence. Honor Cap. No emojis.

board packetagenda outlinetopic notes