#

Key takeaways

• Also says its TM-B Launch Edition e-bike has started moving to a US warehouse.

• Customer deliveries are expected from early August through September.

• The case shows how supply-chain delays can affect hardware timelines.

• For Moroccan teams, it is a useful reminder to plan for procurement, support, and compliance.

• The lesson is broader than bikes: hardware projects need realistic schedules and clear risk controls.

Rivian spinoff Also says its delayed TM-B electric bike has started shipping. The company says the $4,500 TM-B Launch Edition is moving from its manufacturer to a US warehouse. Customer deliveries are expected from early August through September.

That timeline matters because it shows how hardware products can slip even after launch plans are set. For Moroccan readers, the main lesson is not the bike itself. It is the operational risk behind electric mobility products, especially when supply chains are tight.

What the source says

Also was spun out in 2025 with $105 million in backing. The company is also developing cargo and autonomous-delivery vehicles. The source says the TM-B launch was delayed before shipping began.

This is a narrow but useful example. It shows that even well-funded hardware teams can face delays between product announcement and delivery. For Moroccan mobility teams, that gap can affect planning, procurement, and customer expectations.

Why this matters for Morocco

Morocco-centered teams often need to make decisions before a product is fully available. That can include fleet planning, pilot design, service support, and spare-parts strategy. If a product depends on imported hardware, the delivery schedule may shift.

That is why cautious planning matters. A Moroccan buyer or operator would need to test assumptions about lead times, customs handling, after-sales support, and maintenance capacity. If those assumptions are wrong, the project can stall even when the product itself is promising.

Language mix also matters. Technical teams may work across English, French, and Arabic. Documentation, training, and support materials may need to be adapted before any deployment can work smoothly.

Possible use cases in Morocco

The source mentions cargo and autonomous-delivery vehicles, which makes the company relevant beyond consumer bikes. For Moroccan logistics teams, that kind of product could be interesting for last-mile delivery planning. But that is only an assumption based on the product category, not a claim about local adoption.

A Moroccan operator might use a similar product in a controlled pilot. The pilot would need clear routes, defined service windows, and a maintenance plan. It would also need cybersecurity checks if the vehicle depends on connected software.

For public or private mobility teams, the practical question is simple. Can the product be supported locally with the available skills and infrastructure? If not, the project may need a phased rollout.

Risks and governance

Hardware delays are only one risk. Procurement risk is another. A team may budget for a product before delivery dates are stable, then face schedule changes that affect operations.

Privacy and cybersecurity also matter. Connected mobility products can collect operational data. Moroccan policymakers and operators would need to review what data is collected, where it is stored, and who can access it.

Compliance is another issue. Any deployment would need to fit local rules and internal governance. The source does not provide Morocco-specific legal details, so the safe approach is to treat compliance as a project requirement, not an afterthought.

Infrastructure is also a constraint. Electric mobility depends on charging, maintenance, and service planning. If those pieces are weak, the product may not deliver its expected value.

What Moroccan teams should do next

Start with a small pilot. That helps teams test delivery timing, support quality, and maintenance needs before making a larger commitment. It also reduces the risk of buying hardware that arrives late or needs more support than expected.

Build a procurement checklist. It should cover lead times, warranty terms, spare parts, training, and service response. For Moroccan teams, it should also cover language support and documentation quality.

Ask for data and integration details early. If a product uses software, teams should know what data it generates and how it connects to existing systems. That is important for privacy, cybersecurity, and operational control.

Plan for local constraints. Skills, infrastructure, and support capacity can shape whether a product succeeds. A realistic plan should assume delays and include fallback options.

Bottom line

Also's TM-B shipping update is a small product story, but it has a wider lesson. Hardware timelines can move, even after funding and launch plans are in place. For Moroccan mobility teams, the safest response is careful planning, not excitement alone.

The right approach is to test assumptions early. That means checking procurement, support, compliance, and operational fit before scaling. In Morocco, as elsewhere, the best hardware projects are the ones that are designed for real-world constraints from day one.