Active development. Offline-capable merchant operations: products, sales, receipts, stock, expenses, customers/debtors and owner visibility.
Product portfolio
Distinct systems. Shared engineering discipline.
Talunza products are developed as real operating boundaries, not as names for every idea. Status labels separate current development from future direction.
Current portfolio
Built from problems we can observe.
Product scope can evolve as field evidence becomes stronger. Nothing below should be read as a claim that unreleased software is already production-ready.
Active development. Transport and distribution workflows around journeys, capacity, custody, pickup, delivery and proof.
Active early build. Phone-first local intelligence for prices, availability, transport, outages, events and finding useful things nearby.
Pilot/research direction. School operations and learning intelligence with teacher authority, offline support and strong learner-data safeguards.
Field-led direction. Evidence capture, operational observations, assets, incidents and work performed away from a desk.
Physical service boundary. Vehicle, tractor and machinery diagnostics, repair and preventive maintenance supported by digital lifecycle records as capability launches.
Product rule
An idea does not automatically become a product.
New repositories and public product names require a real deployable, operational or commercial boundary. Shared capabilities stay shared until evidence proves otherwise.