CSignal — Product Design Spec

Author: Anuj Uppal, VP, Campana & Schott Date: March 24, 2026 Status: Ready for Build Day Build Day Team: TBD (1 builder + 4 non-builder roles)

1. Problem Statement

Consulting firms produce status decks. Clients consume them. The process is broken in three ways:

1. Stale on arrival. A deck represents a snapshot in time. By the time it's formatted, reviewed, and sent, the information is already outdated.

2. Disproportionate effort. Consultants spend up to 30% of their time on formatting, branding, and assembling decks — work that adds zero strategic value.

3. Information asymmetry. The client only knows what's happening when the consultant decides to tell them. Between updates, they're blind. Bad engagements hide in the gaps.

4. No common language across firms. Every consulting firm reports differently — different formats, different metrics, different definitions of "on track." The client's program management office has to wrangle five different decks into a coherent picture of what's actually happening across their portfolio. It's data integration work that shouldn't exist.

The deeper problem: a status deck, a decision brief, and an escalation artifact are three different products jammed into one PowerPoint file. The format hasn't evolved because no one has offered the client something better.

What this really is: CSignal is a high-powered program management tool disguised as a reporting platform. By enforcing consistent metrics, status definitions, and tracking mechanisms across every firm and every engagement, it gives the client a single, unified operating picture of their entire consulting portfolio — no interpretation required, no data wrangling, no reconciling McKinsey's format against Accenture's format against the boutique firm's Word doc.

2. Product Concept

One-Sentence Pitch

CSignal is a real-time client portal where every consulting engagement shows up as a living deck — always current, always branded, always accessible — so the client never has to ask "where are we?" again.

How It Works

Consultants submit updates through a simple input portal (structured fields + narrative text + meeting transcript uploads). An AI transform layer converts raw input into branded, deck-formatted slide content. Clients access a URL and see their engagements as living presentations that update in real time.

The Strategic Play

CSignal is deployed in the client's environment. The C&S engagement is the first project on the platform. The client then uses it for all their consulting engagements — Deloitte, Accenture, McKinsey, whoever. C&S collects recurring license revenue. Other firms are forced to report through C&S's platform, on C&S's terms.

The firms that resist look like they have something to hide. "Why won't you give us real-time visibility?" is a question no consultant wants to answer.

3. Target Buyer

Primary buyer: The client executive (VP, SVP, C-suite) who manages multiple consulting engagements and is frustrated by information asymmetry.

What they do with decks today:

• Forward them up the chain as proof of progress (reporting artifact)
• Review them to make decisions (decision-support tool)
• Barely read them — they just want to know things are on track (comfort blanket)

Different decks serve different purposes at different phases. CSignal handles all three by keeping the familiar deck format while making the content always current and always accessible.

Secondary beneficiary: The consulting firm. Consultants stop wasting time on formatting. But this is a side effect — it's not what gets the PO signed.

4. Architecture

Three Layers

4.1 Input Layer — Consultant Portal

How consultants feed the system. Three input channels:

• Structured fields: Project status (green/yellow/red), phase, % complete, key milestones, risks, decisions needed, next steps. Fast, consistent. Five fields max for quick updates.
• Narrative input: Free-text or pasted meeting minutes. The consultant dumps raw notes, transcripts, or a summary paragraph. AI does the rest.
• Transcript upload: Paste or upload from ambient scribes (Fireflies, Otter, etc.). The AI extracts key decisions, action items, and status signals from the raw transcript.

Each submission is timestamped and associated with a firm and a project.

4.2 Transform Layer — The Engine (Core IP)

This is where the defensible value lives. A Claude-powered pipeline that:

• Takes raw input (structured fields + narrative + transcript) and produces deck-formatted slide content
• Enforces consistent branding: fonts, colors, section headers, slide structure — every output looks like it came from the same design team
• Uses a Skill/Gem to anchor the output format (section headers, tone, level of detail) so it never drifts
• Runs at low temperature for consistency — the "steep-walled valley" principle from the Engine Room training
• Generates an executive summary slide automatically from the raw inputs
• Detects and flags risks, blockers, and decisions needed — pulls them to the top

4.3 Display Layer — Client Portal

Two views, both served as web pages:

Single-project view (the living deck):

• Looks and feels like a presentation — slide-shaped cards, one per section
• Sections: executive summary, progress, risks, decisions needed, next steps, activity log
• Always shows the latest state
• Client can scroll through or click through slide-by-slide
• Historical versions accessible via a timeline scrubber

Executive rollup view (the dashboard):

• All firms/projects on one screen
• Each project shows: firm name, project name, status color, last updated timestamp, one-line summary
• Click into any project to get the full living deck
• This is the view executives use to manage their entire consulting portfolio

4.4 Tech Stack (Hackathon)

• Frontend: Next.js or HTML/Tailwind — whatever the builder is fastest with
• Backend: Lightweight API (Node or Python) receiving submissions, calling Claude for transformation, storing output
• Storage: SQLite or flat JSON files — hackathon-grade, not production
• Deployment: Vercel, Replit, or local with ngrok — whatever gets a shareable URL fastest
• No auth for the demo. Each firm gets a unique URL for input. Executive view is a single public URL.

5. Hackathon Execution Plan

The Unique Advantage

This team's raw material is the other teams' output. The hackathon itself becomes the demo. Four "consulting firms" (the four Build Day teams), each with a company name, each producing real meeting minutes and status updates every 30 minutes, all feeding into CSignal.

By the end of the day, the platform has real data from real teams. The pitch isn't "imagine if..." — it's "you've been watching it work for the last four hours."

Build Day Agenda Integration

The overall Build Day agenda must include mandatory status submissions from all teams every 30 minutes. The CSignal team's Product Owner negotiates this into the agenda at kickoff.

Timeline (Cold Start — No Pre-Work)

Critical Risk & Fallback

The first 90 minutes are heads-down building with nothing impressive to show. The team has to trust the process. The payoff comes in the last hour when the platform has real data and the demo sells itself.

Fallback: If the full pipeline isn't working by +90 min, the builder focuses on getting the single-project living deck view perfect for one team's data. The executive rollup becomes a mockup in the pitch. Half the vision working with real data beats the full vision half-working.

Role Allocation

6. Defensibility & Competitive Moat

The Equalizer Effect

Consulting firms today deliver wildly different reporting experiences. McKinsey shows up with a 40-slide deck that's a work of art — perfect formatting, world-class design — but may be light on substance. A boutique firm with three people on the ground doing the real work submits a plain Word document because they don't have a design team. The client ends up comparing packaging instead of performance.

CSignal eliminates this. Every firm reports through the same structure, the same format, the same branded template, the same metrics. Status means the same thing across every engagement. Milestones are tracked the same way. Risk definitions are consistent. The platform handles the design so the content is the only variable. The client can finally compare substance to substance — milestones hit, risks flagged, decisions made — without being distracted by who has the better PowerPoint team.

For the client's program management office, this is transformative. Today they spend hours every week reconciling different reporting formats into a single portfolio view. CSignal gives them that view natively. One screen, all engagements, all firms, consistent metrics, no wrangling. It's not just a reporting tool — it's the program management layer they've been building manually in spreadsheets.

This is a leveling force that benefits the client and, strategically, benefits firms like C&S. We're not going to out-format McKinsey's 200-person design studio. But on a level playing field where the output format is standardized, our depth of work speaks for itself. CSignal shifts the competition from "who makes the prettiest deck" to "who's actually delivering results."

Why a Client Would Pay — and Keep Paying

• The switching cost is the data. Once six months of engagement history lives in CSignal, the client isn't ripping it out. Every month of use deepens the lock-in.
• The network effect across firms. Once the client mandates all consulting firms report through CSignal, each new firm added makes the executive rollup more valuable. The platform gets better the more firms use it.
• The equalizer creates mandate pressure. Once the client sees standardized reporting from two firms, they'll mandate the rest. No executive wants to go back to comparing apples-to-PowerPoints. Each new firm onboarded reinforces the standard.
• The AI transform layer is the moat. Anyone can build a dashboard. The hard part is turning messy meeting minutes into consistently branded, structured, deck-quality output. That Skill + RAG + low temperature specialization takes real tuning and improves with use.

Pricing Model

• Per-project, per-month subscription. Client pays for each active engagement on the platform.
• Engagements roll on and off. Revenue scales with the client's consulting spend — which is already budgeted.
• Anchor to cost replaced: If a consultant spends 5 hours/week on status decks at $300/hour, that's $6,000/month per engagement in formatting labor. Price CSignal at $500-1,500/month per project. The ROI is immediate and obvious.

Competitive Positioning

The closest analogue: "What if your consulting firm's status deck updated itself?" Nothing on the market does this.

7. Success Criteria

Hackathon Demo (April 17)

• Input form accepts submissions from all four teams
• AI transform layer converts raw meeting minutes into branded deck content
• Single-project living deck view renders for at least one team
• Executive rollup view shows all four teams with status, last updated, and drill-down
• Real data from 3+ hours of actual team submissions populates the platform
• Judges can interact with the live URL during the pitch

"Would a Client Pay For This?" Test

• The demo uses real data, not fake data
• The executive rollup answers "where are all my engagements?" in one glance
• The living deck replaces a formatted PowerPoint with zero formatting effort
• The pricing math makes the ROI self-evident
• The competitive dynamic (other firms reporting through your platform) is articulated clearly

8. Open Questions

• What branding should the living deck default to? Client branding? Firm branding? Co-branded?
• Should the timeline scrubber show every submission or aggregate by day/week?
• How should the platform handle conflicting or contradictory updates from the same team?
• What's the right data retention policy for client environments?
• Should there be notification/alerting (e.g., "Project X just went red")?

This spec was developed through a structured brainstorming session using the Consulting 2.0 Evaluate-Iterate methodology. It serves as both the design document for the CSignal team and the format template for all Build Day product idea submissions.