KiteHR
The founder reports 184 users after 9 days, but 0 paying customers and 0 signups converted to active use. Most users came from manual sharing, major traffic days averaged 0 seconds of engagement, and the founder concluded they had been building and broadcasting instead of talking to people.
View sourceProduct snapshot
What it was
KiteHR is a free applicant tracking system for startups and small teams that need to manage users, jobs, and candidates without paying upfront.
Who it was for
Problem / value
The product offers unlimited users, jobs, and candidates for free, with a paid Pro plan for AI features such as resume parsing, candidate scoring, and interview question generation.
Core workflow
Track candidates and jobs; Let small teams use an ATS without a credit card; Add AI resume parsing and candidate scoring through a paid plan
Core dependency
The founder reported 167 of 184 users came from manual link sharing and 13 from organic search.
Product form
Pricing model
Founder-reported model is free unlimited ATS access, with Pro at $49/month for AI features.
Competitors or alternatives
What happened
Summary
The founder described KiteHR as a free unlimited ATS for startups and small teams, with unlimited users, jobs, and candidates.
Outcome
KiteHR shows a free unlimited SaaS launch that generated signups but not active use or paid conversion.
Core risk
Free Unlimited Saas Produced Signups Without Activation Or Paid Demand.
Timeline
- Founder reported launching 9 days before the post
- Founder reported 184 total users
- Founder reported 0 paying customers and 0 signups converted to active use
- Founder reported 167 of 184 users came from manual link sharing
Before you build
Why it matters
This is a clean indie SaaS activation lesson. A free plan can reduce signup friction, but it can also attract curiosity clicks without proving that users understand, trust, or need the product enough to activate.
Primary check
Prove that signups become active HR workflows and paid upgrades before making free unlimited access the main growth bet.
Checklist
- Can you name the first buyer segment and the repeated job they need solved?
- Can you reach that segment without relying on one fragile channel?
- What happens if the platform, API, or data source changes terms or blocks access?
- What evidence would disprove the Free unlimited SaaS produced signups without activation or paid demand. risk?
- Measure active use separately from signups, especially when the product is free.
- Manual link sharing can create traffic that looks like traction while engagement stays at zero.
- A free unlimited plan needs a clear reason to trust it, not only a generous offer.
- For workflow tools like ATS software, concierge onboarding with real hiring teams may teach more than broad posting.
Relevant if
- You are building a similar web app with public-source distribution risk.
- Your product depends on another platform, search channel, API, or third-party data source.
- You need to validate who will repeatedly pay before investing in product polish.
Less relevant if
- You already control a reliable acquisition channel for the exact buyer segment.
- The product is an internal tool with no need for public distribution.
Pre-build tests
- Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
- Ask users to commit to a paid pilot, not only to join a free waitlist.
- Prototype the highest-risk platform or data dependency first and document fallback options.
Transferable lessons
- Measure active use separately from signups, especially when the product is free.
- Manual link sharing can create traffic that looks like traction while engagement stays at zero.
- A free unlimited plan needs a clear reason to trust it, not only a generous offer.
- For workflow tools like ATS software, concierge onboarding with real hiring teams may teach more than broad posting.