Company

The people answerable for the work

Institutional buyers ask who is accountable before they ask what you build. This page names the posts, what each one owns, and where escalation reaches.

Speak with the engagement desk

Accountability is a named post

We publish who owns what because a client escalating an issue should never have to discover the org chart by trial and error. Every engagement has a named executive sponsor and a named practice lead from the first scoping call.

Independent gates

Security review can halt a production release
Data protection sits outside delivery and reports to the board
Neither gate can be overridden by a delivery deadline

One escalation path

Practice lead for anything technical
Director of Delivery for scope, schedule or service level
Managing Director as the final point, without a queue

Continuity

Named engineers are not rotated without your consent
Bench cover is our obligation, not your risk
Handover is contractual at the close of every engagement

Executive and technical leadership

Eight posts carry the division. Five are firm-wide; three lead the engineering disciplines that most engagements draw on first.

Appointment to be announced

Managing Director

Answerable to the board of Jiranisoko Market Ltd for the division as a whole: commercial performance, client relationships at executive level, and the standards the firm holds itself to.

Executive sponsor on Tier-1 and public-sector engagements
Final escalation point for any client dispute
Accountable for the published compliance and service commitments

Appointment to be announced

Chief Technology Officer

Owns the technical direction of the division and the architecture standard applied across all six disciplines. Signs off the architecture decision record on every engagement above an agreed threshold.

Architecture review and technical risk sign-off
Engineering ladder, hiring bar and technical development
Technology selection policy and its exceptions

Appointment to be announced

Director of Delivery

Accountable for every engagement meeting its baseline, its service tier and its handover obligation. Owns the delivery reporting a client sees each week.

Engagement staffing, sequencing and capacity
Service level performance and the quarterly service review
Cutover authorisation on production migrations

Appointment to be announced

Head of Information Security

Owns the information security management system and the compliance register published on this site. Holds an independent veto on any production exposure that has not passed security review.

ISMS, control framework and audit readiness
Security review gate before production exposure
Responsible disclosure intake and incident response

Appointment to be announced

Data Protection Officer

Statutory role under the Kenya Data Protection Act 2019. Independent of delivery, reporting to the board, with authority to halt processing that cannot be justified.

Data Processing Addendum and the sub-processor register
Data subject rights requests and breach notification
Data protection impact assessments

Appointment to be announced

Practice Lead — Artificial Intelligence & Automation

Technical quality across the AI and automation discipline, including the evaluation and guardrail standards that make an agent system defensible to a risk committee.

Model risk, evaluation harnesses and human oversight design
First technical responder on AI and automation enquiries

AI & Automation

Appointment to be announced

Practice Lead — Financial Technology & Payments

Technical quality across payments engineering, including PCI-DSS scope control, reconciliation correctness and the failure paths that define payment integration.

Cardholder data scope and tokenisation architecture
First technical responder on payments enquiries

FinTech & Payments

Appointment to be announced

Practice Lead — Cloud Infrastructure & DevOps

Technical quality across cloud architecture and delivery engineering, including landing zone design, migration cutover assurance and the pipeline controls that fail closed.

Landing zone standards and cost governance
Cutover rehearsal and rollback design

Cloud & DevOps

Publication gate G-09 — 8 of 8 outstanding

These posts exist and their accountabilities are real, but no appointee has been recorded against them. Supply a name and photograph for each, with that person's consent to external publication, before launch — procurement reviewers verify the names on this page. Set name and photo_path on the team_members row; the card layout does not change.

How this is governed

Accountability on a page is worth what the framework behind it is worth. The governance register carries the compliance status, service level framework and data protection obligations these posts are answerable for.

Governance register Delivery model

Request for Proposal

Begin with a scoped conversation, not a sales call.

Our intake is structured so that the first response you receive is technical. Tell us which of the following describes your position and we will route your enquiry to the engineering lead who owns that practice.

Enterprise modernisation An existing system — core, legacy or on-premises — that must be migrated, re-architected or integrated. New product build A platform to be taken from concept or specification to production under a fixed scope. Team augmentation Senior engineering capacity embedded into an existing team and roadmap.

Submit a Request for Proposal Speak with our engagement desk

Enquiries are acknowledged within one business day and answered substantively within two business days. All submissions are treated as confidential; a mutual non-disclosure agreement is available before disclosure of scope.