Choosing the technology for a project requires balancing proven software and tools against cutting edge offerings. The former have a track record of success, while the latter come with promises of an efficiency boost. We try to gain the best of both worlds by selecting a single area in the project to fold in new technology and building the rest of the project on a proven platform.

This approach limits the project’s exposure if the new technology turns out to be hype that can’t live up to the reality. Just as importantly, it let’s us embrace new technology so we can keep our development process as efficient as possible.

In future phases of the project we re-examine the new technology we used and determine if it has earned a place among our preferred tools, or if it should be avoided in the future.

The majority of our server side code is developed in PHP. To some, PHP is a crufty old programming language that lacks features new languages bring to the table. We’d challenge that opinion. PHP has been well maintained, and the style that we develop software in utilizes its modern enhancements. More importantly, when we develop in PHP we can be confident that there is a large ecosystem of programmers who can maintain and improve the source code should you decide to have a firm, other than Ideas2Executables, work on your code.

In short, we treat the custom software we develop for you as an important asset to your company. We want that asset to be something you’re happy with and can benefit from for many years to come. We believe PHP and other well established technologies help to ensure this goal.

We have developed a wide range of software, from the plugins that power a tech blog, to video education platforms to a simulator to help a professional gambler. And yet, we have never built games. While we are open to the possibility of developing games in the future, we don’t have any experience in this area and would therefore most likely not be the best firm to develop your game idea.

Yes, we are generally glad to sign an NDA before you tell us any information about your idea. One exception to this is when an NDA contains a non-compete clause. We are unable to sign an NDA in this case. Frequently, we strike non-compete provisions and are able to agree to the rest of the document without concern.

Yes. You absolutely own the software that you have paid us to develop. You may do anything you wish with this software, from giving it away for free, to selling it to another party. We retain no rights to it. If a future customer approached us with a similar idea, we would recommend they contact you to purchase rights to use your software.

When we develop software, we look at the final product as an important asset that we strive to make as valuable and robust as possible.

While we are always glad to offer advice on marketing and SEO, we recognize that like other aspects of running a successful software business, we are not experts in these areas. Therefore, we don’t offer any paid services on these topics. We love to code, so that’s our exclusive focus.

No. Small projects are often a great way to get started. They are a low risk way to ensure that your organization and Ideas2Executables can smoothly work together to accomplish the task at hand. We often fix small bugs or may write a small plug-in as an introductory project.

Yes. We split projects into manageable phases through a process known as iterative development. You, in the role of project owner, have the ultimate say of what features go into a phase. Though this doesn’t happen often, it is possible that you may request a number of features that make the project size larger than we’re comfortable working with.

As you can imagine, project cost varies widely depending on the software that needs to be built. As a general guide, we split the implementation of an idea into separate projects through a process known as Iterative Development. Each development phase is typically between $10,000 and $20,000 USD.

When we work on existing code, work is done at an hourly rate, which we can cap to avoid a surprisingly large bill.

Our services have a fee, so we can’t build software for you for no charge. However, we frequently talk with individuals at the start of their idea journey before they have the funding figured out. We can recommend zero-dollar steps you can take to start building out your idea. Send us a contact-us message and we’ll be glad to setup a time to chat with you.

No. One of the key reasons for this decision is that we find it essential to have a clear owner of the project: you. While we always provide recommendations for how a project could proceed, you have the final say. Structuring the ownership of the idea around this methodology helps draw clear lines for us to follow.

We do agree that bringing in other stakeholders to fund a project can be an excellent way to build out an important team that will provide both financial and strategic support.

We split an idea into projects through a process known as Iterative Development. A project typically takes anywhere from a couple of weeks to a couple of months depending on the work needing to be completed.

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.