Talk to the Statum
engineering team

Start a technical discovery conversation about custom software, integration work, or product delivery. We help teams define scope, constraints, and implementation priorities before writing any code.

What to bring

You do not need a finished brief to start.

A short description of the people involved, the part of the work that is difficult today, the systems already in place, and the decision you need to make next is enough.

The workflow

What people are trying to do, where the process slows down, and what a better outcome would look like.
The current systems

Existing software, data sources, providers, and constraints that the work must respect.
The first decision

Whether the next step is discovery, a focused build, an integration review, or something else.

Project enquiries

Use email for RFPs, requirements, project context, and documents that will help us understand the work.

Call the team

Call if talking through it will be easier than writing it down. We can discuss the problem, current systems, and what you need to decide next.

254 721 553 678

When it makes sense to talk

Statum works with organisations that need to build, improve, or connect important software. The best starting point is a clear description of the work, the people involved, and the outcome you need.

✓ Custom Enterprise Software

You have a business process that standard software does not represent well. You may need a tailored ERP, CRM, customer portal, workflow, or payment integration that fits the way your team operates.

✓ API & System Integration

You need to connect systems that currently rely on manual transfers. We can assess integrations with M-Pesa (Daraja), SMS, KRA services, SAP, Oracle, and other systems where the interfaces and data flows can be understood.

✓ High-Growth Startups

You are building an MVP and want to decide what belongs in the first release, what can wait, and what technical foundations the team should protect as the product develops.

✕ Who We Are Not For

We may not be the right fit for a small one-off edit or a project that does not need software planning, integration, or ongoing ownership. We can usually establish that early in the conversation.

What the team brings

We bring software engineering, product thinking, and knowledge of the local operating context. The tools and architecture depend on the product, existing systems, team, and constraints.

»

Fintech & Payments

Payment flows, payroll calculations, and transaction records where configured.
»

Logistics & Tracking

Fleet management, real-time GPS tracking, and delivery optimization.
»

EdTech & LMS

Student record management and high-volume learning platforms.
»

Public-sector workflows

Regulatory reporting and government API connectivity where the project requires it.

What we can assess

Payments and callbacks

M-Pesa STK Push, C2B, B2C, reversals, and reconciliation paths.
Existing systems

Oracle, SAP, ERPs, CRMs, SMS providers, legacy systems, and internal APIs.
Delivery conditions

Offline use, permissions, audit trails, support, backups, and handover.

What to have ready

Bring whatever you already have. If the brief is still rough, we can start with the problem and work out the detail together.

📄

The problem

What is difficult today, who feels it, and what should change.

📅

Timing

A deadline, launch window, or other date that affects the order of work.

💰

Budget range

An approximate range helps us frame the first release and the options around it.

🔗

Existing systems

Links, documentation, sample data, or provider details for software the work must connect to.

What happens after you get in touch

We keep the first steps short and make the decision at each stage explicit.

Read the context

We read what you send and come back with questions, a call, or a sensible next step.

Ask the hard questions

We map the current systems, people, data, exceptions, and requirements that will affect the work.

Scope the work

When there is enough information, we provide a proposal or estimate with assumptions, exclusions, and the next decision.

Agree the start

Once the agreement and priorities are settled, the team confirms the first delivery checkpoint and starts the work.

Working model

Remote-first, with Nairobi meetings when they add value

Statum works remotely by default and coordinates discovery, delivery reviews, and support through documented workflows. For higher-stakes scoping or stakeholder sessions, we can meet in Nairobi by appointment.

Discovery first

We clarify goals, dependencies, and rollout constraints before committing scope.

Delivery ownership

Named technical contacts, sprint reviews, and implementation checkpoints.

Security and data handling

Project plans consider access control, data handling, and operational requirements.

Handover plan

Documentation, support options, and ownership expectations are defined upfront.

Inquiry FAQ

We can use an initial conversation to understand the project and decide what to investigate next. Any later discovery work is agreed before it begins.

We can review and sign an NDA where the project requires one. Please send your standard agreement or ask us about the information you need to protect.

We work remotely and can meet in Nairobi by appointment when an in-person session helps with scoping or stakeholder discussions.

The start date depends on scope, availability, decisions, and the agreement. We confirm the proposed sequence and timing after the initial discussion.

Where we meet

Nairobi Meetings by Appointment

We work remotely with clients in Kenya, East Africa, and beyond. Meetings in Nairobi are available by appointment when they add value.

Talk to the Statum engineering team