Web applications & SaaS platforms — multi-user systems with roles, billing and tenant isolation where needed.
service · systems
Software shaped around
your business — not the reverse.
When spreadsheets crack and off-the-shelf tools force you into someone else's workflow — that's when custom software pays for itself.
who this is for
Sound familiar?
- Operations running on WhatsApp threads, spreadsheets and memory
- Businesses that outgrew their SaaS subscription's limits
- Founders building a platform, marketplace or SaaS product
- Teams needing one source of truth across departments
the honest bit
What it costs.
Focused internal tools start around KES 150,000; multi-workflow platforms run KES 400,000+ depending on integrations, roles and reporting. I phase scope so the first release proves value before the budget doubles.
deliverables
What you get.
Internal business systems — CRMs, dashboards, inventory, booking engines, approval workflows.
Portals — customer, vendor or staff portals with self-service accounts.
Legacy rescue — audit and rebuild of systems abandoned by a previous developer.
Payment & messaging rails — M-PESA, Stripe, SMS and WhatsApp wired into the workflow, not bolted on.
Deployment & documentation — runbooks, admin training and a system your next developer can actually read.
how it ships
The process.
step 1
Process mapping
We document how work actually flows today — every workaround included. The system mirrors that, cleaned up.
step 2
Written scope
Deliverables, milestones and cost in writing before code. You approve the spec, not a mood board.
step 3
Phased build
Core workflow first, in front of you on staging. Edge cases and automation follow.
step 4
Rollout & support
Data migration, staff onboarding, monitoring — then a support plan that keeps it running.
proof
Relevant work.
Not mockups — systems running in production.
// related reading
faq
Straight answers.
Custom software vs buying a SaaS subscription?
If a KES 3,000/month tool covers 90% of your workflow, use it. Custom wins when the work is your advantage — a process competitors can't copy, or when per-seat fees outgrow a one-time build. I'll tell you which side you're on.
What happens if you're unavailable later?
You get documented, conventional code (Laravel/Node + a mainstream DB), your own repo, and a handover doc. Any competent developer can take over — deliberately.
Can you take over a half-finished system?
Yes — code rescue is a real service. I audit what exists, tell you what's salvageable, and quote the honest finish or the honest rebuild.
How do we handle changes mid-project?
Scope is written down; changes get priced and scheduled explicitly. No silent scope creep, no surprise invoices.
Describe the process that's breaking — I'll map the system that fixes it.
Written scope, honest pricing, 30-day defect warranty on everything I ship.