Software systems proven in real operations.

Proof points

What this evidence establishes

The resulting system created a traceable stoppage lifecycle instead of a collection of disconnected values. Production and engineering could review the same event history, operator explanations remained linked to the machine evidence and integration failures were diagnosable rather than silently absorbed.

Proof points

What this evidence establishes

The operation gained faster item lookup and a reconstructable history. Scans reduced typing, while event and validation logic prevented the label from becoming a meaningless shortcut around process control.

Proof points

What this evidence establishes

The prototype became a decision tool rather than a fragile demonstration. Stakeholders could repeat the workflow, inspect failures, review captured evidence and understand which risks remained before enclosure, certification or production engineering.

Proof points

What this evidence establishes

Users could inspect what the system understood before creating or changing ERP structures. Existing one-page designs continued to work, unusual files became diagnosable and stock, BOM and operation gaps were visible before they reached live manufacturing data.

Proof points

What this evidence establishes

The business gained a searchable service history and a clearer view of work in progress. Technical evidence stayed attached to the job that produced it, customer reports could be generated from controlled records and hand-offs became visible instead of relying on repeated follow-up.

Proof points

What this evidence establishes

Quality staff could move from source record to validated certificate through one controlled path. The system reduced repetitive transcription, made missing data visible before issue and created a searchable document history tied back to the operational record.

Proof points

What this evidence establishes

Assembly League became INESSOFT's strongest public demonstration of low-level language design, modular architecture and simulation thinking. Although commercially experimental, it proves the ability to build unusual technical systems rather than only conventional CRUD applications.

Proof points

What this evidence establishes

Leobot accumulated a substantial real operating history: more than 9.4 million page views, 43,000 user accounts, 9,000 orders, 7,000 invoices, 134,000 units sold and over R2.6 million in recorded sales across its lifetime snapshot. The more important result is the engineering feedback loop created by owning the platform. INESSOFT learned how catalogue architecture, SEO, stock truth, internal tools and incremental modernisation interact over many years.

Proof points

What this evidence establishes

PromoStars established a new national discovery surface in a category that previously depended heavily on agencies, social media and word of mouth. The platform reached hundreds of curated public profiles within its first months, earned strong organic visibility across national, city and service-intent searches, and created a repeatable buyer journey from search to shortlist and enquiry. More importantly, it taught INESSOFT how structured content, curation and operational marketplace design reinforce each other.

Proof points

What this evidence establishes

WaiterPlease produced a complete end-to-end SaaS pattern from account creation and physical QR deployment through anonymous request capture and staff-side completion. It also generated valuable product lessons: a minimal customer interaction demands rigorous backend design, operational software must fit the staff response process, and commercial adoption requires venue onboarding and distribution rather than feature completeness alone.

Proof points

What this evidence establishes

The platform gave participating brands store-level visibility into market execution and competitor conditions that were otherwise difficult to consolidate. It created a stable commercial software stream for INESSOFT and established an important engineering pattern that remains relevant today: mobile capture at the point of work, controlled reference data, resilient synchronisation, central SQL records and role-appropriate management reporting.

Proof points

What this evidence establishes

The games generated substantial passive income and reached more than 2 million active accounts at peak. More importantly for later INESSOFT work, they created practical experience with concurrency, state modelling, data efficiency, live-user support and the commercial reality that even strong software needs distribution.