Yes. Most projects start that way. Walk us through where the work gets stuck, or where the tool you are using falls short. The first call is about the problem, how it works today and who it affects. The plan comes after that.

Usually. Most business software can be connected, and one of the first things we do is check what yours allows. Where something will not connect properly we will say so early, because that changes what is worth building. Keeping the tools that already work is almost always cheaper than replacing them.

We agree the scope and the cost of a stage before that stage starts, so you are approving a number you have already seen rather than finding out at the end. If priorities change part way through, that changes the next stage rather than the whole project. Some builds are complicated enough to be worth scoping properly first, and we will tell you if yours is one of them.

What we build for you is yours, and the agreement sets that out in writing before the build starts. Most systems also run on third party platforms and licensed components, and those keep their own terms. So rather than one blanket answer, the agreement says exactly what transfers to you and what is licensed.

You get handover documentation and time with your team so they can use the system properly. After that it is your call. Some clients want us involved on an ongoing basis, some want us only when something needs changing, and some take it in house. We agree which of those it is before launch rather than after.