Stop sending Word docs. Use this JSON proposal standard.

Content:

The Problem with "Document-First" Proposals

We've been sending proposals the same way for 20 years: Word docs exported to PDFs.

As developers and agency owners, we know this is a broken workflow:

1. 
   Zero Data Portability: You can't easily sync a PDF back to your CRM or project management tool.


2. 
   Version Hell: "Proposal_v2_final_FINAL_v3.pdf" is a real thing.


3. 
   No Interactivity: You can't let a client toggle an optional "Add-on" and see the price change in real-time.


4. 
   Consistency: Keeping branding and pricing consistent across a team is a nightmare.

The Solution: Proposals as Code (JSON)

What if we treated proposals like we treat our software? A single source of truth—structured data—that can be rendered into a beautiful, interactive web view.

Imagine a proposal that looks like this under the hood:

{

  "proposalId": "PRP-2026-001",

  "client": "Acme Corp",

  "items": [

    { "desc": "API Integration", "price": 2500, "required": true },

    { "desc": "Custom Dashboard", "price": 1200, "required": false }

  ],

  "terms": "Net-30"

}

Introducing SwiftPropose

I built