Retired — we say why
NeoService
An internal ticketing system for service issues — roles, lifecycle, and an analytics view.
Who it's for Internal team only
Retired — and here is the honest reason why.
The post-mortem
NeoService came out of an internal need to track service issues properly rather than in a chat thread: a ticket with an owner, a lifecycle, escalation to the right department, and enough reporting to see where things were getting stuck.
It got as far as a working system with authentication, roles and an analytics dashboard, and it was never customer-facing.
It is retired for good. Service desks are a solved, crowded category, and there is no version of this we would take to market — the honest place for it is this list, with the reason attached.
More from the same engine
-
SamSupport
LiveA drop-in live voice-assistant SDK that gives any web app page-aware spoken guidance.
Read the story -
LeadGenAI
BuildingFinds sales leads across X, Reddit, LinkedIn and Hacker News and scores buying intent.
Read the story -
WebsAI
BuildingA QA agent that checks any website like a human and reports what's broken.
Read the story