Web platforms and applications
Customer-facing products, portals and marketing sites — built to be fast, searchable and usable on the phones your visitors actually own.
Software Development
Software that goes into daily use, and stays yours
We design, build, deploy and hand over production web software — the platform your customers use, the admin area your team runs it from, and the plumbing between them. One small team from scoping to support, and a written guide at the end so you are not tied to us.
What's included
- Web applications, portals and marketing sites
- Admin areas and content management your team actually operates
- Accounts, subscriptions, payments and permissions
- Business dashboards, reporting tools and integrations
- Deployment, monitoring and support plans
What this covers
What we build
We design and build software that goes into daily use: customer-facing platforms, internal tools, company websites and the admin areas that keep them current. The same small team scopes, builds, deploys and supports the work, and every build is handed over with a written guide so your team can run it without us.
Admin areas and CMS
The control room behind the site: listings, content, photographs, staff and settings, editable by your team without a developer in the loop.
Accounts, payments and permissions
Sign-in, subscriptions, checkout and the rules about who may see or change what — the parts that are expensive to get wrong later.
Dashboards and reporting tools
Internal screens that answer a standing question — this week's numbers, this month's pipeline — without anyone exporting a spreadsheet.
Automations and integrations
Wiring your systems to each other and to the services they depend on, so a step that took a person an hour takes nobody any time at all.
Deployment and support
Hosting, domains, backups and monitoring set up properly, plus a support arrangement for after launch. We support what we ship.
Who this is for
Two kinds of people ask for this
They arrive with different worries, so it is worth saying which one you are when you get in touch.
You have a process that software should be holding
- Work currently living in spreadsheets, WhatsApp threads and one person's memory
- A website you cannot update without going back to whoever built it
- Manual steps repeated daily that could be done once, properly, in code
- Systems that do not talk to each other, so the same data is typed in twice
You have a product to get in front of real users
- A first version that has to be real software, not a clickable prototype
- Accounts, payments and an admin area from day one, not bolted on later
- Someone who will tell you which half of the scope to cut to ship this quarter
- A codebase and accounts in your name, so the next developer is not blocked
How it runs
What working with us looks like
Four stages, and you can stop after any of them. Nothing here depends on committing to the whole thing up front.
- 1
Scope
We talk through the problem, then come back with what we would build, what it costs and how long it takes — in plain language, before anyone writes code.
- 2
Design
Screens and flows first, so the arguments happen over a layout rather than over a half-built feature.
- 3
Build in the open
You get working software early and often, on a real URL. You steer it while changes are still cheap.
- 4
Launch and hand over
We deploy it, put the accounts in your name, and write you a guide to running it. Support continues on whatever arrangement suits you.
What you get out of it
- A product in production, not a prototype — see ReviseMed and TrustCreast Homes
- Replace manual spreadsheets and WhatsApp threads with software that holds the process
- Own what we ship: your accounts, your code, and a guide to running it
What we work in
- TypeScript
- React
- Next.js
- Node.js
- PostgreSQL
- Supabase
- Paystack
- Vercel
Questions
The ones we get asked
Do we own the code and the accounts?
Yes. The repository, the hosting, the domain and every third-party account are in your name, and we hand over the credentials at launch. If you later move to another developer, nothing about our setup makes that harder.
What happens after launch?
Every build ships with a written handover guide covering the day-to-day jobs — adding content, handling enquiries, changing details — so your team is not dependent on us for ordinary work. Beyond that, we offer support arrangements for updates and fixes.
How long does a build take?
A focused marketing site with an admin area is usually weeks; a platform with accounts, payments and multiple user types is usually months. You get a real estimate at the scoping stage, not before — a number quoted before anyone has understood the problem is a guess.
Can you take over something someone else built?
Sometimes. It depends on what it was built with and what state it is in. We will look at it and tell you honestly whether it is cheaper to continue it or to rebuild — including when the answer costs us the bigger job.
Have something you need built?
Book a free 20-minute consultation. Tell us the problem and we'll tell you honestly what it needs — including when the answer is not us.