ProductsArtifactsLive
Get the work, not just the answer.
Documents, code, charts and web pages, written beside the chat and kept as versions. Ask for a change and the result is a new version you can compare and download.
Show 6 unchanged lines
- 77 - Prove that new users complete the core workflow without support.
- 88
- 99 ## Week 1: Lock Core & Stress Test
- 10-- **Focus:** Freeze features, push release candidate, run load and failure drills.
- 11-- **Owners:** Engineering & Product
- 12-- **One metric:** Critical bug count (target: 0 by Wednesday)
- 10+- Freeze features and push the final release candidate by Monday.
- 11+- Run load and failure drills across production infrastructure.
- 12+- **Owner:** Engineering & Product | **Metric:** Critical bugs (target: 0 by Wednesday)
- 1313
- 1414 ## Week 2: Warm the Funnel
- 15-- **Focus:** Send launch teasers, onboard early access users, finalize support playbooks.
- 16-- **Owners:** Growth & Customer Ops
- 17-- **One metric:** Waitlist-to-beta conversion rate (target: 30%)
- 15+- Send launch teasers and onboard the early access cohort.
- 16+- Finalize support playbooks and prepare customer onboarding guides.
- 17+- **Owner:** Growth & Customer Ops | **Metric:** Waitlist-to-beta conversion (target: 30%)
- 1818
- 1919 ## Week 3: Final Polish & Go Live
- 20-- **Focus:** Dry-run launch day messages, monitor pre-launch traffic, flip the switch on 28 October.
- 21-- **Owners:** All hands (Founder leads comms, Engineering on standby)
- 22-- **One metric:** First 48-hour activation rate (target: 40%)
- 20+- Dry-run launch messages and monitor pre-launch traffic patterns.
- 21+- **Owner:** All hands (Founder leads comms) | **Metric:** First 48-hour activation rate (target: 40%)
- 22+- **Rollback trigger:** Revert to the previous stable release if uptime drops below 99% or activation falls under 25% in the first 24 hours.
Rebuilt from a live Cruxy account; every control shown is one Cruxy has today. Try it here. Anything that needs an account takes you to sign in.
How it works
Artifacts, step by step.
- 01
Ask for the work
A plan, a page, a script, a chart. Cruxy writes it in the side panel, beside the conversation.
- 02
Revise by asking
Tell Cruxy what to change. Each revision is saved as a new version; nothing is overwritten.
- 03
Compare and download
Compare versions in the panel and download the one you want.
Today
What it does today. And what it does not do yet, said plainly.
DOES TODAY
- Documents, code, charts and web pages
- Written alongside the conversation, in a side panel
- Every version kept
- Compare versions
- Download the artifact
- On every plan, Free included
NOT YET
- Editing in place: changes come from asking Cruxy, which saves a new version
- Export to PDF, Word, PowerPoint or Excel
- Publishing an artifact as a site
Questions
Good to know.
A document, a piece of code, a chart or a web page that Cruxy generates alongside the conversation. It lives in a side panel with every version kept, ready to download, instead of being buried in a chat scroll.
More of Cruxy