Business context
Your products, customers, internal workflows, existing constraints, and priorities are documented before the solution is defined.
PROCESS / CLARITY BEFORE DEVELOPMENT
A clear agreement.
A purposeful build.
The Venzoh proposal defines your platform phase by phase: what will be built, what you will receive, how each phase is reviewed, and what sits outside the scope, before development begins.
ENGAGEMENTCore platform + optional modules
DELIVERY MODEL14 core phases in 5 milestones
INVESTMENTStarting at $60,000, fixed price
TIMELINE16–19 weeks for the core platform
01 / CONTEXT & OUTCOME
The reason for the project comes first.
The proposal begins with the current business situation, the problem to solve, and the result the new commerce application should create.
Proposed solution
A custom storefront, customer area, online payments and an administration workspace on one modular back end, with optional wallet, installments and in-store POS.
Expected outcome
A clearer shopping journey, more manageable store operations, dependable business logic, and a maintainable foundation for future development.
02 / SCOPE OF WORK
The complete system, clearly separated.
Only the items listed in each phase of the proposal are included. The platform brings together the following product areas.
Customer shopping experience
- Custom design direction in Figma and a responsive storefront
- Catalog, variants, search, filters and product detail pages
- Cart, coupons, checkout, shipping zones and tax rates
- Online payments through one provider (Stripe recommended)
Accounts and self-service
- Registration, email verification and secure login
- Profile, saved addresses, wishlist and order history
- Return requests and refunds to the original payment method
- Optional: wallet & store credit and installment plans (modules A and B)
Store operations
- Products, inventory, customers, promotions and homepage content
- Orders, returns, reviews and contact form submissions
- Staff roles, an activity log and spreadsheet product import
- Transactional emails, reports and a sales dashboard
Application foundation
- TypeScript, Next.js and a modular NestJS back end
- GraphQL API and a PostgreSQL data model with Prisma ORM
- Automated tests on every update and OWASP Top 10 protection
- Technical SEO, Google Analytics 4 and Search Console
- A storefront built to WCAG 2.1 AA accessibility guidelines
- Optional: in-store POS (module C)
03 / DELIVERY PLAN
Fourteen phases.
The core platform runs in 14 phases grouped into 5 milestones. Every phase ends live on your private staging site, and every milestone closes only when you have accepted its work.
M1Foundation & Storefront
- 01Discovery & Storefront Foundation11–13 days
- 02Product Catalog & Product Experience10–11 days
- 03Authentication & Customer Accounts4–5 days
M1 accepted · day 29
M2Inventory & Admin
- 04Inventory Management5–6 days
- 05Admin & Backoffice10–11 days
M2 accepted · day 46
M3Cart, Checkout & Payments
- 06Cart & Promotions6–7 days
- 07Checkout, Shipping, Tax & Orders8–9 days
- 08Payment Integration5–6 days
M3 accepted · day 68
M4Returns, Notifications, Engagement & Analytics
- 09Returns & Refunds3–4 days
- 10Transactional Notifications3–4 days
- 11Customer Engagement4–5 days
- 12Analytics & Reporting4–5 days
M4 accepted · day 86
M5SEO, Launch & Handover
- 13Technical SEO3–4 days
- 14Production Launch, UAT & Handover5–6 days
M5 accepted · day 96
Live on your staging siteMilestone acceptedShown at the upper estimate of 96 business days
04 / WHAT YOU WILL RECEIVE
The handover is part of the product.
Each phase ends with a stated deliverable. At launch, you receive the complete platform and everything needed to run it.
- 01
Approved application
The storefront, customer area, payments and administration panel described in the 14 core phases, plus any optional modules you choose.
- 02
Back end and data layer
Server-side services, business rules, database design, APIs, validation and role-based access control.
- 03
Project source code
The source code repository, database design and Figma design files, owned by you on full payment.
- 04
Production launch
Deployment on a Linux VPS or AWS EC2, with HTTPS, server hardening, daily backups and uptime monitoring.
- 05
Testing and review
Automated tests in every phase, user acceptance testing support and production smoke tests.
- 06
Handover documentation
Technical and deployment documentation, plus an admin user guide for your team.
- 07
Video tutorials
Short recorded video tutorials for every key admin task, with follow-up questions answered in writing during the warranty.
- 08
90-day warranty
For 90 days after go-live, defects in the accepted scope are fixed at no charge.
05 / DELIVERY PROCESS
A controlled path from discovery to handover.
- 01
Discovery
A questionnaire and a written workshop in a shared document, ending in a written scope confirmation.
- 02
Design & architecture
Figma designs for key screens and an architecture planned for every phase and module you choose.
- 03
Build & demonstrate
Each phase is developed, tested and demonstrated on your private staging site with release notes.
- 04
Review
4 business days to send consolidated written feedback, with up to 2 feedback rounds per phase.
- 05
User acceptance
You test complete business flows on staging, and reported issues are fixed.
- 06
Launch & handover
Go-live, handover of code, documentation and video tutorials, and a 90-day warranty.
06 / SHARED RESPONSIBILITIES
A successful delivery needs clarity on both sides.
Development responsibility
- Plan and build each phase as written in the proposal
- Handle all technical setup and configuration
- Demonstrate every phase on staging with release notes
- Test, launch and hand over the platform
- Keep business information, data and credentials confidential
Business responsibility
- Name one point of contact who can make decisions and approve phases
- Provide brand assets, page content and legal texts (terms, privacy, returns)
- Create third-party accounts in the business’s name, using the step-by-step setup guide
- Enter the product catalog through the admin panel or the spreadsheet import
- Review each phase within 4 business days and fund each milestone before it starts
07 / COMMERCIAL BOUNDARIES
What is not included in the fixed price.
Anything beyond the written scope can be added later as a separate change request, with its own estimate and timeline.
Third-party and infrastructure costs
The cloud server (VPS or AWS), domain, payment processing, email delivery, storage, CDN and any other external service are paid directly by the client. Their pricing is set by each provider.
Content and data
Copywriting, translation and product photography are not included. Product data entry and migration from an existing store, and integrated card readers through Stripe Terminal, are available as separate services.
Change requests
New or changed functionality is estimated in writing, with its cost and timeline impact, and starts only after written approval. Feedback within the written scope is not a change request.
Warranty versus maintenance
The 90-day warranty covers defects where the platform does not work as described. New features, changes made by others and third-party failures are not covered; a monthly maintenance plan is quoted separately.
08 / ACCEPTANCE & PAYMENT
Nothing important is left implied.
Phase acceptance
A phase is accepted when its deliverables work as described. If no feedback arrives within 4 business days, the phase is deemed accepted.
Five fixed-price milestones
$60,000 USD for the core platform; each optional module is its own milestone. Each milestone is funded before its first phase starts, and a milestone closes when all of its phases are accepted.
Getting started
Work begins when Milestone 1 is funded. The core platform takes 16–19 weeks. Delivery dates move by the length of any delay in feedback, decisions, content or account access.
HAVE A PROJECT IN MIND?