UK software consultancy
Dusk Engineering Services
We build and look after the software businesses run on. Usually web apps, APIs, and the cloud they sit on — often for teams who've inherited something complicated and need it to stop being a problem.
services
What we do
01
Web applications
Internal tools, customer portals, dashboards. The screens your team opens every morning, and the ones your customers judge you by.
02
APIs and services
The plumbing everything else talks to. Written to still make sense in two years, when someone else is the one fixing it.
03
Cloud and hosting
Infrastructure that copes when you're busy and costs little when you're not. Set up so you can see what it's doing and what it's costing.
04
Making systems talk
Your CRM, your finance system, that supplier with the ancient API. We get them agreeing with each other, and keep them agreeing.
05
Releases and monitoring
Deploy on a Tuesday afternoon without holding your breath. Find out something's broken before a customer tells you.
06
A second opinion
Sometimes you don't need a build. You need someone senior to look at what you've got and say plainly what they'd do. You get that in writing.
about
What you can expect
Small team, direct contact. No account managers, no ticket queues, and nobody hands your project to someone cheaper once you've signed.
You own all of it
Code lands in your repository from day one. Your cloud account, your domains, your data. If we go separate ways, nothing of yours leaves with us.
We choose dull tools
Proven over exciting. You should be able to hire for this stack, and still be running it in five years.
We write things down
Why we chose what we chose, how to run it, and what to do when it breaks at 3am. Nobody should have to guess.
Same people start to finish
Whoever you speak to first is who writes your code. No handover to a delivery team you've never met.
engagement
How a project runs
01
A conversation
An hour on a call. What you've got, what hurts, and what you actually need. No slide deck.
02
Something in writing
Within a week: what we'd build, how, and what it costs. A fixed price wherever the work allows one.
03
We build it
Two-week cycles, working software throughout, and a short update every Friday. Nothing saved up for a big reveal.
04
You take it over
Running on your infrastructure, documented to match, with a proper walkthrough for whoever picks it up.
05
We stay, or we don't
Keep us on for support, or take it in-house. Both are fine — that's rather the point of step four.
contact
Get in touch
Tell us what you're trying to do and what's getting in the way. We reply within one working day.