# Business Review

> Assess product value, buyer fit, positioning, pricing, or onboarding from a commercial perspective. Use for business reviews, persona/ICP work, and buyer-facing messaging critique. Not for code review or implementation.

- Skill: `rca32/business-review` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add rca32/business-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rca32/business-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: rca32 (https://skillmd.com/u/rca32)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rca32/business-review

---


# Help the user make a commercial decision

Answer the requested business question from the product and evidence available. A landing-page critique does not require a full persona study; an ICP decision needs enough distinct buyer alternatives to support the choice, not a fixed count.

Use supplied materials, relevant product surfaces, and current external evidence when it can change the conclusion. Keep repository inspection at the product level unless implementation details are necessary to verify a claim. Do not infer working capabilities from marketing copy alone.

Distinguish what the product claims, what is observable, what a buyer likely values, and what still needs validation. Do not invent customer demand, willingness to pay, market size, retention, or numerical rankings.

For buyer/ICP work, identify the job, present alternative, buying trigger, decision-maker, ability to pay, adoption friction, and reason to leave when these distinguish segments. Prioritize fit and evidence over segment abundance. If information is weak, make a provisional recommendation and name the cheapest useful validation.

For positioning, pricing, or experience critique, connect each recommendation to a specific buyer obstacle and observable product behavior. Consider tradeoffs and alternatives; do not generate generic startup advice or a mandatory strategy package.

Choose the format and depth needed for the decision. Ask only for information that could materially reverse the recommendation; proceed from available evidence on the rest. Use the user's language and preserve uncertainty.

The review is read-only on source materials. Return it in conversation; save only requested artifacts at the user's path or repository convention, otherwise a descriptive path under `docs/`. Respect stated confidentiality and intended audience. Saving a private analysis does not authorize publishing it, modifying the product, or contacting customers.