niche-advantage
Use this skill when the user is a domain expert building for their own industry and wants to leverage their professional expertise as a competitive advantage. Also use when the user mentions 'I'm a [profession] building for [same profession],' 'I know my industry,' 'I have connections in my field,' 'how do I reach other [professionals],' or 'industry-specific marketing.' Covers using professional networks for sales, authority content, industry distribution channels, and positioning 'built by a practitioner' as a moat.
What this skill does
# Leverage Your Niche You spent 20 years becoming an expert. That expertise is your unfair advantage — no VC-backed team can out-understand a practitioner. This skill helps you turn your professional knowledge, network, and credibility into distribution, content, and positioning that competitors can't copy. ## Core Principles - "Built by a 15-year [profession]" is more convincing than any feature comparison. - Your professional network is warmer than any cold outreach list. Use it. - You can write content no generalist marketer can. Your authority is real. - Industry-specific channels (associations, conferences, trade publications) convert better than generic channels for niche SaaS. - Your biggest risk isn't competition — it's building for yourself instead of the market. --- ## Your Unfair Advantages (Use All of Them) | Advantage | What It Means | How to Use It | |-----------|--------------|---------------| | You ARE the customer | You know the pain firsthand | Your experience is your product spec and your marketing copy | | Professional network | You know 50-500 people in your industry | Warm outreach, beta testers, first customers, referral partners | | Industry credibility | Peers trust a practitioner over a tech company | "Built by a [role]" positioning, authority content, conference speaking | | Domain vocabulary | You speak the language | Copy that resonates, SEO keywords nobody outside the industry would know | | Workflow knowledge | You know the real process, not the textbook version | Build for how the job actually works, not how it's supposed to work | --- ## Distribution: Where Your Customers Already Are Forget generic startup advice about Twitter threads and Product Hunt. Your customers are somewhere specific. ### Find Your Industry's Channels **Tell AI:** ``` I'm a [profession] building a SaaS tool for other [professionals]. Help me identify where [professionals] actually spend time and make buying decisions: 1. Professional associations and organizations (national, state/regional, local) 2. Industry conferences and trade shows (annual, regional) 3. Trade publications and newsletters (online, print) 4. Online communities (forums, Facebook groups, LinkedIn groups, Slack/Discord) 5. Continuing education / certification programs 6. Industry-specific software review sites or directories 7. Referral networks and peer groups (masterminds, study groups, local meetups) For each, tell me: - How to get in front of this audience (speak, sponsor, contribute, advertise) - What it costs (free, cheap, expensive) - Expected timeline to results ``` ### Channel Prioritization for Solo Founders Start with ONE channel. Master it before adding another. | Priority | Channel | Why | Effort | |----------|---------|-----|--------| | 1st | **Your personal network** | Warmest leads, fastest feedback, free | Low | | 2nd | **Professional association** | Concentrated audience, built-in credibility | Medium | | 3rd | **Industry online community** | Scale beyond your network, free | Medium | | 4th | **Trade publication/newsletter** | Authority positioning, broad reach | Medium | | 5th | **Conference speaking** | Highest credibility, face-to-face | High | --- ## Sales: Warm Channels Beat Cold Outreach You don't need to "do sales." You need to tell your peers about the thing you built to solve the problem they all have. ### The Practitioner's Sales Approach **Week 1-2: Inner Circle (10-20 people)** - Personal message to colleagues you actually know - Not a pitch — a conversation: "I built this thing to fix [pain]. Can I show you?" - Ask for honest feedback, not just praise - Offer free access in exchange for feedback **Week 3-4: Extended Network (50-100 people)** - LinkedIn/email to professional connections - Frame as: "I've been working on something for [our profession]" - Include a specific result: "It cut my [task] time from 3 hours to 20 minutes" - Ask: "Do you deal with this too? Happy to give you early access." **Month 2+: Community Outreach** - Post in industry forums/groups (value first, product second) - Offer to present at local association meetings - Write for trade publications about the problem (not your product) **Tell AI:** ``` Write outreach messages for my SaaS product: - I'm a [profession] who built [product] to solve [pain] - Target: other [professionals] in my network Write 3 versions: 1. Personal message to a close colleague (informal, asking for feedback) 2. LinkedIn message to a professional connection (warm but professional) 3. Post for an industry online community (value-first, not salesy) Use the language [professionals] actually use. No startup jargon. Don't say "excited to announce" or "revolutionize." Say what it does and why it matters. ``` --- ## Content: Write What Only You Can Write Generic content marketing advice doesn't apply to you. You can write things no content marketer could because you've lived it. ### Authority Content Types | Content Type | Example | Why It Works | |-------------|---------|-------------| | "I did X wrong for 10 years" | "Why I stopped [common practice] after losing $50K" | Credibility through vulnerability | | Industry myth-busting | "3 things every [role] gets wrong about [topic]" | Only an insider can call this out | | Behind-the-scenes workflow | "How I actually handle [complex task] (not how the textbook says)" | Real-world > theory | | Tool/process comparison | "I tried 5 [category] tools. Here's what actually works." | Peer recommendations convert | | Regulatory/compliance clarity | "What [new regulation] actually means for your practice" | Expertise as a service | **Tell AI:** ``` I'm a [profession] with [X] years of experience building a SaaS for [audience]. Help me create 5 content pieces that leverage my domain expertise: Topics I know deeply: - [Topic 1 — something you have strong opinions about] - [Topic 2 — a common mistake in your field] - [Topic 3 — something that recently changed in your industry] For each content piece: - Title (specific, not clickbait) - Platform (where my audience will see it — industry publication, LinkedIn, forum) - Key insight only a practitioner would know - Natural mention of my product (if relevant, or skip it) Write in the voice of an experienced [professional] sharing with peers — not a marketer. ``` ### Content Distribution Your content goes where your audience already reads — not where startups post: - **Trade publications** — Many accept guest contributions. Your practitioner perspective is exactly what they want. - **Association newsletters** — Often desperate for member-contributed content. - **Industry LinkedIn groups** — Write posts as a peer, not a vendor. - **Conference presentations** — Talk about the problem, not your product. The product sells itself at the booth afterward. - **Continuing education** — Some tools can be positioned as practice improvement, which ties into CE requirements. --- ## Positioning: "Built by a Practitioner" as a Moat ### Why This Positioning Wins When a dentist evaluates two scheduling tools: - **Tool A:** "AI-powered scheduling platform for healthcare professionals" (built by a tech team) - **Tool B:** "Built by a dentist who was tired of losing $2,000/month to no-shows" (built by a practitioner) Tool B wins on trust every time. The practitioner understands the specific workflow, the specific pain points, the specific edge cases. ### How to Communicate It **On your landing page:** - Hero: Lead with the pain, not the product - Social proof: "I'm [name], a [profession] of [X] years. I built this because [pain]." - Throughout: Use industry terminology naturally (not defined — your users already know) **In conversations:** - "I built this because I was dealing with the same problem in my own practice" - "I've been a [role] for [X] years — this is the tool I wished I had" **In content:** - Write from first-person professional experience - Reference specific scenarios your audience rec
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.