They are handled differently.
A revision changes something already covered by the specification. A bug is delivered behaviour that does not match it. Bug fixes do not consume a revision round.
01Commission process
Twelve stages.
No hidden handover.
The workflow keeps requirements, payment, revisions, approval and support visible from the beginning of the commission.
-
01
Initial enquiry
Explain the requirement
The client contacts NDev Studios with the project idea, goals, preferred timeframe and any known requirements.
-
02
Discovery and clarification
Confirm scope and limitations
The project is discussed in detail, including technical requirements, deliverables, access needs and practical limitations.
-
03
Proposal and quotation
Receive the written proposal
The proposal confirms the agreed scope, estimated schedule, price, payment structure, two included revision rounds and the support period.
-
04
Approval and initial payment
Formally accept the commission
After launch, the client approves the proposal and terms. The required initial payment is then made through a GBP Stripe invoice.
-
05
Project setup
Prepare the workspace
A project record and Discord communication channel are created, and references, credentials and required materials are collected.
-
06
Development
Build to the approved specification
NDev Studios develops the project with direct progress updates. Larger commissions may be divided into agreed milestones.
-
07
Testing and internal review
Verify functionality and reliability
The work is tested for functionality, reliability, security and compatibility, with identified issues corrected internally.
-
08
Client review and revisions
Preview and provide feedback
The client receives a preview or test version. Up to two grouped revision rounds are included for changes within the agreed scope.
-
09
Final approval and payment
Approve the completed work
Once approved, the remaining balance becomes due. New features or major scope changes require a separate quotation.
-
10
Delivery and handover
Deploy or deliver the project
The completed work is delivered or deployed with the agreed files, documentation, setup details and usage instructions.
-
11
Support period
Activate 30 days of included support
Support begins after the client receives, tests and activates the project, or automatically seven days after delivery if activation is not confirmed.
-
12
Project completion
Close and archive the commission
After support ends and outstanding covered issues are resolved, the project is closed. Further work begins as a new request.
That is a scope change.
A new system, major redesign or additional feature outside the accepted proposal is priced and scheduled separately before work begins.
Development is paused.
The commission pauses after 14 days without a required response and may close after 30 days following written notice.