Every project is scoped individually, but most engagements follow a similar structure. This keeps timelines clear, costs predictable, and decisions straightforward.
Most projects begin with a written Statement of Work outlining scope, deliverables, timeline, and total cost. This creates a shared understanding before development starts.
To reserve development time and begin work, an initial deposit is typically required. For most projects, this is approximately one third of the total project cost.
The site is developed using an MVP-first approach. Core pages and functionality are built first, followed by consolidated rounds of feedback to keep progress efficient.
Once the site is ready for public launch, the remaining balance is typically invoiced. This payment is due before the site goes live.
After payment, the site is deployed to the live domain, indexing is enabled, and monitoring is activated. Ownership transfers once the full project balance is paid.
After launch, clients may choose to retain hosting and monitoring, or self-host. Post-launch work is handled as needed and scoped separately.
These are typical ranges for custom site builds in the professional services space. Your actual quote will be based on specific scope and requirements.
| Item | Typical Approach |
|---|---|
| Project fee | Fixed price, defined upfront |
| Deposit | ~1/3 to begin work |
| Final payment | Remaining balance before launch |
| Scope changes | Estimated and approved in advance |
| Service | |
|---|---|
| Hosting & Monitoring | Starts at $60/month (Scales with needs) |
| Large Changes | Quoted separately |
| Small Updates | Billed using a batching model |
Work outside the original scope or included monthly allowance is billed separately.
Smaller updates are typically handled using a batching approach rather than one‑off micro‑charges. Each batch has a minimum billing block, with additional time within the same batch billed at a lower rate.
Estimates are always provided before work begins.
Professional services carry a fixed coordination cost. Even small changes require setup, context, testing, and deployment.
Less administrative time per change.
Efficient time-blocking ensures reliability.
Fewer individual invoices to manage.
Clients who group related updates generally see better outcomes and lower overall spend than those requesting isolated changes.
The process is designed to be transparent, and predictable. Exact structure may vary by project, but billing and scope are always discussed upfront, in writing, before work proceeds.
Start a Conversation