Get familiar with the three most common types of "apps" that can be built for smartphones and laptops.
Working with a software consultancy (often called a "dev shop") can feel a little intimidating for non-technical clients. Learn about the most critical elements you should cover in every contract.
"It's just an iPhone app with five screens, what will it take so long?!" Why are software timelines so mysterious?
Congratulations! You've selected a developer to build your app, and the contract signed. What do you do next? How do you ensure that the app that's being built on your behalf is in fact the app that you will need.
There are two popular approaches to contracting with a "dev shop" or software consultancy. The most common option is an hourly rate, also known as “Time and materials.” The other, less common offering is "fixed price" or "fixed bid". In this article I'll summarize the highlights of each.
For a long time, I only signed "time and materials"-based contracts, but have since switched to exclusively doing fixed-price work. In this article I highlight the key reasons why I prefer fixed-price contracts, and why you should insist on them from your dev shop, too.
It's been said that "it's easier to learn than to unlearn." Beliefs formed from a bad experience become calcified and make it harder to work with a new team the next time around.
A brief glossary for non-technical folks embarking upon technical projects for the first time.
When you're faced with choosing a software development consultant or "dev shop", it can be hard to know where to start. In this post I cover the most important things you should know before you pick up the phone.