How much does it cost to build an app? What the figure doesn't tell you
How much should you budget to build an app? The figure alone is not enough: aim for a goal rather than a feature list, with users from the first month.
We develop your sales team’s bespoke CRM, usable within a month, on a fixed monthly budget, and keep adjusting it as the way you sell evolves.
A CRM is a back office: it brings together your customers and your prospects, with the history of your exchanges and what remains to be done for each of them.
A bespoke CRM is built around the way you sell, and it evolves when that changes.
A CRM is a business application. If it is the running of your business (orders, stock, invoicing) that you want to equip, see our page on bespoke ERP systems.
Part of your business runs on software you will not replace, such as your accounting or invoicing package. Your CRM can connect to it, so that the same information is entered only once and stays consistent from one system to the next.
If the CRM you use today needs to be taken over or rebuilt, see our page on taking over and modernising an application.
If an off-the-shelf CRM fits the way you sell, and its vendor makes the adjustments you ask for, it remains the simplest choice.
In a CRM, everyone sees where their sales proposals stand and what remains to be done for each one.
In a CRM, each person should see only the customers and cases that concern them. The server checks their rights at the entry point of every route.
A CRM stores the personal data of your prospects and your customers, and the GDPR governs what you collect.
In a CRM, everyone is alerted before a follow-up or a contract renewal, as far ahead as they choose.
Your CRM evolves without losing its business rules: its calculations and its special cases are checked before every change.
We start by talking with the users of your application, to understand their needs. From those needs, we specify each feature, then we develop it.
We test and sign off every feature before it goes live. If you would rather not delegate this, you test and approve it yourself.
What has been tested and signed off goes live. Every day, you see the application move forward on your acceptance environment.
The users of your application work with it from the first month of development, and how they use it determines the next feature or features.
For a Dutch manufacturer of safety footwear, we worked on this migration: Ember.js 2 to 3 in Octane syntax, Symfony 2 to 4.
The budget is built with you, from your numbers and your objectives: together we set the amount and the problem your application has to solve. Your application is usable within a month of development. From then on, the budget covers its maintenance and evolution for as long as you want, so that it keeps adapting to your business. Invoicing is monthly and fixed, with no surcharge for licences or number of users. You know your exact spend before you start.
The source code, infrastructure, deployment pipeline and documentation are your intellectual property once the first monthly invoice is paid.
The zero-regression guarantee applies from day one. If an accepted and approved feature starts behaving differently after a change, we fix it at no extra cost and we lock the behaviour with an automated test so it cannot come back.
You can terminate the contract in writing at any time, without justification. During the reversibility month, we support your team until they can build, test and deploy without us.
The budget is built with you, from your numbers and your objectives: together we set the amount and the problem your application has to solve. Your application is usable within a month of development. From then on, the budget covers its maintenance and evolution for as long as you want, so that it keeps adapting to your business. Invoicing is monthly and fixed, with no surcharge for licences or number of users. You know your exact spend before you start.
A bespoke CRM makes sense when no product on the market follows the way you sell, or when its vendor does not make the adjustments you need. In other cases, the existing product remains the simplest option.
Yes. We start by gathering the access and deploying the application to an acceptance environment. We then write tests for the journeys its users depend on, before making any change. If there is documentation, we read it.
Yes, as long as that software offers a way to exchange its data, most often a data exchange interface (API). That way, each piece of information is entered only once and stays consistent from one system to the next.
Your application is usable within a month. After that, we adjust it as your business evolves, for as long as you wish.
The source code, infrastructure, deployment pipeline and documentation are your intellectual property once the first monthly invoice is paid.
In the first month, the first 15 working days are a trial period. Delivered features are accepted as they come in, by you or by us if you delegate acceptance to us. If you do not want the deliverables and do not wish to continue, no invoice is issued and you owe nothing. If you want your application in production before the trial period ends, you can ask us in writing: we issue the invoice for the days worked, and we release to production once it is paid.
No minimum commitment duration. You can terminate the contract in writing at any time, without justification.
Thirty minutes to understand your situation. If we can help, a second meeting takes place within 48 hours to build the quote together.