TL;DR: Multi-tenant admin, custom reporting, marketplace payments, native mobile, and open-ended integrations each blow past a one-day scope. Ship one core loop first; add these in phase two.
Fixed price only works with fixed scope. These five requests look reasonable in a bullet list — and each one can add days, not hours.
1. Multi-tenant admin with roles
"Super admin, org admin, member, guest, audit log" sounds standard. It is also a permission matrix, invitation flows, and UI for every role.
Ship instead: Single-tenant admin or one admin email gate. Add roles when you have paying customers.
2. Custom analytics dashboards
Founders want charts before they have data. Building filters, exports, and date ranges is a product — not a sidebar widget.
Ship instead: Event logging or a link to Plausible/PostHog. Dashboards after you know which metrics matter.
3. Marketplace / split payments
Stripe Connect, KYC, payouts, and dispute handling are not a "quick Stripe add-on."
Ship instead: Single-seller Checkout for your MVP hypothesis. Marketplace is Custom tier territory.
4. Native iOS + Android apps
Mobile clients double your surface area: auth, push, store policies, and release cycles.
Ship instead: Responsive web app. Validate retention before app store overhead.
5. "Any API integration you need"
Unbounded integrations are unbounded risk. Each OAuth flow, webhook, and rate limit is its own mini-project.
Ship instead: Name one integration that blocks the core loop. List the rest as phase two.
How we keep 24 hours real
- Fixed tiers with explicit feature caps
- Intake form enforces tier choice before we start
- Custom tier for honest quotes when the list above is required
Read MVP vs prototype vs landing page if you are still choosing the size of first ship.
Next step
Submit your project with one core user action — we will tell you early if scope needs Custom tier.
Related posts
Ready to ship your MVP?
Start your project