Six months for a white-label support platform is solid — the scope you're describing (ticketing, automation, embeddable, tokenized access) is way more than most side projects take on.
The decision to embed support inside the product rather than redirect to a helpdesk is the right call for most SaaS. Context switching kills the support experience and makes the product feel less polished.
What's your current approach to onboarding new SaaS founders onto Vickrt? And have you considered positioning specifically toward bootstrapped/indie founders who can't justify Intercom pricing?
🚀 Entrepreneur · Developer (Next.js / React / Golang) I design and develop fast, scalable, and production-ready web applications for startups and growing companies. 📩
Appreciate that yeah the scope got bigger than expected once I started thinking beyond just “basic ticketing”.
On onboarding, I’m trying to keep it as frictionless as possible: the idea is that a founder can plug Vicket into their product in ~10 minutes with an API key and a prebuilt component, then customize progressively (templates, workflows, etc.) only if they need it. I’m also leaning toward good defaults so you’re not forced into a long setup phase like most tools.
And yeah, the indie/bootstrapped angle is 100% something I’m considering. A big part of why I started this is exactly that, most tools either get expensive fast or feel overkill early on. So positioning Vicket as something lightweight, embeddable, and predictable in pricing for smaller SaaS makes a lot of sense.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Six months for a white-label support platform is solid — the scope you're describing (ticketing, automation, embeddable, tokenized access) is way more than most side projects take on.
The decision to embed support inside the product rather than redirect to a helpdesk is the right call for most SaaS. Context switching kills the support experience and makes the product feel less polished.
What's your current approach to onboarding new SaaS founders onto Vickrt? And have you considered positioning specifically toward bootstrapped/indie founders who can't justify Intercom pricing?
Appreciate that yeah the scope got bigger than expected once I started thinking beyond just “basic ticketing”.
On onboarding, I’m trying to keep it as frictionless as possible: the idea is that a founder can plug Vicket into their product in ~10 minutes with an API key and a prebuilt component, then customize progressively (templates, workflows, etc.) only if they need it. I’m also leaning toward good defaults so you’re not forced into a long setup phase like most tools.
And yeah, the indie/bootstrapped angle is 100% something I’m considering. A big part of why I started this is exactly that, most tools either get expensive fast or feel overkill early on. So positioning Vicket as something lightweight, embeddable, and predictable in pricing for smaller SaaS makes a lot of sense.