🐕

bringing it together

The task now is to sit back and look at the PRECISE framework, the prompt context, the format control and constraints and success criteria to write your own hardcore prompt.

A tip here before we get started:

  • the length of a prompt takes up tokens
  • content you provide to AI takes up tokens
  • the returned output takes tokens.

And each model can provide a differing number of tokens. It’s worth knowing that before you build highly sophisticated prompts of this kind. You need to make sure you limit it to the extent it’ll work with the tools you have. The good news is, you can try and simplify or make more complex if you needed.

It’s also worth noting that using a commercial API in the form of Claude Code or something like that drastically increases your available token length on any singular transaction; so if you want to do powerful things that’s the best way to go.

Here is an example to test your skills:

Your company needs a comprehensive sales proposal for a $500K enterprise software deal

  1. Apply PRECISE framework

    2. Define role, requirements, environment, constraints, intent, success, examples.

  2. Build context pyramid

    3. Include strategic, operational, audience, and basic context layers

  3. Specify professional format

    4. Structure, length, style, elements, formatting, compliance

  4. Define comprehensive constraints

    5. Content, style, technical, brand, legal, audience constraints

  5. Set multi-dimensional success criteria

    6. Functional, quality, brand, audience, efficiency success measures

And here is a cheat code from the heavens. You can ask AI to pre-fill that if you want. Maybe try it for yourself first. Then get AI to do it. And see which did a better job. AI is awesome at writing prompts which is super interesting.

Now give it a go.

Here is an example - for this exercise, I created with Grok 3:

Prompt for Creating a Comprehensive Sales Proposal for a $500K Enterprise Software Deal

PRECISE Framework

Role

You are a senior proposal writer and strategic communicator for a leading enterprise software company, specializing in crafting persuasive, high-stakes sales proposals.

Requirements

  • Develop a sales proposal for a $500K enterprise software deal targeting a mid-to-large corporation.
  • Address the client’s needs for scalability, integration, security, and ROI.
  • Include technical details, value propositions, pricing, and implementation plans.
  • Use data-driven arguments and client-specific insights to strengthen the pitch.

Environment

  • The client operates in a competitive industry (e.g., finance, healthcare, or manufacturing) with complex IT infrastructure.
  • Decision-makers include C-suite executives (CEO, CFO, CIO) and IT managers.
  • The proposal will be evaluated in a formal RFP process with multiple stakeholders.

Constraints

  • Proposal must align with industry standards (e.g., ISO 27001 for security).
  • Adhere to client’s RFP guidelines, including submission deadlines and format.
  • Avoid overly technical jargon to ensure accessibility for non-technical stakeholders.
  • Stay within a 20-page limit, including appendices.

Intent

  • Convince the client that your software solution is the best fit for their strategic goals.
  • Build trust through transparency, credibility, and a client-centric approach.
  • Secure the deal by demonstrating superior value and differentiation from competitors.

Success

  • The proposal is shortlisted for final negotiations.
  • Client perceives the solution as innovative, cost-effective, and aligned with their needs.
  • Stakeholders approve the proposal for its clarity, professionalism, and persuasiveness.

Examples

  • A successful proposal for a $750K SaaS deal that won by emphasizing ROI and seamless integration.
  • A competitor’s proposal that failed due to vague pricing and lack of client-specific customization.

Context pyramid

Strategic context

  • The client aims to modernize their IT systems to stay competitive and reduce operational costs by 15% over 3 years.
  • Your company is positioned as a market leader in enterprise software with a focus on innovation and customer success.
  • The deal aligns with your company’s goal to expand its footprint in the client’s industry.

Operational context

  • The client’s current systems are outdated, causing inefficiencies and security vulnerabilities.
  • Your software offers cloud-based scalability, AI-driven analytics, and robust cybersecurity features.
  • Implementation requires a 6-month rollout with minimal disruption to client operations.

Audience context

  • Primary audience: C-suite executives prioritize ROI, strategic alignment, and long-term value.
  • Secondary audience: IT managers focus on technical feasibility, integration, and support.
  • All stakeholders value clear communication and evidence-based claims.

Basic context

  • The proposal is part of a competitive RFP process with a submission deadline in 2 weeks.
  • The deal size is $500K, with potential for upsell to $750K in future phases.
  • The client is based in North America, with global operations.

Professional Format

Structure

  1. Cover Page: Company logo, proposal title, client name, date.
  2. Executive Summary: 1-page overview of the solution and value proposition.
  3. Client Needs Analysis: 2-3 pages summarizing the client’s challenges and goals.
  4. Solution Overview: 4-5 pages detailing the software’s features, benefits, and differentiation.
  5. Implementation Plan: 2-3 pages outlining timeline, milestones, and support.
  6. Pricing and ROI: 2 pages with transparent pricing, cost-benefit analysis, and ROI projections.
  7. Case Studies: 1-2 pages of relevant success stories.
  8. Appendices: Technical specifications, compliance certifications, team bios.

Length

  • 15-20 pages, including appendices, to balance depth and conciseness.

Style

  • Professional, persuasive, and client-centric tone.
  • Clear, concise language with minimal jargon.
  • Use of visuals (charts, diagrams) to enhance readability.

Elements

  • Executive summary tailored to C-suite priorities.
  • Data-driven ROI calculations and competitive benchmarking.
  • Client-specific customization based on RFP requirements.
  • Testimonials or case studies from similar industries.

Formatting

  • PDF format, 12-point Arial or Times New Roman font, 1.5 line spacing.
  • Consistent branding with company logo, colors, and typography.
  • Numbered sections, table of contents, and page numbers.

Compliance

  • Adhere to RFP guidelines (e.g., submission format, word limits).
  • Include required certifications (e.g., SOC 2, GDPR compliance).
  • Ensure accessibility (e.g., alt text for visuals).

Comprehensive Constraints

Content constraints

  • Focus on client-specific challenges and solutions, avoiding generic content.
  • Include at least 3 case studies or testimonials to build credibility.
  • Provide clear pricing without hidden costs.

Style constraints

  • Maintain a confident yet respectful tone, avoiding aggressive sales tactics.
  • Use active voice and action-oriented language (e.g., “Our solution delivers…”).
  • Avoid humor or overly casual language to maintain professionalism.

Technical constraints

  • Ensure compatibility with client’s existing systems (e.g., ERP, CRM).
  • Provide technical specifications in an appendix for IT stakeholders.
  • Use secure file formats (e.g., password-protected PDF) for submission.

Brand constraints

  • Align with company branding guidelines (e.g., logo placement, color palette).
  • Highlight core brand values: innovation, reliability, customer success.
  • Use approved templates and messaging frameworks.

Legal constraints

  • Include standard disclaimers for forward-looking statements (e.g., ROI projections).
  • Ensure compliance with data privacy laws (e.g., GDPR, CCPA).
  • Avoid proprietary or confidential client data without permission.

Audience constraints

  • Tailor content to resonate with both technical and non-technical stakeholders.
  • Address C-suite priorities (e.g., cost savings, scalability) in the executive summary.
  • Anticipate objections (e.g., implementation risks) and provide counterarguments.

Multi-Dimensional Success Criteria

Functional success

  • The proposal meets all RFP requirements and submission deadlines.
  • It clearly articulates the software’s features, benefits, and implementation plan.
  • Pricing and ROI sections are transparent and compelling.

Quality success

  • The document is error-free, with consistent formatting and branding.
  • Visuals and data are accurate, relevant, and easy to understand.
  • The proposal is polished and professional, reflecting high standards.

Brand buccess

  • The proposal reinforces the company’s reputation as a trusted industry leader.
  • It aligns with brand values and messaging, enhancing client trust.
  • It differentiates the company from competitors through unique value propositions.

Audience success

  • C-suite executives find the executive summary compelling and strategic.
  • IT managers trust the technical details and implementation plan.
  • All stakeholders perceive the proposal as tailored to their needs.

Efficiency success

  • The proposal is completed within 10 business days to meet the RFP deadline.
  • It reuses existing templates and case studies to streamline development.
  • The document is concise, avoiding unnecessary content while remaining comprehensive.

Conclusion

And remember - you can use this content to create your own prompts with your own inputs. Don’t spend too much time thinking about it. Just do it!