FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
I'm a 1-person technical founder. Do I need incident response workflows at this stage?
Yes, more than at 20 people. At 20 people, you have ops teammates who catch the gaps; at 1 person, a 2am alert means you forget to update the status page, you miss the email to affected users, and the postmortem never gets written. Tycoon's main value for solo founders is being the ops shell while you're deep in diagnosis — the comms layer runs without needing your attention. Most solo technical founders set this up after their first major incident, wishing they'd had it for that one.
What about false-positive alerts — PagerDuty goes off for non-incidents all the time. Does this create noise?
AI CTO learns your false-positive patterns over 2-4 weeks. Alerts that historically resolved in <5 minutes without action get a lower severity (P3) and skip the customer-comms workflow entirely — they still create an incident record for tracking but don't update the status page or draft comms. This dramatically reduces alert fatigue. True incidents get the full workflow; false positives get logged and ignored. Over time, the alert-quality improvements (tuning thresholds, deleting noisy alerts) compound because you're seeing the patterns clearly.
Our customers are enterprise with SLAs. We can't send 'we're working on it' tweets; they need formal RCAs.
Enterprise mode. AI Customer Support drafts customer-account-specific communications: direct email to the customer's primary contact with incident details, impact on their account specifically, and a formal RCA within the SLA window (typically 5 business days). Parallel public comms still run for transparency but the enterprise path is first-priority. For multi-tenant platforms, AI Customer Support identifies which enterprise accounts were affected vs not and only notifies affected ones — no false-positive panic emails.
How does this handle partial outages — some users affected, not all?
Precise targeting. From your logs + error tracking, AI CTO identifies the exact affected cohort (e.g., 'users on Chrome 120+, with checkout feature flag enabled, in us-east-1 region'). Status page updates note the partial impact. Customer comms go only to affected users (not a panic email to your whole list). Comms copy reflects the specific symptom the affected cohort experienced, not generic 'service degradation'. This prevents the common mistake of over-communicating (alarming unaffected users) or under-communicating (affected users feel ignored).
Postmortems are only useful if action items actually get done. Does this track completion?
Yes. Each action item gets a Linear/Jira ticket with owner + deadline auto-created from the postmortem. AI CTO tracks completion and reports in the weekly engineering digest: 'action items from 4 past incidents: 7 closed, 2 in progress, 1 overdue'. Overdue items escalate to you. The compounding effect: teams with this workflow typically see P0 incident frequency drop 40-60% over 6 months because the action items actually ship, not because the team gets magically better at writing code.