How do you scope and estimate a custom development project?
How requirements become a fixed scope, a timeline, and a number you can plan around.
Scope comes from discovery, not from a wish list. We document the current process, define the new one, inventory the systems and data involved, then size the build in phases so the first release is genuinely usable. A firm number before that work is a guess.
What discovery actually covers
- The current process, step by step, including the spreadsheet somebody maintains by hand. That spreadsheet is usually the whole project.
- Who does what in the new process, and what each role needs to see and not see.
- Systems and data: every platform involved, what it holds, whether it has an API, and which system is the source of truth for each field. Two systems both claiming to own a record is the most expensive thing to discover late.
- Volume and timing. Records per day, whether sync needs to be real time or nightly.
- What happens when it fails, and who needs to know.
- The definition of done. The specific outcome that means it worked.
Why estimates before discovery are unreliable
Nearly all the risk in a custom build sits in things nobody mentions on the first call: an undocumented legacy field, an API that does not expose the object you need, a permissions model that cannot express your approval rules, a data set that is messier than anyone believes. An agency that quotes a firm price in the first meeting is either padding heavily or planning to renegotiate later. The honest sequence is a small paid discovery, then a scope and estimate you can actually hold someone to.
Phasing, so you get value early
Break the build so that phase one solves the most painful part and goes live. Real usage tells you what phase two should be, and that is almost never what the original wish list said. It also limits what you lose if priorities change. Resist the version that requires eleven months before anyone touches it.
What it costs
Custom work is scoped per project, so we do not publish a single number, because a price for an unknown scope is not information. Ongoing and smaller work runs on published retainer rates on the retainers page, including flexible digital support at 10 hours for $1,900, 15 for $2,775, 20 for $3,500 and 40 for $6,750 per month, and HubSpot technical support at $195 per hour. To scope something, contact us. Background on how developers think about this is in this post.
Related: Does LevelUp Digital build custom web applications?. How long does a custom integration project take?. What is a custom API integration?. What infrastructure do you use for custom integrations?.