# Can you build an internal tool around the way our team actually works? Canonical URL: https://newphysician.org/can-you-do-this/build-an-internal-tool/ Yes. The useful design starts with the work and its exceptions, not with a generic dashboard. An internal tool should make ownership, next actions, and the current state clearer while reducing repeated entry and dependence on one person's memory. What a solution might involve Observe a complete item moving through the process. Define roles, states, required information, and exception routes. Build the smallest useful workspace, then add permissions, search, change history, and exports that let the organization retain control of its own records. What needs care Automating a disputed process can harden the wrong rules. Conflicting definitions, unofficial approvals, and missing owners should be resolved before code enforces them. Sensitive information needs an explicit access model and retention decision, not a hidden spreadsheet copied into a database. How we would judge whether it works A routine item and an exception both reach the right owner. Staff can find the source of a decision, recover from a mistaken entry, and continue when the usual operator is away. The tool has a named operational owner. Likely engagement Business Engine: $5,000 to $15,000. This is a likely starting tier, not a quote. Scope, access, dependencies, and responsibility for operation need agreement first. Discuss Business EngineWhat to send first Share a redacted example, the people involved, and the steps that currently require chasing or retyping. Send me the messy version. Experience and scope Selected builds documents the currently authorized public proof. This page describes a proposed approach, not a claim of a completed client engagement in this exact workflow. Related problems Can you turn our spreadsheet process into a reliable workflow? Can you fix an approval process that keeps work stuck? [Send me the problem](https://newphysician.org/send-me-the-problem/)