Solutions That Drive Growth

Both, and which one suits you depends on how well defined the work is rather than on how large it is. A scope we can both describe precisely — a website, a defined integration, a mobile app with an agreed feature list — is better fixed-price, because you carry no risk of the estimate moving. Work that will evolve as you learn from it, such as an evolving product or ongoing platform development, is better on a retainer, because a fixed price for an undefined scope is either padded in our favour or becomes a dispute. We will tell you which one we think applies before you ask.

You do. Custom work we build for you is yours on final payment, delivered in your own repository, with no licence back to us and no dependency on us to keep running it. The one honest exception is our own platform products, such as the white-label GPS platform, which are licensed rather than sold — you brand it and operate it, but you are not buying the source. We state which model applies to each item in the proposal rather than leaving it to be discovered later.

Yes, and a good share of our work is exactly that rather than greenfield builds. Joining an existing codebase does mean the first week or two is slower than either side expects, because reading unfamiliar code honestly takes that long and anyone promising otherwise has not read it. We would rather set that expectation than quietly miss an early deadline. If the existing system has problems we think are serious, we will say so plainly and separate what must be fixed from what merely offends us.

Launch is when software starts being used, which is when the things nobody predicted begin to appear, so we treat the period after it as part of the work rather than as an upsell. What that looks like in practice is agreed before launch, not after: who is on call, what counts as an emergency, what response time you are actually buying, and what sits outside support and will be quoted separately. Vague support promises are easy to make and worth very little when something breaks on a Friday evening.

Small enough that we will sometimes tell you not to build it. If an off-the-shelf tool does ninety per cent of what you need for a fraction of the cost of custom work, saying so costs us one project and is the reason the next one arrives. Where custom development genuinely pays is where the process is specific to how your business works, where an integration does not exist, or where you are building something you intend to sell. Describe the problem rather than the solution you have in mind, and we will tell you which of those applies.