Contact person: Startup MVP development -- 2

Phone:Show

Email:Show

Location: Magnolia, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Startup MVP Development — Bloom (Flower Marketplace Prototype) About the project:

We are Bloom, a new digital marketplace connecting people who want to send flowers with local florists in their ZIP code.
Think Uber Eats for flowers: the customer customizes a bouquet, the system routes the order to the florist in the same ZIP code, and the florist prepares and delivers it.

Our long-term vision is to build a scalable app + portal ecosystem for the U.S. floral industry. But before building the full production platform, we want to start with Phase 0: a functional MVP prototype.

Objective:

Deliver a functional prototype that looks and feels real, but works with mock/simulated data.
This prototype will be used to:

Convince florists to join Bloom (subscriptions).

Show potential investors and partners a working demo.

Prepare the ground for Phase 1 (pilot with real payments, dispatch, inventory).

Scope & Deliverables:
1. Landing Web (2–3 weeks)

Inspired by “Uber Eats for Restaurants” style.

Sections: value proposition, how it works, pricing model (subscription + commission).

Application form for florists (name, ZIP, contact info).

Blog/FAQ placeholder + basic legal pages.
Deliverable: Hosted landing page + working form.

2. Florist Partner Portal (3–4 weeks)

Inventory demo: upload flowers with price/stock (mock data).

Orders demo: inbox → accept → prepare → deliver (simulated states).

Upload photo evidence (saved to demo folder).

Basic reports (mock sales & acceptance rates).
Deliverable: Web portal (desktop) connected to backend mock.

3. Customer Mobile App (4–6 weeks)

Bouquet configurator: add flowers (blocks x3/x6/x9), see live pricing.

Full order flow → checkout simulated (no Stripe yet).

Catalog by ZIP (mock data).

Basic notifications.
Deliverable: APK/IPA installable builds + source code.

4. Backend Mock + Integration (2–3 weeks)

API endpoints (inventory, orders, status) with mock data.

Light DB (Postgres/SQLite).

Dispatch logic simplified (assign order to demo florist).

Documentation in Postman/Swagger.
Deliverable: Mock backend running in AWS.

5. QA + Coordination

Test complete flow: customer → florist → backend.

Bug reporting & validation.

Ensure flows match acceptance criteria.
Deliverable: QA report + stable demo prototype.

Timeline

Total: 10–12 weeks (can overlap tasks).

Week 1–2: Landing

Week 3–5: Florist Portal

Week 4–8: Mobile App (parallel)

Week 7–10: Backend Mock

Week 11–12: QA + Final delivery

Required Team

1 Project Manager

1 UI/UX Designer

1 Frontend Developer (Landing + Portal)

1 Mobile Developer (React Native/Flutter)

1 Backend Developer (Node.js/Python)

1 QA Tester

1 DevOps Engineer (AWS deploy basic)

Budget

Total Phase 0: $15,000 – $22,000

With LatAm teams (Venezuela, Argentina, etc.), optimization possible: $12,000 – $15,000.

Payments will be milestone-based (Landing, Portal, App, Backend, QA).

Acceptance Criteria

Customer app shows only available flowers in ZIP (mock data).

Order can be created and assigned to demo florist.

Florist uploads 2 photos (ready & delivered).

Customer receives simulated notifications.

Landing page live & collecting florist leads.

Why this project is exciting

Bloom is not “just another delivery app.” It is:

A scalable marketplace model in the $50B U.S. floral industry.

A community tool that helps local florists get more clients.

A customer experience revolution (custom bouquets, subscriptions, even “Bloom Eternal” post-life flower memberships).

Phase 0 is only the beginning. We want a team that thinks long-term and could grow with us into Phase 1 (real payments, dispatch, subscriptions) and beyond.

Deliverables: Prototype ready to demo (Landing + Portal + App + Backend mock) within 10–12 weeks.
Goal: Convince florists, start capturing subscriptions, and prepare for scaling." (client-provided description)