Client Document Flow — Real Business Process

The core principle: Clients sign 1–2 documents max. Everything else lives on your website or gets sent as reference material they don't need to sign. The goal is to remove friction while still being fully protected.

How the Document Stack Actually Works

CLIENT EXPERIENCE          WHAT THEY SIGN         WHAT LIVES ON YOUR WEBSITE
─────────────────          ──────────────         ──────────────────────────
"I want to work with you"  │                      Terms of Service
        ↓                  │                      Privacy Policy
"Looks great, let's go"    │                      Cookie Policy
        ↓                  │                      Refund & Cancellation Policy
[signs 1 contract] ────────┘                      IP Policy
        ↓                                         AI Use Policy
[pays deposit]                                    Hosting SLA Policy
        ↓                                         Acceptable Use Policy
[project starts]

The standalone contract (e.g., Web Design Contract) contains a single clause like:

"By signing this Agreement, Client acknowledges and agrees to Webility's Terms of Service, Privacy Policy, Refund Policy, and Intellectual Property Policy, available at webility.local/legal."

That one sentence replaces six separate policy documents the client would otherwise need to read and sign. They're still bound by them — they just access them via your website like any professional service company.

Scenario A — SMB Client

Profile: Local business, e-commerce shop, professional services firm, startup. Typical engagement value: $2,000–$25,000. Expectation: Quick to decide, minimal paperwork, just get it done.

flowchart TD
    A([🔎 First Contact\nInbound inquiry or referral]) --> B

    B[Discovery Call\n30–45 min\nVerbal intake — no forms yet]
    B -->|Not a fit| C([👋 Polite decline email\nNo documents])
    B -->|Good fit| D

    D[Send Proposal\n📄 1 document · 2–4 pages\nScope · Timeline · Price · Next steps]
    D -->|No response after\n1 follow-up| E([Close — no further action])
    D -->|Questions / negotiation| D2[Revised Proposal\n📄 Same doc, updated]
    D2 --> F
    D -->|Yes, let's go| F

    F[Send Standalone Contract\n📄 1 document\nWeb Design · Branding · AI · Maintenance]
    F --> F1["Contract references website policies\n⚠️ Client does NOT receive or sign:\n· Privacy Policy · ToS · AUP\n· Refund Policy · IP Policy\n→ All linked in contract as webility.local/legal"]
    F --> G

    G[Send Deposit Invoice\n📄 1 document\n50% of project value]
    G -->|Invoice paid| H

    H([✅ PROJECT STARTS\nAll legal requirements met\nDocuments signed: 1 · Documents sent: 3])

    H --> I

    I[Kickoff — Send intake forms\n📄 Brand & Content Intake Form\n📄 Technical Access Request\nThese are OPERATIONAL forms, not contracts\nFill in and return — no signature needed]

    I --> J[Project Runs\n📄 Change Order if scope changes\n1 page · client signs · work starts]

    J --> K[Delivery & Training\n📝 Training walkthrough call\n📄 Training Guide sent as reference PDF\nNo signature needed]

    K --> L[Send Satisfaction Survey\n📄 Short form · 5–8 questions\nOptional — generates testimonials]

    L --> M([🎉 Project Closed\nTotal docs signed by client: 1–2\nTotal docs touched: 4–5])

    style A fill:#3A86FF,color:#fff
    style H fill:#22c55e,color:#fff
    style M fill:#22c55e,color:#fff
    style C fill:#94a3b8,color:#fff
    style E fill:#94a3b8,color:#fff
    style F1 fill:#fef3c7,color:#1a1a1a

SMB Document Summary

Total signed by SMB client: 1 (always) + 1 per scope change

SMB — What to Say at Each Stage

After discovery call — sending the proposal:

"Great talking with you. I'm attaching a proposal covering scope, timeline, and investment. It's [X] pages — the key numbers are on page [2]. Let me know if you have questions or want to adjust anything."

When they say yes — sending the contract:

"Exciting! I've sent a contract via [DocuSign/HelloSign] — it's [X] pages and covers the project scope we discussed. Our general policies (refund, IP, privacy) are linked at the bottom rather than repeated in the document to keep it short. Once signed, I'll send the deposit invoice and we'll lock in your start date."

What if they ask about policies?

"All our policies are published at [webility.local/legal] — same as what any professional firm would have. The contract points to them rather than duplicating 20 pages. Happy to walk through anything specific."

Scenario B — Enterprise Client

Profile: 200–5,000 employees. Multiple stakeholders. Procurement department. Compliance requirements. Multi-region or multilingual. Typical engagement value: $50,000–$500,000+. Expectation: Thorough process, formal documentation, legal review on their side.

flowchart TD
    A([📣 First Contact\nOutbound · RFP · Referral · Event]) --> B

    B[Send Capabilities Deck\n📄 1 document\nServices · Process · Results · Team\nUsed as leave-behind before or after intro call]
    B --> C

    C[Intro / Discovery Meeting\n60–90 min · Multiple stakeholders\nNo forms sent yet]
    C -->|Not pursuing| D([👋 No further action])
    C -->|Interest confirmed| E

    E{Sensitive IP\nor data discussed?}
    E -->|Yes| F[Send NDA\n📄 1 document · Mutual\nSigned before sharing\npricing strategy or IP]
    E -->|No| G
    F --> G

    G[Scoped Discovery Sessions\n1–3 working sessions\nSend: Discovery Questionnaire\n📄 Structured intake · client fills in\nNo signature needed]
    G --> H

    H[Send Enterprise Proposal\n📄 1 document · 15–25 pages\nExec summary · Solution · Scope\nTimeline · Investment · ROI · Legal appendix]
    H -->|Revisions needed| H2[Revised Proposal\nUsually 1–2 rounds]
    H2 --> I
    H -->|Approved in principle| I

    I[CONTRACT PHASE\n2–6 weeks typical\nLegal teams involved on both sides]
    I --> I1[Send MSA\n📄 Master Service Agreement\nUmbrella commercial terms\nClient legal reviews · may redline]
    I1 --> I2[Send SOW\n📄 Statement of Work\nThis project's specific scope\nSent after MSA is agreed]
    I2 --> I3{Personal data\nprocessed?}
    I3 -->|Yes| I4[Send DPA\n📄 Data Processing Agreement\nGDPR · PIPEDA · Law 25 compliant\nSchedule to MSA]
    I3 -->|No| I5
    I4 --> I5[Deposit Invoice\n📄 50% of project value\nIssued after MSA + SOW signed]
    I5 --> J

    J([✅ PROJECT STARTS\nDocuments signed: 2–3\nMSA + SOW + optional DPA])

    J --> K[ONBOARDING PHASE — Week 1–2]
    K --> K1[Send Enterprise Onboarding Protocol\n📄 1 document\nStakeholder map · RACI · Escalation\nProcurement checklist · Compliance\nSigned by both parties]
    K --> K2[Send Technical Access Request\n📄 1 document\nAll system credentials\nFilled in by Client IT team]
    K --> K3[Send Brand & Content Intake\n📄 1 document\nBrand foundation · Audience\nContent inventory\nFilled in by Marketing team]

    K1 --> L
    K2 --> L
    K3 --> L

    L[Kickoff Meeting\n60–90 min · Full stakeholder group\nAgenda sent 24h prior\nNotes sent within 24h after]
    L --> M

    M[PROJECT EXECUTION\nWeekly: Status report emailed\nBi-weekly: Risk register updated\nMonthly: Executive Briefing\nPer phase: Milestone review + written approval\nAs needed: Change Orders — signed before work]

    M --> N[QA & PRE-LAUNCH\nInternal: Launch Checklist\n📄 Not sent to client\nShared for UAT sign-off only]
    N --> O[Launch Authorization\n📧 Written email approval from\ndesignated Project Owner\nDNS change authorized in writing]

    O --> P[HANDOVER PHASE]
    P --> P1[Handover Report\n📄 1 document\nDeliverables · IP transfer · Source files\nCredentials transferred · Signed by both]
    P --> P2[Training Sessions\n1–3 sessions\nTraining Guide sent as reference\nNo signature needed]
    P --> P3[Final Invoice\n📄 Remaining balance\nIP transfer confirmed upon payment]

    P1 --> Q
    P2 --> Q
    P3 --> Q

    Q[PROJECT CLOSE]
    Q --> Q1[Satisfaction Survey\n📄 Full 8-section version\nSent to Project Owner + Exec Sponsor]
    Q --> Q2[Case Study Discussion\n📧 Email conversation\nIf approved — separate permission form]
    Q --> Q3[Maintenance / Hosting Proposal\n📄 New proposal for ongoing engagement]

    Q1 --> R([🎉 Engagement Complete\nTotal docs signed: 3–5\nMSA · SOW · DPA · ENT Onboarding · Handover])

    style A fill:#3A86FF,color:#fff
    style J fill:#22c55e,color:#fff
    style R fill:#22c55e,color:#fff
    style D fill:#94a3b8,color:#fff
    style I fill:#f59e0b,color:#fff
    style K fill:#6D28D9,color:#fff

Enterprise Document Summary

Total signed by Enterprise client: 4–5 core documents + change orders

Side-by-Side Comparison

Practical Setup Requirements

For this flow to work, you need three things in place before sending your first contract:

1. E-signature Tool

Send contracts via a tool that captures legally binding electronic signatures:

• Recommended: DocuSign, PandaDoc, HelloSign (Dropbox Sign), or Adobe Acrobat Sign
• Client receives an email → clicks → signs → both parties get a signed PDF automatically
• Cost: ~$15–$30/month — non-negotiable infrastructure for an agency

2. Policies Live on Your Website

These pages must exist at a stable URL before you reference them in any contract:

Add a /legal hub page that links to all of the above — this is the URL you put in contracts.

3. Contract Clause That Ties It Together

Every standalone contract should include (adjust the URL):

Incorporated Policies: By signing this Agreement, Client acknowledges that they have had the opportunity to review and agree to be bound by Webility's published policies, incorporated by reference: Terms of Service, Privacy Policy, Refund & Cancellation Policy, Intellectual Property Policy, and Acceptable Use Policy, all available at webility.local/legal. These policies may be updated with [30] days' written notice.

That clause does the work. Clients are legally bound to all 6+ policy documents without receiving or signing each one individually.

What Actually Goes Into the SMB Contract

The standalone contract (e.g., contract-web-design.md) is the only thing an SMB client signs. To keep it concise while remaining comprehensive, it covers:

Total: ~3–4 pages. A client can read it in 5 minutes and understand it without a lawyer.

Edge Case Handling

Webility — CLIENT-PROCESS-FLOW-v1.0 Internal reference — describes how the document library is used in real client engagements.