Carousel — "Paperwork Out. Revenue In."
Concept — watch this play like one reel
Unifying visual motif: "The Ledger." Every slide is a ledger page. Left column in muted red = Hours Out (cognitive paperwork drain). Right column in deep green = Hours In (revenue-generating cognition redeployed). Each slide adds a row. By slide 9, the ledger is full and visually loaded. Slide 10 is the ARI CTA — the ledger closes and hands control to the reader.
The kinetic story a viewer gets from swiping: a bookkeeping ledger slowly filling up, going from empty and red-tinted to full and green-weighted. Static slides, but the sequence feels like a time-lapse of a balance sheet flipping.
Design system (same across all 10 slides)
- Aspect ratio: 1080×1350 (LinkedIn / Instagram carousel sweet spot)
- Background: Off-white
#FAF7F2(paper texture, subtle grain) - Accent dark: Deep navy
#0B1F3A(trust, enterprise) - Accent red (Hours Out): Muted brick
#A63A2A(urgent but not alarmist) - Accent green (Hours In): Deep forest
#1F5F3D(revenue, growth) - Typography:
- Headlines:
FrauncesBold 72pt (editorial weight, serif authority) - Subheads:
InterMedium 38pt - Body:
InterRegular 28pt - Numbers (hero):
FrauncesBlack 180pt — these are the visual drama - Recurring frame element: A thin navy hairline border 48px from edges, with "AJAY TYAGI · DKUBE" footer on every slide, and slide-number indicator bottom-right (e.g.,
03/10) - Motif anchor: Left margin carries a vertical label "HOURS OUT" (brick red), right margin carries "HOURS IN" (forest green). Visible on every slide.
---
Slide 1 — The Hook
Headline (hero type): 7,000 hours.
Subhead: One mechanical contractor. One AP queue. Last year.
Visual: The ledger begins — a single red row at the top of the left column showing "7,000" in hero black. Right column is empty. The tension is in the asymmetry.
Transition cue: "Swipe to see where it went."
---
Slide 2 — The Pattern
Headline: Your operations team isn't slow.
Subhead: The paperwork is.
Visual: Ledger now shows the red "7,000" fading into multiple smaller red rows — hinting that this isn't one problem, it's five. Right column still empty.
Body micro-text (bottom): *This is the pattern we're seeing across $50M–$1B mechanical, industrial, and manufacturing contractors in 2026.*
---
Slide 3 — Where the Time Actually Goes
Headline: Five paperwork streams. Five drains.
Visual layout: Ledger left column now populated with five red rows, each with a label + an hour range:
| Stream | Hours/yr |
|---|---|
| Submittals & RFIs | 12,000 – 18,000 |
| Bid-document scope capture | 6,000 – 10,000 |
| Change order drafting | 2,500 – 4,000 |
| AP exception reconciliation | 5,000 – 9,000 |
| Safety / QA-QC / close-out | 8,000 – 14,000 |
| Total cognitive drain | 40,000 – 60,000 |
Right column still empty. The weight is obvious.
---
Slide 4 — The Math Nobody Runs
Hero number (center): $4.2M – $12M
Subhead: What that cognitive drain costs — per year — in the hourly value of the people doing it.
Body micro-text: *Senior estimators, experienced AP clerks, project engineers — billed at the value their judgment actually produces ($85–$200/hr).*
Visual: The ledger's left column now shows a dollar figure stamped across the bottom in brick red. Right column still empty, and starting to feel like an accusation.
---
Slide 5 — What Changes
Headline: Agentic AI doesn't replace your team.
Subhead: It absorbs the cognitive paperwork feeding them.
Body micro-text: *Not a chatbot you open. An agent that reads the submittal, drafts the response, routes the exception — before your engineer opens their inbox.*
Visual: First green row appears in the right column — labeled "ABSORBED" with a small arrow pointing from red column → green column. The ledger starts to balance.
---
Slide 6 — The One Architectural Catch
Headline: One condition: it has to be *actually* private.
Subhead: If your prompts leave your VPC, this doesn't work. Compliance will catch it. Legal will kill it.
Body micro-text: *Three tests: prompts never leave your network, model weights you control, tamper-evident audit trail. Everything else is a vendor's promise.*
Visual: Small lock icon (navy) appears at the column boundary, with the caption "IN-VPC ONLY." Red column behind it shows a faded "$1.4M" — ghost of the industrial firm's failed vendor experiment.
---
Slide 7 — What You Reclaim
Hero number: 2,000 hours / year
Subhead: Per mid-sized mechanical contractor. In the first twelve weeks.
Visual: Three green rows now in the right column:
+2,000(reclaimed cognitive capacity)+3 to 7(additional project awards — from estimating capacity freed)+8-12%(service density — from dispatch paperwork freed)
Left column's red starts to look reduced. Ledger tipping toward green.
---
Slide 8 — The Revenue Translation
Hero numbers stacked:
+$15M to +$35M Awarded revenue +$3M to +$5M Incremental service +$600K to $1.2M Margin from CO prevention
Subhead: This is what 2,000 reclaimed hours compounds into, at a typical $200M mechanical contractor.
Body micro-text: *Not productivity theatre. Specific, boring, repeatable redeployment of cognitive hours from paperwork to pipeline.*
Visual: Ledger's right column now visibly outweighs the left. The color balance has flipped from red-dominant to green-dominant.
---
Slide 9 — The 12-Week Test
Headline: $25K pilot. Twelve weeks. Measured ROI.
Subhead: Your team picks the wedge. We build against your baseline. If it doesn't pay back, you don't renew.
Body micro-text: *This is the delivery model. No six-month requirements phase. No perpetual professional services. No license before proof.*
Visual: The ledger closes — book imagery, "BALANCED" stamp in green across the bottom. A faint dotted line points to slide 10.
---
Slide 10 — The Ask
Headline: Find out where your 2,000 hours are.
Subhead (hero type): wnbpc.app
Body:
Take the AI Readiness Index. 30 questions. 5 minutes.
*You get a scoped report identifying the two or three places in your operation where a 12-week pilot would pay back fastest. Based on your systems, your team, your project mix. No sales call required.*
Visual: Clean, the ledger is gone — just the URL in oversized Fraunces black, a QR code bottom-right linking to wnbpc.app, and a small Ajay Tyagi byline + headshot bottom-left. "DKUBE · Private AI for industrial contractors" footer.
---
Voice-check
- ✓ Opens with specific number (7,000)
- ✓ First-person plural used ("What we're seeing…", "what we build")
- ✓ Fragment cadence ("One contractor. One AP queue.")
- ✓ Closes on ARI CTA
- ✓ No banned phrases (no leverage-as-verb, no "revolutionize", no "game-changer", no "journey", no "enterprise-grade")
- ✓ Numbers stacked for CFO scannability on slides 4, 7, 8
Production notes for designer / generation tool
For Claude design / Gemini Nano Banana Pro / fal.ai:
- Use the design-system block above verbatim as the style prompt
- Generate each slide as a separate 1080×1350 PNG
- Maintain the left-margin "HOURS OUT" / right-margin "HOURS IN" labels on every slide for visual continuity
- Final export: 10 PNGs + 1 master PDF with all slides for LinkedIn upload
Alt-text for accessibility (LinkedIn post):
*10-slide carousel visualizing how a $400M mechanical contractor reclaimed 4,900 cognitive hours per year from AP reconciliation — and what happened when those hours were redeployed into cash-flow forecasting and bid capacity.*
Caption for LinkedIn post (paired with the carousel upload):
Last year a $400M mechanical contractor I worked with ran the numbers on their AP team. Not headcount. Cognitive load.
7,000 hours/year matching packing slips to POs. Twelve weeks later — same team, same hours — that was down to 2,100. The reclaimed 4,900 hours funded a cash-flow forecasting initiative their CFO had been trying to staff for three years.
The pattern repeats. Mechanical contractors over $50M have five paperwork streams draining 40,000–60,000 cognitive hours a year from people whose judgment is billed at $85–$200/hr by the work they produce.
The leverage isn't AI replacing the team. It's agentic AI absorbing the cognitive load feeding them — and the team redeploying into the work that actually multiplies revenue.
The five streams, the math on reclaimed hours, and the one architectural catch that kills most vendor deployments 👇
Find out where your 2,000 hours are hiding: wnbpc.app