[Zoho CRM] Embed live, versioned proposals within client records

I've been building a CRM + itinerary builder specifically for travel agencies for about a year, and along the way I've talked to dozens of agency owners about why they'd given up on HubSpot, Pipedrive, Zoho, etc. and fallen back to spreadsheets + Word docs. Sharing a few patterns I keep seeing, in case it's useful for anyone here — travel agencies choosing a CRM, other service businesses with similar workflows (wedding planning, custom manufacturing, architecture, legal), or CRM power users who like seeing where generic tools fall short. Not trying to sell anything, just sharing what I've learned. **1. The trip proposal has to live** ***inside*** **the CRM, not as an attached PDF.** For a travel agency, the core deliverable is the trip proposal itself. Generic CRMs let you attach a PDF quote to a deal, but the actual workflow is: draft in Word → export PDF → email client → client asks for changes → update Word → re-export → email v2 → repeat. By version 3, nobody on the team knows which PDF is current, the client has 4 emails in their inbox, and the branding/layout drifts each version. The fix isn't "better file management." It's embedding the proposal as a live, versioned object inside the client record — a single shareable link that auto-updates, keeps branding consistent, and centralizes every version for the whole team. This pattern likely applies to any service where the proposal evolves through back-and-forth (architects, wedding planners, custom fabrication, legal drafting). **2. Payment state belongs on the deal record, not in a separate invoicing tool.** Travel agencies juggle deposit → balance → supplier payments out → occasional refunds, all tied to specific trip dates. Every agency I've talked to was reconciling payment state across their CRM, their invoicing tool, and a shared spreadsheet. The moment "paid / unpaid / overdue" lives directly on the client record with visibility on what's due this week, team coordination jumps. Generic CRMs treat payments as an integration problem; for service businesses with deposits and long fulfillment cycles, it's a core CRM problem. **3. The default pipeline stages don't match how travel agencies actually work.** "Prospect → Qualified → Proposal → Negotiation → Closed Won" is fine for SaaS. For an agency, the real stages are: inquiry → v1 quote → v2 quote → deposit paid → balance paid → pre-departure → in-trip → return → review. "Closed Won" isn't the end of the relationship — it's the middle. Trying to force this into a standard CRM pipeline means people stop trusting it and go back to their own spreadsheet. **4. For small agency teams, the #1 CRM value isn't individual productivity — it's team visibility.** The feedback I hear most from users isn't "this saves me time on my own tasks." It's "my manager/owner finally knows where every booking stands without having to ask me." For a 3–10 person agency, the real win is killing the daily "where are we on the Martin booking?" conversation. Owners and managers can see open tasks, upcoming client departures, pending payments, etc. at a glance. Worth optimizing your CRM setup around team visibility specifically, whatever tool you end up using. **5. Lead capture friction is still a weird blind spot in most CRMs.** Half the agencies I talked to were still copy-pasting leads from their website contact form into their CRM manually. A simple webhook from form → CRM solves it in an afternoon, but most generic CRMs make this unnecessarily complex (zapier subscription, premium plan, custom fields mapping hell). For small teams, auto-capturing leads directly should be table stakes in 2026. **Question for the sub:** for travel agency owners or anyone running a service business with long, iterative fulfillment cycles — how are you handling the "live proposal / deliverable" problem in your CRM? Custom objects in HubSpot? External tool + webhook sync? Notion/Airtable glued on top? Or do you just accept the friction and train the team around it? Genuinely curious, because this is the #1 thing I hear pushing agencies off generic CRMs, and I want to understand what workarounds exist.