The CLI for solo technical founders shipping weekly
Define · Develop · Deliver · Feedback · Iterate
LoopKit is a command-line tool that helps solo technical founders ship every week. It closes one lightweight loop — define the bet, build against it, ship, collect feedback, and decide the next move.
If you've ever:
- Started a project and abandoned it at 80%
- Built something nobody wanted
- Felt overwhelmed by scattered tools (Notion, Trello, Twitter, email)
- Struggled to write launch copy
- Lost track of what to work on next
...LoopKit is for you if you live in git and want a weekly shipping habit.
LoopKit is built on one belief: Shipping is a skill, not a talent. And like any skill, it improves with practice and a system.
Most founders fail not because they can't code, but because they:
- Don't validate before building
- Don't ship consistently
- Don't learn from feedback
- Don't iterate based on what they learned
LoopKit forces you to do all four, every single week.
Every successful product follows this loop. LoopKit makes it explicit and automatic.
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ DEFINE │ → │ DEVELOP │ → │ DELIVER │ → │ LEARN │ → │ ITERATE │
│ (init) │ │ (track) │ │ (ship) │ │ (pulse) │ │ (loop) │
└─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘
↑___________________________________________________________|
Question: What should I build?
Before you write a single line of code, LoopKit forces you to answer 5 questions:
- What are you building? (one-liner)
- What problem does it solve? (be specific)
- Who is your ideal customer? (the narrower, the better)
- Why hasn't this been solved? (your insight)
- What's your MVP? (the smallest version that delivers value)
An AI then scores your answers on three dimensions:
- ICP Clarity (1-10): Do you really know who you're building for?
- Problem Strength (1-10): Is this a real, painful problem?
- MVP Focus (1-10): Is your MVP small enough to ship this month?
Why this matters: Most founders build for "everyone" with a "solution looking for a problem." This step prevents that.
Output: A brief.md file with your uncomfortable truth, bet, scores, riskiest assumption, and a validation plan.
Time: Under 5 minutes for first value
Question: Am I making progress?
LoopKit replaces your scattered task manager with a simple tasks.md file:
# MyProject — Tasks
## This Week
- [ ] #1 Set up landing page
- [ ] #2 Configure Stripe
- [ ] #3 Implement auth
## Backlog
- [ ] #4 Add dark mode
- [ ] #5 Write API docsMagic features:
- Auto-close via git: Write
[#1]in your commit message → task automatically marks as done - Shipping score: Done tasks / Total tasks × 100. Aim for > 70%.
- Score delta: Compare your shipping score to last week (e.g.
↑+12%or↓-8%) for a daily progress anchor. - Daily Standup: Run
loopkit track --standto log your #1 focus for the day and build daily momentum. - Stale task detection: Tasks open for 3+ days get flagged. Keep, snooze, or cut them.
- Smart Benchmarks: Compares your performance against the network, unlocking after you reach 4 weeks of data.
- Never deleted: Cut tasks move to
cut.md— you might want them later.
Why this matters: Visibility creates accountability. A 60% shipping score is a data point, not a feeling.
Output: A clear board showing what's done, what's open, and your momentum.
Time: 30 seconds to check, 10 seconds to add a task
Question: How do I tell the world?
Shipping isn't just deploying code. It's announcing it to the right people on the right platforms.
LoopKit asks: "What did you ship?" Then AI generates:
- Hacker News: Title + body (no hype, developer tone)
- Twitter: 3-tweet thread (build in public style, with character count warnings)
- Indie Hackers: Narrative post (story-driven)
You can use, edit, regenerate, or skip each draft. After reviewing the drafts, you run through a pre-launch checklist to ensure you updated your README, landing page, analytics, and feedback form.
Why this matters: Writing launch copy takes 1-2 hours. LoopKit does it in 30 seconds. The faster you launch, the faster you learn. By generating the drafts first, you get immediate value before doing the housekeeping tasks.
Output: Published posts + a ship log saved for your records.
Time: 5-10 minutes
Question: What do my users think?
Most founders build in a vacuum. LoopKit makes feedback collection automatic.
Two ways to collect:
- Inline:
loopkit pulse --add "User said the pricing is confusing"(automatically deduplicates) - Shareable form:
loopkit pulse --share→ get a URL + QR code → embed on your site (widget outputs your actualprojectId)
Once you have 5+ responses, AI clusters them into:
- Fix now (critical issues)
- Validate later (ideas to explore)
- Noise (outliers and off-topic feedback)
Why this matters: 12 random DMs become 3 clear priorities. Data beats intuition.
Output: Clustered feedback with representative quotes (never invented).
Time: 2 minutes to set up, 10 seconds to analyze
Question: What should I do next week?
Every Sunday, LoopKit synthesizes your week:
- Tasks completed vs. planned
- What you shipped
- Feedback received
- Your shipping streak
- Proof this week: score delta, weeks active, decisions made, and feedback acted on
- Revenue: Include MRR updates inline via
loopkit loop --revenue <amount>
Then AI names What Moved Forward and recommends The One Thing to focus on next week, following this priority:
- Fix now (critical user issues)
- Ship (finish what's almost done)
- Validate (test your riskiest assumption)
- Next task (whatever's next in your plan)
You can accept it, change it, or skip it. Your choice is recorded.
Why this matters: The hardest part of every week is deciding what to work on. LoopKit decides for you — based on data, not mood.
Output: A proof loop, a loop log, a next-week priority, a build-in-public post you can share, and a beautiful ASCII Proof Card that auto-copies to your clipboard for easy tweeting.
Time: 2 minutes
loopkit init my-project
# Answer the 5 questions
# Get your scored briefloopkit track --add "Set up landing page"
# Work, commit with [#1], task auto-closes
loopkit track # Check your progressloopkit ship
# "What did you ship?" → "Landing page with email capture"
# Use AI-generated drafts to announceloopkit pulse --share
# Share the link in communities
# Collect responsesloopkit loop
# Review your week
# Accept the AI's recommendation
# Share your BIP postRepeat every week.
Your shipping score is done tasks / total tasks × 100.
| Score | Meaning |
|---|---|
| 90-100% | Crushing it |
| 70-89% | On track |
| 50-69% | Falling behind — cut or snooze tasks |
| < 50% | Stuck — loopkit loop will help |
Don't aim for 100% every week. That's a recipe for burnout. Aim for consistency (70%+).
Beyond the base shipping score, LoopKit calculates your overall LoopKit Score (0-100). This aggregates your shipping consistency, your active week streak (bonus multiplier), and your feedback responsiveness (pulse bonus). A high LoopKit Score means you are excelling across all vectors of building, shipping, and learning.
LoopKit is the single source of truth for your founder journey. Log your structured revenue entries directly via:
loopkit revenue --add "12/mo Stripe"Or when closing your loop on Sunday:
loopkit loop --revenue 240Consecutive weeks where you run loopkit loop and close your synthesis.
If you miss a week, your streak resets, but you get a gentle acknowledgment to help you start a new streak today. A 4-week streak means you've shipped and reflected for a month straight. This is the #1 predictor of eventual success.
Sometimes you'll disagree with the AI's recommendation. That's fine — override it and record your reason.
But if you're overriding > 50% of the time for a month, ask yourself: Is the system wrong, or am I avoiding hard truths?
- Cut: "This task is no longer relevant." (Saved to
cut.mdforever) - Snooze: "I'll do this later." (Hidden until the date you pick)
Rule of thumb: If a task is stale for 3 days, cut it. If it's important, it will come back.
- Run
loopkit loopevery Sunday at the same time. Make it a ritual. LoopKit will even provide a cron reminder hint after you initialize a project. - Set a calendar reminder. "Sunday 9 AM — LoopKit Loop"
- Share your BIP post every week. Public commitment = accountability.
- Break tasks into < 2 hour chunks. Small tasks get done. Big tasks linger.
- Front-load your week. Do hard tasks Monday-Tuesday. Momentum carries you.
- Use the
--addflag constantly. Ideas become tasks in 10 seconds.
- Share your pulse link in 3 places minimum. One community isn't enough.
- Ask specific questions. "What confused you?" gets better answers than "What do you think?"
- Respond to feedback publicly. "Thanks for the feedback, fixing this week!" builds loyalty.
- Spend 5 extra minutes on the ICP question. The narrower, the better. "Dentists in Texas" beats "healthcare professionals."
- If your problem score is < 6, interview 5 potential users before building.
- If your MVP score is < 6, cut features until it hurts.
Once you opt into telemetry (loopkit telemetry on), LoopKit can unlock market intelligence features. These are secondary add-ons; the five-command weekly loop is the core product.
After you run loopkit init, LoopKit analyzes your ICP, problem, and MVP category. If other founders are exploring similar spaces, you'll see a hint:
Trending Validation
5 other founders are exploring similar ICP spaces this month.
Run `loopkit radar` to see recent launches in your category.
View full trends on your dashboard at /dashboard/trends — ranked lists of top ICPs, problems, and MVP types across all opted-in founders.
Scan Product Hunt and Hacker News for recent launches in your category:
loopkit radarLoopKit auto-detects your project's category from your brief and searches for relevant launches. Results show:
- Launch name, tagline, and URL
- Platform (Product Hunt or Hacker News)
- Relevance score (0-100%)
- How recent the launch is
You can also scan any category:
loopkit radar --category "ecommerce"Results are cached for 24 hours. No API keys required.
View competitor radar on your dashboard at /dashboard/radar — a full page with sortable/filterable launch table, platform badges, relevance scores, "this week" stats, and average relevance across all tracked launches.
Track funding rounds, developer activity, and hiring in your category:
loopkit timingLoopKit auto-detects your project's category and analyzes:
- Funding velocity — recent funding rounds in your space (↑ ↓ → trend)
- Developer activity — GitHub repo growth and star counts (↑ ↓ → trend)
- Hiring demand — job postings in your category (↑ ↓ → trend)
- Composite score — 0-100 score with signal label (heating / stable / cooling)
You can also scan any category:
loopkit timing --category "ecommerce"Results are cached for 7 days. No API keys required.
View market timing on your dashboard at /dashboard/timing — a full page with composite score hero card, signal breakdowns with sparklines, history chart, and interpretation guide with actionable recommendations.
Find low-competition keywords in your niche for content strategy:
loopkit keywordsLoopKit scans free SEO data sources (Google Autocomplete, Reddit, GitHub) and returns:
- Keyword score (0-100) — higher = better opportunity
- Search volume estimate (high/medium/low)
- Competition level (low/medium/high)
- Related search suggestions
Results are sorted by score. "Low-hanging fruit" keywords (low competition, decent volume) are highlighted at the top.
$ loopkit keywords
Found 12 keyword opportunities.
3 low-hanging fruit
Keyword Score Volume Competition
──────────────────────────────────────────────────────────────────────
saas metrics dashboard 82 ███ high low
→ saas metrics dashboard template, saas metrics dashboard examples
solo founder tools 75 ██░ medium low
indie hacker analytics 68 ██░ medium mediumYou can also scan any category:
loopkit keywords --category "ecommerce"Results are cached for 7 days. No API keys required.
Detects recurring failure patterns from your local history and surfaces them with actionable suggestions during your Sunday loop.
When it appears: After 4+ weeks of data, if any of these patterns are detected:
| Pattern | What it means |
|---|---|
| Overplanner | You plan 8+ tasks but consistently finish <30% |
| Snooze Loop | You keep snoozing or leaving the same tasks open |
| Ship Avoider | 3+ weeks with no ship + low score |
| ICP Drift | Score declining + feedback says wrong problem |
| Scope Creep | Adding tasks mid-week repeatedly |
Example:
$ loopkit loop
⚡ Pattern Interrupt — 5 weeks of data
📋 OVERPLANNER (3 weeks)
You plan 8+ tasks but finish ~25% of them.
→ Plan 3 must-do tasks per week. Everything else goes to backlog.
→ If a task has been open 2+ weeks, cut it or ship it.After you ship, see what anonymized founders in your category shipped this week.
Example:
$ loopkit ship
🚀 Peer Inspiration — This week in saas:
• "Stripe billing portal integration"
• "Webhook retry logic with exponential backoff"
• "Public API docs with Swagger"
You're not alone. Keep shipping.Only appears if telemetry is opted in. No usernames or identifying details — category and ship description only.
Your personal shipping coach that analyzes your patterns and tells you exactly what to do next.
loopkit coach # Full coaching plan
loopkit coach --off # Disable
loopkit coach --on # Re-enableWhen coaching appears:
- After
loopkit loop— one priority moment based on your current state - After
loopkit track— when you're stuck with 0 tasks - During
loopkit ship— if you're avoiding shipping - Dashboard —
CoachingWidgeton overview page
Example moments:
🚨 Critical: Ship Avoider Detected
You haven't shipped in 4 weeks. Building without shipping is just inventory.
→ Ship anything this week — even if it's imperfect.
Run: loopkit ship
💡 Week 3 Milestone
You've been validating for 3 weeks. 73% of founders who ship by week 4 reach revenue.
→ Make this the week you ship something public.
Run: loopkit ship
Coaching respects your attention: max 1 moment per command, never the same moment twice in a row, and critical moments are never silenced.
Skip the blank page. Start with a pre-scaffolded task list matched to your project type — then let AI personalize it to your specific idea.
loopkit init my-saas --template saas
loopkit init my-app --template mobileAvailable templates:
| Template | Best For |
|---|---|
saas |
Subscription B2B/B2C software |
api |
Developer-facing services |
mobile |
iOS/Android apps |
cli |
Terminal tools |
newsletter |
Curated content products |
agency |
Client service businesses |
open-source |
Public libraries/frameworks |
marketplace |
Two-sided platforms |
ai-wrapper |
LLM-powered interfaces |
Templates pre-fill:
- ICP hint in the
initprompt placeholder - Tasks.md scaffold with 5-10 AI-personalized tasks in your backlog
When you select a template, AI reads your answers (problem, ICP, MVP) and personalizes the task list — rewording tasks to match your domain, removing irrelevant ones, and adding up to 2 project-specific tasks. If AI is unavailable, the hardcoded template tasks are used as a fallback.
You can also select interactively:
loopkit init my-project
# → Use a project template? Yes
# → Choose a template: [select from list]LoopKit's intelligence features require opt-in telemetry:
loopkit telemetry on # Enable anonymous data sharing
loopkit telemetry off # Disable
loopkit telemetry status # Check current status
loopkit telemetry export # Download all your data
loopkit telemetry delete # Delete all server-side dataWhat's collected (when opted in):
- Anonymized ICP, problem, and MVP categories from your brief
- Aggregate usage patterns (which commands you run, not what you type)
- Shipping scores and streak lengths
What's NEVER collected:
- Project names, task content, or brief text
- API keys or personal identifiers
- Raw feedback responses
All raw data stays in .loopkit/ on your machine. Server-side data is aggregated and anonymized.
| Plan | Cost | AI | Best For |
|---|---|---|---|
| Free | $0 | 10 calls/day | Trying LoopKit, side projects |
| Solo | $19/mo | 100 calls/day | Serious solo founders |
| Pro | $39/mo | Unlimited + BYOK | Power users, multiple projects |
Free tier includes: All commands, local storage, basic AI, dashboard read-only.
Paid tiers add: Unlimited AI, hosted feedback forms, dashboard full access, team features (coming soon).
Q: Do I need to be technical to use LoopKit?
A: You need to be comfortable with the command line. If you can run npm install and git commit, you can use LoopKit.
Q: What if I have multiple projects?
A: loopkit track --project other-project switches contexts. Each project has its own brief, tasks, and history.
Q: Can I use LoopKit with my existing tools?
A: Yes. LoopKit writes to standard files (tasks.md, brief.md) that you can edit manually. It complements, not replaces, your IDE and git workflow.
Q: What happens to my data?
A: Everything is stored locally in .loopkit/ by default. Feedback forms use Convex for real-time collection. If you authenticate with loopkit auth, your loop logs and ship logs optionally sync to your web dashboard so you can view trends and benchmarks. Local data remains the source of truth — sync is best-effort and never required.
Q: Does LoopKit work offline?
A: Mostly. init, track, and loop work fully offline. ship and pulse need internet for AI features, but your work is saved locally.
Q: What if the AI gives bad advice? A: Override it. The AI is a partner, not a boss. But if you find yourself overriding every week, consider whether you're avoiding hard truths.
"The goal is not to build a perfect product. The goal is to build, learn, and iterate faster than anyone else."
LoopKit is not a todo app. It's not a project manager. It's a weekly shipping loop.
The difference:
- A todo app helps you organize work.
- A shipping system forces you to finish work, learn from it, and do better next week.
Your job is not to write code. Your job is to ship value to users.
LoopKit keeps you honest about that.
- Documentation: https://loopkit.dev/docs
- GitHub: https://github.com/loopkit/loopkit
- Twitter: https://twitter.com/loopkit
- Email: support@loopkit.dev
Last updated: April 2026 · v0.1.0 (IE-7 through IE-17 shipped · Pattern Interrupt + Peer Inspiration + Keywords + Timing + Radar + Trending + AI Coach all complete · P0 launch blockers resolved)