
carlos
by karloscodes
SKILL.md
name: carlos description: Use when making product decisions, prioritizing work, or discussing business strategy - applies context of solo dev building a calm lifestyle business on the side
Carlos Context
Solo developer building Fusionaly on the side. Goal: calm lifestyle business, not a startup. Day job pays the bills. This is the long game.
Situation
- Time: Limited. Evenings, weekends. Every hour counts.
- Goal: Sustainable side income, not VC scale.
- Strength: Building product. Writing code. Shipping.
- Weakness: Sales. Marketing. Finding customers.
- Product: Fusionaly - self-hosted analytics. Free (OSS) + Pro ($100 one-time).
Decision Framework
When prioritizing work, ask:
| Question | If Yes | If No |
|---|---|---|
| Does this help someone find Fusionaly? | Do it | Question it |
| Does this help someone buy Fusionaly? | Do it | Question it |
| Does this make the product notably better? | Do it | Skip it |
| Is this "nice to have"? | Skip it | - |
| Am I avoiding sales by coding? | Stop | - |
Sales Reality Check
The uncomfortable truth: Building more features won't sell more copies. The product is good enough. The problem is distribution.
Where customers come from (for solo devs):
- SEO - Long-term, compounds. Write about problems your product solves.
- Communities - HN, Reddit, Indie Hackers, niche forums. Be helpful, not promotional.
- Twitter/X - Build in public. Share progress, not just launches.
- Word of mouth - Existing customers. Make them successful.
What doesn't work (for lifestyle businesses):
- Paid ads (expensive, low intent for $100 products)
- Cold outreach (time-intensive, low conversion)
- Waiting for people to find you
Weekly Priorities
Given limited time, allocate roughly:
| Activity | Time | Why |
|---|---|---|
| Support existing users | 20% | They're your best salespeople |
| Content/SEO | 30% | Compounds over time |
| Product improvements | 30% | Keep it good, not perfect |
| Community presence | 20% | Be where customers are |
Content Ideas That Sell
Write about problems, not features:
- "Why I stopped using Google Analytics"
- "Self-hosted analytics for GDPR compliance"
- "How to track [specific use case] without third-party scripts"
- "Analytics for [specific audience]: what you actually need"
When Stuck on Sales
- Talk to users - Email 5 existing customers. Ask what they love, what's missing.
- Look at competitors - Where do they get customers? Copy what works.
- Find 1 community - Go deep in one place instead of shallow everywhere.
- Ship something visible - Changelog, blog post, tweet. Activity attracts attention.
Red Flags
Stop and reassess if you catch yourself:
- Building features no one asked for
- Refactoring code that works
- "Improving" things instead of shipping
- Avoiding customer conversations
- Comparing to funded competitors
The Long Game
This is a marathon, not a sprint. Fusionaly at 100 customers = $10K. At 1000 customers = $100K. At your pace, that might take years. That's fine.
Focus on:
- Making each customer successful
- Building SEO momentum
- Staying consistent, not intense
Ignore:
- Viral launches (they fade)
- Competitor funding news
- "Growth hacking"
Mantras
- "Ship beats perfect"
- "One customer at a time"
- "The product is good enough. The problem is distribution."
- "Coding is comfortable. Sales is necessary."
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です