Custom Websites
Marketing sites, product sites, and portfolios engineered for speed, search visibility, and editorial control.
- Next.js builds
- Headless content
- Design systems
Software Studio / Nairobi
Software with a point of view.
Reimburse Systems Inc designs and builds custom websites, commercial platforms, and enterprise systems for organisations that care how their tools look, load, and last.
- Founded in Nairobi
- Led by Hillary Mokaya
- Web · Software · Systems
What we do
A studio for digital products that have to work.
From a single marketing site to a multi-role enterprise platform, every engagement is designed as one system — structure, interface, and code held to the same standard.
01 02 Commercial Software
Billing, inventory, booking, and internal tools shaped around how your business actually runs — not how a template assumes it does.
- Web applications
- Payment flows
- Admin tooling
03 Enterprise Systems
Multi-role platforms with permissions, audit trails, and integrations built to survive real organisations and real audits.
- Role-based access
- Data migration
- API integrations
04 Blog & Publishing Platforms
Editorial workflows, category structures, and reading experiences that reward both writers and readers.
- CMS architecture
- Editorial workflow
- Reading experience
05 Systems Design
Architecture, data models, and interface patterns decided before the first line of code — so the build has a spine.
- Domain modelling
- Architecture review
- Technical strategy
06 Maintenance & Growth
Monitoring, iteration, and feature work after launch. Software is a living system; we stay to keep it healthy.
- Observability
- Feature sprints
- Performance care
Selected work
Systems in the field.
A sample of platforms we have designed and shipped — commerce, publishing, intelligence, and field operations.
Fintech · Portfolio Intelligence
HisaTrack
A portfolio intelligence platform that turns scattered statements into one calm, decision-ready view.
ProblemInvestors were reconciling holdings across spreadsheets, broker PDFs, and chat threads — slow, error-prone, and impossible to audit.
SystemWe designed a single ledger model with nightly ingestion, allocation analytics, and a dashboard that leads with decisions rather than data dumps.
OutcomePortfolio reviews that took an afternoon now happen in minutes, with a clean audit trail behind every figure.
- portfolio review
- 4 min
- data sources unified
- 12
- reconciliation accuracy
- 99.9%
- Next.js
- TypeScript
- PostgreSQL
- Node.js
Commercial · Operations
Ledgerline
A commercial operations suite for a growing distributor — orders, stock, and fulfilment in one console.
ProblemOrders lived in WhatsApp, stock lived in a spreadsheet, and fulfilment lived in someone's memory. Growth made every gap louder.
SystemAn operations console with order pipelines, stock movements, and role-scoped views for sales, warehouse, and finance.
OutcomeOne source of truth from quote to delivery, with status visible to everyone who needs it and no one who doesn't.
- fewer order errors
- 62%
- faster fulfilment
- 3×
- source of truth
- 1
- Next.js
- PostgreSQL
- Prisma
- Redis
Publishing · Editorial Platform
Sarova Journal
An editorial platform where long-form writing is treated as the product, not the afterthought.
ProblemA publishing team was fighting a blogging tool that buried archives, mangled typography, and made every story feel disposable.
SystemA custom publishing workflow with issue structures, contributor roles, and a reading experience tuned for long-form attention.
OutcomeWriters write; the system handles structure. Archives became browsable, and reading time went up across the board.
- avg. reading time
- 2.4×
- to publish a draft
- 18 s
- lighthouse SEO
- 100
- Next.js
- MDX
- PostgreSQL
- Vercel
Enterprise · Field Operations
CountyMesh
A field-operations system connecting county teams, dispatch, and reporting across low-bandwidth environments.
ProblemField teams collected data on paper, synced whenever they returned to the office, and leadership saw reality a week late.
SystemA resilient mobile-first field app with offline capture, a dispatch map, and live reporting dashboards for regional leads.
OutcomeReports land the same day they're collected, and dispatch decisions are made on the current state of the ground.
- reporting lag
- 0-day
- field teams live
- 40+
- first by design
- Offline
- Next.js
- PWA
- MapLibre
- PostgreSQL
How we work
Clarity before code.
Every engagement follows the same disciplined arc — so the surprises are creative, never structural.
Discover
We start with the organisation, not the interface. Workflows, constraints, data, and the people who will live with the system — mapped before any pixel is drawn.
Design
Architecture and interface are designed together. Information structure, interaction patterns, and visual language are agreed as one system, on paper and in prototypes.
Build
Typed, tested, and reviewed. Small vertical slices ship early so reality can correct the plan, and the codebase stays legible the whole way through.
Evolve
Launch is a milestone, not the finish line. We instrument what matters, iterate on evidence, and keep the system fast as it grows.
The studio
Built on Waiyaki Way.
Reimburse Systems Inc is a software studio with a single obsession: digital systems that behave as well as they look. We work with businesses, publishers, and enterprises who want software built with taste and engineering discipline in equal measure.
The practice is led by Hillary Mokaya, our leading developer, who sets the technical direction on every engagement — from the first architecture sketch to the last performance pass. Design and engineering sit at the same desk here; that is why our interfaces hold together and why our systems stay fast years after launch.
We are deliberately small. Every project gets senior attention, direct communication, and a team that answers the phone. No hand-offs to strangers, no ticket queues, no theatre.
- systems shipped
- 40+
- industries served
- 12
- clients retained
- 98%
- average MVP
- 6 wks
Notes from the studio
Thinking in public.
Short essays on systems, publishing, and the craft of building software that lasts.
Why systems design comes before the first screen
Interfaces are the visible part of a much larger decision. Start with the data model and the workflow, and the screens almost design themselves.
Read noteWhat a publishing platform owes its writers
A blog tool should disappear. What remains is the sentence, the structure, and the archive — the three things that make writing compound.
Read noteDesigning software that survives the second year
Year one proves the idea. Year two proves the architecture. Notes on building systems that get cheaper to change as they age.
Read note
Start a project
Have a system worth building?
Tell us what you are trying to make work — a website, a platform, a messy workflow that needs a proper system. We will tell you honestly what it takes.