MyNetstar · Product Requirements v1.1 Interactive

1. Executive summary

Project 720 delivers the next generation of MyNetstar. The proposed December 2026 release is organised around four customer themes: Onboarding and Entry, Family and Location Sharing, SOS and Response, and Commerce and Payments. This document presents the best desired proposition so engineering can assess feasibility, size and cost. Final December inclusion of individual components is a Project 720 scope decision informed by that costing.

The scope is evidence-led. Phase 01 research (387 households) validated the concept at 4.51 of 5 appeal with a price corridor of R150 to R400, and showed that people, not vehicles, are what customers protect first. The largest unmet need is dispatched help reaching a loved one.

MyNetstar sells the existing consumer range in-app. Fitted vehicle products (Netstar Basic, Early Warning, Plus) follow a fitment fulfilment route. STARtag is a vehicle-linked recovery product. STARtag BLE is a separate Bluetooth tag proposition for pets and portable belongings, with its own purchase, delivery, QR activation and pairing journey. Onboarding is deliberately light: both a new customer and a recognised existing customer reach a usable Home quickly, then are prompted to create a Family Circle or add protection rather than being forced through circle creation before entry.

2. Product vision

MyNetstar enables South Africans to protect the people, vehicles and things that matter most through one trusted protection platform.

A household should get into the app quickly, see everyone safe on one map, reach verified help when eligible, and add the protection they need without leaving MyNetstar or the public website. The free family circle makes protection accessible to any household with a phone. Netstar products, from fitted vehicle recovery to STARtag BLE tags for pets and belongings, are bought, fulfilled and managed inside the app.

3. Product objectives

4. Success metrics

Measures are separated by funnel stage rather than combined into one activation number. Numerical values are working targets pending ratification.

Event tracking ships with the release so every measure is available from launch.

5. Scope

Four customer themes carry the December proposition. STARtag BLE is woven through Onboarding and Entry, Commerce and Payments, Assets and the shared map rather than being a fifth theme.

6.1 Onboarding & Entry

Purpose: get any person into MyNetstar quickly, capturing only the minimum needed to establish the account and meet confirmed compliance, then let Home guide the next step. The platform, not the customer, decides the branch after OTP. ▶ Run it in the prototype

Journey A · New customer (light onboarding)

Splash → mobile number → OTP → minimum personal details (first name, surname, email; identity only where genuinely required) → permissions (location, notifications, in customer language, declinable where legally possible) → account created automatically in CRM → Home. From Home, the customer is prompted to create a circle, add something they protect, or explore protection options.

Journey B · Existing customer (recognition)

Splash → mobile number → OTP → account recognised → confirm identity → existing estate loaded → Home. No re-registration. Nothing already held is re-asked unless it needs confirmation or correction. A circle is prompted from Home if none exists.

6.2 Family & Location Sharing

Purpose: a free, private circle with a live shared map. Circle creation is prompted from Home, not forced in onboarding. The map carries people, vehicles and STARtag BLE items with distinct visual treatment and accurate status language for each. ▶ Create a circle · ▶ Open the map

6.3 SOS & Response

Purpose: one tap reaches verified armed and medical response for eligible members. SOS is delivered through Netstar Companion, a standalone response membership that is a product in its own right, not part of the vehicle packages. ▶ Open Safety and hold SOS. The entitlement toggle demonstrates configurable states.

6.4 Commerce & Payments

Purpose: sell and fulfil the range in-app with product-appropriate routes. Fitted vehicle products follow a fitment route with in-app slot selection where operationally possible. STARtag BLE follows a delivery and QR-activation route. The meeting favoured customer self-service over routing every sale through a consultant. ▶ Run the buy flow

A · Fitted vehicle products

Examples: Netstar Basic, Netstar Early Warning, Netstar Plus. Desired route: choose product → vehicle details → verified quote → payment method → fitment address → choose home (mobile fitment) or fitment centre → calendar scheduler: pick a date and time slot → confirm with WhatsApp booking, reminders and technician details → confirm order → fitment tracking → successful fitment → subscription activation and billing.

B · STARtag BLE

STARtag BLE requires no fitment. Route: choose STARtag BLE → item or use-case selection → quantity → delivery details → payment → fulfilment → delivery tracking → QR activation → active. See Section 6.5 for the full journey.

C · Assisted-completion products

Where a product genuinely cannot yet complete fully in-app, the app captures the lead and all available information, confirms exactly what happens next, shows the assigned order state, preserves progress and states an expected response period. Generic “someone will call you” wording without status or accountability is not used.

Payment

6.5 STARtag BLE journey

STARtag BLE is the Bluetooth tag proposition for pets and portable belongings: a pet, keys, bag, bicycle, laptop, luggage or another valuable item. It is a distinct product from STARtag, the vehicle-linked recovery product. STARtag BLE has its own purchase, delivery, pairing and activation journey. ▶ Run the STARtag BLE flow

Purchase and fulfilment

Home or Assets → Add something you protect → STARtag BLE → choose item type → quantity and pricing → delivery details → payment method → order confirmation → delivery tracking → delivered → activate. Item types may include pet, keys, bag, bicycle, laptop, luggage or other valuable item; category availability is configuration and some categories require commercial confirmation. Fulfilment is via an approved logistics provider (integration is a dependency, not hard-coded here). Order states: order placed, preparing for dispatch, dispatched, out for delivery, delivered, ready to activate, activated. No state claims the item is protected before activation.

QR activation and pairing

After delivery: open the STARtag BLE activation journey → scan the QR code on the packaging or device → validate the device identifier → follow physical activation instructions → pair the device to the account → select what the tag protects → name the item → optionally upload a photo (subject to feasibility) → select or create an owner → select the family circle or sharing settings → confirm permissions and privacy → see the item in Assets and on the map. Manual code entry and a support route are provided if the QR cannot be scanned.

6.6 Assets experience

Purpose: Assets represents the full estate, not a shop. It shows existing vehicles and vehicle products, STARtag vehicle products, STARtag BLE devices, and items in progress, with acquisition available as one action within managing the estate. ▶ Open Assets

Acquisition options: add a vehicle, add vehicle protection, buy STARtag BLE, activate a delivered STARtag BLE, add another protected item. STARtag BLE detail shows name, photo, item type, owner, assigned circle, last seen, connection or proximity state, battery where supported, activation date, device identifier, sharing controls, mark-as-lost where supported, remove or transfer, and support. Vehicle telematics fields are not shown on a STARtag BLE item.

6.7 Settings

The burger menu carries the settings surface required by the journeys. Vehicle products and STARtag BLE devices are listed separately, never as an ambiguous “Linked STARtags”. ▶ Open Settings

7. User journeys

8. Assumptions, dependencies and decisions required

Commercial decisions

SOS entitlement and pricing; product qualification rules for SOS; STARtag BLE pricing and subscription model and its billing trigger; the approved product catalogue and rate card; whether STARtag BLE is in the December release or sequenced shortly after; product and category availability.

Operational dependencies

Fitment scheduling accuracy; fitment-centre and mobile-technician capacity; assisted-sale fallback ownership; logistics fulfilment and delivery tracking; customer-support ownership; recovery support for STARtag BLE items.

Technical dependencies

CRM account creation; existing-customer recognition; automatic asset linking; product catalogue integration; payment tokenisation; scheduler integration; logistics-provider integration; QR activation service; BLE pairing and device status; image storage and retrieval; map support for people, vehicles and BLE assets; event tracking; notification channels; POPIA consent and data handling.

Governance decisions

The final December cut; best-case scope versus engineering-feasible scope; which capabilities may release in January or February if they do not fit December; the authoritative decision-makers for scope and entitlement. The transcript records a chicken-and-egg: the business case needs scope, scope needs the business case. The approach is to present the best-desired scope, have engineering size and cost it, then cut by effort.

9. Out of scope

STARtag BLE is included in the best-case requirements for engineering sizing and commercial prioritisation. Its final December inclusion remains subject to scope, cost and feasibility approval, and it may be sequenced to a January or February launch if it does not fit December.

Minimum STARtag BLE journey (in scope for sizing): purchase, delivery tracking, QR activation, asset creation and map visibility. Future STARtag BLE functionality (out of scope): advanced community finding, sophisticated lost mode, extended recovery networks, automation, analytics, multiple accessory types and other capabilities not yet approved.

Also out of scope for this release: deeper self-service and servicing beyond the journeys above, the full notification centre, adjacent propositions, behaviour-driven personalisation, insurance and driver-behaviour propositions, and scam protection (pursued as a partner evaluation). Vehicle and Telematics is the existing product; customers continue on current functionality and only the integration points required by the four themes are in scope.