How Phoenix Works
Step by step. From conversation to transformation.
Discovery Call
A 30-minute conversation. What system are we talking about? What does the team understand about it? What has been tried? What does success look like? No pitch. No slides. We are figuring out whether Phoenix is the right approach for your problem — and being honest if it is not.
Signal Extraction
We gather everything known about your system — documentation, API specs, database schemas, architecture notes, or nothing if nothing exists. From this, A-00 produces the mission brief: a structured document that tells every downstream agent what the system is, what workflows it handles, what it connects to, and what the team already knows. This is the heads-up before the forage begins.
Forage & Extraction
A-01 and A-02 run in sequence. A-01 traces every workflow from its server-side entry point through the call stack to its terminus — producing ASCII flow traces, one per process. A-02 traces the same workflows through the user interface — producing ASCII wireframes, screen by screen. Together these two layers capture what your system does and how your users experience it. Both in plain language. Both permanent.
Synthesis & Architecture
A-03 reads both layers together and produces the semantic intent specs — one per workflow, answering what it was actually trying to accomplish. A-04 reads those specs alongside the mission brief and recommends the modern stack that best fits what the system needs to do and what your company already is. Custom work is flagged explicitly before build begins.
Build & Validate
A-05 builds in six passes — UI shell first, then API layer, data layer, external integrations, background processes, and finally the test suite. You review and sign off between every pass. When the build is complete, A-06 runs four validation stages: unit tests, integration tests, Playwright UI tests, and system load tests. Binary outcome per workflow — certified or returned with a precise gap report. Nothing ships without certification.
Handoff
Assessment clients receive the process catalog, UI traces, intent specs, gap analysis, and executive summary — the documentation their system never had. Blueprint clients receive the stack recommendation and build blueprint on top of that. Full Cycle clients receive everything: production codebase, deployment pipeline, complete test suite, the full EMBER artifact trail, and the certification document. Everything is yours. No lock-in. Clean handoff.
Ready to Start the Conversation?
30 minutes. No pitch. Just clarity about your system and your options.
Book Discovery Call