Yes, we can.
Before we begin your project, we work with you to write a detailed project specification and then provide you with a fixed-price quote to deliver the work. This fixed price and specification protects you: you can hold us accountable to deliver exactly what has been put to paper, for that exact cost. No hidden charges, no sneaky fees, everything is clear and concise
A fixed price and accurate specification may take a commitment of time from yourself, and Appsido, to reach. Before that commitment is made, you may appreciate a ballpark quote. See below.
Get a free quote >

Yes, we will always try and give you a ballpark, or approximate, price as early as possible; normally on your first call or email. Having a rough idea of expected costs as soon as possible helps you to qualify whether your what you have in mind is commercially feasible and if you would like to investigate further.
Ballpark estimates are educated guesses based on our experience, so please remember that the actual final cost may go up or down as we take the time to explore your requirements in more detail. The more information you can provide us with about what you need, the more accurate our ballpark estimate is likely to be.
Get a free quote >

Talk to us. If you share your idea via this form, one of our team will respond within one working day by email or phone.
If you’d prefer to speak to us right now, call 961 3989420 and one of the team will talk through your ideas and project.
We never hard sell, all calls are without obligations, and we’re always happy to help.
Tell us about your idea > Get a free quote >

Yes, most of the apps we make support both iOS and Android mobile platforms. It’s common for people to want their applications to work across web and mobile devices, so we use development frameworks such as React and React native that enable us to quickly support both platforms.

Yes, in fact nearly every mobile app that we build also needs a web based application behind the scenes to drive it. Ever logged into an app? There is a web server in the background serving the app with data that is checking whether you have permission to log in, or not.

We don’t just blindly begin building your requirements; we start by having a meeting to understanding the commercial factors that are driving the need for your project. We want to get to a position very quickly where we know enough to challenge you on the assumptions you’ve made about the features you require.
Once we understand your business, we go to lots of effort at the start of a project to work with you and scope out your requirements in detail.
You don’t just want us to tell you that we understand your project, we need to prove it to you. This is why we will often create a 10+ page requirements specification, with wireframes where appropriate, before we design a single pixel, or write a line of code.

Yes, you will be assigned appropriate copyright or licence rights for the bespoke code that we write for your project. We are transparent with intellectual property rights, and you will have the opportunity to review our code ownership terms before the project begins.

Many factors contribute to launching a successful project, and some requirements may result in the project taking longer to develop than others.

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 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 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.

Yes, in fact, we highly recommend that you begin by launching the simplest possible version of your vision possible 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 mobile app projects.
For web apps, we use frontend layout frameworks such as bootstrap and foundation in combination with front-end code frameworks such as React. On the back-end, we usually use a PHP framework such as Laravel, with the occasional project in NodeJS.

We start by creating a central database that will hold all your data; we then put in place an interface (an API) to allow the web and mobile apps to send and receive this data.
Think an API digital version of a drive-through burger restaurant. If you ask the teller for a burger, then you'll get given one from the kitchen. Ask them for a trampoline and tell you that they don't sell that product. When we build a connection between your web app and your mobile app, we will configure these rules but based on the functionality of your system.

Yes, we specialise in highly bespoke projects, and it is common for us to work with existing systems and teams.
When working closely with other suppliers that are relevant to your business, we aim to build a strong collaborative relationship with a focus on cooperation and support for all of those involved.
If these stakeholders are crucial to the success of the project, then we would recommend arranging a call or meeting with them early to explore their ideas and identify how to work around any potential environmental limitations.

Yes, if it’s digital. Most app projects start with creating custom visuals of how the app will look and feel before we start development.
We begin the design process by discovering the value behind your brand, its image and your business as a whole. Once we understand your requirements and objectives, we can engineer a design that is easy to use and performs for your business. I use the word 'engineer' here as good design is more than just pretty pictures, what we build has to work for you. Often this means users that enjoy using the site or app and onboarding processes that are optimised to convert clients.
We'll usually begin the design process by wireframing the various sections of project thinking carefully about the user journey throughout the whole process. Once you're happy with the wireframes and specification will design sharp-looking mockups demonstrating how your app or website will look once built. You'll be given the opportunity to feed back on the look-and-feel and we won't begin coding it up until you are happy and have signed off on the artwork.

Probably, yes. We prefer to follow our own design process if possible as it allows us to deliver the best quality and consistency, but we can be flexible with this.
If your designs are strong and we are confident they will be effective, then yes, we will be able to work with them. If, however, they do not meet our high standards, then we will be honest and recommend that we create the designs for you instead.

We naturally provide a degree of strategic support around your business and marketing plans based on our experience as part of every project, and we can build tools to integrate with your social media or email marketing software. However, we are not an end-to-end marketing agency so don’t write copy or manage your marketing campaigns for you.
If you need strategic marketing, social or SEO support, then we have some trusted partner companies that we work with on a regular basis that we’d be happy to introduce you. If you'd like an intro to one of our preferred suppliers, then please feel free to contact us and let us know what you need.

Yes, we will need your support with testing the project, please.
We have processes for testing and quality assurance, but the way that we think and use your app is different to how you will. You defined the project, and you know what you want better than anyone, so you’ll probably use and interact with what we’ve built in ways that we couldn’t have predicted.
Even if everything works 100% perfectly when we hand it over to you, you will need to check that everything works as expected to sign-off on the work with confidence that we've delivered the project to meet your specification.
Testing and achieving sign-off will require some time investment at the end of a project, and potentially at intervals across the life of the project too – So make sure that you set aside some time in your diary for when it’s needed.

There is a difference between a website and a web app, so this answer will exclusively talk about website content management. If you want to know how we build apps, then please read our reply to “What programming languages and frameworks do you use”.
We use a lot of different content management systems, and each one has its own set of pros and cons. Our usual go-to's are Laravel, NodeJS and Drupal.
Sometimes you may have more advanced plans for your website. You may want user login features with a bespoke dashboard, tools to take recurring payments, or want the option to build an app that connects to your website to populate it with data. If you fall into this category, then you should probably consider us building your site using a development framework such as Laravel or NodeJS ExpressJS.

Please, let us hear it!
Ask Appsido a question >