How does the 24-hour delivery actually work?

Once you submit your project request and we approve it, our team starts building immediately. We work in focused sprints, handling everything from frontend to backend to deployment. You receive regular updates throughout the process.

What tech stack do you use?

We build with Next.js 14+ (App Router), TypeScript, Tailwind CSS, NextAuth for authentication, PostgreSQL for database, and Stripe for payments. This stack is proven, scalable, and easy to maintain.

Upon full payment, you receive ownership of the source code, GitHub repository, database schemas, and configuration files created for your project. See our Terms of Service for details on deliverables and third-party components.

What if I need changes after delivery?

All plans include a support period (7–30 days depending on tier) where we help with bug fixes and minor adjustments. For larger changes, we offer additional development at competitive rates.

Can you handle custom integrations?

Yes. Our Custom tier includes integrations with third-party APIs, services, and platforms. Tell us what you need during the project request phase.

We set up everything on your own infrastructure — whether that is Vercel, Railway, or a VPS. You own the hosting account and have full control. We provide the initial setup and deployment.

What happens if my idea is too complex?

We review every request before starting. If your project requires more time, we suggest a custom timeline or break it into manageable phases. We are transparent about what is achievable in 24 hours.

Do you offer refunds?

If we cannot deliver the scope in your approved tier or custom quote within the agreed timeline, we will refund fees paid for that project. Other refund requests are handled as described in our Terms of Service.

Post-Launch: Tier-Based Support and What Counts as a Bug Fix

TL;DR: Every handoff includes a tier-based support window (7, 14, or 30 days) for defects in what we shipped — things that worked at delivery and broke, or never matched the agreed scope doc. New features, integrations, and design changes are phase two.

Founders worry about being alone the moment the preview goes public. Here is how support works after your MVP ships.

Included: tier-based support window

Starting at handoff (code archive + preview/production access):

Tier	Support window
Spark	7 calendar days
Launch	14 calendar days
Scale	30 calendar days
Custom	As stated in your quote

During your window, we cover:

Bug fixes — regressions in shipped flows (auth, core loop, payments if in tier)
Deployment issues on the environment we documented at delivery
Clarifications on how the codebase is structured
Security issues in our delivered code — treated as urgent

Response target: business hours, async-first (email / dashboard messages).

Counts as a bug

Checkout succeeded in testing but fails in production with the same config
Customer cannot sign in despite valid credentials
Data written on submit does not appear on dashboard
Preview URL returns 500 for the shipped build

Does not count as a bug (change request)

"Add Stripe subscriptions" after fixed Checkout was scoped
New third-party integration not in the statement of work
UI redesign or new pages
Performance work on datasets 10× larger than discussed
Features you deferred during intake ("we'll add later")

Those are quoted as Custom follow-on work or a new tier engagement.

How to report an issue

Open your project in /dashboard
Use project messages with steps to reproduce
Include browser, URL, and screenshot if UI-related

For production-down emergencies, use the contact email on your handoff doc.

After your support window

You own the roadmap. We can quote:

Retained hours for small fixes
New sprints for features
Hardening pass (tests, monitoring) — see our quality practices

Next step

Planning your first ship? Pick a tier and submit your project.