React
Our usual choice for web applications. It suits products that will keep changing, and it's familiar enough that another developer can pick up the work later.
TECHNOLOGY
A short stack we know well, chosen so projects can be built, handed over, and maintained. It's not a catalogue of every library we've tried.
HOW WE CHOOSE
As a small team, we stay with tools we can ship with and explain. If your environment already points somewhere else, we treat that as a fact about the project. We'd rather work with what your people can operate than introduce a stack only we understand.

What people touch. We pick tools a small team can ship with and hand over later.
Our usual choice for web applications. It suits products that will keep changing, and it's familiar enough that another developer can pick up the work later.
For React products that need routing, SEO-friendly pages, and a clear path to static or server-rendered delivery. Our own website is built on it.
A strong fit for larger, form-heavy applications, where one clear structure for modules, routing, and forms matters more than flexibility.
For real apps on both iOS and Android when two native codebases would drift apart. If a website would serve people better, we build for the browser instead.
Where the business rules live. The choice follows the project, not fashion.
A good fit for business systems that need a long life, especially when Microsoft tools or SQL Server are already part of your setup.
For APIs and web backends. One language from screen to server helps a small team move quickly.
A structured Node.js framework for APIs that need clear modules and boundaries, with room to grow without turning into a tangle of files.
Someone has to look after this once we've finished. That person is part of the decision.
When you already license it, already have someone who can run it, or are building on .NET and want the data layer in the same family.
Our usual recommendation when the choice is open. It's reliable, widely understood, and available on both major clouds.
How the product gets hosted, recovered, and handed over.
Hosting and managed services when you or the product are already there, or when using a specific service makes more sense than building it ourselves.
So what runs on a developer's machine is what runs in production. That makes handover and recovery much simpler.
Every project is in version control from day one. A history someone else can read is part of finishing the work.
Tell us what you use today. We'll say honestly whether we can work with it, and where we'd suggest something different.
Start a conversation