Articles on building business software: custom applications, choosing a development partner, and the decisions that shape a project before code is written.
2 articles · Latest
Custom software is built around one organisation’s processes, users and systems, rather than adapted from a product designed for a general market. It makes sense when core work depends on workarounds, disconnected tools or manual steps that a standard product cannot remove.
Most of a project’s success is decided before development starts: understanding the problem, who will use the software, which systems it must connect to, and what the first useful version needs to do.
Short answers to common questions in this area.
Designing and building software for a specific organisation’s workflows, users and systems, instead of configuring an off-the-shelf product.
When existing products force workarounds for a core process, cannot integrate with the systems you rely on, or the process itself is what sets your business apart. For standard needs such as email or accounting, an established product is usually the better choice.
A description of the problem, who will use the software, the systems it needs to work with, and a rough budget and timeline. A complete specification is not needed to start.
Yes — internal systems, portals, SaaS products and business applications, from planning through production.
Custom software development
