THE TAKEAWAY

Look for the repeated work between your existing tools before committing to another platform.

Look for the repeated workaround

Custom software is worth exploring when people repeatedly compensate for a mismatch between the business and its tools. They might combine several records before answering a customer, copy the same data into three systems, or build a fragile spreadsheet to manage an important decision. Write down the workaround and the consequence when it fails. That is a better starting point than a feature wish list.

Separate configuration from a product gap

Sometimes the existing platform already supports the work through better configuration or an integration. Sometimes the process itself needs to change. Compare those options before building. A custom app makes more sense when the workflow is distinctive, recurring, and important enough to maintain as part of the business.

Prototype the difficult moment

You do not need every screen to test the core idea. Focus a prototype on the action people struggle with today: reviewing an exception, approving a customer request, or understanding the state of a project. Put it in front of the people who do the work. Their questions will reveal missing context faster than a long feature specification.

Include the operating responsibilities

A production application needs more than its happy path. Plan ownership, data access, error recovery, support, and changes to connected services. If AI helps with the work, decide how its output is reviewed and what happens when it is uncertain. These responsibilities belong in the scope and budget.

Define success before the build

Choose measures that reflect the task: completion time, error frequency, successful customer actions, repeated use, or avoided manual handoffs. Establish the starting point where practical. The app earns its place when it improves the real work enough to justify the effort of running it.

About this field note

Original MKAIN editorial framework for planning a project. Examples are illustrative, with no claim of measured client performance. Published October 28, 2026; no corrections recorded. Send a correction or question.

Put the idea
to work.

Bring us the customer problem or workflow you want to improve.

Talk about your project