Hire only after you can describe the business problem, the people affected, and what a better process should accomplish. You need clear operational context, not technical specifications.
Look for workflow understanding
A capable provider should ask how work moves through the business, where information lives, which exceptions matter, and who can approve decisions. A polished portfolio is useful, but it does not replace the ability to understand operations.
Ask questions that reveal responsibility
The proposal should make ownership, security, testing, support, and outside-service costs understandable to a nontechnical owner.
- What would you exclude from the first version?
- How will access, backups, and sensitive data be handled?
- What happens when an integration fails?
- Who owns the code, data, domain, and service accounts?
- How are changes estimated after launch?
Watch for avoidable red flags
Be cautious when someone promises a precise price without understanding the workflow, dismisses testing or maintenance, uses accounts the business cannot access, or recommends custom software before considering established products.
Common questions
What small-business owners often ask
Should I hire a freelancer or an agency?
Either can work. Compare who will actually do the work, continuity, communication, process, security practices, and the support available after launch.
Do I need a technical specification first?
No. Bring the workflow, examples, users, problems, and desired outcome. A good provider can help translate those into a scope.
Who should own the software accounts?
The business should retain appropriate access to its domain, hosting, data, integrations, and other critical services, even when a provider administers them.
KindBuilt can help you determine whether a focused internal tool makes sense.