Book a $1,500 website, get GTA 6 free →
Book a 30-min call →
21 days · from $1,500 · fixed

Ship It Live · web app sprint

A working web app, live in 21 days.

The dashboard your team runs on spreadsheets. The portal your clients keep asking for. Designed, built and live in three weeks, at a price agreed before it starts.

Enter to send
4.93★ / 32 reviews 75+ shipped Kickoff in 24h

Quick answer

A focused web app — an internal tool, dashboard or customer portal — can be designed, built and deployed in 21 days from a fixed $1,500. Three weeks is enough when the app has one clear audience and one clear job, with data and access decided up front.

By Shaheer Malik · Updated

The plan

Web app development in 21 days: the day-by-day plan

Day one to day 21, written down.

You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.

The scheduleDay 1 → day 21
01Map the processDays 1–3
02DesignDays 4–9
03BuildDays 10–17
04Migrate and testDays 18–19
05LaunchDays 20–21
  1. 1

    Days 1–3

    Map the process

    How the work happens today, where it breaks, and which parts the app should own. Usually shorter than expected because you already know.

  2. 2

    Days 4–9

    Design

    Screens, states and permissions designed and reviewed. Internal tools live or die on density and speed, so both get decided deliberately.

  3. 3

    Days 10–17

    Build

    Database, access control and the interface, with a staging URL early so your team can click through it while there is still time to change things.

  4. 4

    Days 18–19

    Migrate and test

    Your existing data imported and checked. This is usually the fiddliest part and it gets its own time rather than being squeezed into launch day.

  5. 5

    Days 20–21

    Launch

    Live, with your team walked through it and the old spreadsheet archived rather than quietly kept open.

What from $1,500 gets you

What's included in web app development from $1,500

Everything needed to launch — nothing padding the invoice.

Product design for the whole tool, not just the main screen
Login, roles and permissions appropriate to who uses it
A real database with import from whatever you use now
The views, filters and exports people actually asked for
Deployed on your domain or inside your infrastructure
Responsive, so it works on the phone as well as the desk
Source code and design files yours at handover
30 days of post-launch support, included

Who books this

Who web app development in 21 days is for

Built for

Teams running a critical process on a spreadsheet nobody trusts

Businesses whose clients want a portal instead of email threads

Operators who know exactly what they need and want it built

Real situations

Why teams book web app development

Five ways this shows up, and what actually fixes it.

Not hypothetical — the shape of the problem before someone books this sprint, and the specific part of the build that resolves it.

Situation 1

A critical process still lives in a shared spreadsheet

A team runs a genuinely important part of the business — bookings, inventory, client status — through a spreadsheet that everyone is quietly afraid to touch, because one wrong formula breaks everything downstream.

Days 1-3 map exactly how the process runs today, and by day 21 it's real software with roles, permissions and a proper database instead.

Situation 2

Clients keep asking for a portal instead of email threads

A service business manages every client update over email, and clients have started asking, politely at first, whether there's 'a place to log in and see status' instead.

A client portal ships in three weeks, with logins, roles and the specific views and exports clients actually asked for.

Situation 3

Knows exactly what's needed, just needs it built

An operator has spent months refining exactly what the internal tool should do — no discovery phase needed — but has no way to turn that clear spec into working software.

With the process already mapped, days 4-9 go straight to design, and a staging URL is live by day 10 for early review.

Situation 4

Paying per seat for a tool that fits two-thirds of the process

A team pays a growing monthly bill for off-the-shelf software that handles most of their workflow but forces awkward workarounds for the parts that don't fit its model.

A tool built around the actual process, not a vendor's assumptions, replaces the workaround entirely — and the source code is owned outright.

Situation 5

Old system's data needs to move somewhere real

A business has years of records in a spreadsheet or a discontinued tool and dreads the idea of manually re-entering everything into whatever replaces it.

Days 18-19 are reserved specifically for importing and checking existing data — treated as its own phase, not squeezed into launch day.

The honest part

When web app development in 21 days is the wrong choice

When 21 days is the wrong answer.

A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.

Apps needing deep integration with legacy enterprise systems, where the integration is the project.

Anything requiring compliance certification — HIPAA, SOC 2 — which is a programme, not a three-week build.

Processes nobody has agreed on yet. If the team disagrees about how the work should happen, software will not settle it.

Scopefrom $1,500 · 21 days

Inside the 21 days

  • Product design for the whole tool, not just the main screen
  • Login, roles and permissions appropriate to who uses it
  • A real database with import from whatever you use now
  • The views, filters and exports people actually asked for
  • Deployed on your domain or inside your infrastructure
  • Responsive, so it works on the phone as well as the desk
  • Source code and design files yours at handover
  • 30 days of post-launch support, included

Quoted as one number before day one. A week running long is mine to absorb.

Outside the line

  • Apps needing deep integration with legacy enterprise systems, where the integration is the project.
  • Anything requiring compliance certification — HIPAA, SOC 2 — which is a programme, not a three-week build.
  • Processes nobody has agreed on yet. If the team disagrees about how the work should happen, software will not settle it.

Real work, sized and priced separately. You hear it before you book, not at handover.

What it costs

How much does web app development cost?

On this sprint, web app development starts at $1,500 for 21 days of work. The exact price is fixed in writing once the scope is agreed, before anything starts, and it does not move if the work takes me longer than planned. It covers all 8 items listed under what's included.

In the price

  • Everything in the list of what's included
  • The 21-day schedule, written down before you commit
  • Changes inside the agreed scope

Paid separately, directly by you

  • Running costs after launch: hosting, domain and the third-party services the build uses
  • New scope added after the plan is agreed, priced in writing before work on it starts

Fixed price, hourly or a monthly retainer

CompareThis sprintHourlyMonthly retainer
When you know the totalBefore work startsWhen the work is doneMonth by month
If it takes longer than plannedI absorb itYou pay for the extra hoursYou pay for the extra months
A change of scopePriced in writing firstMore hours on the invoiceAdded to the queue

Why I price this way, and when it is the wrong model, is on no hourly rates, and what happens from first message to launch is on how it works.

Where this sits on the price list

  • Every sprint is priced on one published ladder: $700 for 5-day sprints, from $1,500 for 14- and 21-day builds, and from $2,500 for 30-day apps. Every price is on pricing.
  • Not sure what the first version should include? The 5-day discovery sprint ends with a written scope and a fixed quote, and its $700 comes off the build if you book within 30 days.
  • After launch, the monthly partnership covers a steady stream of changes for $2,500 a month, and you can pause it.
  • For a bigger or different build, the project cost calculator and the MVP timeline estimator give a first number in a minute.

After launch · Keep It Live

After launch, I can keep it live.

Hosting, backend, storage, email, security updates, backups and store updates for a flat $299 a month. No team to hire and no servers to manage. You own the code and can leave or sell the app at any time.

See how Keep It Live works

$299 a month · no minimum term

  • Servers
  • Backend and database
  • File storage
  • Email
  • Security
  • Store updates

Questions

Web app development: your questions answered

Before you book

An internal tool, an admin dashboard, a client portal, a booking system, a CRM for how you actually work. One clear audience, one clear job. If it needs several unrelated modules it is bigger than a 21-day sprint and I will scope it properly.

One workflow, not a platform

A 21-day web app is one authenticated workflow in production — not a clickable prototype deck and not a multi-module platform.

Write the job before the stack

When [primary actor] needs to [job], they use this app instead of [spreadsheet / email / workaround], and success looks like [observable event] (saved, submitted, assigned, exported).

If you need several unrelated modules on day one, it is bigger than this sprint — we scope it properly instead of pretending 21 days covers a platform.

Belongs in this 21-day sprintSwitch slug / separate project
One audience, one primary workflowMulti-product “company OS”
Auth + roles needed for that jobNative App Store / Play shipping → mobile cluster
Your data model cut for v1Heavy AI eval harness → /shipitlive/ai-app-in-30-days
Internal ops tool shapeNarrower internal-only framing → /shipitlive/internal-tool-in-21-days
Billable multi-tenant SaaS shape/shipitlive/saas-mvp-in-30-days

Auth + data that must exist in v1

The live timeline already assumes access and data are decided up front. Make the minimum concrete.

v1 checklist (process language)

PieceDone-when looks like
Sign-in pathUsers who should get in, get in; others do not
Roles (if needed)Only the roles the workflow requires — not a full IAM product
Data model cutTables/fields for the job; rest deferred
Import (if scoped)Existing records checked — treated as its own phase, not launch-day squeeze
Backup / export expectationYou know how to get data out if accounts move

Soft planning markers (not an SLA): map the process early; staging URL for review mid-sprint; import window before you call it done when data move is in scope.

Default bias at handoff: cloud / auth vendor accounts in your name so you own the relationship.

Production bar

“Live” for an app means real users on a production URL — not staging cosplay.

Done-when checklist

  • Production URL on HTTPS
  • Auth works for the agreed roles
  • Primary workflow completable end-to-end
  • Error / monitoring hook if scoped on the call
  • Admin escape hatch for the named owner (reset, disable, export — whatever the charter needs)
  • Staging reviewed → production cutover owned

We do not invent MAU, uptime %, or performance numbers here. Soft production-ready wording: the agreed workflow runs for real users on production, with a path to see and fix breaks.

Extra questions

Existing FAQ already covers what counts as a web app, cost, data migration, infrastructure, post-launch changes, and whether the team can use it without training.

Native mobile in the same 21 days?

Usually no. App Store / Play packaging is a different cut — see the mobile cluster (/shipitlive/mobile-app-in-30-days, /shipitlive/ios-app-in-30-days / /shipitlive/android-app-in-30-days siblings). Responsive web for the workflow can still ship here when that is the right product.

Who owns cloud / auth vendor accounts?

You do, by default. Keys and billing visible to you at handoff.

Internal tool vs SaaS MVP vs this page — which slug?

Web app (this page): one authenticated workflow — portal, dashboard, booking-style job — from $1,500 · 21 days.
Internal tool: ops-team-shaped tool — /shipitlive/internal-tool-in-21-days.
SaaS MVP: billable product path — /shipitlive/saas-mvp-in-30-days.
If you are unsure, say the audience and the success event on the call — we pick the sharper slug.

Agents / AI in the same sprint?

Light assist can fit when it serves the workflow. A full agent loop with shadow mode belongs on /shipitlive/ai-agent-in-21-days. Chores vs product craft: agents help the build; they do not replace the craft of auth, data, and production cutover.

Is day 21 a guarantee the app never breaks?

No. Day 21 means the sprint build, auth + data v1, production bar, and handoff package are done. Software still needs owners and fixes. Day counts are planning, not an SLA on uptime or growth metrics.

21 days from now, this could be live.

A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.