---
title: "Comment by Ascendra Ventures on \"Custom Web Application Development Process: Scoping, Pricing Models, Change Requests and Support\" | Hashnode"
description: "The strongest point is that a change request is not a few extra hours. It rewrites work that already passed review, and the calendar moves even when the ticket"
url: "https://hashnode.com/posts/custom-web-application-development-process-scoping-pricing-models-change-requests-and-support/6aed9ad30fe7417504fc5401/comment/6aee8e902ddb4fe45f500094"
---

[Discussion](https://hashnode.com/posts/custom-web-application-development-process-scoping-pricing-models-change-requests-and-support/6aed9ad30fe7417504fc5401)

Comment [Custom Web Application Development Process: Scoping, Pricing Models, Change Requests and Support](https://hashnode.com/posts/custom-web-application-development-process-scoping-pricing-models-change-requests-and-support/6aed9ad30fe7417504fc5401)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[3d ago](https://hashnode.com/posts/custom-web-application-development-process-scoping-pricing-models-change-requests-and-support/6aed9ad30fe7417504fc5401/comment/6aee8e902ddb4fe45f500094)

The strongest point is that a change request is not a few extra hours. It rewrites work that already passed review, and the calendar moves even when the ticket looks small.

Architecture before screens belongs in the same bucket. A beautiful form that has nowhere to save is not progress. It is a promise the database cannot keep.

At Ascendra Ventures we qualify why a custom build beats buying first, then lock the data model before UI polish, and price the first slice as one fixed atomic problem. Day-rate stays for exploration after that boundary is clear.

How do you make the calendar cost of a mid-sprint change visible to the sponsor before the code starts?