Frequently asked questions

Both have pros and cons, for example, mobile apps cost more upfront but can be available offline. It really depends on the problem you are trying to solve, and whether a mobile app is the right solution for your users. You may even need both. We should talk and work it out.

The most important thing is knowing what you want to achieve with your application. Who are you building it for? Why do they need it? What should it do? Preparing a basic brief is a great way to get your thoughts in order.

Not at all. We welcome your input and ideas if you have technical expertise but we are here to guide you through the process at whatever level suits you.

That depends on the application, but we usually find we can give you a rough idea quite quickly. We also try to limit the size of an initial phase of development so that you can get it out and into the hands of your customers before investing too much time and money, with no feedback.

We’ll work with you to define the scope and requirements of your project from the start, so we’ll be able to tell you within a few weeks roughly how long it will take.

We have a lot of processes in place to guarantee quality. This involves developer reviews, unit testing and quality assurance testing. We test each feature and each functional area, and re-test when we make changes to that part of the software.

Yes of course! We like to work closely and in partnership with our clients. This allows us to be reactive to your requirements and to keep you up to date on what we are doing.

We’ll get the application into production. You can host it yourself or we can do that for you. We can also provide on-going support for issues encountered whilst the application is in use. We’ll agree a reasonable amount of support time based on the requirements of your application and we’ll give you regular updates on how much you’ve used.

Yes, as part of our design process we will build a hi-fidelity UX simulation, which will allow you to test the functionality we are planning to develop and to provide feedback, before we develop it.

You should consider the long term costs, like hosting on Azure or AWS, support, future changes, upgrades to technology and releases.

In terms of other costs, you should bear in mind what you might need to do in order for your application to succeed, for example, launching the product, PR, marketing, branding, user guides and documentation.

Of course, we will provide regular recommendations on upgrading your software. You should bear in mind that you might need to perform minor upgrades every few months and you are likely to need a significant upgrade every 2-3 years to ensure your application is up to date in terms of security and best practices.

No. You might be tempted to consider every eventuality and option but you are better off concentrating on key features that solve key issues for your users. This will enable you to deliver a small and defined MVP and allow you to move on to those nice-to-have features at an earlier stage.

Having an in-house software development team can be a great idea. However, recruitment can be time-consuming and costs are high. If you need to get started right away, then using a software company like ours can be a more cost effective alternative. You can just use us whenever you need us.

All our development work goes through our SCRUM process, this means that you can rely on your work being delivered as part of a two week sprint. It also means that we don’t ring fence developers to specific projects, so you aren’t dependent on specific individuals for the development of your project. You have access to our entire team of experienced developers.

We work closely with you throughout your project, so you aren’t likely to need much training. However, we can provide demos and training to team members outside the project group when required, either as part of user acceptance testing (UAT) or after launch.

Most of our customers prefer to write their own documentation and guides as they have the best understanding of their user base. However, we can support you in creating that documentation if it’s something you need, just let us know.

By default, because we have written the code, we will own the IP. However, we understand that this is your idea and your product, and we will happily include a deed of transfer in your Master Services Agreement to ensure that ownership of the IP ends up with you.