Quotation — Phases 1, 2 & 3 Fixed Prices
Rebels Rest — Digital Platform
(rebelsrest.com web build & 2027 application programme)
Prepared by CodeCraft Labs for BHS · All communication in writing
How to use this document. This is CodeCraft Labs' fee proposal to BHS for the scope below — your client pricing is yours to set. If you lift figures into your own customer-facing document, please carry each figure together with its stated conditions, labels and dates: every price on these pages is defined by the assumptions printed with it, and the figures without them are not the same figure.
Cover note
Thank you for the complete round of answers received on 19 October 2026 — milestones, the contracting party, the content chain and the app platform are now confirmed in writing, which is what makes a fixed price possible. The delivery dates in the dependency schedule below are my requirements for holding the 30 November / 10 December timeline — please confirm them in writing.
Fixed price for Phase 1 (custom-coded masterbrand site, 7 pages, to the 10 December launch) is stated below with its full assumption set. Phases 2 & 3 are provided as fixed prices, with the November 2026 discovery meetings refining requirements within those prices (terms with each figure below).
If there's a budget ceiling
Tell me before we start and I'll recommend what to phase or trim — we'll re-quote the reduced scope at a lower price; the base price for the full scope as written stays unchanged. No silent scope cuts.
Build fee vs running costs
This quote is the build fee only. Hosting (Vercel), the domain (rebelsrest.com), database platform (Supabase), video hosting (YouTube/Vimeo embeds), analytics and any third-party services are the client's (Rebels Rest) running costs, set up and billed in the client's own accounts.
Recommended technical stack
| Layer | Choice |
|---|
| Frontend | Next.js (App Router) + React + Tailwind CSS |
| Motion & 3D | Motion/Framer Motion · react-three-fiber (glTF/GLB) |
| Data & forms | PostgreSQL via Supabase (client-owned) |
| Deployment | Vercel (client-owned account) |
| Analytics | GA4 + Search Console (client-owned) |
Recommended for this build: server-rendered static pages for technical SEO, smooth client-side page transitions for the 3D journey, and one Postgres database that the Phase 2 dashboard can ingest directly — no migration later. Any deviation forced by asset or hosting constraints will be flagged and agreed before implementation.
Tax: CodeCraft Labs is not a registered VAT vendor — no VAT is charged on the figures in this document.
Phase 1 — Custom web development (fixed price)
Fixed price — CodeCraft Labs fee to BHS
R144,000 · fixed · no VAT
Covers the scope as written below and no more; additions are quoted separately and approved in writing first. Valid until 18 November 2026. Payment: 50 / 25 / 25 milestones (see below).
In scope
- 7 pages: master landing page (rebelsrest.com) + one page each for Farming, Extracts, Eco, Academy, Foundation, Ventures / Partner With Us — all under rebelsrest.com (no separate domains)
- Magazine-style interactivity: maps, carousels/sliders, animated scroll experiences, video integration (large video masters hosted on YouTube/Vimeo — client's running cost)
- 3D plane page-transition journey: integration of the supplied 3D/interactive assets (single scene, transitions across the 7 pages, web-ready format per Appendix A) — bespoke 3D authoring or additional scenes/heavy WebGL choreography beyond the handoff specified in Appendix A are priced add-ons
- Forms: investor, B2B and RSVP forms — stored to a database from day one and emailed (Phase 2 dashboard can ingest them later; no migration)
- Private investor downloads: form submit → manual approval → unique expiring link emailed (member accounts / portal = add-on)
- Technical SEO setup, GA4 + Search Console, deployment configuration
- Content entry: supplied copy/media entered into the agreed page templates (restructuring, re-writing or layout changes beyond the templates = change request)
- Staging deploy, UAT support and the full launch sequence (timeline below)
- English-language site; modern evergreen browsers; no CMS — content changes after launch go through the developer (retainer or change request)
Not in scope (priced separately if wanted)
- Brand identity design — third-party design agency's scope (assets integrated per Appendix A)
- Nested sub-pages beyond the 7 pages · bespoke interactive work beyond the supplied assets · CRM integration · member accounts
- Post-launch content edits, new pages, re-designs (site retainer or change requests)
- Third-party/running costs (listed in cover note)
Timeline & milestones confirmed 19 Oct
- Staging deployMon 30 November 2026 — feature-complete; placeholders only where final assets are still outstanding
- Testing + revisionsTue 1 – Wed 9 December 2026 — client testing and up to 3 revision rounds
- ApprovalEverything approved before Thu 10 December
- Live (target)Thu 10 December 2026
- Soft-launch eventSat 12 December 2026
Dependency dates — the timeline stands on these
| Asset group | Required by |
|---|
| Brand pack (logo, palette, typography) | Fri 30 Oct 2026 |
| All content — copy, photography, video | Mon 2 Nov 2026 |
| 3D plane + interactive/motion assets (per Appendix A) | Fri 20 Nov 2026 |
| rebelsrest.com registered | Within 48h of quote acceptance |
These dates assume acceptance of this quote by Friday 23 October 2026. Should acceptance land later, no problem — the engagement continues on the same price and terms, the dependency dates and delivery timeline re-baseline from the actual kickoff date (shifted by an equal number of working days), and I'll issue an updated schedule at kickoff so the launch target stays intact. Development proceeds in parallel with asset production; placeholders are used until final assets are delivered and integrated on receipt. The final assets are required in time for the stated integration and content-entry windows: assets received after their window delay staging and live dates by an equivalent number of working days.
If the schedule is compressed by late dependencies
Delivery dates are conditional on the dependency dates stated above: late receipt shifts them by an equivalent number of working days. Any acceleration to recover lost time (overtime, parallel workstreams) is quoted separately and proceeds only on written approval; unless so approved, delivery continues on the shifted dates at standard working hours.
Revisions & approval — how the 1–9 December window works
- 3 revision rounds included (per the client's own pricing guideline). Each round = one consolidated set of feedback covering the site as delivered in that round. Additional rounds = scope creep, quoted separately.
- 48-hour feedback turnaround per round (calendar hours — the launch window doesn't pause for weekends). No consolidated feedback within 48h of a round delivery = that round is accepted.
- Every round response carries a triage note: "fixed: [defects]" · "quoted separately for your approval: [change requests]". Nothing on a change request proceeds until approved in writing.
- Defects vs changes — the reference documents for every round are this scope, the supplied designs and the supplied content. Work bringing the site in line with those references (including content corrections) is free; anything beyond them (new ideas, re-styling, rewrites) is a change request — welcomed, quoted before it starts, optional, and never a condition of launch.
- Final approval by end of Wed 9 December. If no final sign-off is received by then, the site is deemed approved for go-live on 10 December per the agreed milestone.
Payment milestones 7-day terms
| Milestone | Trigger | Amount |
|---|
| 1 — Deposit | On acceptance, before kickoff | R72,000 (50%) |
| 2 — Staging | Feature-complete staging deploy (30 Nov) | R36,000 (25%) |
| 3 — Go-live | Site live (10 Dec) | R36,000 (25%) |
Invoices are issued to BHS and are payable within 7 days; work does not commence on a milestone until the preceding invoice is settled. CodeCraft Labs is not a VAT vendor — no VAT charged. Kickoff follows acceptance of this quote, confirmation that the client has accepted BHS's engagement, signature of the BHS subcontract (to follow for review), and receipt of the deposit.
Warranty, data & responsibilities
- Warranty: 30 days from go-live, fixing faults in delivered scope at no charge. Beyond it — new changes, third-party asset issues, content edits — are billable (retainer or change request).
- POPIA: the client is the responsible party for personal data collected via the site forms (RSVP, investor, B2B). CodeCraft Labs builds to specification and processes personal data only on the client's instructions — not as data controller.
- Domain, hosting, database and analytics accounts are created from scratch in the client's own name and remain the client's assets.
Site maintenance — optional yearly tiers
Site maintenance retainer — optional · CodeCraft Labs
| Tier | Includes | Per month |
|---|
| 1 — Essential Care | 1 hr/month · hosting & platform oversight, security/dependency updates, uptime + analytics summary | R1,800 |
| 2 — Business recommended | 3 hrs/month · + content & layout changes (copy, images, dates, small tweaks), 48h turnaround | R3,500 |
| 3 — Growth | 6 hrs/month · + feature enhancements (components, sections, campaign pages), priority turnaround | R7,000 |
| 4 — Scale | 20 hrs/month · + everything in Tier 3, expanded capacity (larger features, parallel workstreams) | R16,000 |
| Custom | None of the tiers above fit? A tier can be scoped to your needs — quoted on request | On request |
Minimum 3 months per chosen tier; tier changes by written notice ≥14 days before quarter-end, effective the next quarter. Monthly billing; cancel on 30 days' notice. Included hours are capped monthly and do not roll over; work beyond the cap is a change request at R6,000/day pro-rated, pre-approved in writing first. Warranty fixes in the first 30 days after go-live do not consume retainer hours.
Phases 2 & 3 — Agricultural & supply-chain application (2027)
Phase 2 — MVP operational app + outgrower onboarding · early 2027 · fixed price — CodeCraft Labs fee to BHS
R800,000 · fixed
PostgreSQL multi-tenant architecture (separate tenant organisations) · MFA & role-based users (farmers, processing staff, super admins) · barcode/QR scanning with offline queuing · farmer dashboard (cycles, health logs, restock reminders) · processing portal (batch receipt, weights, received vs rejected yield) · data importing (capability/tooling) · web app and native iOS/Android apps installed directly (not public app stores; access granted per onboarded user). Price includes contingency for: business-rule complexity (harvest/health/yield formulas), data-import reality, offline sync conflicts, dual-platform delivery. The data-import scope is the import capability (tooling), not a guaranteed volume of data — the fixed price is not reduced if little or no data exists to import at go-live. Material changes beyond this scope are change requests, quoted and approved in writing before any such work starts.
Phase 3 — Integrations, logistics, payments, metrics · mid–late 2027 · fixed price — CodeCraft Labs fee to BHS
R600,000 · fixed
Logistics API integrations (waybill generation, freight tracking, transit portals) · payment gateways + order management (restocks, outgrower payouts) · processing efficiency metrics engine + advanced analytics · scale beyond pilot. Price includes contingency for: courier API availability/fees, gateway specifics & multi-currency, payout rules, volume growth. Material changes beyond this scope are change requests, quoted and approved in writing before any such work starts.
What the fixed prices assume — and the November discovery meetings
The fixed prices above are based on a pilot-scale assumption and the scope as currently written. The November 2026 discovery meetings (farmers + the client team; US specialists if available in November) will refine the requirements within those prices — the following inputs shape the build, and anything material beyond the stated scope is a change request, quoted and approved in writing before any such work starts:
- User roles and what each must do in the app (farmers, warehouse staff, clients, investors, admins)
- Expected scale: number of farmers/tenants, organisations/tenants, and order volumes
- What systems and data the client already uses (software, spreadsheets, machinery output) and formats available for importing
- Specifications of the machinery arriving from China — especially any data protocols or APIs it exposes
- Courier specifics (e.g. DHL refrigerated) and which APIs are available on their account
- Payment preferences: gateways, currencies, and who holds the merchant accounts
- Business rules as they apply them today: harvest timeframes, disease/health metrics, yield and rejection calculations
- Target milestones per phase for the 2027 rollout
Maintenance retainer for the platform (indicative)
Once site + apps are deployed — same three tiers
R1,800 / R3,500 / R7,000 / R16,000 · per month · custom on request
Tier 1 (1 hr/month) oversight · Tier 2 (recommended) + 3 hrs/month · Tier 3 + 6 hrs/month · Tier 4 + 20 hrs/month — scope also covers backend/database oversight and app-store/OS compatibility maintenance. A custom tier can be scoped on request if none of these fit. Included hours capped monthly (no rollover); overflow = change request at agreed rates. Third-party costs (app-store accounts, hosting, database platform, payment gateways) are client running costs. Quarterly tier switching as per the site tiers.
Indicative — firm at the November 2026 discovery, before any Phase 2 contract
Phases 2 & 3 exclusions: brand identity design · third-party, merchant, app-store and gateway fees · discovery-meeting travel · yearly retainer firm price (stated above as indicative until discovery).
Appendix A — Asset requirements (for the design & UX/asset teams)
Per the follow-up answers of 19 October: I specify the formats, the teams deliver to spec. Please share this appendix with the design/asset teams via the dedicated groups once we move forward — delivery dates as per the dependency table.
Brand pack by Fri 30 Oct
- Logo: SVG (primary) + high-res PNG; include horizontal lockup as used on the site header
- Colour: exact values in HEX/RGB, including a light/dark pairing if the brand has one
- Typography: font files (woff2) or licensed web links + weights used; note licence covers web use
- Guidelines: brand/mini style guide if one exists (PDF fine)
Photography with content · by Mon 2 Nov
- Full-resolution originals (JPEG/PNG/TIFF); hero-grade images ≥ 2400px wide
- Landscape + portrait crops where available; consistent file naming (page-ingredient based)
- Short list of which images belong to which page
Video with content · by Mon 2 Nov
- Masters as H.264 MP4 (1080p minimum; 4K welcome) — web optimisation on my side
- Intended use noted (hero loop vs in-page); suggested hero loop 8–15s, no audio
- Large masters/YouTube-Vimeo links for hosting — running cost sits with the client
3D plane & interactive/motion assets by Fri 20 Nov
- Preferred: glTF / GLB (the web-native 3D format; compatible with the three.js direction mentioned — "3js format")
- Plane model with materials/textures embedded (GLB), PBR textures ≤ 2048px, compressed (Draco/meshopt) — target under ~5MB for the scene
- Motion: static or animated model + a short flight/transition animation (glTF animation), or the full scene choreography if authored on your side — please confirm which in writing
- Micro-interactions/motion graphics: Lottie (JSON) or source files (After Effects .aep) if Lottie export is planned
- Anything that cannot meet this spec: flag early with what you can deliver, so integration approach and any impact on price/timeline can be agreed before handoff
Development runs in parallel with your asset production — placeholders cover the interim. What matters is on-spec format and delivery within the dates above; the 20 November date is the integration window before staging (30 Nov). Assets arriving after their window move staging/live by the equivalent number of working days.
Acceptance
Acceptance of this quotation (email confirmation or signature below), confirmation that the client has accepted BHS's engagement, signature of the BHS subcontracting agreement (to follow for review), and receipt of the 50% deposit together commence the engagement. This document and its stated conditions form the agreed basis of the Phase 1 build.
Accepted for BHS — name & signature
Date
Azgar Tar
Founder
From concept to deployment — we build software that moves your business forward.