Skip to content
All work

Prototype · Solution design

MX Composer Prototype

A working prototype built solo in two weeks and run like a product, from discovery to deploy. Built to test a 50% cut in client goal live times and to move Solution Architects from a sales posture into a partnership.

My role
Solo designer and builder (discovery, PRD, spec, build, and stakeholder share)
When
2025
Tools
Google AI Studio, Claude Code, Vercel

The problem

Client goal live times were too slow, and the Solution Architect role read as transactional, a sales conversation, rather than a collaborative partnership with the client.

Approach

  1. Ran it like a product: discovery, PRD, spec, then build.
  2. Built the prototype from scratch with no engineering oversight, end to end in two weeks.
  3. Scaffolded in Google AI Studio, then migrated the code and iterated with Claude Code.
  4. Deployed to Vercel so the prototype was shareable the same day.
  5. Shared with the Chief of Staff and a lead PM for feedback and to align on the vision.

Outcomes

  • The Chief of Staff offered to help find sponsorship for it.
  • Demonstrated a shift in the SA role, from a sales conversation to a collaborative partnership.
  • The design target was a 50% reduction in client goal live times. That is the projection the prototype was built to test, not a measured result.

Media

MX Prototype Composer home screen: the headline "Build your MX-powered experience in minutes," a prompt-to-prototype entry point, and a footer noting it is an unaffiliated portfolio prototype.
Composer v0.6, the live prototype's entry point.
Email copied: mitchellgdyer@gmail.com