Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
190 changes: 190 additions & 0 deletions docs/ACTIVATION_PLAN_30_60_90.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,190 @@
# SignalGrid 30/60/90 Activation Plan

## 1) Current State

SignalGrid is in a **controlled-demo-ready** stage and is positioning as a:
- runtime decision layer,
- Zero Trust orchestration capability,
- for shared-device/mobile frontline environments,
- combining identity + device posture + session context for access decisions.

### What is ready now
- Narrative and demo framing for runtime decisioning.
- Controlled demo flow suitable for discovery conversations.
- Initial outreach assets and objection themes drafted.

### What is not validated yet
- No production-ready claims are made.
- No compliance guarantees are made.
- No replacement claim is made against IAM/UEM/ITSM platforms.
- Remediation actions remain simulated unless validated with real integration evidence.

---

## 2) 30-Day Goals (Days 1–30)

### Primary objective
Start external validation immediately while tightening messaging based on real discovery input.

### Targets
1. Send first 20 outreach messages to qualified prospects/partners.
2. Book 1–3 discovery calls.
3. Capture top 5 recurring objections and buying criteria.
4. Confirm first integration proof target and acceptance criteria.
5. Produce one concise follow-up artifact for call participants (1-page overview).

### Exit criteria for day 30
- Outreach activity is consistent (not ad hoc).
- At least one live discovery conversation completed.
- Clear short list of integration proof requirements documented.

---

## 3) 60-Day Goals (Days 31–60)

### Primary objective
Convert early discovery into one concrete technical credibility signal.

### Targets
1. Complete one integration proof-of-concept path.
2. Refine demo sequence using discovery objections and language.
3. Document 3 scenario-based decision outcomes (allow/deny/unknown) using external posture signals.
4. Identify at least one serious design-partner candidate.

### Exit criteria for day 60
- Integration proof demonstrates ingestion of at least one real posture source.
- Messaging is updated with explicit “what we are / what we are not” boundaries.
- At least one design-partner conversation reaches next-step planning.

---

## 4) 90-Day Goals (Days 61–90)

### Primary objective
Run a constrained design-partner/pilot evaluation with clear evidence output.

### Targets
1. Execute one constrained pilot/design-partner evaluation scope.
2. Produce one proof artifact (demo evidence package, case note, integration evidence, or signed interest).
3. Define go/no-go criteria for post-pilot expansion.
4. Create a prioritized backlog of product and integration improvements from pilot feedback.

### Exit criteria for day 90
- At least one external proof artifact exists and can be shared with qualified prospects.
- Decision made: continue current motion, narrow focus, or pivot segment/integration emphasis.

---

## 5) Weekly Operating Cadence

### Monday (Plan)
- Review prior week metrics.
- Confirm outreach targets for the week.
- Choose one messaging or demo refinement objective.

### Tuesday–Wednesday (Execution)
- Send outreach messages.
- Run discovery calls.
- Capture objections, language, and integration asks.

### Thursday (Build + Validate)
- Progress integration proof tasks.
- Update demo script based on discovery findings.

### Friday (Synthesize + Decide)
- Publish weekly scorecard.
- Record risks, blockers, and decisions.
- Set next-week priorities and owner commitments.

---

## 6) Outreach Targets

### ICP emphasis
- Security, identity, and IT operators supporting frontline/shared-device environments.
- Teams managing identity and device posture fragmentation across multiple systems.

### 30-day outreach targets
- 20 outbound messages sent.
- 1–3 discovery calls booked.
- At least 10 meaningful response datapoints (positive, neutral, or objection-based).

### Message discipline
- Lead with runtime decision-gap problem.
- Avoid claims of replacing IAM/UEM/ITSM.
- Invite feedback on real operational blockers.

---

## 7) First Integration Proof Recommendation

### Recommended first proof
**Microsoft Intune / Entra ID posture proof**

### Why this first
- Strong fit with shared/mobile frontline environment use cases.
- Clear posture signal source for decisioning.
- High credibility gain with minimal proof scope.

### Minimal proof flow
1. Device identifier submitted to SignalGrid decision flow.
2. Intune/Entra posture/compliance state looked up.
3. SignalGrid decision input combines identity + posture + session context.
4. Decision result returned as allow / deny / unknown.

### Scope guardrails
- Do not position as full production integration.
- Keep remediation actions simulated unless specifically validated.

---

## 8) Success Metrics

### Activity metrics
- Outreach messages sent per week.
- Discovery calls booked and completed.
- Follow-up artifact delivery rate.

### Learning metrics
- Number of recurring objections captured.
- Number of messaging refinements applied.
- Number of integration requirements confirmed by prospects.

### Evidence metrics
- Integration proof milestone completion.
- Design-partner progression stage.
- Existence of shareable proof artifact by day 90.

---

## 9) Kill/Pivot Signals

Trigger reassessment if 2+ conditions persist for two consecutive review cycles:

1. Outreach conversion remains near zero despite message iteration.
2. Discovery calls consistently indicate no meaningful pain in target segment.
3. Integration proof cannot be completed within constrained scope.
4. Core objection repeatedly becomes “existing tools already solve this fully” without rebuttal traction.
5. No design-partner path emerges after sustained outreach and demo iteration.

### Pivot options
- Narrow target segment further.
- Shift first integration proof target.
- Reframe value proposition around strongest validated use case.

---

## 10) Owner Checklist

### Weekly checklist
- [ ] Outreach target count set and executed.
- [ ] Discovery insights logged within 24 hours.
- [ ] Objection tracker updated.
- [ ] Integration proof next task assigned.
- [ ] Demo/messaging delta documented.
- [ ] Friday scorecard published.

### Monthly checkpoint checklist
- [ ] 30/60/90 milestones reviewed against exit criteria.
- [ ] Risks and assumptions updated.
- [ ] Go/hold/pivot decision recorded with rationale.
Loading