Hub drive or mid-drive for a city e-bike programme

Start with the decisions that change the programme

A reliable programme does not begin with a long list of components. It begins with the market, intended use, sales channel, expected volume and the level of change required from a proven base platform.

These decisions determine which architecture is realistic, what must be validated, which documents are required and whether the commercial framework can support the intended launch.

Define the operating brief

• Destination market and intended vehicle category
• Use case, rider profile and expected operating conditions
• Target volume, launch timing and commercial price position
• Brand, component, packaging and digital requirements

Ask for evidence, not broad capability claims

Once the brief is clear, compare suppliers through the evidence they can connect to the actual programme. A factory image or certificate list is useful only when it is tied to the selected product, production route and destination market.

Every important statement should lead to a specification, test record, controlled document or named programme responsibility.

Keep component selection on the customization page, commercial timing in the development process, validation evidence in engineering, and origin or delivery questions in the production-route discussion.

Turn the discussion into a reviewable brief

The next useful step is a short document that records the assumptions behind the enquiry. It does not need to be final, but it should be specific enough for engineering and commercial teams to identify gaps before a quotation is treated as comparable.

1. Choose the closest proven platform.
2. List only the changes needed for the market or brand.
3. Identify the applicable validation and certification path.
4. Confirm sample, approval and production responsibilities.