ServicesAboutTeamPricingBlogContact
Start a project
— team / felixtech

Small team. Senior
engineers. Long tenure.

Three engineers. No project managers, no salespeople, no junior offshore. Every line of code you commission is written by someone with a name on this page.

— 3 full-time engineers
— 0 project managers
— 0 salespeople
— 2.4y median client tenure
FM01
Felix Muhoro
Founder · Lead Engineer
· Kerugoya, KE · GMT+3
· since 2022

Founded the studio in 2022 after seven years writing Laravel and Node for Kenyan SMEs and fintech operators. Writes most of the M-Pesa code and signs off on every production deploy. The on-call number on the homepage goes to his phone.

— stack
LaravelNext.jsM-Pesa DarajaKRA eTIMSPostgreSQLMySQLHetznerCloudflare
— currently shipping
  • →HyipX — production M-Pesa wallet (99.94% callback reliability)
  • →JuaKali OS — offline-first PWA for Jua Kali traders
  • →Skyrush — multi-tenant partner platform
DK02
Daniel K.
Senior Frontend Engineer
· Nairobi, KE · GMT+3
· since 2024

Joined in 2024 from a Nairobi fintech. Next.js, React Native, and a borderline-unhealthy attention to Core Web Vitals. Owns the frontend stack across our client roster and most of the design-system work — including the site you are reading.

— stack
Next.js 14React NativeTypeScriptTailwindFramer MotionViteVercel
— currently shipping
  • →felixtechltd.com — Lighthouse 97 mobile, sub-1.8s LCP on Slow-3G
  • →Sparkle Payments — merchant dashboard, Laravel + Inertia
  • →Trader's Hub Ke — Deriv API client (deriv.felixmuhoro.dev)
AW03
Ann W.
Backend Engineer · DevOps
· Kerugoya, KE · GMT+3
· since 2025

Joined in 2025 after four years on platform teams. Owns PostgreSQL, Laravel queues, and the GitHub Actions pipelines that make our deploys boring. Runs the on-call rotation and the quarterly restore tests on backups — because backups you have never restored are not backups.

— stack
PostgreSQLRedisLaravel HorizonGitHub ActionsDockerGrafanaLokiPagerDuty
— currently shipping
  • →Deploy pipeline overhaul — 1m 12s build + deploy on main
  • →Observability stack — Grafana + Loki across 47 production deploys
  • →Quarterly backup-restore drills on every active client
— ch. 02 / how we work

How a project actually runs.

No surprises in week three. Same rhythm whether you brief us on a marketing site or a multi-tenant SaaS — the only thing that changes is the sprint count.

01

Discovery week

One week, paid. You get a written scope, a schema sketch, a sprint plan, and a fixed quote — keep them whether or not you continue with us.

02

Two-week sprints

Friday demo on a real staging URL. Written update in your inbox before the demo, GitHub Projects board open, PRs reviewed by a second engineer before merge.

03

Production deploy

Zero-downtime rollout, backups verified by automated restore, observability wired in, on-call rota named. We do not call it shipped until somebody is paged when it breaks.

04

90-day stability

Three months of fixes, performance work, and small features included after launch — same engineer, no new statement of work for bug fixes.

— ch. 03 / hiring

We are not hiring right now.

We have refused growth twice when it would have meant hiring against the quality bar. When that changes, the role will appear here first — not on LinkedIn, not via a recruiter.

Open application? info@felixtechltd.com — three paragraphs about something you have shipped to production, and a GitHub profile we can read.

Want to work with us?

One 30-minute call. Bring your problem — we'll bring an honest read on whether we are the right shop.

Start a conversation →