The experience
A personal AI advocate with its own character and voice, approached through the cat’s name. Characterful wearable delivery and a more focused owner assistant for care and setup.
Investors & partners / Development overview
Character and connection
for everyday
cat care.
BatCat is developing a personal advocate, a connected two-device kit and an owner app. The opportunity is to bring an engaging daily experience together with useful care information.
Current stagePrototype development
Working components and human-tested interactions. The complete wearable system and commercial model still need validation.
A concise overview to take away
Download the overview Public development overview · Draft v0.6 · 7 October 2026 · Plain text
The proposition
Connection people
want to return to.
Cat owners need an experience that fits everyday life. The product hypothesis is that a recognisable advocate, useful owner tools and connected observations can make that relationship more engaging.
The system
Two complete interchangeable devices per cat. The cat’s identity and history persist across hardware, with an owner app for records, preferences and care.
The wider context
BatCat is the cat-focused product within Companion AI’s broader companion and advocate direction. Other applications remain exploration, rather than committed products.
Proposed business model
A device kit.
An ongoing relationship.
Hardware
Affordable entry hardware, with Basic, Intermediate and High-End device tiers planned. Core BatCat capabilities are intended across the range.
Subscription
Recurring service and data connectivity are the recorded business direction. Plans need customer price testing and measured delivery costs.
Route to customers
This website introduces BatCat and gathers opt-in interest. Customer trials would inform the offer before a confirmed kit and subscription can be ordered.
No final retail tariff, carrier agreement, validated margin, launch date or investment terms are published. Historical cost scenarios are planning material.
Evidence and milestones / Reviewed 7 October 2026
Follow the evidence.
See the dependencies.
Explore demonstrated components, the connected tests still needed and preparation for a customer offer. These are development stages, without committed dates.
All three stages are shown below. The review date is a context refresh, not a claim that every test was newly repeated.
Demonstrated prototype
Recorded results with a defined scope. A component result does not establish the whole product.
Prototype result
Characterful conversation
Human-tested Android wake, reply and follow-up conversations include short locked-screen trials.
- What this establishes
- Bounded conversation behaviour on tested Android and headset routes.
- Scope to retain
- Current phone microphone reliability remains an active issue. Complete wearable conversation is a separate test.
Local owner prototype
Useful care organisation
Per-cat records, Calendar, manual wellbeing entries, reviewed reports, care reminders and map/zone interfaces.
- What this establishes
- Owner record and care workflows in a local prototype.
- Scope to retain
- Production access, connected observations and customer use need their own validation. Website examples are fictional.
Wearable component tests
Clear recording, delivered
A complete experimental wearable microphone recording was received in full over mobile data. The received audio was reviewed as clear.
- What this establishes
- A bounded microphone-recording and upload result on an experimental device.
- Scope to retain
- A correct spoken answer has since been heard on the physical wearable, but it was very slow. Repeatability, recovery, speaker clarity and continuous capture remain open.
Awaiting connected validation
Join the working parts and measure the complete experience on appropriate hardware.
Integration milestone
Complete the device conversation
Build on the human-confirmed spoken answer by validating acceptable response time, repeated physical exchanges and reliable recovery.
- Depends on
- Repeatable capture and transport, supported device playback and the existing Advocate service.
- Next evidence
- A complete exchange, followed by longer idle, reconnect and noise tests with stated conditions.
Connected-device milestone
One cat across two devices
Validate fresh outdoor location and identity continuity when the worn device changes.
- Depends on
- Accuracy-aware location records, honest coverage gaps, authorized enrollment and a clear worn-unit assignment.
- Next evidence
- Measured routes and swaps. Charging-unit presence must not be treated as the cat's whereabouts or activity.
Wearable validation milestone
Fit, endurance and observations
Measure the complete assembly's fit, weight, heat, battery endurance and waterproof performance.
- Depends on
- Appropriate wearable assessment and real worn-device telemetry with personal baselines.
- Next evidence
- Measured hardware use and accuracy tests before activity, rest or roaming insights are released. Rest estimates are not proof of sleep.
Commercial preparation
Turn measured product use into a customer offer and a sustainable delivery plan.
Proposed customer milestone
Define a useful pilot
Test whether character, care records and connected observations earn a place in owners' daily lives.
- Depends on
- Customer interviews, willingness-to-pay research and a clearly scoped, supervised trial.
- Next evidence
- Recorded feedback and use against agreed pilot questions. No customer results or sales traction are claimed here.
Proposed cost milestone
Measure the whole service
Cost both devices, connectivity, voice and AI usage, media, storage and customer support.
- Depends on
- Current hardware and operator quotations, measured workloads and stated light/heavy usage assumptions.
- Next evidence
- A costed pilot and tested customer offer. Historical scenarios are planning material, not validated margins or tariffs.
Proposed delivery milestone
Prepare for customers
Define production access, data handling, support and supplier arrangements before commercial delivery.
- Depends on
- Recording and retention rules, company/ownership records and applicable launch requirements.
- Next evidence
- An agreed delivery and support plan. Engineering, connectivity and pilot partnerships can be explored through an enquiry.
No items are shown for this stage. Choose “All stages” to return to the overview.
Requirements and proposed milestones are distinct from demonstrated results. Device specifications, prices, launch dates and investment terms remain unconfirmed.