Skip to main content
Studio planning desk and delivery workspace.
TERMS // PLAIN ENGLISHDEV404 // EDITORIAL PAGE

Clear commercial boundaries make better projects.

These terms explain how Dev404 handles scope, approvals, ownership, and support so there is less ambiguity once delivery starts.

Commercial note

The point is clarity, not hidden clauses.

Delivery runs better when the commercial boundaries are visible early: what is included, what changes timing, and what happens after launch.

Scope and estimates

Pricing and timing are based on the agreed scope. If the scope changes materially, the project needs to be re-costed or re-phased.

Approvals and timing

Projects move through agreed review points. Delayed approvals can move delivery dates because active capacity has to be managed properly.

Ownership and support

Final assets transfer after final payment. Ongoing support sits inside a separate support or retained arrangement unless agreed otherwise.

Working terms

The practical version of how delivery governance works.

The intent is to keep expectations aligned while the work moves. That means fewer surprises around scope, approvals, ownership, and support responsibility.

Section 01

How scope works

Estimates are based on the agreed requirements at the time of proposal or kickoff. New features, extra integrations, or larger content requirements may need a change to scope, timing, or cost.

Section 02

How approvals affect delivery

We use review points to keep quality and direction clear. If feedback or approvals are delayed, the delivery timeline may need to shift to reflect active project capacity and realistic sequencing.

Section 03

Who owns what

Once the commercial side of the project is settled, ownership of the final paid-for deliverables transfers to the client. Dev404 may still reuse non-confidential patterns, learnings, or structural approaches across future work.

Section 04

What happens after launch

Post-launch fixes, support, and ongoing improvements are handled according to the support arrangement in place. If there is no active support arrangement, any new work is scoped separately.

Best next stepDEV404 // NEXT STEP

If the project still needs shaping, start with an assessment before formal delivery begins.

That route gives both sides a clearer understanding of scope, complexity, and likely constraints before a proposal or kickoff locks the work in.

Guidance

Want the data handling side as well? Review the privacy and POPIA page.