You will be assigned a dedicated project manager, who will be your primary point of contact throughout the development process.
All of your requests and questions are managed through our support portal, to ensure we give you a swift response, and your work is prioritised appropriately. We also offer a range of support and maintenance options to ensure we are responsive to your requests after the launch date.
You can read more about our project management process in our answer to "How will you project manage my project (e.g. AGILE, Waterfall, etc)?".

Many factors contribute to launching a successful project, and some requirements may result in the project taking longer to develop than others. However, for estimation, a good guide is that a project will typically take one month for every £5k (+vat) of development work.

In some cases yes, in others, no.
Can nine women deliver a baby in one month? This analogy can be applied to tech projects too.
Sometimes, by dedicating more developer resource to a project, it can be completed much faster. But in other situations, we may be restricted by the project, technology or security requirements.
If you have a date requirement, contact us as soon as possible so we can do our very best to meet it.

Yes, we offer the option to engage us on an ad-hoc basis for support, or have monthly retainer options should you require a more consistent and reliable level of service.
Ad-hoc support can work for projects that need minimal support as to avoid the need for fixed ongoing monthly costs. However, this can be at the expense of responsivity as requests are scheduled based on when our resource is available.  Most of our clients choose to have at least a small monthly support retainer to get the best responsivity, as dedicated time is scheduled months in advance. If you have a highly technical project with us, then we would recommend opting for a monthly support retainer to cover small ad-hoc changes, improvements, updates and support.
We base our retainer pricing on the amount of development and support hours you need each month. The number of hours that you need depends on many factors such as the size of your project, or the number of new features you are likely to need each month that you’d like to be covered by your retainer arrangement. It’s important to us that you get value-for-money so we’d recommend putting together a nice-to-have list so that your allocation is used each month on value-adding improvements.
Should you have ongoing project requirements beyond the launch of the first version of your website or app, then you may want to consider taking an AGILE approach to your project and have an ongoing retainer arrangement with us that allows us to build, test and deploy larger new features every month. Under this agreement, we would have a retainer allowance which pays for enough time to develop significant new features. At the start of each month, we would agree on the work that is going to form part of the next sprint (i.e. the next 2-4 weeks) and would deliver the work at the end of that period. Read more about AGILE v.s. Waterfall with our answer to "How will you project manage my project (e.g. AGILE, Waterfall, etc)?".
Clients who favour AGILE, typically understand that we need to perform significant amounts of work over the coming months, but they might not know when they need what feature, or if the requirements will change. It’s common for start-ups to go AGILE, as the way that users engage with the product once it launches can have a significant impact on which features or changes need to be prioritised, or may give light to new high-priority changes that would be difficult to predict before launch.

Yes, in fact, we highly recommend that you begin by launching the simplest possible version of your vision first and continue to adapt it over time. This staged approach is called launching a "minimum viable product" (MVP).
  The idea behind launching an MVP is that you’ve inevitably made assumptions, and you can’t test these assumptions until you release something to the world. By releasing a lean first version, you can test your assumptions and use this information to decide on the priorities of future requirements. It reduces engineering waste.
We have some options around making future changes to your app or website.
You can either commission us to update your app or website on a project-by-project basis, whereby we specify, quote, schedule and finally deliver a fixed set of requirements as-and-when you need them. Or, we can take an AGILE approach whereby we schedule in a certain amount of developer time each month to constantly improve things for you. Both approaches have merit, and it’s likely that you will know instinctively reading this as to which is right for you.

We like to use open source languages wherever possible with HTML, CSS and JavaScript on the front end, and JavaScript or PHP on the back end. We use React Native for most mobile app projects, but will sometimes use Cordova or PhoneGap should we be working within tight budgets or need to support web, Android and iOS quickly.
For web apps, we use frontend layout frameworks such as bootstrap, foundation, material and SemanticUI in combination with front-end code frameworks such as React or Angular. On the back-end, we usually use a PHP framework such as Laravel or Yii2, with the occasional project in NodeJS.