Get in touch

Tell us about your project and we can discover how we can help you achieve your goals together.

Book a call

15 minutes to talk through your project and see how we can help.

Daniel profile image

Frequently asked questions

What happens when I get in touch?

We will review your enquiry and come back to arrange an initial conversation. That first call is a chance to understand what you are trying to do, what stage you are at, and whether we are a good fit to help.

What is a discovery call?

A discovery call is an initial conversation to understand your product, software, or operational challenge. It is not a sales pitch. It is a practical discussion focused on what you need, what matters most, and what the right next step might be.

What will we talk about on the call?

We will usually cover the basics of your project, the problem you are trying to solve, who the software is for, any constraints you are working with, and what stage you are at. If you already have clear requirements, we can discuss those too. If not, that is completely fine.

Do I need a full brief or specification before getting in touch?

No. Many projects start with a rough idea, an existing problem, or a sense that current systems are not working as they should. We can help shape the problem properly before jumping into features or delivery.

Who is the discovery call for?

It is usually for founders, product owners, operational leads, or teams responsible for improving an internal system or digital product. Anyone involved in defining the problem or deciding next steps is welcome.

What kinds of projects do you usually work on?

We work on bespoke web and mobile software that is business-critical, operationally important, or expected to evolve over time. That includes new products, internal systems, customer-facing platforms, and software connected to real-world workflows or devices.

Can you help if we already have software in place?

Yes. We often work with organisations that need to improve, extend, stabilise, or rethink existing software. That might mean rescuing a difficult product, adding new capability, or making a platform easier to maintain and grow.

What happens after the call?

If it looks like a good fit, we will outline the most sensible next step. That might be a follow-up conversation, a more structured discovery phase, a proposal, or advice on how to approach the work. If we are not the right fit, we will say so clearly.