Web development
Web development and web application design
Front end, back end and database, built to be fast on the connections your users actually have.
A site that takes nine seconds on a mid-range Android over mobile data has failed, whatever it scores on a developer's laptop over office fibre. We set a performance budget at the start, in kilobytes and in seconds on a named device and connection, and treat exceeding it as a defect rather than a trade-off to discuss later.
The work covers the whole stack: interface, API and database, plus the design system that keeps the tenth page consistent with the first. For applications rather than sites, that means the same attention on the parts users do not see, such as how a form behaves when the request fails halfway.
Accessibility is built in rather than audited at the end. Semantic markup, keyboard paths that work, contrast that holds, and text that a screen reader can follow. It is also, incidentally, most of what makes a site legible to a search engine, which is why we set up analytics and search visibility as part of the same pass.
What you get
- Design system and component library
- Front end, API and database
- Performance and accessibility budget
- Analytics and search visibility setup
Who this is for
- Marketing and communications teams
- Organisations replacing a dated site
- Product teams needing a web front end
How the engagement runs
Six steps, in this order.
Skipping one of these is how projects end up rebuilt. The order matters more than the ceremony.
- 01
Consultation
We sit with the people who do the work and find out what actually happens, including the workarounds nobody documented.
- 02
Planning and proposal
Scope, timeline and cost in writing, with the assumptions listed. If something is unknown, it is named as unknown.
- 03
Design and development
Data model first, then interface. You see working software early and often rather than a demo at the end.
- 04
Testing and refinement
Functional, load and user acceptance testing. Findings go on a list that gets closed, not a list that gets discussed.
- 05
Implementation and integration
Migration, integration with existing systems and a cutover plan that accounts for the day the old system is switched off.
- 06
Training and support
Your team is trained on the system they will use, and we stay on for maintenance, updates and the questions that arrive in month three.
Questions
Asked before we start.
Something not covered here? Email us and a person will answer.
Do you build on WordPress?
For a content-led site with non-technical editors, a CMS is often the right answer and we will set one up properly. For anything with real application logic, permissions or integration, we build it rather than bend a CMS into a shape it was not designed for.
Can we edit the content ourselves?
Yes, where that is the requirement. We wire content to a CMS your team can use, and train them on it at handover. Where the content genuinely never changes, we will tell you that a CMS is an unnecessary moving part.
Does the site get built for search engines?
Server-rendered pages, clean URLs, structured data, a sitemap and metadata come as standard rather than as an add-on. That covers the technical half. The other half is the content and the links pointing at it, which is work on your side that we can advise on.
Scoping
Send us the process that keeps breaking.
A short description is enough to start. We will come back with whether it is a product, a build, or something you can fix without buying software.
Nairobi office
10th Floor, Applewood Adams, Ngong RoadNairobi
Kenya
- Phone
- +254 701 684 754
- Hours
- Mon–Fri, 08:30–17:30 EAT