This is a role guide, not an installed employee. Tycoon now offers outcome-specific Agents and Agent Teams in Market. Nothing is hired or activated until you choose it.
What your AI UX Writer does
Workflows on autopilot
Pre-ship copy review
Every new feature gets a copy pass before release: button labels, errors, tooltips, empty states. No ship without the pass.
Error message audit
Quarterly review of every error message in the product. Rewrites anything that says 'something went wrong' into specific, actionable copy.
Onboarding flow design
Builds onboarding copy sequence from welcome screen through first-value moment. Tests for completion rate and iterates.
Empty state library
Every empty state in the product has purpose: teach the feature, suggest the next action, or explain why the list is empty in a way that does not blame the user.
Transactional email templates
Maintains clean, branded templates for every automated email: signup confirmation, password reset, invoice, feature announcement.
A/B test copy execution
For high-traffic surfaces (signup page, paywall, upgrade CTA), runs structured A/B tests with sufficient sample size and writes up the learnings.
Without vs With a AI UX Writer
- Error messages say 'Something went wrong, please try again'
- Empty states apologize instead of teaching
- Onboarding is a skipped 3-step tour that teaches nothing
- Transactional emails look like they're from a 2012 phpBB forum
- A human UX writer is a $140K+ hire most small teams cannot justify
- Errors say exactly what failed and what the user should do
- Empty states turn a blank screen into a first action
- Onboarding copy runs alongside action, not in front of it
- Every email is branded, clear, and useful
- AI UX Writer covers the work at the quality of a senior writer
A day in the life of your AI UX Writer
08:30New checkout flow ships tomorrow. Writes copy for 18 states: loading, success, validation errors, payment failures, network timeout. Delivers to Figma.10:30Audits the production error messages. Finds 23 that say 'something went wrong'. Rewrites each with the actual failure and recovery path.12:30Pairs with the brand designer on the new welcome email template. Lands on a 60-word body that explains the first action clearly.14:30Writes the empty state for the new dashboard. Turns a blank screen into three example actions with real links to help.16:00Reviews the A/B test on the upgrade CTA. Variant B ('Upgrade to keep your automations') beats A ('Upgrade Now') by 11.4% with significance.17:30Logs: 18 states copied, 23 errors rewritten, 1 A/B test result published.