Capabilities
What has to happento a product.
Every physical product passes through the same four kinds of work before it exists in someone’s hands. Not four services bought separately — four things that have to be true, and that have to stay connected to each other.
- 01
- Develop — Idea
- 02
- Prototype — Defined form
- 03
- Produce — Production object
- 04
- Deliver — Packaged product
How to read this page
Claim less.Show more.
A capability list is easy to write and proves nothing. What follows describes the work a product actually requires, and what Phoenix Rising can show of it. Where something depends on the specific product, this page says so instead of inventing a general answer.
Four families
Develop. Prototype.Produce. Deliver.
One product, four states of being real. Each family is a kind of work the product passes through — not a service sold separately from the others.
01Idea
Develop
Define what needs to exist.
Before anything can be designed, someone has to decide what the product actually has to do — for the person buying it, and for the people who will have to build it. Most of what goes wrong later is decided, or left undecided, here.
Product definition
What the product is, who it is for and what it has to do — settled before anything is styled around it.
Requirements
The intent restated as things that can be checked rather than argued about later.
Intended customer and use
Where the product will be used, by whom, and under what conditions it has to keep working.
Design direction
The form the product takes, chosen against its constraints rather than ahead of them.
Development planning
What has to be resolved, in what order, and what each step is meant to answer.
Technical questions
The things nobody yet knows — named early, while there is still time for the answers to matter.
Materials considerations
What the product could be made from, and what each choice commits it to downstream.
Manufacturing considerations
How the product would be made, brought into the conversation while the design can still absorb it.
Commercial constraints
What it has to cost, when it has to exist, and what volume it is meant to reach.
Engineering questions — structure, fit, how a part behaves in use, whether it can be made the way the design assumes — belong in this stage, because naming them early is what makes them answerable at all. Which of them a given product needs, and who answers them, is agreed per project rather than listed here as a standing service.
Explore your idea02Defined form
Prototype
Make the idea testable.
A prototype is not a smaller version of the product. It is an instrument built to answer a specific question, and the question decides how it is made, what it is made from, and how much it is worth spending on.
Concept
Does this make sense as an object at all? Size, form, layout, and how it reads in a hand.
Function
Does it do what it is supposed to do, under the conditions it will actually meet?
Production direction
Could this be made repeatedly? Fit, assembly and the decisions production will depend on.
Form
Proportion and presence, which arguments about renderings rarely settle.
Use
What happens when a real person handles it without being told how.
Materials
How a chosen material behaves once it is a part rather than a specification.
Assembly
Whether the parts go together in an order someone can repeat.
No single prototype answers all of these. One built to test how a product feels in the hand will not tell you whether it can be assembled on a line, and one built to prove assembly will not tell you whether anyone wants it. Asking a prototype for more than it was built for is how confidence gets misplaced.
Continue development03Production object
Produce
Turn definition into repeatability.
Making one is a different problem from making the same thing again. Production is the work of turning a resolved design into a process that produces the same result without anyone standing over it.
Production requirements
What has to be true of the product, the parts and the process before a run can begin.
Factory communication
Keeping the intent of the design intact in the conversation with the people building it.
Production planning
Sequence, dependencies, and what has to be decided before anything is committed.
Repeatability
The difference between one good batch and a process that produces good batches.
Quality criteria
What “acceptable” means, written down while it can still be discussed rather than disputed.
Packaging requirements
How the product is protected, presented and handled once it physically exists.
Production changes
What happens when something has to change after a process is already running.
Volume considerations
How quantity moves every other decision — process, cost and risk all travel with it.
Tooling is the point where a design stops being adjustable, which is why it is treated as a decision rather than a step. What tooling a product needs, what a run costs, how long it takes and which manufacturing arrangements apply all depend on the specific product — so none of it is published here as a general answer.
Discuss production04Packaged product
Deliver
The product still has to arrive.
A finished product is not a delivered one. What happens after production shapes decisions made long before it — and a product that cannot survive the journey was not finished in the first place.
Packaging
Protection and presentation, decided against how the product will actually travel.
Handling
What the product has to survive between the line and the person who opens it.
Destination requirements
What a market expects of a product arriving in it, which is rarely only a label.
Delivery planning
When things have to exist, and what that means for every decision upstream.
Repeat orders
What changes, and what must not, the second and tenth time a product is made.
Changes over time
Products and their requirements both move. Neither stays finished.
This is about how delivery requirements shape product and packaging decisions. Phoenix Rising is not a freight forwarder or a logistics company, and which delivery functions a given project involves — and who performs them — is agreed per project rather than claimed here.
Any stage.Let's build it.
Whether you have an idea, a prototype or a product ready for production, the right starting point depends on where your project is today. Tell us where you are.