Start a project conversation

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.

Useful context for discovery

You do not need a finished brief to start.

A useful first conversation usually covers the people involved, the work that is difficult today, the systems already in place, and the decision that needs to be made next.

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 when a conversation will be easier than email. We can discuss the problem, current systems, and the next useful step.

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.

// Technical Stack Readiness

const StatumStack = {

backend: ["Java/Spring", "PHP/Laravel"],

frontend: ["Vue.js", "React"],

mobile: ["Flutter", "Native"],

databases: ["PostgreSQL", "Oracle"],

infrastructure: () => "Kubernetes / AWS"

}

What to Prepare

To make our initial consultation as productive as possible, we recommend having the following ready:

📄

Project Vision

A clear summary of the problem you are trying to solve or the opportunity you want to capture.

📅

Desired Timeline

Any specific deadlines or market launch windows you have in mind.

💰

Budget Bracket

Having a rough budget range helps us suggest the best architectural approach for your scale.

🔗

System Access

Documentation for any existing systems or third-party APIs we need to integrate with.

Our Engineering Process

From first contact to project kickoff, we keep the scope, decisions, and next steps visible.

Initial Review

We read the context you share and respond with questions or a clear next step.

Discovery

We hold a technical discovery session to map your architecture and detail functional requirements.

Proposal and next steps

We provide a proposal or estimate when the scope is clear enough to support one, including assumptions and next steps.

Kickoff

Once the agreement and priorities are clear, the team confirms the delivery plan and starts the agreed 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.

Clear handover

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 is useful for 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