The buyer's guide
The Guide to Hiring Custom Software Development — Written by the Vendor Side, So You Can Hire as an Equal
We have sat on the vendor side for over 10 years and seen projects end beautifully and fail before they began. Nearly all the difference is set by what the buyer does before signing and at acceptance. This guide lays out the six stages worth walking, each with its deep-dive article — useful whether you hire us or anyone else.
The six stages
Hiring custom software development, professionally
Every stage has its own in-depth article. Read the one you face now, or the whole path before you start searching.
Define the problem before defining the system
Most failed projects begin by commissioning the system in someone's head without ever walking how the work actually runs and where it hurts. Walk the real process once first, then decide what to build — the answer is often much smaller than expected.
Write the TOR from outcomes, not feature lists
The one document that decides the project's fate: precise about outcomes, flexible about method, a testable acceptance criterion on every item, and source-code ownership stated from day one.
Select the vendor, and read the quotations properly
Good vendors ask sharper questions, visit the floor, and push back on scope. The warning sign is the unusually fast quote far below everyone else with no questions asked — the cheapest price on signing day tends to be the most expensive after rework.
A contract that phases payment and protects ownership
Installments tied to actual acceptance, not calendar dates. Source code and data belong to you, exportable in standard formats, with handover terms if the caretaker ever changes — a good system must outlive whoever built it.
Accept through UAT built from real work
Make your hardest month the exam, put the real floor staff at the keyboard, triage defects by severity, and accept phase by phase — before the big payment and all your leverage leave your hands.
Go live with a plan, then maintain for the long run
Launch day needs an hour-by-hour plan, rollback criteria, and a hypercare period stated in the contract. After that comes ongoing care with explicit response times — an unmaintained system decays every day with nobody watching.
FAQ
Common questions before hiring development
What does custom software cost?
Small web systems start in the high tens of thousands of baht; mid-size business systems run hundreds of thousands to millions. The drivers are logic complexity, integration count, and the quality of the brief. A clear TOR genuinely lowers the price, because vendors stop pricing in uncertainty.
How long does it take?
Small systems run one to two months; mid-size systems three to six when delivered in phases. The biggest variable the buyer controls is decision speed — having someone with authority available to answer the development team's questions every week.
Who owns the source code?
You should, always, once the contract is paid — with data-export rights in standard formats and handover documents. It belongs in the TOR and contract from day one. At Whale Task we hand over code and ownership to the client. No lock-in.
How is this different from buying off-the-shelf?
Off-the-shelf is faster and cheaper when your work resembles most businesses. Custom pays off when the process that wins you customers exists in no standard system, or when accumulating yearly licenses outrun development cost while the fit still is not right. Good answers usually mix both.
Already have a project in hand?
Send us your draft TOR for a free review — or talk to us before any document exists and we will help frame the problem first. No commitment.
Free consultation