Valor Patent Risk

BYY Strategic Services filed the Valor patent in South Africa and internationally in 2023, and markets Valor as the “world’s first patented voice-activated panic super app.” For any new entrant — including a project building its own voice model — the patent is the single most important legal hurdle, and it must be assessed before commercial launch.

What the patent claim covers (so far as is public)

The claim scope is not yet public in any specific form. BYY’s marketing materials describe Valor as covering:

  • A user-defined custom voice phrase that, when spoken, triggers an emergency dispatch
  • Real-time GPS transmission to a control room on phrase detection
  • Ambient audio monitoring by the control room during the incident
  • Banking fraud notification triggered by the same safety event

What the claims actually recite — wording, dependencies, and whether they are method, system, or apparatus claims — determines what is and is not infringing. Until the application publishes (typically 18 months after the earliest priority date, so likely some time in 2024–2025 depending on filing route), the operational claim scope is not knowable from public sources. A formal patent search via the CIPC patent database, WIPO PATENTSCOPE, and Espacenet is the prerequisite to any meaningful freedom-to-operate (FTO) opinion.

Does building our own model change anything?

No — independent creation is not a defence to patent infringement. This is the most commonly-misunderstood point in the IP-versus-build conversation, and it deserves to be stated plainly:

  • Copyright protects expression, and independent creation is a complete defence.
  • Patents protect claimed inventions, and anyone practising the claims infringes, regardless of whether they invented it themselves, never read the patent, or trained their own ML model from scratch.

So the question “if we train our own wake-word model, are we clear of Valor’s patent?” reduces to a different question: do the patent’s claims read on our system? If the claims describe “a method comprising: detecting a user-configured voice phrase on a mobile device; transmitting a GPS coordinate to a remote dispatch service; activating an armed-response workflow” — then any product that does those steps is exposed, irrespective of which wake-word engine, which dataset, or which neural architecture is used under the hood.

Conversely, if the claims are narrower — e.g. tied to specific control-room ambient-audio monitoring plus a banking-fraud notification step — then a product that omits one of those elements may not infringe, again regardless of the underlying model.

The model is not the patent. The system-level claim is.

Available defences and design-arounds

Defence / routeDescriptionStrength
Non-infringementShow that our claim chart does not have an element-by-element match against any independent claimHighest leverage — design-around is achievable if claims are narrow
Prior art invalidityVoice-triggered alerts predate 2023 (Siri 2011; Alexa 2014; Picovoice Porcupine custom wake words 2018; bSafe voice SOS pre-2020; openWakeWord 2022)Strong — formal art search needed
Obviousness (s 25(10) SA Patents Act)Combining known wake-word detection + known panic dispatch APIs may be obvious to a skilled personModerate — courts vary
Patent not yet grantedSA Patents Act 57/1978 uses a deposit (non-examination) system — a granted SA patent is presumptively valid but has not been examined for novelty or inventive step. International national-phase examinations (US, EU) may differ.Practical — SA grant ≠ enforceability proven
Compulsory licence / negotiationIf FTO opinion confirms infringement, licence-in is an option; pricing must fit unit economicsLast resort
  1. Patent search & FTO opinion — instruct an SA patent attorney (Spoor & Fisher, Adams & Adams, Edward Nathan Sonnenbergs IP) to pull the published BYY/Valor application(s) and produce an element-by-element claim chart against our intended product. Budget: R40K–80K. Non-negotiable.
  2. Prior-art collation — assemble an evidence file of voice-triggered safety/SOS art predating BYY’s 2023 priority date (bSafe voice SOS, Picovoice custom wake words, academic wake-word literature, app store releases). This file feeds both invalidity and design-around.
  3. Design-around brief — once claims are visible, instruct the engineering team in writing on which architectural elements to avoid (e.g. omit ambient-audio monitoring; omit banking-fraud cross-trigger; alter control-room interaction model). Document the design choices contemporaneously — this becomes evidence of good-faith non-infringement.
  4. Insurance — IP infringement liability insurance is available in SA at modest premiums for early-stage software companies and is recommended once revenue is non-trivial.
  5. Defensive publication — publish our novel technical contributions (e.g. SA-language wake-word DTW approach, stressed-speech detection method) to establish prior art that prevents BYY (or a successor) from broadening claims via continuations.

Bottom line

Valor’s patent is a real risk that is independent of our model architecture. Building our own wake-word model does not, on its own, route around the patent — what matters is whether our end-to-end system practises BYY’s claims. The combination of (a) SA’s deposit patent system (grant ≠ proven validity), (b) extensive pre-2023 prior art on voice-triggered SOS, and (c) the likelihood that BYY’s claims are narrower than the marketing-grade phrase “world’s first voice-activated panic super app” suggests, means the risk is manageable but not ignorable. Treat the FTO opinion as a Phase 0 deliverable — before significant engineering spend — not a Phase 1 task.

Connections

Ontology Valor Patent Risk [relates] Valor Valor Patent Risk [relates] BYY Strategic Services Valor Patent Risk [distinct_from] POPIA

Sources