Software, thought through from the work outward.

01 / Convictions

What the designs are built on

• The work comes before the software.

  Every good system starts on the shop floor, at the front desk, in the paperwork nobody wanted to talk about. The exceptions are the real specification.

• Rules are data, not code.

  Each client, country and industry brings its own rules. When those live in configuration, the next client is a setting. When they live in code, the next client is a fork.

• Trust is a feature, designed on day one.

  Permissions, audit trails and privacy shape the first diagram. Retrofitting them later costs far more than drawing them early.

• The boring stack is a decision.

  Proven tools, clear boundaries and small moving parts keep a system running through the busiest service of the week.

• Software that people can use beats a perfect plan.

  Real hands on a working system teach faster than any review meeting.

02 / Different answers

The usual move, and the better one

Real examples of where a different line of thinking changed the outcome.

• Customers

  Add a Borrower table, then a Supplier table, then a Guarantor table, and duplicate the same person in each.

  One customer who can hold many roles. Fewer records, cleaner reports, and a model that survives new kinds of relationship.

• Printing

  Install a full local web stack beside every printer and hope it keeps running.

  A small print bridge that speaks the printer's language while the rest of the system stays in the cloud.

• Access

  A login screen, then trust everything behind it.

  Hardware-bound device enrollment, a token per device and an audit trail, so every action traces back to a trusted device.

• Local rules

  Hard-code one country's payroll and leave rules, then rewrite for the next.

  Jurisdiction rules held as configuration, including layered ones such as statutory sick leave paired with social-security benefits.

• Bugs

  Patch the symptom where it shows up.

  Trace it through the logs to the mapping layer where the data first went wrong, and fix it there once.

• AI

  Bolt on a chatbot and call it intelligent.

  Assistants that draft and summarize while people stay in charge, and vision models that turn scanned paper into structured data.

03 / Reach

Built for different places

Currencies, regulations and payment habits change from one market to the next. Delivery across the Caribbean, Africa, South America and the United States made that the default design constraint rather than an edge case: systems are configurable by nature, not local by accident.

• Multi-currency
• Multi-tenant
• Payments
• Role-based access
• Compliance
• Integrations
• Device integration
• AI-assisted workflows

04 / Proof

Where the thinking shows up

• 01Passport NexusCase management→

  Application management for investment-migration agencies: case pipelines, document handling, partner and client portals, and a full audit trail.

• 02POS SuiteRestaurant & retail→

  Cloud point-of-sale for restaurants and retail (iRestrack and Zettaz Cloud POS): ordering, printing, device integration and payments across multi-tenant deployments, plus an iRestrack POS app for iOS and Android.

• 03PayTimeHR & payroll→

  HR and payroll software with configurable rules, multi-currency handling and subscription billing, built for the cloud.

• 04PaisePathFinance→

  A finance application for configurable lending: eligibility, repayment schedules, interest calculation and collections.

• 05Tours & ChartersBooking→

  A booking and operations platform for tour and charter operators, with the Zettaz Crew mobile app for iOS and Android.

• 06VotersMatrixOrganization platform→

  A configurable platform for organizing large field operations: hierarchies, teams, outreach workflows and AI-assisted features.