Onboarding
Before we build,we define.
A productive manufacturing relationship starts with clarity: about the product, about where the work has actually reached, about what needs to happen next — and about whether Phoenix Rising is the right fit to help move it forward.
- Principle
- Clarity before commitment.
- Stages
- Start · Fit review · Define · Onboard · Begin
- Commercial terms
- Agreed per project, not published
What this page is
This explains how Phoenix Rising works, not a system you sign into. There is no account to create, nothing to upload and nothing to pay for here. Starting a project sends nothing automatically — the structured intake prepares a summary in your browser, and reaching Phoenix Rising is still a direct conversation.
Contact Phoenix RisingFit review
First, we determinewhether the work fits.
A structured review of what is known about a project, so both sides can decide what the appropriate next conversation is.
Phoenix Rising reads what is available about the product: where it has reached, what it is meant to do, what the goals are, what the requirements look like and which questions are still open. Some of that usually arrives incomplete, which is normal and is part of what the review is for.
The purpose is not to grade the project. It is to work out whether there is a sensible path forward together, and if there is, what the first part of it should be.
This is a conversation between people, and it depends on what a project needs and what is going on at the time. Phoenix Rising does not publish eligibility criteria, response times or acceptance rates, because none has been set.
What it is not
- A certification or an approval
- An engineering validation of the design
- A formal manufacturing or supplier audit
- A guaranteed feasibility study
- A score, a rating, or an automated decision
The engagement path
From a projectto an engagement.
Five stages between telling us about a product and work starting on it. None of them is automated, and none of them happens without both sides agreeing to it.
01Scattered
Start
Tell us where the project is today.
An idea, a prototype, or a product that needs to be made repeatedly. Where a project has actually reached decides almost everything about what should happen next, so it is the first thing worth establishing.
- An idea
- A design or prototype
- Ready for production
02Grouped
Fit review
First, we determine whether the work fits.
A structured review of what is known about a project, so both sides can decide what the appropriate next conversation is.
- What the product is and what it has to do
- Where the work has reached
- Goals and constraints
- Requirements, as far as they exist
- Open questions and unknowns
A review, not an application. Phoenix Rising does not publish acceptance criteria or response times, and nothing about this step is decided by software.
03Bounded
Define the engagement
Define the work before doing the work.
If there is a fit, the next step is to agree what the engagement actually is. Both sides should understand the shape of the work before any of it begins — including the parts that are still unknown.
- Scope
- Responsibilities on each side
- Known requirements
- Open questions
- Decisions that will need making
- Commercial terms
- Timing
- How communication works
- What information or materials are needed
Commercial terms are part of that conversation and are agreed per project. Nothing about fees, rates, minimums or payment is published on this site, because what an engagement involves depends entirely on the product and the stage it arrives at.
04Organised
Onboard
Get the right information in one place.
Onboarding is the work of preparing a project so it can actually start — gathering what already exists, identifying what does not, and making sure the people who need to decide things are part of the conversation.
- Project brief
- Requirements
- Reference material
- Drawings
- CAD
- Specifications
- Samples
- Existing supplier or manufacturing information
- Who the decision-makers are
- Communication expectations
How that material is exchanged is arranged per project. There is no client portal on this site, and nothing can be uploaded here — this describes the preparation, not a piece of software.
05Resolved
Begin the work
Then the project moves forward.
From here the project joins the development path. Where it joins depends entirely on what already exists — the sequence is a typical shape, not a queue everyone has to start at the front of.
How we develop products
Where a project joins
Nobody startsat the beginning.
Define, develop, prove, produce. A project that already has a working prototype does not go back to defining what the product is, and one that is ready for production does not restart at ideation.
An idea
Define
What the product is has to be settled before anything can be engineered around it.
A design or prototype
Develop
Something exists. The question is what stands between it and something that can be built repeatedly.
Ready for production
Produce
The product is resolved. The work is turning it into a process that repeats.
These are typical entry points, not rules. What a project needs depends on what it already has.
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.