Sales Motion Content Strategy — Feb 2026
Cadence: 3 posts/week (1 per account: Luke, Robert, Uttam)
Purpose: Drive pipeline directly. Showcase real client engagements. Build credibility for all three accounts.
Created: 2026-02-20
Status: Strategy confirmed — Week 1 outlines ready. Weeks 2+ require proof point collection (see Action Items).
Part 1: What Is “Sales Motion” Content?
Sales motion content is proof-first, pipeline-driving content — posts that put a real client transformation at the center, anchor on hard numbers, and invite similar prospects to start a conversation.
It is not thought leadership (broad education) and not product marketing (feature-focused). It is evidence that Brainforge delivers measurable results for clients that match the reader’s profile.
The one-sentence definition:
“Here’s a problem a client had, here’s what we built, here’s what changed — working on something similar?”
How it differs from other content types
| Type | What it does | When to use |
|---|---|---|
| Thought leadership | Educates, builds awareness, grows audience | Always running — organic credibility builder |
| Sales motion | Converts awareness → pipeline. Showcases real results | 3×/week — the engine behind demos booked |
| Product / feature | Explains what we built | Sparingly — leads with solution, not problem |
Sales motion posts are the last mile between someone knowing Brainforge exists and them sending a DM.
Part 2: Services to Feature
Not every post needs to feature every service. Match the service to the account’s voice and the strongest available proof point.
| Service | What it solves | Primary account | ICP |
|---|---|---|---|
| Agency Intelligence (briefs, client prep, reports/insights) | Teams spending 4–5 hrs/brand on manual work; copy-paste workflows; no shared knowledge | Luke | Creative/advertising agencies, 50–500 ppl |
| Edge-to-Activation (E2A) | Attribution gaps; platforms over-claiming; 15–30% of conversions invisible; no single source of truth | Robert, Uttam | E-commerce, performance marketers |
| Data & Analytics (Snowflake/dbt/Fivetran) | No single source of truth; siloed reporting; reactive decisions; no cost forecasting | Robert, Uttam | E-commerce, any company with multi-source data |
| Custom AI builds (chatbots, scoring, qualification) | Manual triage; slow qualification; customer support load; no AI layer on proprietary content | Any account | Varies — use case-specific |
Week-by-week suggestion:
- Week 1: Agency Intelligence (Luke), Data/Analytics (Robert), ROI from data work (Uttam)
- Week 2: E2A/attribution (Robert), Agency Intelligence ROI (Uttam), Custom AI build (Luke)
- Week 3: Mix — use whatever proof points have been gathered from Ray/Ryan input
Part 3: Proof Points Bank
Only use numbers confirmed in vault docs. Do not invent or extrapolate.
Agency Intelligence
| Metric | Value | Source |
|---|---|---|
| Brief time saved | 4–5 hours → 45 min | Agency client case study |
| Meeting prep saved | 30–40 min → 5–7 min | Agency client case study |
| Monthly time reclaimed | 120+ hours/month | Agency client case study |
| Annual value of time saved | ~100/hr blended) | Agency client case study |
| Brief throughput | 3x output, same team | Agency client case study |
| AI generation quality | 75% done on first generation (briefs) | Demo transcripts |
| Report quality | 70%+ on first run (reports) | Demo transcripts |
Data & Analytics / Snowflake (PP2G)
| Metric | Value | Source |
|---|---|---|
| Shipping rate discounts | 80–90% discounts negotiated with UPS/FedEx | PP2G case study |
| Shipping savings | Hundreds of thousands of dollars | PP2G case study |
| AI POC delivery time | ~2 weeks (pool Q&A chatbot with image support, QA, handoff) | PP2G case study |
| Stack deployed | Snowflake, dbt, Fivetran, Rill Data, Prophet | PP2G case study |
Edge-to-Activation (E2A)
| Metric | Value | Source |
|---|---|---|
| Conversion recovery | Double-digit % of customers with no prior attribution visibility recovered | E2A offer doc |
| Misallocation corrected | Six-figure misallocations corrected | E2A offer doc |
| Reporting accuracy | 95% reporting accuracy | E2A offer doc |
| Invisible conversions | 15–30% of conversions invisible to client-side tracking | E2A offer doc |
| Deal example (anonymised) | $18K closed in 3 days — e-commerce brand, audit-first-then-pilot pattern | Pipeline data |
Lead scoring / qualification
| Metric | Value | Source |
|---|---|---|
| Profiles qualified | 69 profiles qualified in minutes | Sales docs |
| Scoring time | 5–10 min → <30 sec per lead | Sales docs |
| Volume | 20–30 qualified conversations/month | Sales docs |
Speed / delivery
| Metric | Value | Source |
|---|---|---|
| Time to working system | 2–3 weeks | Offer docs / vault |
| Engagement range | 30K typical · 90-day implementation | Agency Intelligence |
| E2A entry point | $18K (Phase 0 + Phase 1 audit-then-pilot) | Pipeline data |
Proof points still needed (get from Ray / Ryan before meeting)
- Client names we can use publicly — Which clients have approved being named vs. anonymised only?
- Testimonials or direct quotes — Any written/verbal client feedback we can excerpt?
- E2A client results beyond MinuteMD — Any other e-commerce wins with hard numbers?
- Agency Intelligence named client — Can we name the agency or must we anonymise?
- Third Bridge / Inteleos / other pipeline outcomes — Any proof points from recent calls?
- Robert’s and Uttam’s preferred framing — What do they want to be known for on LinkedIn? (Technical builder vs. GTM partner?)
Part 4: CTA Framework
Keep CTAs simple. One CTA per post. Match the ask to where the reader likely is.
| CTA type | When to use | Example phrasing |
|---|---|---|
| DM me (soft) | Default — starts a conversation, low friction | ”Working on something similar? DM me.” |
| Book a call (direct) | When post is clearly service-specific and reader is warm | ”If you want to see your gap — book a call. Link in comments.” |
| Link in comments | When a demo, white paper, or asset is directly relevant | ”We put together a walkthrough of exactly this. Link in comments.” |
| Request a demo | When post demonstrates a feature visually (video/screenshot) | “Want to see it run on your data? DM me to set up a demo.” |
Default CTA for sales motion posts: “Working on [X problem]? DM me.” — it’s the lowest-friction path to a discovery conversation and fits LinkedIn natively.
Part 5: Account Voice Guide
Each account posts once per week. The same story can be told by all three — but from a different angle. A prospect might follow all three accounts and see three posts about the same client; that’s intentional social proof.
Luke — Client Journey / Transformation Stories
Positioning: Luke is the trusted guide who led the engagement. Posts feel like a case debrief told by the person who ran the room.
Voice: Narrative, empathetic, outcome-first. “Before they came to us…” → “Here’s what changed.” Not technical. No jargon. Numbers land the story.
What he highlights: The before state (the painful manual reality), the transformation, the human impact (what the team could actually do differently). Occasional vulnerability — “we didn’t know if this would work.”
Format tendency: Story-led. Short paragraphs. Before/after structure. Ends with a curious, low-pressure DM CTA.
Example hook style:
“One of our agency clients spent 4–5 hours per brand building creative briefs. With 60+ brands, that math doesn’t work.”
Robert — Technical Depth / Implementation Approach
Positioning: Robert is the engineer/architect who knows exactly how the system was built and why each decision was made. Posts feel like reading a build log from someone who cares about craft.
Voice: Direct, precise. Shows the stack. Explains trade-offs. Comfortable saying “we chose X over Y because…” Not salesy. Credibility through specificity.
What he highlights: The technical problem (what made it hard), the stack and decisions made, the lesson or insight that’s generalizable. Numbers appear as outputs, not headlines.
Format tendency: Problem → decision → system → what we learned. Sometimes list-based. Ends with “working on something like this? DM me.”
Example hook style:
“We modeled a 7-figure shipping contract in SQL and used it to walk into UPS negotiations as the data authority. Here’s how we did it.”
Uttam — Results / ROI
Positioning: Uttam is the results-focused executive who cuts to what changed. Posts feel like a board update: crisp, numbered, no fluff.
Voice: Punchy. Data-first. Before/after. Short sentences. Comfortable being direct about dollar impact. Builds credibility through numbers, not narrative.
What he highlights: The before metric, the after metric, the delta. Why it mattered (business context in 1–2 sentences). What this unlocks next.
Format tendency: Before: [number]. After: [number]. What we did: [1 sentence]. What opened up: [1 sentence]. CTA.
Example hook style:
“An e-commerce company had no visibility into their shipping spend. We fixed that. They saved hundreds of thousands of dollars in 12 months.”
Part 6: Reusable Post Template
This is the fill-in-the-blank framework any team member can use to produce a sales motion post. Fields marked [REQUIRED] must be filled; fields marked [OPTIONAL] can be skipped if not available.
SALES MOTION POST — [ACCOUNT] — [DATE]
SERVICE: [Agency Intelligence / E2A / Data & Analytics / Custom AI]
ICP TARGET: [Who this is written for — e.g. "Agency ops leaders", "E-commerce performance marketers"]
PROOF POINT: [Which client or result this is based on — named or anonymised]
---
HOOK (1–2 sentences — client's painful before state):
[Start with the problem, not the solution. Make the reader feel the pain before you describe fixing it.]
CHALLENGE (2–4 sentences — what made this hard to solve):
[Why couldn't they just fix it themselves? What was the structural or process barrier? Be specific.]
APPROACH (3–5 bullet points or sentences — what Brainforge built/implemented):
[Concrete: what did we build, what stack, what decisions? Not a product pitch — a build description.]
RESULTS (2–4 sentences — what changed, with numbers):
[Specific metrics only. Before → after. Time saved, money saved, team capacity unlocked.]
[Do not invent numbers. Use only vault-confirmed proof points.]
CTA (1 sentence):
[Default: "Working on [X]? DM me." — adjust to match post tone and service]
---
VOICE CHECK before posting:
[ ] Does the hook lead with the client's pain, not Brainforge's product?
[ ] Are all numbers sourced from confirmed vault proof points?
[ ] Is the CTA one sentence, low-friction, and specific to the post?
[ ] Has this been reviewed against the LinkedIn pre-publish checklist?
[ ] Is any client named — if so, do we have approval to name them?
Part 7: Week 1 Post Outlines
Theme: “What we actually built and what changed.”
All three posts are grounded in real delivered work. Week 1 establishes credibility before expanding into thought leadership or feature-focused angles in later weeks.
Post 1 — Luke | Agency Intelligence | Client Transformation
Service: Agency Intelligence
ICP target: Creative agency ops leaders, strategy directors, agency founders
Proof point: Agency client (anonymised) — brief generation + knowledge base
Hook:
One of our agency clients was spending 4–5 hours per brand building creative briefs. With 60+ brands on retainer, that’s not a workflow problem — it’s a capacity ceiling.
Challenge:
The hard part wasn’t the work itself. It was that the knowledge existed — brand tone, past campaigns, client preferences — but it lived in people’s heads and scattered docs. Every brief started from scratch. Strategists were the knowledge base, and that didn’t scale.
Approach:
- Indexed the agency’s client knowledge into a queryable system — past campaigns, preferences, performance data, context
- Built a brief generator that draws from that knowledge: calendar → brief → designer handoff in one flow
- Added client intelligence layer for meeting prep — any team member can ask “what were last month’s top campaigns?” and get a cited answer in minutes
- Automated weekly reporting: data flows from Meta, Google, Klaviyo, Shopify → AI narrative summaries → Slack delivery on schedule
Results:
Brief time dropped from 4–5 hours to 45 minutes per brand. Meeting prep went from 30–40 minutes to 5–7 minutes. The team reclaimed 120+ hours a month — roughly $144K in annual capacity at a blended rate. Same team, 3x the output.
CTA:
If you’re running an agency and your strategists are the bottleneck — not the work — DM me.
Post 2 — Robert | Data & Analytics | Technical Depth
Service: Data & Analytics (Snowflake, dbt, SQL contract modeling)
ICP target: Data engineers, analytics leads, CTOs, ops leaders at e-commerce companies
Proof point: PoolPartsToGo (PP2G) — UPS contract modeling and negotiation
Hook:
We built a SQL model of a 7-figure shipping contract and used it to walk into UPS and FedEx negotiations as the data authority on every shipment the client had ever made. Here’s how we did it.
Challenge:
The client (e-commerce, multi-channel: Amazon, Shopify, DTC) had no clear view of what they were actually being charged vs. what their contract said. Hundreds of SKUs, multiple carriers, scattered invoices. You can’t negotiate what you can’t see — and they couldn’t see it.
Approach:
- Mapped every contract term into a rule-based SQL model: each order tied to the applicable package price and actual invoice
- Ran the model against historical shipments to produce a cost forecast by volume, growth trajectory, and new markets
- Built dashboards in Rill Data for daily KPI tracking — so the client could see the numbers the same way we did before and during negotiations
- Joined negotiations with UPS and FedEx as the data authority — not as a consultant, as the person who’d modeled their entire cost structure
- Stack: Snowflake + dbt + Fivetran + Rill Data + Python/Prophet for forecasting
Results:
Negotiated 80–90% discounts on shipping rates. Savings landed in the hundreds of thousands of dollars. Dashboards are now in daily operational use — the client makes pricing, bundling, and campaign decisions from the same system.
CTA:
If you’re running complex cost structures or shipping spend without a model under it — DM me.
Post 3 — Uttam | Data & Analytics | ROI / Results
Service: Data & Analytics
ICP target: E-commerce founders, CFOs, ops leaders — anyone responsible for cost and margin
Proof point: PoolPartsToGo (PP2G) — results-focused framing
Hook:
An e-commerce company had no visibility into what they were actually paying their shipping carrier. They had a contract. They had invoices. They didn’t have a model connecting the two. We fixed that.
Challenge:
When you’re shipping hundreds of SKUs across Amazon, Shopify, and DTC with multiple carriers and regional pricing tiers — your contract is only as useful as your ability to model it. They couldn’t model it. So every rate was just… whatever the invoice said.
Approach:
We built a rule-based SQL model that mapped every contract term to every shipment. Forecasted their spend across volume scenarios and new markets. Joined them in carrier negotiations with the full picture in hand.
Results:
- Before: No cost model. Reactive on invoices. Zero negotiating leverage.
- After: 80–90% discounts negotiated on shipping rates. Savings in the hundreds of thousands of dollars.
- Time to working system: Weeks — not months.
- Ongoing: Dashboards in daily use. Team makes pricing and bundling decisions from the same data.
The shipping savings paid for the engagement many times over.
CTA:
If there’s a cost structure in your business that you’re flying blind on — DM me.
Action Items Before Content Planning Meeting
Get from Ray / Ryan
- Which client names can be used publicly vs. must be anonymised?
- What do Ray and Ryan think the sales motion should prioritise — agency clients, e-commerce, or both equally?
- Any direct client quotes or testimonials they have on file?
- Are there E2A client results (beyond MinuteMD) with shareable numbers?
- What’s Robert’s preferred LinkedIn positioning — technical builder, GTM partner, or executive strategist?
- What’s Uttam’s preferred angle — operator/results focus, or executive/vision focus?
Gather before Weeks 2–3
- Pull any written feedback from PP2G (Ben, Kim) — direct quotes for Uttam or Robert
- Confirm agency client ROI numbers with the team — are 120 hrs/month and $144K safe to publish?
- Third Bridge call outcome — potential proof point for knowledge base + proprietary content use case
- MinuteMD results — any post-go-live metrics to add to E2A proof point bank?
Handoff Notes
- Framework: Hook (pain) → Challenge (why hard) → Approach (what we built) → Results (what changed) → CTA
- CTA default: “Working on [X]? DM me.” — keep it consistent and low friction
- Numbers policy: Use only vault-confirmed proof points. No invented or extrapolated stats.
- Client naming: Until approval is confirmed, anonymise all clients (e.g. “an agency client,” “an e-commerce company”)
- Pre-publish: All posts must pass the LinkedIn pre-publish checklist before going live — especially for client details
- Voice: Each account has a distinct angle on the same story. Intentionally let all three cover the same client from different POVs.
- Related files:
- Agency Intelligence 9 Post Outlines — Luke’s Agency Intelligence posts already drafted
- E2A 12 Post Outlines — Robert and Uttam’s E2A posts
- E2A Content Strategy — E2A voice and pillar guide
- PP2G Case Study — source for Posts 2 and 3
- LinkedIn Pre-Publish Checklist — mandatory before every post