01 / Build
Services

Software built to run.

Custom systems, AI retrieval, and the platforms underneath. We design and build for production from day one — not slide decks, not pilots that never ship, not “MVPs” that quietly become the permanent thing.

What we build

Four things we ship regularly.

Most engagements are some combination of these. The stack moves with the problem.

01

APIs & backends

Production APIs with proper auth, observability, and rate-limiting from the first commit. Async where it earns its complexity, synchronous where it doesn’t. We instrument everything — you should be able to answer “what happened at 14:32?” without grep.

  • FastAPI
  • Node
  • Postgres
  • MongoDB
  • Redis
02

Web & mobile apps

User-facing software for shoppers, vendors, internal operations, field teams. Mobile-first when the user is on a phone; web-first when they’re at a desk. Both built to work on slow networks — most of our users are on 3G most of the time.

  • Next.js
  • React Native
  • Expo
  • TypeScript
  • NativeWind
03

AI retrieval & search

Hybrid search (BM25 + vector), multimodal search (text and image), and retrieval-augmented generation against your own data. We pick embeddings, chunking, and reranking for the corpus — not the demo. Most deployments cost less to run than one engineer’s salary.

  • Weaviate
  • pgvector
  • Vertex AI
  • OpenAI
  • RAG
04

Payments & local rails

M-Pesa STK Push and B2C, card processing via the local gateways, bank transfer reconciliation. We’ve built this before. The first time anyone integrates Daraja, it costs them a month. It doesn’t need to.

  • M-Pesa Daraja
  • Card processors
  • KCB
  • Equity
How a build engagement runs

Discovery, then ship in fortnights.

  1. 01

    Discovery

    2 weeks · fixed price

    We write the architecture, the build sequence, and the number. If we’re not the right team for it, we say so.

  2. 02

    Foundation

    Weeks 1 – 4

    Auth, data model, CI/CD, observability, the first vertical slice all the way through. The boring scaffold that decides whether everything that comes after is fast or slow.

  3. 03

    Build

    Two-week increments

    Demo at the end of every sprint. Roadmap is negotiable, cadence isn’t. You always know what’s shipping next Thursday.

  4. 04

    Operate

    Ongoing

    We stay on as the operating team — incidents, releases, the quiet day-to-day — unless you’ve hired one internally.

Have a project in mind?

Tell us what you’re trying to do. The more specific the brief, the faster we can tell you whether we’re the right team for it.