Selected professional work / Webflow Marketplace
One Marketplace.
Connected work.
Micah’s work across Webflow’s Marketplace connects the tools creators use to prepare and manage their work with the systems reviewers use to evaluate it.
Selected professional work by Micah Johnson for Webflow, presented as individual portfolio work. Webflow did not commission this work through CREATE SOMETHING. Individual contributions are described within a wider team and platform context.
- Contribution
- Product development, workflow design, integration engineering, reusable review guidance
- Story
- Eight studies · Five stages · A 2:48 walkthrough
- Evidence
- Recorded interfaces, historical footage, and labeled offline replays · October 2026
A compilation of actual captured screens and labeled offline replays. Setup, input and connection prerequisites remain bounded demonstrations, not full production acceptance. Individual portfolio work by Micah Johnson.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
Validator shows setup; Preflight shows connected input paths. Skills is an offline source/static-evaluation replay. No app analysis runs here.
Recorded use / 30-day snapshot
The work behind
the numbers.
4 October–2 November 2026 · UTC
Checked 3 November 2026 · Cloudflare D1A dated view of activity in the tools. Select a measure to inspect what was recorded and what it can establish.
Review toolsRecorded tool calls
Asset DashboardLegacy application
All definitions are available in the counting method below.
What this records
Template Review MCP
Calls to tools that retrieve template review context, run checks, and support review actions.
87 tool failures were recorded within these calls. A tool call is one step in a review, not a completed review.
Cloudflare D1 · tool-invocation records
This count does not establish review quality or final approval.
Read the studyTests, operator activity, repeat visits, and retries are not separated. These counts do not establish unique users, completed reviews, or hours saved.
Counting method and full definitions
The window begins on 4 October 2026 at 00:00 UTC and ends before 3 November 2026 at 00:00 UTC. This is a fixed snapshot, not a live counter.
- Template Review MCP · 9,188 recorded tool calls
- Calls to tools that retrieve template review context, run checks, and support review actions. 87 tool failures were recorded within these calls. A tool call is one step in a review, not a completed review. This count does not establish review quality or final approval.
- App Review MCP · 959 recorded tool calls
- Calls to tools that bring app versions, review context, and submission evidence into the reviewer’s workflow. No tool failures were recorded in this window. Recording is best effort, so that is not a guarantee of perfect reliability. Tool results do not establish review quality or final approval.
- Dashboard loads · 4,042 recorded load events
- Events recorded when the earlier Asset Dashboard loaded. Repeat visits can produce more than one event. These records belong to the legacy application, not the Cloud port or native Creator Hub. A load event does not establish a unique creator or a completed task.
- Asset updates · 251 completion events
- Asset-update completion events recorded by the earlier Asset Dashboard. A completion event is an application event label, not an independent check of the saved business record. Events can be missed or repeated. This count does not describe the Cloud port or native Creator Hub.
Counts come from stored tool-invocation records and legacy Dashboard analytics in Cloudflare D1. Recording is best effort. These records are separate from the historical footage and offline replays. They do not establish revenue or a measured improvement over an earlier process.
The challenge
The handoff is part of the product.
A Marketplace experience extends far beyond a listing page. A creator needs to understand the requirements, prepare an asset, submit it, respond to feedback, and maintain the listing. Reviewers need the right version, reliable evidence, and clear authority to act. When those steps live in separate tools, people have to reconstruct the workflow themselves.
Micah’s work addresses those handoffs across creator tools, submission flows, review tooling, the creator workspace, and the public Apps Marketplace. The individual studies describe the contribution within Webflow’s wider team and platform context.
The review tools use the Model Context Protocol (MCP) to give an AI assistant structured access to review information.
Explore the work
Eight connected studies.
01Asset Dashboard
A workspace for the work after submission
Validator App
Make template requirements actionable in Designer
Preflight App
Give app review evidence a clear origin
webflow.com/apps
Improve discovery and operation inside the Apps Marketplace
Submission forms
Make intake confirm what happened
Template/App Review MCP
Bring review context to the reviewer’s tools
Skills
Turn review experience into reusable preparation
Marketplace listings
Keep creators connected to the listing they are editing
The design decision
Make the evidence clear.
Keep the decision with its owner.
The central design decision was to keep evidence states explicit. A request accepted by a server is different from a confirmed review record. A passing validation run is different from approval. A feature merged behind a flag is different from a broadly released experience.
The creator gets a clearer next action. The reviewer can inspect the version, findings, and context behind a proposed action. An assistant’s access to review information does not grant authority to approve an asset.
What the study establishes
Inspect the work and its limits.
The documented result is a set of connected product surfaces and operational tools, with current implementation evidence and historical examples of deployment and workflow verification. The portfolio demonstrates the breadth of the work and the decisions connecting it. It does not establish a measured increase in revenue, adoption, approval rate, or review speed.
The films show specific interactions. Validator shows setup; Preflight shows connected inputs. The template form remains unsent, and the App form shows its connection prerequisite. Review MCP and skills are offline evidence replays. Dashboard footage is historical. The individual studies keep these distinctions beside each recording.
The recordings document specific product behavior and implementation decisions. They do not establish complete production acceptance.