AppGrout Choose a defined service
Review the package boundary, prerequisites, exclusions, price, delivery target, and policies. Share only a short non-confidential summary before the NDA.
Clear gates from payment to handover.
AppGrout separates payment, confidentiality, technical authorization, and delivery. Work starts only when the requirements for your specific engagement are complete.
Accept the scope and pay
Accept the exact scope and booking terms, then pay through the official payment option shown at checkout. A transfer claim or browser redirect is not payment confirmation.
Payment is verified
AppGrout verifies the settled amount, currency, and order reference. Your matching email can then claim the private project workspace.
Complete confidentiality and authorization
Sign the agreed NDA before sharing private materials. Separately confirm which repository, environment, accounts, tests, and changes are authorized.
Finish the readiness gate
Provide the agreed intake, access, test accounts, reproducible baseline, and any required backup or rollback plan. The delivery clock starts only when these prerequisites are complete.
Review or repair begins
The named engineering lead works within the recorded boundary. Any material scope issue is raised before out-of-scope work is performed.
Receive written progress
The portal records the current stage, next action, delivery target, and blockers. Optional calls support the work but do not replace written decisions.
Delivery and handover
Receive the agreed findings, code changes, verification notes, or handover. The delivery states what was checked, what was not checked, and what remains open.
Review, retest, and close
Raise a claimed scope mismatch promptly. If limited retesting is included, submit the agreed fixes within its window. Then revoke access and schedule working evidence for deletion.
Start condition
When is an engagement ready to begin?
Payment reserves the engagement. The published delivery estimate starts after every applicable readiness item is complete—not merely when checkout finishes.
- Verified payment and accepted terms
- Executed NDA when private material is required
- Written authorization for the exact systems and activities
- Repository and test-environment access at the minimum necessary level
- Test accounts and safe evidence needed for the agreed journeys
- Reproducible baseline and acceptance criteria for repair work
- Backup or rollback path for any approved production change
Delivery targets
Two to three business days after the readiness gate is complete.
Three to five business days after the readiness gate is complete.
One five-business-day engineering sprint after the readiness gate is complete.
These are targets for the published fixed scope, not guarantees for an expanded scope or a project delayed by unavailable access, client decisions, or an external platform.
If something changes
A new user journey, repository, role, integration, or feature may change the scope. We document the impact and ask for written approval before additional paid work begins.
Safe access comes first
We prefer named accounts, staging environments, synthetic data, reviewable branches, and revocable access. Production changes require explicit authorization and a rollback path.