When starting a new software project, there are a series of questions that need to be explored before diving headfirst into the development cycle. At Atomic, we often spend time in what we call the “Research, Design, and Planning” phase of the project to do just that.
I’ve been selling custom software projects for nearly a decade. In my opinion, the most important part of the sale is correctly setting the client’s expectations for the design and development journey that’s in front of them. A key expectation to align on is the engagement model. Over the past few years, I’ve been describing […]
If you’ve worked with other custom software companies, you’ll notice that Atomic’s approach to budgeting is unique. It’s a lot more time-intensive and comprehensive. In fact, when I deliver a budget model to a customer who is comparison shopping, they often tell me something like, “This is the most comprehensive analysis I have seen from […]
One factor that determines the success of product development is how much value customers get from the product being built. This is why I’m a proponent of surveying customers before, during, after product development.
When clients first contact us about building a mobile app, they often wonder if they should build separate native mobile apps for both Android and iOS platforms, or if they should use a cross-platform framework. In the past, cross-platform frameworks have gotten a bad rap, and for good reason. They were slow, they didn’t look […]
These days, most companies are expected to have some sort of digital or connected solution. Even industries that have been paper-based or seem removed from connected solutions are feeling pressure. Their executives may think they need a solution, but what should it be? And how do you determine if software is the right solution?
Over the years, I have seen business people and stakeholders become frustrated with the teams who make custom software for them. It’s understandable! Few people have any preparation for their first custom software project. They dive in with enthusiasm and subject matter expertise. Sometimes, it goes great. Sometimes, it goes poorly. I believe that the […]
Sometimes, an engagement doesn’t go according to plan, and it’s a good idea to agree on what to expect if this occurs. Custom software contracts commonly define how to fix a situation if expectations aren’t being met, and they may also define rights for terminating an engagement.
Custom software services contracts should call out the promises you and your partner make to each other. The contract should also define who will be responsible, and to what degree, if certain issues arise.
Custom software contracts need to be clear about intellectual property rights—the ownership and use rights for each component in the final product. A software product can have some components that are custom, some that are open-source, and others that are commercially licensed. And each can have separate IP rights.