Facet

Video equipment sales, rentals & production — early concept exploration

Status: In development · early-stage concept ahead of a full discovery phase

Overview

Facet is a real business currently being built by my friend Noel, an entrepreneur who acquired the domain with the goal of serving video creators through equipment sales, rentals, and production services. The scope and direction of the business are still being defined between us — this page documents my early design thinking, not a finished or validated solution.

My Role

Initial visual and UX exploration, ahead of a formal discovery phase with the founder. I'm using this early stage to test ideas and directions before requirements are locked in.

Context

Video production businesses that combine equipment sales, rentals, and production services typically serve a mixed audience — some visitors are comparing gear to buy, others need something short-term for a shoot, and others want to hire the studio outright. Because Facet's exact business model is still being shaped, my early exploration treats this as an open design question rather than a solved one: how might a single site clearly serve browsing, renting, and booking without those paths competing with each other?

Early Exploration

The current direction leans into bold, high-contrast visuals suited to a creative/production audience — dark backgrounds, warm accent color, and strong typography to signal craft and precision rather than a generic e-commerce feel.

[Insert your Framehaus screenshot(s) here]

This is a starting point for conversation, not a final layout — elements like navigation structure, the rental vs. sales split, and the booking flow are all still open questions I plan to work through with Noel directly.

What's Next

  • A real discovery conversation with the founder to define the actual business model (rental-first, sales-first, production-first, or a blend), target customer, and priorities

  • Competitive research once the business direction is clearer

  • Wireframes and user flows built from real requirements, rather than assumptions

  • Iteration based on Noel's direct feedback as the founder

Reflection

I'm including this project because it's real — a real domain, a real founder, and real stakes — even though the process is still early. I'd rather show honest, in-progress thinking than present assumptions as a finished, validated solution.