# Umbra Studio — Post-Branding Next Steps

**Date:** April 16, 2026
**Status:** Branding complete. These five items are unblocked.

---

## 1. Case Study #1 — Indietheka as Lighthouse Case

**What:** Populate `umbra-studio-case-study-template.html` with the Indietheka agentic operation as the first completed case study.

**Content to document:**
- Baseline workflow (pre-agent): manual editorial calendar, human-written reviews, manual cross-posting, manual Spotify playlist curation
- Agentic redesign: RSS poller → WordPress publisher → album review agent → distribution agent → social posting agent → Spotify sync
- Measured outcomes: posts/day, agent invocations/week (160+), distribution reach (platforms covered), time-to-publish deltas, human hours saved per week
- Reusable patterns: content ingestion pipeline, multi-platform distribution agent, editorial governance layer

**Effort:** ~1 session. Pull metrics from live operation.

---

## 2. Sales Deck — `umbra-studio-deck.pptx`

**What:** 12–15 slide deck using the `pptx` skill. Built on the Studio brand system.

**Slide outline:**
1. Title: Umbra Studio — Workflow Redesign for the Agentic Era
2. The Gen AI Paradox (McKinsey stat, framing)
3. What we do (Lighthouse Sprint, one sentence)
4. The Lighthouse Sprint — 4 stages
5. Stage deep-dive: Discovery
6. Stage deep-dive: Redesign
7. Stage deep-dive: Build + Handoff
8. Why us — Operator credibility
9. Case study: Indietheka (from case study #1)
10. Case study: Transit + Radiohead Community (secondary proof)
11. Who it's for (ICP)
12. Engagement structure + pricing shape
13. Team / qualifications (Abe + Umbra Group)
14. What happens next (30-min call CTA)

**Effort:** ~1 session after case study is done.

---

## 3. Pricing — Publish or Keep Off-Surface

**Decision needed from Abe:** Does Studio publish pricing on /studio, or keep it behind qualification?

**Default framework:**
- **Lighthouse Sprint:** $XXk fixed fee (6–10 weeks, full engagement)
- **Discovery-only engagement:** $XXk fixed fee (2 weeks, ends with a report + go/no-go recommendation)
- Outcome-tied: if the measured outcome doesn't hit a pre-agreed threshold, a portion of the fee is refunded or deferred

**Open questions:**
- What are the actual dollar figures?
- Do we publish a range ("starting at $Xk") or keep pricing off-surface entirely?
- Is the outcome-tied mechanism a percentage holdback, a success bonus, or something else?

---

## 4. Lead-Gen Plan — ICP + Warm-Intro Pathways

**Ideal Customer Profile (draft):**
- Company size: 100–2,000 employees (mid-market sweet spot)
- Industries: insurance, financial services, healthcare ops, professional services, legal ops, content operations
- Role: VP Operations, VP Process Improvement, Chief of Staff, Head of Digital Transformation
- Trigger: recently hired an "AI lead" or "Head of AI" and the pilots haven't scaled; or internal mandate to show AI ROI by next board cycle
- Disqualifier: companies looking for chatbot implementations, RAG-only projects, or "AI strategy" without a specific workflow in mind

**Three warm-intro pathways:**
1. **Anthropic network:** Abe has direct relationships from operating on Claude at scale. Anthropic's enterprise team may have customers stuck in the pilot-to-production gap — exactly Studio's sweet spot. Ask for introductions to customers who've deployed Claude but haven't seen workflow-level impact.
2. **Ex-colleagues and professional network:** Anyone who's moved into ops/transformation roles at mid-market companies. Reach out with the one-pager and an honest ask for a 30-min conversation.
3. **Indie music industry crossover:** The Indietheka/Transit network includes label ops people, distributor contacts, and music-tech founders who may have enterprise ops connections or may themselves need workflow redesign for their own companies.

---

## 5. First Qualified-Lead Email Template

**Draft (5–8 sentences, reads like a person wrote it):**

> Subject: Rebuilding [workflow] around agents — quick question
>
> Hi [Name],
>
> I run Umbra Studio — we redesign workflows around agents for mid-market organizations. Not strategy work; we build and hand over working systems in 6–10 weeks.
>
> I noticed [specific trigger — e.g., "your team recently posted a Head of AI role" / "we have a mutual connection in [person]" / "your company was mentioned in [context]"]. That pattern usually means there's a workflow somewhere that's costing you more than it should.
>
> We've been running our own agentic operations across five properties (160+ agent invocations/week), and every pattern we sell has been stress-tested on ourselves first.
>
> Would a 30-minute call make sense? No deck, no pitch — just an honest conversation about whether the workflow you're dealing with is one we can rebuild.
>
> Best,
> Abe
> Umbra Studio · umbrastudio.com

**Note:** Customize the [specific trigger] for each lead. Generic versions of this email don't work.

---

*This document is the plan-of-record for the next session. Abe will kick off each item sequentially, starting with the Indietheka case study.*