Delivery Timeline
| Week | Focus | Output |
|---|---|---|
| Week 1 | Scope freeze, user flows, UI direction, architecture setup | Final screen list, technical setup, confirmed launch assumptions |
| Week 2 | UI screens and backend foundation | Core app screens, database, auth, and admin base |
| Week 3-4 | Customer app, catalog, cart, checkout, payment setup | Customer ordering flow ready for internal testing |
| Week 5-6 | Vendor app, rider app, order states, admin operations | End-to-end order flow across all roles |
| Week 7 | Notifications, basic reports, privacy labels, manual controls, launch settings | Phase 1 operations flow ready |
| Week 8 | Testing, fixes, deployment preparation, handover checklist | UAT build and admin handover |
| Week 9-10 | Buffer for gateway, app store, client feedback, polish, and production deployment support | Phase 1 production-ready launch build |
Domain and Customer Information Capture
| Area | Recommended Setup | Output |
|---|---|---|
| Custom URL | Connect a branded subdomain through AWS Amplify Domain Management after DNS access is confirmed | A cleaner client-facing URL such as proposal.smnify.com or a project-specific subdomain |
| SSL and DNS | Use Amplify-managed SSL, then add the DNS records at Route 53, GoDaddy, Namecheap, Hostinger, or the current domain provider | HTTPS-ready proposal or product preview link |
| Lead Capture | Add an enquiry form for name, company, email, phone, city, requirement, budget range, preferred launch timeline, and consent | Structured customer or partner information for sales follow-up |
| Storage and Alerts | Use a fast form tool for early sharing, or AWS API Gateway + Lambda + DynamoDB/SES for a fully AWS-native setup | Lead records plus email notification to the business team |
| Privacy | Collect only business contact and requirement details on the public page; avoid sensitive documents or personal verification files | Safer first-contact workflow |
Not Included in Phase 1
Advanced Product Features
- Wallet and loyalty system
- Referral and campaign engine
- Advanced analytics dashboards
- AI recommendations or personalization
- Multi-branch vendor operations
- Complex coupon abuse controls
Advanced Operations
- Automated dispatch algorithm
- Route optimization and batching
- Automated refunds
- Automated vendor/rider payouts
- COD reconciliation
- Fraud scoring
Advanced Compliance
- External KYC provider integration
- Complex state-wise rule engine
- Legal research or legal sign-off
- Advanced audit reporting
- Automated document expiry controls
Scale and Infrastructure
- High-scale cloud architecture
- Load testing
- Data warehouse
- Business intelligence setup
- Multi-city expansion controls
- Separate brand or city expansion beyond the agreed launch scope
Client Responsibilities
- Confirm legal product category and city/service area before development lock.
- Arrange payment gateway approval for the chosen product category.
- Provide brand name, logo, support contact, policy text, and business details.
- Provide vendor and rider onboarding data for UAT and launch testing.
- Confirm app store, payment, hosting, and third-party service ownership details.
- Pay third-party costs directly: hosting, SMS, payment gateway, maps, storage, email, and any KYC provider.
Next step: Once scope, legal assumptions, service area, payment gateway, domain access, and brand inputs are confirmed, Smnify can freeze the screen list and start Phase 1 delivery.