Client Lifecycle, Qualification, Onboarding & Project Delivery Process
The end-to-end 16-stage delivery lifecycle governing how client projects are qualified, scoped, contracted with milestone escrow, built in transparent sprints, verified, and handed over.
The LETSCOOKTECH Delivery Model#
LETSCOOKTECH operates on a structured, specification-driven delivery process designed to eliminate project surprises, scope creep, and delivery delays.
We do not operate on open-ended hourly billing or vague, uncosted promises. Every engagement follows a disciplined 16-Stage Lifecycle State Machine backed by milestone-based escrow. Work is broken into 1–2 week focused sprints where deliverables, acceptance criteria, and costs are locked in writing before build commences.
Clients maintain 100% financial and technical control: milestone escrow is deposited prior to sprint kickoff, reviewed and verified in User Acceptance Testing (UAT), and released only upon client approval with simultaneous source code handover.
- Transparent milestone escrow: uncommenced work is 100% refundable.
- Weekly async visibility: video walkthroughs and staging demos keep clients informed.
- Strict scope control: changes are evaluated transparently with formal Change Requests.
- No hostage code: source code and IP transfer upon milestone sign-off.
1. Complete 16-Stage Lifecycle State Machine#
Every project progresses through predictable, documented states:
• Stage 1 — Initial Enquiry: Intake of client business need via website, referral, or Ely AI assistant. • Stage 2 — Fit Review / Qualification: Evaluation of problem alignment, capability fit, timeline viability, and budget realisticness. • Stage 3 — Discovery Workshop: Deep-dive technical investigation mapping users, workflows, integrations, and architectural constraints. • Stage 4 — Engagement Acceptance Gate: Formal internal decision to accept, suggest an alternative route, or decline gracefully. • Stage 5 — Solution Architecture & Proposal: Delivery of fixed-scope SOW, milestone breakdown, and Architecture Decision Records. • Stage 6 — Contracting, Payment & Capacity: MSA signature and milestone escrow deposit for Milestone 1. • Stage 7 — Account & Stakeholder Onboarding: Creation of private communication channel, project board, and staging environment. • Stage 8 — Project Intelligence Questionnaire: Structured collection of brand assets, third-party credentials, and domain access. • Stage 9 — Requirements Baseline & Traceability: Freezing the functional requirements register and testable acceptance criteria. • Stage 10 — Design & Technical Architecture: Wireframing, UX flows, data model schemas, and API contracts. • Stage 11 — Sprint Implementation: 1–2 week focused development sprints with automated CI/CD checks. • Stage 12 — Verification & Internal QA: Cross-browser testing, integration checks, security review, and performance audit. • Stage 13 — Change Control: Formal management of any scope alterations via written Change Request Forms. • Stage 14 — Production Deployment & Rollback Prep: Pre-flight verification, DNS configuration, and automated release. • Stage 15 — User Acceptance Testing (UAT) & Sign-Off: Client testing against agreed acceptance criteria and milestone sign-off. • Stage 16 — Handover, Warranty & Care Transition: Full repository transfer, credential migration, 30-day warranty, and optional Care retainer.
2. Stage 1 & 2: Initial Enquiry, Fit Review & Qualification Gate#
Before taking on any project, LETSCOOKTECH conducts a rigorous Fit Review to ensure mutual alignment. We intentionally decline projects that do not match our capability or operational values to protect client outcomes.
Qualification Scorecard Criteria: 1. Problem Clarity: Does the client have a defined business problem rather than an ambiguous desire for 'an app'? 2. Capability Alignment: Does the required stack match our `PRODUCTION_READY` capability register (LCT-C06)? 3. Decision-Maker Access: Is there a designated technical or business decision-maker with authority to review and approve milestones? 4. Commercial Realism: Does the client's budget align with the architectural complexity required? 5. Timeline Viability: Can the project be delivered responsibly without reckless shortcuts?
Internal Red Flags (Automatic Decline Triggers): • Demands for fixed enterprise builds on unrealistic micro-budgets. • High-harm, unlawful, or predatory business models. • Refusal to agree on written acceptance criteria or milestone escrow terms. • Requests for speculative, unpaid design or architecture work.
3. Stage 3 & 4: Discovery Workshop & Dynamic Branches#
When a project involves complex workflows, third-party integrations, or architectural uncertainty, we conduct a structured Discovery & Solution Blueprint (Offer 3) before quoting a large build. Discovery eliminates costly misunderstandings by producing concrete engineering specifications.
Discovery branches into six specialized technical tracks:
• Branch A — Business Launch: Brand positioning, content hierarchy, SEO keywords, local search optimization, enquiry capture flows. • Branch B — Commerce Launch: Product catalog taxonomy, SKU variants, payment gateway compliance (Razorpay/Stripe), shipping rules, order fulfillment workflows. • Branch C — Custom Software & Internal Systems: Entity relationship diagrams (ERD), user permission matrices (RBAC), multi-tenant data isolation, third-party API contracts. • Branch D — Workflow Automation: Source and destination API field mapping, webhook triggers, rate-limit thresholds, retry strategies, and failure notification channels. • Branch E — System Modernization & Recovery: Legacy codebase review, vulnerability profiling, dependency upgrade paths, database migration safety. • Branch F — AI & Knowledge Systems: Domain dataset evaluation, chunking strategies, vector search retrieval architecture, prompt guardrails, and human review fallbacks.
4. Stage 5 & 6: Proposal, SOW & Milestone Escrow Model#
Our commercial proposals are unambiguous engineering specifications, not vague marketing decks. Every Statement of Work (SOW) defines:
{
"sow_id": "SOW-2026-089",
"client": "Acme Corp",
"project": "B2B Customer Order Portal",
"milestones": [
{
"milestone_number": 1,
"title": "Architecture, Auth & Core Data Model",
"duration": "2 weeks",
"deliverables": [
"Database schema with Prisma migrations",
"NextAuth JWT authentication with RBAC (Admin, Staff, Customer)",
"Staging environment deployment with seed data"
],
"acceptance_criteria": [
"Automated test suite passes with 100% assertion rate",
"Unauthenticated API requests receive 401 Unauthorized",
"Customer role cannot query Admin analytics endpoints"
],
"escrow_amount": "$3,500",
"ip_transfer": "Transferred upon milestone sign-off"
}
]
}- Escrow protection: funds for Milestone 1 are deposited into escrow before sprint kickoff.
- No surprise invoices: scope, price, and deliverables are fixed in writing per milestone.
- Orderly progression: Milestone 2 commences only after Milestone 1 is verified and approved.
5. Stage 7 & 8: Onboarding & Secure Credential Protocol#
Once contracting is complete, we initiate client onboarding through a standardized, secure protocol:
• Communication Channels: Dedicated Slack or private WhatsApp channel for asynchronous day-to-day coordination; email for official contractual notices. • Project Tracking: Shared Kanban board (Linear / GitHub Projects) displaying sprint backlog, active tickets, and blocker items. • Zero-Knowledge Credential Vault: Third-party API keys, domain DNS credentials, and database passwords are exchanged via encrypted password vaults (e.g. 1Password / Bitwarden secure shares). Committing credentials to chat or email is prohibited. • Asset Collection: Structured intake of logos, brand guidelines, typography, copy assets, and regulatory disclosures.
6. Stage 9–12: Sprint Execution, Async Updates & Internal QA#
Development occurs in focused 1–2 week sprints. We maintain complete transparency throughout development:
• Weekly Asynchronous Walkthroughs: We record concise (3–5 minute) Loom video walkthroughs demonstrating functional software on the staging environment, detailing completed work, upcoming tasks, and any client dependencies. • Live Staging Environment: Clients receive a password-protected staging URL (e.g. `staging.client.letscooktech.com`) to inspect real working features in real time. • Rigorous Internal QA: Before asking a client to review a sprint, LETSCOOKTECH engineers execute internal cross-device QA, form validation checks, error-state simulations, and automated test passes. We never treat clients as our initial bug-testers.
7. Stage 13: Scope Control & Formal Change Request Procedure#
In software projects, requirements naturally evolve as clients see working software. To prevent conflict, timeline slips, and budget inflation, all scope changes are handled through a transparent Change Request (CR) process:
1. Identification: Either party identifies a requested feature, design alteration, or integration not included in the signed SOW. 2. Impact Assessment: LETSCOOKTECH prepares a written Change Request Form within 48 hours detailing: - Technical description of the change - Additional cost (if any, calculated against our standard rate card) - Impact on project delivery timeline - Dependencies and risks 3. Client Decision: The client reviews the CR and may approve, defer to a future phase, or withdraw the request. Work on the change begins only after written client approval.
- No silent scope creep: existing milestone timelines are protected.
- Zero surprise charges: no work outside SOW is billed without prior written authorization.
8. Stage 14 & 15: Production Cutover & User Acceptance Testing (UAT)#
When milestone development is completed on staging, the project enters formal User Acceptance Testing (UAT):
• 5-Day UAT Window: The client is granted 5 business days to test the deliverables against the agreed acceptance criteria. • Defect Severity Triage: - Severity P1 (Critical): Core functionality broken, data loss risk, checkout blocked → Immediate emergency fix within 24 hours. - Severity P2 (Major): Significant feature defect with non-trivial workaround → Resolved within 48 hours. - Severity P3 (Minor): Minor functional flaw or edge-case glitch → Resolved prior to production cutover. - Severity P4 (Cosmetic): Visual alignment, typo, minor spacing → Batched and resolved in final polish. • Formal Sign-Off: Once all P1 and P2 items are resolved, the client executes the written UAT Acceptance Record, authorizing escrow release and production deployment.
9. Stage 16: Project Closure, 100% Code Handover & Care Retainers#
Upon project completion and final milestone approval, LETSCOOKTECH completes the project closure checklist:
• Complete Codebase Handover: Transfer of GitHub/GitLab repository ownership to client account. • Production Infrastructure Transfer: Transfer of hosting projects (Vercel, AWS), databases, domain records, and third-party SaaS accounts directly to client billing. • Operational Runbook: Provision of `/docs/DEPLOYMENT.md` containing backup procedures, environment configs, and operational instructions. • 30-Day Fair-Play Defect Warranty Kickoff: Commencement of our 30-day warranty covering reproducible defects matching the signed SOW. • Optional Care Retainer Transition: Seamless transition to our monthly Care & Improvement retainer (Offer 7) for proactive dependency updates, security monitoring, and ongoing feature sprints.