Before you hire a software developer: define the work first

Start with one real example

Choose a recent task: collecting an application, preparing a report, tracking a coaching action, or coordinating a handoff. List who starts it, what information they provide, what happens next, and how the team knows it is complete. Record the exception cases, not just the ideal path.

Replace “we need an app” with a concrete goal such as “staff need one place to see which requests are incomplete and what follow-up is needed.” This illustrative goal leaves room to evaluate an existing tool as well as a custom build.

Prepare a brief before comparing providers

• The people using the system and the decisions they need to make.
• The current workflow, including delays and duplicate entry.
• The information required and where it lives today.
• Existing tools that must stay in use.
• The smallest useful first release.
• A budget range, deadline, and decision owner.

Use fictional or redacted examples during initial discussions. Confirm appropriate handling before sharing personal or confidential records.

Ask for an approach, not just a price

Ask each provider how it will clarify requirements, show a working prototype, test the important workflows, and handle changes. Compare what is included in the quote: design, development, data work, deployment, training, and support may be separate items.

Ask who will control the domain, hosting, accounts, and source code, and how your organization can export its information. Those terms belong in the agreement, not in assumptions made after the build.

Contact NovaPath while the question is still open

You do not need a technical specification to start. Describe the task, the friction, and the result you want. NovaPath can discuss whether the next step is clarifying the workflow, evaluating an existing tool, or scoping custom software.

An initial inquiry starts that discussion; project recommendations, fees, deliverables, and timing are established through scoping.