FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
Can Tycoon actually hit Product Hunt #1 for us?
Tycoon handles the coordination that's necessary but not sufficient. PH #1 requires genuine product excellence, a supportive community, and a meaningful wave of engaged upvotes in the first 8 hours. Tycoon makes the coordination layer error-free (launch timing, outreach to your network, support flood handling, hourly updates) which is what separates 'could have been #1 if we'd coordinated better' launches from successful ones. The underlying product and community are still your job.
Our launches are mostly internal-feature releases to customers, not PH-style big bangs. Does this workflow apply?
Yes, with channel remix. For customer-only launches, the channels compress: customer email, in-app notification, changelog post, documentation update, support team briefing, maybe a tweet for existing followers. Same orchestration logic applies — you tell AI CEO the release goes Thursday and everything ships coordinated. Skip the PH/HN channels and keep the rest. Some companies do 2-4 internal launches per month using this lighter workflow and a quarterly 'big launch' with the full PH/HN treatment.
What about repositioning launches — not a new feature but a new way to talk about the company?
Tycoon handles those well because the asset production scales across channels from one positioning brief. You provide the new positioning (messaging doc, differentiation, proof points); AI CMO translates it into the full suite of launch assets: new homepage copy, email to customer base, X thread announcing the shift, LinkedIn post, blog post explaining the why, PR outreach to journalists who cover your space. Repositioning launches are actually higher-stakes than feature launches and benefit more from coordinated execution.
Does this work for enterprise launches that require private customer comms?
Yes, with confidentiality controls. Enterprise launches often need pre-briefs to specific customers under NDA before public launch. AI Customer Support handles the pre-brief sequence (scheduling briefing calls, sending confidential FAQs, following up with specific customers for testimonial quotes) in a scoped-private manner. Public assets don't publish until the customer briefings are complete. The orchestration value is actually bigger for enterprise because the dependency chain (briefings → testimonials → customer quotes in launch → public launch) is longer.
How does this handle last-minute changes — we decide Wednesday night we want to delay to Monday?
Tell AI CEO 'push to Monday' and the workflow reschedules. All draft assets stay in queue, scheduled posts get pushed back, email sends get re-timed, affiliate outreach gets a 'heads up, we shifted' update. This is where the coordinated workflow outperforms manual launches — last-minute changes in a manual launch often mean channels desync (email goes Thursday but PH post goes Monday because you forgot to reschedule). Tycoon treats the launch as a coherent object with one schedule.