a junk-removal request app for Bay Area customers
Estimated monthly cost at the usage scale below — billed by actual usage
4.80 req/s
Peak Concurrency
443.84 MB
Database Storage
28.75 GB
Object Storage
1.88 GB
Outbound data transfer
What is this app
BayHaul Junk Removal is an online request and scheduling service for Bay Area customers who need junk hauled away. Customers describe their junk and upload photos, while an AI assessment returns a price range and structured detected-item list. After a customer chooses a pickup date, one of nine fixed one-hour slots, and an address, the system calculates the warehouse route so BayHaul staff can review, accept, or decline the request; declined requests can be edited and resubmitted with a refreshed route calculation.
As a customer, I can describe my junk and upload photos to request an AI-assisted price range
As a customer, I can review the detected items and price range for my junk request
As a customer, I can edit and resubmit a declined request for a refreshed quote
As a customer, I can choose a pickup date, one fixed one-hour time slot, and an address for an accepted quote
As a staff member, I can review incoming requests with photos, detected items, address, route distance, and travel time
As a staff member, I can accept or decline a pickup request and optionally add a note
As an anonymous visitor, I can read the public BayHaul service information before starting a request
49000
customers
Registered customers who describe junk, upload photos, receive quotes, schedule pickups, and revise declined requests.
1000
staff_members
BayHaul team members who review incoming requests, inspect photos and route details, and accept or decline pickups with notes.
0
anonymous_visitors
People who browse the public BayHaul service information before deciding whether to submit a request.
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
Multiple integrations and ongoing public service require BASIC.
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
5 req/s
not purchased
(plan/kit 5 req/s)
Covered by plan/kit (margin ~0%)
0
Database storage add-on
465.40 MB
10GB × 1/year, amortized monthly
(plan/kit 200.00 MB + add-on +265.40 MB)
Add-on fills +265.40 MB gap beyond plan/kit
8.33
Object storage
add-on
30.87 GB
100GB × 1/year, amortized monthly
(plan/kit 2.00 GB + add-on +28.87 GB)
Add-on fills +28.87 GB gap beyond plan/kit
2.92
Outbound data transfer add-on
2.02 GB/mo
500GB × 1/year, amortized monthly
(plan/kit 2.00 GB/mo + add-on +16.00 MB/mo)
Add-on fills +16.00 MB/mo gap beyond plan/kit
2.92
AI points add-on
101.5M points
6,000,000 AI Points × 17/month
(plan/kit 103.0M points + add-on +100.5M points)
Add-on fills +100.5M points gap beyond plan/kit
170
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
0.47 GB-month
RDS gp3 storage → 0.05
30.87 GB-month
S3 Standard → 0.71
0.00 GB (first 100GB free)
Internet egress → 0
Total ≈ $331.02 / mo
Pure cloud resources
DEVELOPMENT COST
MONTHLY CLOUD INFRA ($/MO)
MONTHLY TOTAL
(INFRA + OPS)
Traditional outsourcing / build in-house
about $140,000 - $190,000
≈ $331
Based on the AWS estimate above
≈ $2,331
Infra $331 + ops ~$2,000
4-6 months
5 / 5
Vibe Coding
about $18,000 - $25,000
≈ $331
Based on the AWS estimate above
≈ $1,831
Infra $331 + ops ~$1,500
hours
5 / 5
AI full-stack generation
about $8,000 - $11,000
≈ $331
Based on the AWS estimate above
≈ $1,831
Infra $331 + 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
$53
All-in: egress / storage / auto-scaling; excludes AI usage
$53
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 description gives no explicit customer or staff population. This is the standard planning assumption for an unspecified online service and can be adjusted when BayHaul provides its expected registration scale.
We assume this is a standard linear-growth service because online quote requests and staff operations are expected to build gradually after launch rather than arrive as a full pre-existing dataset. If BayHaul launches with a large imported request history or experiences an early burst followed by a stable ceiling, this equivalent operating period can be adjusted.
Customer Quote Submission Window
Customer Quote Submission Window
Daily Public Service Browsing
Staff Daily Review Shift
Customer Quote Submission Window
30
times/month
4.8 req/s
Peak load
We assume quote requests are spread across ordinary business hours but become more concentrated during a typical five-minute demand window, when customers who have decided to use the service submit their descriptions and photos. This scenario is separated from scheduling and staff review because it invokes the quote estimator and writes a distinct set of records. We assume the window occurs daily and lasts 300 seconds, giving 30 monthly occurrences.
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.
Customer creates a junk request and receives an AI-generated price range and detected-item list.
Customer accepts a quote and submits the pickup scheduling details.
Customer revises and resubmits a request after staff decline it.
Staff review route-aware pickup requests and record an acceptance or decline decision.
Anonymous visitor browses the public BayHaul service information.
page
data_table
ai_agent
action_flow
Quote Request Page
Customer form for describing junk, uploading photos, receiving an AI-assisted quote, and revising a declined request.
Quote Review and Scheduling Page
Customer page for reviewing the quote and submitting pickup scheduling information.
Staff Request Dashboard
Staff queue and detail workspace for reviewing, accepting, or declining customer pickup requests.
Public Service Page
Public-facing entry page that explains the online junk-removal request service.
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 will drive resource usage for BayHaul Junk Removal?
How do customer photos affect the estimate?
What happens when a customer submits or revises a quote request?
How does scheduling affect the system design?
Why are external mapping services required?
Copy to discuss with AI
Challenge & re-estimate