Phorage Brand and Commerce MVP
Developed a pre-launch photography-goods MVP covering brand concept, physical product production, customer journey, commerce workflows, and administration.
Quick read
The through-line of the work.
Open
The starting question
I wanted to go beyond showing photographs and find out what experience people need when they meet the work as an actual product.
Build
What I checked
Within an MVP scope, I connected the brand concept, physical goods, product browsing, cart, ordering, and the admin flow.
Turn
What changed my view
This was not a screens-only project: looking at the physical products and the operating flow together is how I found what had to be checked before launch.
Close
Where I draw the line
It is not yet a public market response. I describe it only as a limited test with acquaintances and what the MVP taught me.
01 · Start
The question I began with
How can a personal photography concept be translated into a testable product and service experience before public launch?
02 · Material
The data and evidence
03 · Work
How I worked through it
- 01
Define the concept
Developed the brand story and intended customer experience around photography goods.
- 02
Produce a tangible offer
Created physical products rather than limiting validation to interface mockups.
- 03
Build the service flow
Implemented storefront, filtering, product detail, cart, order, and administration workflows.
- 04
Run a limited early test
Shared or sold a limited number of goods to acquaintances before public launch.
04 · Takeaway
What the numbers suggested
A creative product needs both a coherent customer-facing story and workable back-office operations.
The MVP made customer and operator workflows visible before public launch.
Early acquaintance-based activity is useful for learning but is not public traction.
Not claimed
- Does not claim a public launch. It is a pre-release MVP.
- Does not claim traffic, order, or revenue figures. Only small-scale checks with acquaintances.
05 · Use
Where this helps
The project demonstrates service planning, MVP prioritization, physical-digital integration, and the definition of launch hypotheses and metrics.
06 · Boundary
What still needs checking
- •The number and type of goods produced should be documented.
- •Gifts, product tests, and paid acquaintance sales should be separated.
- •Target customer, qualitative feedback, and launch metrics still require definition.
07 · Figures
Tables and figures
MVP customer journey
Verified sourceThe journey follows the currently implemented MVP routes. It does not represent observed public-user behavior, conversion, or launch traction.
Source · Implemented storefront, product, cart, and order routes
Customer-to-operator workflow
Verified sourceThe workflow connects the customer-facing store to order review. It supports implemented service planning, not scaled order handling or verified sales performance.
Source · Current commerce and administration code