Building an Internal Tool: What to Ask Before You Commission Custom Software

Commissioning an internal tool — a dashboard, a portal, a system that ties existing tools together — is a meaningful investment, and the businesses that get real value from it almost always asked the same handful of questions before writing a brief.

What Specifically Isn't Working Today?

"We need a better system" isn't specific enough to build anything useful from. The businesses that get the most value start by naming the exact moments the current process breaks down — a manual step, a data mismatch, a report that takes half a day to compile — and build outward from there.

Who Will Actually Use It, and How Often?

A tool built for daily use by the whole team needs a different level of polish and speed than one an admin uses once a month. Being honest about actual usage prevents overspending on features nobody will touch and underspending on the parts people will rely on constantly.

What Does It Need to Connect To?

Internal tools rarely live in isolation — they usually need to pull from or push to your existing CRM, accounting software, or ecommerce platform. Knowing these integration points before development starts avoids expensive rework later.

What Happens When It Needs to Change?

Your business will change after the tool is built. Ask how easy future changes will be, who owns the code, and what ongoing support looks like — a tool that can't evolve with the business becomes tomorrow's version of the spreadsheet you're trying to replace.

Answering these honestly before a single line of code is written is what separates internal tools that get used every day from expensive projects that quietly get abandoned. It's the first conversation we have on every internal tools project.