a junk-removal request app for Bay Area customers
Estimated monthly cost at the usage scale below — billed by actual usage
2.47 req/s
Peak Concurrency
2.95 GB
Database Storage
165.99 GB
Object Storage
19.05 GB
Outbound data transfer
What is this app
BayHaul Junk Removal is an online request and scheduling service for a Bay Area junk-hauling company. Customers describe their junk and upload photos, then receive an AI-generated price range and structured detected-item list before choosing a pickup date, one of nine fixed one-hour slots, and an address. The system calculates the warehouse-to-customer driving distance and time, while BayHaul staff review each request and accept or decline it with an optional note; declined requests can be edited and resubmitted for recalculation.
As a customer, I can describe my junk and upload photos to request an AI-assisted price range and detected-item list
As a customer, I can choose a pickup date, one of nine fixed one-hour slots, and an address for my quoted request
As a customer, I can edit and resubmit a declined request so its quote and driving estimate are recalculated
As an anonymous visitor, I can submit junk details and photos online to receive a pickup quote
As a staff member, I can review requests and accept or decline them with an optional note after seeing the driving distance and time
48000
customers
Registered BayHaul customers who submit junk details and photos, review AI-assisted quotes, choose pickup details, and revise declined requests.
2000
staff
BayHaul team members who review incoming requests, inspect photos and route estimates, and accept or decline jobs with optional notes.
0
anonymous_visitors
Public visitors who can begin an online junk-removal request without an established registered account.
Requirements to minimum viable plan to cost
Momen doesn't give a vague quote: it first sizes the project's actual demand for each capability and resource, then costs each item out.
The numbers in the "Project demand" column below — their scale assumptions and derivations — are detailed in Scale & sizing.
Minimum viable plan
BASIC
AI, geocoding, and routing integrations require multiple workflows and integrations, making BASIC the minimum plan.
See the capability-by-capability assessment ▾
PROJECT DEMAND
ALLOWANCE PROVIDED (COMPOSITION)
Basic
Basic is the minimum viable plan
Basic
(Plan tier: BASIC)
See minimum viable plan above
39
single-tenant kit
3 req/s
not purchased
(plan/kit 5 req/s)
Covered by plan/kit (margin ~67%)
0
Database storage add-on
3.17 GB
10GB × 1/year, amortized monthly
(plan/kit 200.00 MB + add-on +2.97 GB)
Add-on fills +2.97 GB gap beyond plan/kit
8.33
Object storage
add-on
178.23 GB
100GB × 2/year, amortized monthly
(plan/kit 2.00 GB + add-on +176.23 GB)
Add-on fills +176.23 GB gap beyond plan/kit
5.83
Outbound data transfer add-on
20.45 GB/mo
500GB × 1/year, amortized monthly
(plan/kit 2.00 GB/mo + add-on +18.45 GB/mo)
Add-on fills +18.45 GB/mo gap beyond plan/kit
2.92
AI points add-on
567.1M points
6,000,000 AI Points × 95/month
(plan/kit 571.0M points + add-on +566.1M points)
Add-on fills +566.1M points gap beyond plan/kit
950
plan + add-ons · usage-based · no development cost
Your options for this project
In the table below, the "monthly infrastructure" for the self-built / AI routes is derived from the AWS list prices shown below, sized against this project's actual usage.
2 × t4g.large × 730h
EC2 t4g.large → 98.11
2 × db.m6g.large (Multi-AZ) × 730h
RDS PostgreSQL db.m6g.large → 232.14
3.17 GB-month
RDS gp3 storage → 0.36
178.23 GB-month
S3 Standard → 4.1
0.00 GB (first 100GB free)
Internet egress → 0
Total ≈ $334.72 / mo
Pure cloud resources
DEVELOPMENT COST
MONTHLY CLOUD INFRA ($/MO)
MONTHLY TOTAL
(INFRA + OPS)
Traditional outsourcing / build in-house
about $140,000 - $190,000
≈ $335
Based on the AWS estimate above
≈ $2,335
Infra $335 + ops ~$2,000
4-6 months
5 / 5
Vibe Coding
about $18,000 - $26,000
≈ $335
Based on the AWS estimate above
≈ $1,835
Infra $335 + ops ~$1,500
hours
5 / 5
AI full-stack generation
about $8,000 - $11,000
≈ $335
Based on the AWS estimate above
≈ $1,835
Infra $335 + ops ~$1,500
hours
3 / 5
Off-the-shelf SaaS / vertical solution
$0
N/A
Priced per seat, not by cloud infra
≈ $16,000+
Per-seat pricing, tens of thousands of users
days
1 / 5
Momen
Recommended
$0
$56
All-in: egress / storage / auto-scaling; excludes AI usage
$56
hours
5 / 5
Servers, databases, traffic and storage are inherent infrastructure costs for this project — you pay them whether you outsource, use Cursor or Lovable, or build it yourself (self-built runs ≈ $441/mo at AWS list prices, often more), plus the extra dev and ops staff. Momen bundles all of it into $368/mo all-in and removes the need for an ops team.
The frontend can be generated with AI tools (Cursor, Lovable, etc.); the hard part is the backend — auth, database, scaling, data security and ops. Momen delivers a production-grade backend as a BaaS: keep the vibe-coding speed on the frontend, while the backend runs on proven infrastructure — reliable, with no self-hosting or ops.
What scale this estimate assumes, and how the numbers are derived
Cost depends heavily on usage volume. First see the key assumptions and business scenarios this estimate uses, then the full calculation derived from each scenario for every resource — all adjustable to your real situation.
We assume 50000 registered accounts because the project description gives no explicit user count or directly implied operating scale, and 50000 is the standard planning assumption for an online service. The number can be adjusted when BayHaul provides its actual customer and staff registration pools.
We assume this is a standard linear-growth service because online quote requests and staff operations are expected to build gradually as BayHaul acquires customers. The equivalent accumulation period is therefore set to 225 days rather than treating the service as fully loaded from launch. If BayHaul is launching with a large pre-existing request history or an immediate marketing burst, this parameter can be adjusted.
Daily Customer Quote Period
Daily Customer Quote Period
Daily Customer Quote Period
Daily Customer Quote Period
Daily Customer Quote Period
30
times/month
2.47 req/s
Peak load
We assume customer and anonymous quote activity is spread across a broad daily operating period rather than pulled into a synchronized signal. The anonymous submission purpose and registered customer purpose are separated because they represent distinct account contexts even though they use the same customer-facing page. A 3,600-second duration represents a typical ten-hour availability and demand window, and 30 monthly occurrences reflect daily operation. This scenario covers quote loading, initial AI estimation, pickup scheduling, and customer resubmission activity.
Main impact: Peak Concurrency
The scenarios above set the assumptions for each resource; below is the full calculation based on those assumptions. Click to expand each item.
How this app works
What exactly does this budget support? Broken down by business scenario, showing the pages, data tables, automation flows and AI
assistant behind each one.
Public visitor path from an initial online quote request to a scheduled pickup request.
Registered customer path for creating, scheduling, and occasionally revising a quote request.
Staff review and decision path for incoming BayHaul pickup requests.
page
data_table
ai_agent
action_flow
Quote Request Page
Customer-facing form for describing junk, uploading photos, reviewing a generated quote, selecting pickup details, and resubmitting a declined request.
Staff Request Dashboard
Staff queue and review dashboard for inspecting customer requests, route estimates, photos, and accepting or declining jobs.
What you might want to know about this project
The Q&A below is generated by AI based on this project's type, features and scale.
What most affects the system's resource usage?
How do uploaded photos affect capacity?
When is routing performed?
What is included in the current scope?
Copy to discuss with AI
Challenge & re-estimate