Services

Named pieces of work you can send to a colleague. They overlap on purpose: a school system is custom software, a web application, and often an integration job as well. If you are unsure which label fits, start with custom software or describe the process you want to replace.

Custom software

Applications modelled on your roles, records and exceptions — not a template forced onto the business.

Details
Application model
  • Roles
  • Records
  • Exceptions
  • Reports
Entities
Statuses
Permissions
  1. Capture
  2. Decide
  3. Record

Business systems

Day-to-day administration: people, money, cases and reports in one place staff can actually operate.

Details
Operational system
  • People
  • Money
  • Cases
  • Audit
Day-to-day work
Exceptions
Reports
  1. Open
  2. Operate
  3. Close

Web applications

Portals for staff, customers, parents, citizens or partners, with permissions on the same data.

Details
Web application
  • Staff
  • Customer
  • Documents
  • Queues
Portal
Permissions
Shared data

Mobile apps

Field work, drivers and anyone who is not at a desk — as a client of the same business rules.

Details
Field client
  • Jobs
  • Status
  • Capture
  • Sync

Same rules as the desktop system.

Workflow automation

Named stages, owners and finance rules instead of email chains and inbox handovers.

Details
Named stages
  1. Capture
  2. Assign
  3. Review
  4. Invoice
  5. Close

AI & automation

Assistants, documents and reporting inside a real application. A model is a component, not the product.

Details
Inside the application
  1. Document
  2. Extract
  3. Record
  4. Human check

Systems integration

Payments, SMS, identity and existing databases, wired in so information is not retyped.

Details
Connected services

API

  • Paystack / Ozow
  • SMS / Email
  • SA ID
  • Existing SQL

Not sure which service to pick?

Send the process, the users and the systems you already have. The label can wait.