Website and web application development
Most of our work starts here. Something is needed that does not exist yet: a site a company can be judged by, an application that does the work the business actually does, or a store that has to take money reliably on a Sunday night. We build it to fit the business rather than fitting the business into a template.
What this covers
Business websites
The site your company is judged by: what you do, who it is for, and an obvious way to start a conversation.
Campaign landing pages
A single page built around one action, so the money spent driving people to it is not lost on the way.
Web applications, portals and dashboards
Software that runs in a browser and does the specific work your business does, for staff or for customers.
Online stores
Catalogue, checkout and everything after it, including the part where somebody still has to pack the order.
Internal tools and admin panels
The screens your own team lives in all day, built for speed of use rather than for a demo.
Booking and ordering systems
Appointments, tables or orders taken without a phone call, and without two people getting the same slot.
Content management your team can actually use
Editing a colleague can do on a Friday afternoon without calling anyone or breaking the layout.
Blogs and content-led sites
Publishing set up so that writing often is easy and each piece can actually be found afterwards.
Multilingual sites
One site that speaks several languages properly, translated and structured rather than machine-guessed.
Member areas and secure sign-in
Accounts, roles and the parts of a site only some people may open, with the security done properly.
How we approach it
Work out what it has to do
Before anything is drawn we establish who uses it, what they are trying to finish, and what would count as it working. Almost everything that goes wrong late in a project was decided badly at this point, and it is the cheapest place to change your mind.
Build the smallest real version first
Something you can open and use early, rather than a long silence followed by a reveal. Correcting a direction is easy while it is still a direction; it is expensive once it is a finished product.
Hand it over able to run
Access, documentation and a walk through it with the people who will use it. You should own the thing outright, not rent our attention to keep it alive.
The rest of what we do
Tell us what is not working
Describe the problem rather than the solution. Working out which part of this applies is our job, not yours.
Start a project