Seven phases. Two gates. Zero surprises.

The seven-phase delivery timeline

1. 01As agreed

   DiscoverUnderstanding your business before proposing anything

   We study your business, your customers and the outcomes you need. This phase produces a shared understanding — and an honest recommendation, including telling you when you do not need us.

   • Business goals and audience mapping
   • Current systems and workflow audit
   • Competitive and channel review
   • Opportunity and constraint assessment
2. 02As agreed

   ScopeA written scope that removes ambiguity permanently

   Every deliverable, timeline, milestone and payment term is written into a Final Scope of Work. You review it, request revisions, and approve it in writing. From this moment, "I thought it would include…" stops being a possible conversation.

   • Structured discovery questions and gap analysis
   • Deliverables, timeline and milestone definition
   • Payment structure per our Payment Policy
   • Written client approval of the final scope

   Approval gate

   Scope changes after approval are possible — but they trigger a new quote and timeline, never silent drift. This is written into the Client Approval Policy.

3. 03As agreed

   PreviewHTML preview where included

   Where included in the agreed process, we provide an HTML Preview for review against the approved scope before the applicable project payment. Backend features and production integrations may be incomplete unless the SOW says otherwise.

   • Preview supplied where included in the agreed process
   • Review against the agreed scope and preview content
   • Revision allowance follows the approved SOW
   • Written approval or revision request recorded

   Approval gate

   Where required by the agreed process, approval of the relevant preview precedes the applicable payment request. The approved SOW determines project-specific payment terms.

4. 04Per agreed schedule

   PaymentMilestone payments, verified and receipted

   Payment follows the schedule in the approved quotation, invoice, and SOW. TECH360 verifies payment status using available transaction records and provider or financial-institution confirmation; a screenshot or pending transfer alone is not conclusive proof of cleared funds.

   • Milestone structure as written in the approved scope
   • Payment instructions with reference to your Client ID
   • Verification before any project status change
   • Receipt and record for every transaction

   Verification gate

   Project commencement and any payment trigger follow the approved SOW. Final source-code handover generally follows verification that required outstanding payments have cleared.

5. 05As agreed in the SOW

   BuildIterative build with milestone acceptance

   Development proceeds against the approved scope in milestones — each accepted in writing before the next begins. Progress updates reach you automatically at milestone boundaries, not when someone remembers to write.

   • Milestone-based development against the scope
   • Automated progress updates at each milestone
   • Revisions as defined in the approved scope
   • Testing against the QA checklist before each acceptance
6. 06As agreed

   DeliverDelivery with a checklist, not a hope

   Delivery is a structured event: the system goes live against the quality checklist, you confirm delivery in writing, and any final payment milestone is settled with the same verification discipline as the first.

   • Live deployment on your hosting or ours
   • Quality checklist verified together
   • Written delivery confirmation on record
   • Final payment milestone settled and verified

   Payment gate

   Unless otherwise agreed in writing, final source-code handover follows verification that all required project payments have cleared.

7. 07As agreed

   Handover & SupportAgreed source code, documentation and handover

   After required outstanding payments are verified and cleared, TECH360 hands over agreed source code, documentation, and Client-owned credentials specifically identified in the approved SOW. Internal secrets and other Clients’ information are excluded. Support is only as agreed.

   • Agreed source package and documentation
   • Client-owned credentials identified in the SOW, where applicable
   • Secure transfer and handover record
   • Support only where included in the agreement