Global web consulting from Nairobi, Kenya
We build websites and web apps on the platform that fits, connect them to the systems you already run, and put the numbers where you can read them. In accounts you own, documented for whoever comes after us, and looked after on a retainer.
If someone sent you here, mention their name and we will start from what they told you.
Registered in Kenya
Shorea Solutions Limited
Certificate number on request
Work to date
Five organisations, from a national programme to a trading venture
Described below. Client names appear as each client approves
We run on our own numbers
Pulse, our own dashboard, read every morning since May 2026
Built the way we build for clients
Where we work
Organisations worldwide
Based in Nairobi, Kenya
Proof
We built our own dashboard this way and have read it every working day since May 2026: revenue against target, cash collected, work in progress, each figure read from the record that made it rather than typed in by someone. It is built the way we build for clients: in our own accounts, documented, and kept working.
The example alongside shows the same view for an organisation that sells through its website, takes payment by M-PESA and keeps its stock in a separate system. The figures are invented. The shape is not: every tile names the system it reads from, and nobody retypes a number.
Revenue this month
KES 4.82M
96% of the KES 5.0M target
From the sales system
Cash collected
KES 3.14M
Up 20% on the same days last month
From M-PESA and the bank, matched to invoices
Orders in progress
24
6 awaiting dispatch, 2 on hold
From the order form and the stock system
Enquiries this month
38
17 from search, 12 from Meta ads, 9 direct
From the website and the ad accounts
Marketing spend per sale
KES 410
Meta KES 620, search KES 280
From the ad accounts and the sales system
Stock below reorder point
6 lines
2 with orders waiting on them
From the stock system
Illustrative example for a business that sells online. Every figure is invented; the layout is the one we build.
Scope
Public sites, member and programme portals, online stores and the web applications behind them. We work across the major platforms, Shopify, WordPress and Drupal among them, and build custom where a platform would get in the way. Everything is registered to your organisation from day one and handed over with a written record of how to change it.
We connect the systems you already run, your website, forms, payments, accounting, stock or programme records, so data flows between them and lands in one place you own. What you get is visibility: one screen that shows what is happening across the organisation, read from the systems themselves rather than from the people reporting on them. Where AI can reliably take over a repeated task inside that flow, we put it to work with a person still accountable for the result.
Google Analytics, Meta, Search Console and your sales system each tell part of the story, and each has a reason to flatter itself. We join them into one view, read at source, so you can see which channels bring revenue, which spend is wasted and what to change next. Independent of the platforms and vendors being measured.
Method
A call, then a short written scope. We look at what you have, who uses it and what breaks, and we say in writing what we would build or fix, in what order, and what it would cost.
Domains, hosting, source code and any database are registered to your organisation from the first day. We work inside them as a named collaborator you can remove, and nothing depends on an account of ours. The same holds for what we connect: the integrations and the dashboards read from your accounts and live in them.
A written record of how the system is put together, where everything lives and how to change it, so your own people or a successor can pick it up without us in the room.
Websites break quietly: an expired certificate, a plugin update, a form that stopped sending. The retainer keeps things patched, backed up and answered, and once a month you get a short note of what was done and what is coming. When something does stop working, we find the cause, fix it and write down why, so it does not happen twice.
What you own
Everything. Domains, hosting, code and data sit in your accounts, documented for a successor. The retainer keeps it working; stopping it does not take anything away.
Who does the work
Engagements are led by our principal, Erick Kagai, who does the build work himself. Where an engagement needs a specialist, a designer or a platform developer, we contract them by name and you meet them.
Work
Described by sector. Client names are added as each client approves naming. Some of this work is the websites and portals underneath; the connected systems described above sit on top of them.
National programme
The programme's public site rebuilt on Drupal for a ministry-run, donor-funded programme, delivered in funded blocks of days with the programme lead signing off each block. Work in progress.
Non-governmental organisation
Domain registrations, hosting and coordination with the organisation's own developer for a climate-resilience NGO, so that its three domains and its Drupal site stay registered, reachable and in one pair of hands.
Insurance
A public site for a personal-accident cover reseller, with an enquiry form whose notifications reach the agency. When the notifications silently stopped, we found the deactivated key and the blocked address and restored them.
Apparel brand
Purchase orders, receiving and backstock for an apparel brand's warehouse, reading stock live from the warehouse system so low stock and incoming orders sit on one screen. Delivered as a working system for the client's review.
Our own business
Revenue against target, cash collected and work in progress, read from our own records every morning. Built, hosted and documented the way we build for clients, and in daily use since May 2026.
Trading venture
A static landing page for a trading venture, built and hosted, then password-protected at the client's request while the venture prepared its launch, on a domain in the client's name.
Questions
Shopify, WordPress and Drupal are the ones we work in most, and we build custom web applications where a platform would get in the way. The platform is chosen for your organisation, not for us. We also take over sites that someone else built, once we have read how they were put together.
You do. Domains, hosting, code, the connections between your systems and any dashboard are registered to your organisation and live in its accounts. You can remove our access at any time and nothing stops working.
Usually, yes. Most systems expose a way to read and write their data, and where one does not we work from exports on a schedule. We start by mapping what you run and where the gaps in visibility are, and the scope says which connections are worth building first.
A screen that reads from your systems as they are, rather than from a report someone prepared. Stock next to incoming orders. Enquiries next to the pages they came from. Revenue against the target you set. We run our own business on exactly this, and the illustrative view above shows the shape of it.
Inside the integration work, on the tasks your people repeat every week: sorting enquiries, drafting the first reply, reconciling records, summarising documents. We put it on the parts it can do reliably, inside your accounts, with a person still accountable for the result, and we say plainly where it will not help yet.
The other half of the picture. Analytics knows about visits, Meta knows about its own ads, Search Console knows about search, and your sales system knows what was actually paid for. Each reports on itself. We join them so you can see, on one screen and on the same terms, which sources bring revenue and which spend to stop.
No. The same view reads organic search, referrals, email and direct sales. Ads are one more source when you run them, and the point is to see every source on the same terms.
Everything keeps running and stays yours. What stops is our patching, backups, monitoring, the same-day answer when something breaks, and the monthly note, so someone on your side takes those over. The documentation is written for exactly that.
Every engagement is scoped to what it actually requires, so there are no packages or published bands. We discuss it on the discovery call, then put it in writing with the scope.
Next step
Thirty minutes. Bring the site that needs building, the systems that do not talk to each other, or the numbers you do not trust, and we will tell you what we would do about it, what it would take, and whether we are the right people to do it.
Our measurement work for online stores, with named results, is at kagai.me.