01

Describe the problem before naming features

Break “we need a system” into specific problems: who enters the same information twice, where progress becomes invisible and which mistakes recur. Follow one real piece of work from beginning to end, noting the tools and information used at each step.

02

Check mature tools first

Standard booking, task management or customer communication may already have suitable tools. Look beyond subscription prices to user limits, data exports, language support, permissions and connections to software you already use. Configuration can be more appropriate than custom development.

03

Find the workflow that is genuinely different

A stable, important process that common tools cannot support naturally may justify custom work. If your business rules change every week, narrow the scope and clarify the process before committing to development. Software cannot decide a business policy for you.

04

Compare the full investment

Custom software involves discovery, development, testing, migration, training, hosting and maintenance. Packaged tools also carry configuration, migration and learning costs. Compare the total over the same time period rather than the first invoice alone.

05

Begin with a complete, useful workflow

A first release should let real people accomplish something valuable, such as creating an order and following its status. Necessary permissions, exception messages and exports matter. A collection of attractive demonstration screens is not the same as a usable workflow.

06

Agree on data and handover

Know who holds the accounts, how data is backed up and exported, and how work continues when people change. Custom projects should also define the source code, deployment, documentation and support handover. These decisions matter before launch.

The reason to build is not “more features”. It is a well-understood workflow that can meaningfully improve everyday work. Validate that workflow, then expand.

Discuss your project