Yes, we absolutely fix bugs in software we didn’t originally author. About half of our customers fall into this category, so let’s talk.

Yes, we install the software we build. This includes uploading mobile applications to the relevant stores. We don’t consider a project complete until your end users are successfully using the software.

Software maintenance is an essential part of our development process. We break the maintenance phase down into three parts: bug fixes, small enhancements and large enhancements. We fix bugs that arise from a fixed price project for no fee, regardless of when you find them. If you discover a bug in our software two years from its release, we’re glad to fix it free of charge.

Enhancements correspond to improvements that are not covered under the original project. We split those into two groups: small and large. For small enhancements, we identify an hourly rate at the launch of a project and any changes you want made to the system can be completed at that rate. Having a predetermined hourly rate allows us to react quickly, making small improvements in an optimal amount of time.

Finally, nearly all software requires regular, significant improvements to stay viable. We handle these larger improvements as their own phase of project development. This typically involves coming up with a new fixed price development plan and then executing this plan.

Some firms charge a retainer or monthly fee for maintenance. We never do this. There will be no charge by Ideas2Executables until you request changes to the software.

No. We often develop software that is not used by the general public. Writing custom software that’s used just by your organization can be a smart way to give your team a competitive advantage. This software has the advantage of not needing the polish that public software looking to attract customers requires. Internal software is all about being efficient, and custom software’s ability to meet your precise needs can thrive in this area.

‘Iterative Development’ is a fancy way of saying that we take a large idea, split it into pieces, and complete each of the pieces in sequence. Iterative development is one of the core strategies we use that helps to deliver successful projects.

MVP stands for ‘Minimal Viable Product.’ It’s the first version of the software that you develop. A well architected MVP has many advantages: it can be cost effective, relatively quick to market and most importantly, it can put you in a position to learn from your customers to help determine what features should be built next.

We can use existing software as inspiration and develop code that behaves in a similar way. What makes our customers successful is when they innovate, bringing new features to market. We would urge you to reconsider your strategy if all you intend to do is to create a duplicate piece of software that’s already on the market.