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.

Preview URL Before You Pay: Why We Show Working Software First

TL;DR: You pay in full before we begin building, then preview a running app on a real URL before final handoff — not mockups. Previews prove the core loop works; they are not a substitute for production hardening.

Agencies sell Figma files. We ship {slug}.on.shipinaday.com — a live Next.js app behind auth, on our preview infrastructure.

What a preview proves

The main user flow actually runs end-to-end
Auth, database, and deployment are wired — not stubbed
Scope matches what you paid for (tier limits apply)
You can share the link with a co-founder or investor

What a preview is not

Load-tested production infrastructure
Every edge case or admin tool
Your custom domain (that comes at handoff)
A promise that every future feature fits the original tier

How it fits our process

Fixed tiers — pay in full, we build, you preview on staging, then receive code archive at handoff
Custom tier — we quote, you approve, then pay; preview follows the same sprint model
Dashboard — track status, ask questions, and manage your project from one place

Why this reduces risk

Fixed price only works when scope is visible. A URL makes scope tangible: either the core loop is there, or we talk before you are surprised at launch.

Next step

Read fixed-price vs custom quote, pick a tier, and submit your project with the one flow you need on day one.