# Ship client funnels without demo fiction.

Agencies lose trust when the workshop cannot branch, the SOW overpromises platform magic, or the proposal cannot explain message costs. Delivery honesty: POCs that look like production, constraints in writing, handoff that survives week two.

## Overview

If you sell social automation, your product is expectations management as much as software. Clients arrive with briefs full of follower-welcome fantasy and “DM everyone” language. This page ranks for agency delivery: how to scope, demo, document, and hand off Instagram and WhatsApp funnels without inheriting ban risk or surprise invoices for the client’s finance team.

## Who this page is for

Social agencies, boutique automation freelancers, and performance teams that implement messaging funnels for clients.

You will recognize this if:

- You run workshops where the demo must branch or the room checks out.
- You write SOWs that must state platform limits in plain language.
- Brand safety will ask whether the stack is official or gray-market.
- You need proposal language for platform vs channel costs.

## Agency delivery fails before the first paid invoice.

A POC that cannot branch teaches the client the wrong product. Week two becomes “why is this different from the workshop?”

Briefs that demand always-on follower DMs set you up to either lie or use scrapers. Both destroy trust; one also risks the client’s account.

Proposals that bury WhatsApp fees inside “software” create finance fights mid-retainer when the first template blast lands.

## How strong agencies run the engagement

Scope truthfully, demo honestly, deliver with handoff, package costs as two lines.

### Rewrite the impossible brief early

Replace follower-welcome fantasy with comment, story, keyword, and lead-capture scope. Link the follow-to-DM page when needed.

### Connect the client’s real channels officially

Client-owned professional accounts and clean OAuth — no session sharing hacks in a freelancer browser profile.

### Demo the path the workshop promised

Branching, waits, field collection, and human handoff in the room.

### Document constraints in the SOW

Private-reply limits, template windows, non-goals, and who owns Meta enforcement risk.

### Hand off with inbox roles and a runbook

Client staff must know when automation stops. Your retainer should not be infinite human cover for a bot wall.

## What agencies sell when delivery is honest

Fewer angry mid-retainer calls. Cleaner scopes. Demos that survive production.

### Workshops that match week-two reality

Clients see branching in the POC, so production does not feel like bait-and-switch.

### SOW language that prevents scope rot

Non-goals and platform limits are written once and reused.

### Brand-safe integration story

Clean adapters make security questionnaires boring — in a good way.

### Proposal math finance accepts

Platform structure vs channel fees as separate lines.

### Reusable education pages for clients

Send use-case pages instead of rewriting the same Loom every kickoff.

### Competitive packaging when procurement asks

Point to the compare page for matrix claims; keep this page about how you deliver.

## Put these in the SOW before kickoff

Expectation debt is more expensive than build debt.

- Meta private-reply and messaging-window rules still apply to every Instagram campaign you ship.
- WhatsApp templates and fees are Meta’s economics — budget them explicitly.
- Follower-welcome is not a reliable official Instagram product surface today.
- Do not put gated AI in a fixed-fee SOW without checking packaging.

## Go deeper

- [Follow-to-DM non-goal](/en/use-cases/follow-to-dm)
- [Comment to DM](/en/use-cases/comment-to-dm)
- [Compare packaging](/en/compare)
- [Pricing rules](/en/pricing)

## Questions agencies ask

### Can a Free POC look like production for a client workshop?

Yes when the workshop needs branching, waits, and field collection — Free Logic is the point. Do not demo scraper features or always-on follower DMs; put non-goals in the SOW early.

### How do we put WhatsApp fees in a client proposal without guessing?

Two lines: platform subscription structure (see /pricing rules) and channel fees itemized at cost. Never present wallet-style prepaid balances as “included messaging.” Seed dollars come at signup, not from this page.

### What happens if Meta enforces against a client mid-retainer?

Higher tiers reference a documented enforcement-playbook posture and published SLAs. That is support packaging, not a guarantee Meta will reinstate the asset. Set that expectation in the SOW.

### Can a solo freelancer run the same stack as a ten-person agency?

Yes as an operator model: official APIs, free Logic for demos, itemized channel costs. Scale seats and SLAs with tiers when retainers justify it — freelancers are first-class, not an afterthought SKU.

### Will SocialReply resell gray-market follower or engagement tools?

No. Official APIs only. Agencies inherit ban risk from scrapers; we will not package that as a paid unlock or white-label growth hack.

### What artifact do we drop into a procurement deck?

/compare for packaging contrasts (Free Logic, billing, wallet, SLA) without inventing competitor price lists. Pair with the client’s solution page for audience-specific constraints.

## Make the next client workshop true.

Start free, demo a branching path, and put non-goals in the SOW before anyone paints a backlog.

[Start free](/en/signup) · [See pricing](/en/pricing)