Confluxion Point — Proposal Template
Lives in: 03 — Pricing & Engagement
How to use: Copy this file (Make a copy in Drive), rename to
proposal-{workflow-slug}, fill in every{{ placeholder }}. When done, render via Picasso (or paste into Canva matching the ET layout).The structure mirrors the ET PSA Workflow proposal that closed. Don't change the structure unless we learn something. Iterate on the content.
Page 1 — The Pitch
Header (consistent every proposal)
- Top-left: Confluxion Point logo
- Top-right: {{ WORKFLOW NAME IN CAPS }} — PROPOSAL
Title block
• PROJECT PROPOSAL
{{ Workflow Name }} Workflow.
Summary box (cream/tan callout)
A working, deployed system that handles the full {{ workflow }} loop — from {{ trigger event }} through {{ output 1 }} through {{ final reconciliation step }} back to your {{ system of record }}.
It runs on your own systems, in your accounts — you own everything that's built. Future workflows plug into the same foundation, so each new one starts faster and costs less than the first.
"The Problem — In Your Words" box
Today this workflow consumes ~{{ X hours/week }} of a team member who bills at ${{ loaded rate }}/hour — roughly ${{ Xrate52 }}/year of labor value tied up in {{ list of manual tasks: inbox watching, PDF dragging, Excel keying, etc. }}. {{ One pain point sentence — e.g. "One typo throws off the running total. One missed threshold delays a pay app invoice." }} This is automation work, not AI reasoning — just reliable execution of a workflow your team already knows.
"What Gets Built" — 5 module cards
For each module:
- Icon (mail, dollar, alert, document, sync, etc.)
- Module title
- 2–3 sentences describing what it does in plain language, naming specific tools (Procore, Sage, Bluebeam, SharePoint, Outlook, Excel, Teams)
Suggested 5 modules to scope from:
- Email Handling & File Routing — watches inbox, parses incoming, files in correct location
- Data Extraction & Tracker Updates — pulls structured data from PDFs/emails, writes to existing tracker
- Automated Threshold Alerts — fires when conditions met, notifies via Teams/email
- Monthly Output Generation — drafts the recurring document/invoice/report from template
- System-of-Record Reconciliation — closes the loop by checking Sage/Procore for status
Page 2 — Timeline + Pricing
"{{ Workflow }} Timeline — 45 Days to Go-Live" (3 cards)
| Card | Header | Title | Body |
|---|---|---|---|
| 1 | WEEKS 1–2 | Discovery + Build | "Environment provisioned. Full historical {{ data }} archive ingested and backtested — not a sample, every record. {{ Core extraction + routing }} live in dev." |
| 2 | WEEKS 3–4 | Integration | "{{ Tracker updates }} + {{ alerts }} + {{ output generation }} against real {{ data }}." |
| 3 | WEEKS 5–6 | Go-Live + Warranty | "{{ Reconciliation }} wired in. Full end-to-end testing. Production deploy. 30 days of warranty fixes start the day you go live." |
Pricing & Terms (dark navy block)
Foundation — $22,000 one-time
Azure environment (tenant + Key Vault + Storage), Microsoft Graph (email · SharePoint · Teams access), secure connections to {{ tools }}, security review, monitoring + alerts, CI/CD, audit logging. Proof it's working: Teams runs log + a sortable SharePoint list in your tenant where every event writes a row. Never charged on future workflows.
{{ Workflow Name }} — $25,000 build
{{ Component list — be specific }}. {{ Complexity tier note }}.
Payment — 50 / 50
$23,500 at kickoff (signed agreement + environment set up). $23,500 at go-live (acceptance criteria met, signed off). No hourly billing.
Warranty — 30 days
Production bugs fixed at no charge. New scope is a separate quote. After 30 days: $225/hr on-demand.
Proposal Total
Foundation $22,000 + Build $25,000 = $47,000
ROI — The Math (3 columns)
| Column | Header | Number |
|---|---|---|
| 1 | LABOR VALUE TIED UP TODAY | {{ hrs/wk }} × ${{ rate }}/hr × 52 wks = ${{ annual }}/yr |
| 2 | YEAR-1 PAYBACK | {{ annual }} ÷ 47,000 = {{ multiple }}× in {{ months }} months |
| 3 | EVERY YEAR AFTER | ${{ annual }}/yr pure savings — no subscription |
Page 3 — Acceptance Criteria + Sign-off
Pull from the SOW. Every line must be specific and testable.
Source: derived from ET PSA proposal that closed at $47K. Last updated: 2026-05-25