Website & Web App Requirements Template
Organize the items below before requesting outsourcing to receive an accurate quote.
Project Overview
Functional Requirements
Design / UX
Tech / Deployment
Timeline / Budget
Even if you don't have a design mockup, a simple sketch or reference site URL helps us estimate more accurately.
Ready to submit your request?
Send us your requirements and get a free quote within 24 hours.
Use this template and submit your requestA filled example
Below is how a request for an internal room-booking web app was actually filled in. This much detail is enough to price and schedule it.
- One-line summary
- We run shared-office meeting room bookings on a spreadsheet and get double bookings every week. We want booking on the web, visible immediately.
- Who uses it
- About 120 staff across tenant companies (book and cancel only) and three operations staff (full control). Tenants are grouped by company.
- Screen list
- Login, room list, weekly calendar, booking, my bookings / Ops: room setup, all bookings, tenant management, usage statistics
- Must work
- Block overlapping bookings, remind 30 minutes before, record no-shows, total monthly hours per tenant
- Nice to have
- Google Calendar sync, QR check-in on site
- Volume
- Eight rooms, 40–60 bookings a day, one year of history kept
- Where it is used
- Mostly on phones. Only the ops team is on desktop.
- Budget and schedule
- Around 8 million KRW, two months. If that is tight, QR check-in can go.
"Mostly on phones" is the line that moves the price. Mobile-only means one set of screens; getting both desktop and mobile right properly is more work.
What moves the price and the schedule
Two things both called a web app can sit a band apart. The exact figure needs a screen list, but deciding which of these three you are in already places it.
The simplest band — an internal tool people look things up in. Weeks, not months.
Sign-up, password recovery and permission splitting are each work. This is one band up.
Gateway approval, failed payments and refunds come with it. This is the biggest single jump.
So two lines in your request — is login needed, is payment involved — are enough for us to narrow the band straight away. If the budget is fixed, we will also say what has to come out to fit it.
What happens after you hire us
We start by fixing the screen list together. A difference of understanding turns up here almost every time, and it is far cheaper here than after development starts. Then we build screens one at a time and show them to you as they go, so you can say what to change while it is still cheap. We do not build everything and reveal it at the end — by then, undoing a wrong turn is expensive. At the end we walk the acceptance checklist together before the balance is paid.
Worth settling before you hire
Writing the screen list on paper is the fastest start. No drawings needed, just the names in a row — that count is the size of the job. Next to each, note who sees it, and the permission model falls out on its own. Finally mark the features that make it unusable if missing, and when the budget is short we can say straight away what to defer. With those three we can quote without a first meeting.
What goes wrong when a field is left blank
We build it so everyone can edit every booking. Splitting permissions afterwards means rebuilding screens.
Sending messages or email means wiring up an external service. Out of scope now is an added cost later.
One year and five years of history need different approaches to keep queries fast.