We rebuilt elewa.ke from the ground up, and this post is the first thing we're publishing on it. The new site is a simple static build: every page is pre-rendered to plain HTML, CSS and JavaScript ahead of time, so it loads without waiting on a server or a database. We also build and run the site with support from a small fleet of agents.
The bigger change is that we now have somewhere to write again. We used to write a lot, but work got busy and we focused on bringing ideas to life instead of talking about the work. Our thinking mostly lived in proposals, architecture documents and long helpdesk replies that only one client ever saw. Our public record became the products we built. This blog will bring our voice back.
What we'll write about
Technical deep-dives. How we actually built or fixed something: the constraint we hit, the options we weighed, and why we chose the one we did. When we say we start new work on the current stable release of a framework, or that we design for the handover from day one, we'd rather show you the code and the trade-off than assert it.
Real project case studies. What a piece of work looked like from scope to delivery, with real numbers where we can share them and the client's permission where we can't use their name. Including the parts that went sideways, because those are usually where the useful lessons are.
Notes on Odoo and ERP. A lot of our Odoo work is migrating and extending Odoo for European SMEs. Migrations, integrations, the awkward edges of customising an ERP without painting yourself into a corner at the next upgrade.
The latest on AI. Where AI agents actually earn their place in the work and where it doesn't. Concrete use cases, the setups behind them, and the trade-offs we ran into: what a model is good enough for, what still needs a human in the loop, and what a given approach costs to run once it's in production rather than in a demo.
How we work. Fixed-price first engagements, solution design before build, resourcing by level and role. Less as a pitch, more as a walk-through of the mechanics, so you can judge whether it fits how you'd want to work with a supplier.
Stay tuned
We're aiming for posts that are worth the time of the engineer or founder reading them, not filler. If there's something you'd like us to write up, or a problem you're chewing on, get in touch. Otherwise, check back. There's a fair bit we've been meaning to put in writing.
