Skip to content
Shola Japheth

Enterprise platform · Technical lead

From a client's compliance brief to a standalone SaaS product.

A unified platform for enterprise governance, risk management, internal audit and compliance tracking. I led it from first requirements to production, and it now sells as its own product.

Role
Technical Lead / Forward-deployed engineer
When
2023 — present
Status
Live SaaS
Team
~10 engineers incl. offshore, + 3 client-side integration engineers
  • 90%

    SLA adherence

  • +25%

    system reliability

  • 47%

    faster engineer onboarding

The problem

A financial-services client needed governance, risk, internal audit and compliance tracking in one system. The requirements arrived in business and regulatory language, and a distributed team had to build from them. Someone had to turn that language into specifications, workflows and APIs, and stay accountable for the result in production.

What I owned

  • Requirements discovery with client stakeholders
  • Architecture and technical specification
  • Implementation and integration with client systems
  • Deployment, incident management and production support

The system

Delivery topology
  1. Client stakeholders

    governance, risk, audit

  2. Technical lead

    specs · workflows · APIs

  3. Engineering team

    ~10, incl. offshore

  4. Client integration

    3 engineers

  5. Production

    HampshireGRC SaaS

I sat between the client and the engineering team and translated in both directions.

Key decisions

  1. 01

    Classify the problem before fixing it

    For every ambiguous issue, the first question was whether it needed a code change, an architecture change or a process change. Answering that first stopped a distributed team from building the wrong fix.

  2. 02

    Fix causes, not tickets

    Root-cause analysis, preventative engineering and performance monitoring replaced repeat firefighting. Reliability improved by 25%.

  3. 03

    Write it down so the team can grow

    Standardised technical documentation and engineering processes cut onboarding time for new engineers by 47%. That mattered with contributors across time zones.

  4. 04

    Automate the path to production

    CI/CD and infrastructure-as-code made deployments repeatable and 20% faster.

Outcome

  • 90%

    SLA adherence through better incident management

  • +25%

    system reliability

  • 47%

    faster onboarding for new engineers

  • 20%

    faster deployments

Built for a financial-services client whose name is withheld. The product is now public at hampshiregrc.com.

esc
↑↓ to move · ↵ to run