A technically interesting object is not automatically a market-ready object.
That sounds obvious. It was still a lesson I had to pay for in the real world.
By the time the project reached this phase, there was already a lot of serious work behind it: terrain-derived geometry, custom tooling, mold iterations, pour logs, text refinements, process math, and actual candles that looked pretty good. The next step seemed straightforward enough: make the brand legible, get the booth and collateral together, and see what happens when the project leaves the workshop.
What happened was useful, clarifying, and a little painful.
One of the weirder and more interesting things about this project is that branding and commercialization start early.
By late August 2024 there were already:
So this was never a case of “do all the technical work first, then think about customers later.” The customer-facing layer was present early. It just did not become fully decisive until the product had enough shape to test in public.
The downloaded business docs show a pretty serious push here:
Brand Guidelines.docxVolcandles Info Sheets.docxProject Management Materials/Agendas and Meeting Notes.docxMeeting Notes/Vincent _ Bryan #2.docxMeeting Notes/Vincent _ Bryan #3.docxCandle Blurbs.docxThis is not casual doodling. It is a coordinated attempt to make the project presentable and sellable.
The problem in this phase was not just “how do I make the booth look nice?”
The real problem was: how do I explain a terrain-derived, digitally fabricated candle in a way that customers immediately understand and actually care about?
That is a different problem than making the thing.
And it is especially awkward when the internal story is made of:
Customers do not need the full stack trace. Fair enough. But they do need a reason to stop, look, understand, and want the object.
The public-facing documents show the attempted answer.
Brand Guidelines.docx defines typography, palette, and styling. So there was a real effort to build a coherent visual identity instead of just slapping a logo on the thing and calling it a day.
Volcandles Info Sheets.docx frames the work as:
Northwest WaxworksPNW Digital FabricationCandles - Molds - CommissionsThat is a fascinating combination because it is trying to keep the technical novelty visible while also broadening the offer.
Candle Blurbs.docx and the script doc Unforgettable Moments_ Northwest Waxworks.docx push the story toward atmosphere and meaning:
digital topographybespoke codebring a small piece of the Pacific Northwest into your homeThat is a reasonable move. It translates the process into something warmer and more human.
Then the logistics hit:
Last Thursday TODO.docxMarket Plan.mdThis is the practical layer:
That is the point where the project stops being theoretical.
The Bryan meeting notes are especially helpful because they split the work into a pretty honest partnership boundary.
Bryan’s side leans toward:
My side leans toward:
That division makes sense. It also exposes a potential fault line:
If the technical story and the sales story are not tightly coupled, the project can end up impressive on one axis and confusing on the other.
The strongest later note is brutal and useful:
Candles @ public market: not the market
That is the sentence.
There are related notes around it:
Bring the mountain experience to youAnd PROJECTS.md gives the retrospective version:
I do not read that as failure in the big dramatic sense. I read it as expensive clarity.
The market told me something specific:
That is a real lesson. Also a pretty common one, just dressed up here in mountain wax.
This phase changes the project in at least three ways.
Internal logic is no longer enough. Real people in a real setting have to understand the thing.
It is not just geometry, wax, and molds anymore. It is also category fit, booth context, visual punch, and narrative clarity.
The notes after the market are not just disappointed. They are analytical. They ask:
That is useful thinking, even if it arrives wrapped in some frustration.
There is always a tension here.
If I explain the project in the full internal language, it gets too technical and weird. If I explain it only in lifestyle language, I lose the thing that made it interesting to build in the first place.
The whole branding/market phase is an attempt to find a middle ground.
Sometimes it works. Sometimes it gets a little too polished. Sometimes it probably undersells the object. Sometimes it probably oversells the romance.
That is normal. It is what trying looks like.
Even though the market result was not positive, this phase still mattered a lot.
It clarified:
In other words, it made the later pivot possible.
After the first market-facing version of the project stalled out, the interesting question was not whether to keep doing the exact same thing.
The interesting question was: what does the second version look like?
That answer seems to have been some combination of:
Which is, honestly, a pretty good second act.