A startup site MVP: what belongs in the first release
“A startup site MVP: what belongs in the first release” is a working decision, not a decoration. Admin safety at the minimum: a separate login, a real password, no shared admin/admin, and no extra people. Time and price follow the number of scenarios, the readiness of copy, and integrations. “Beautiful design” barely explains an

In this article
“A startup site MVP: what belongs in the first release” is a working decision, not a decoration. Admin safety at the minimum: a separate login, a real password, no shared admin/admin, and no extra people. Time and price follow the number of scenarios, the readiness of copy, and integrations. “Beautiful design” barely explains an estimate.
A figure without a scope is not a price. Two proposals with different lists of work cannot be compared. One person runs the job from the brief to launch, for teams in Belarus and Russia. The first release stays limited to what was written down. Domain, mail, and hosting access are ready before the final build. “We will buy it on launch day” moves the date.
01What time and price are made of
In practice, “A startup site MVP: what belongs in the first release” shows up as a list, not as a mood. Write the visitor action, the materials you already have, and the place where a request must arrive. Then check the same path on a phone. If a step has no owner, it is not ready, even if the layout looks finished.
A useful page answers a specific question and shows the next step. Extra blocks are added only when they remove a real doubt: scope, timing, limits, proof, or how to get in touch. Blocks added “because other sites have them” make the page longer and the request harder to reach. After launch, a month is reserved for layout fixes. New scenarios are estimated separately.
02A concrete pass through the topic
Walk “A startup site MVP: what belongs in the first release” as a visitor would, with a phone in hand. Start from the first sentence: can a stranger tell what is offered and what to do next without opening a menu? Then follow the form or the order path and name the person who receives it. If that person is “someone in the team”, the path is not finished. Write the doubts a real customer raises — price boundaries, timing, what is not included, how to get in touch — and answer them on the page in the same words you would use on a call. Leave out trophies, vague years of experience, and any promise that a visitor will get the same outcome as an example. The page should still make sense if the decorative blocks are removed.
Before any visual work, collect a small pack: the offer in one or two sentences, who it is for, three facts you can prove, one limit you will not hide, two references you like for the job rather than for the color, and the channel where requests are read every working day. For “A startup site MVP: what belongs in the first release” this pack is the brief. If a fact is missing, the page should say so instead of filling the gap with a generic claim. Access to the domain, mailbox, and hosting belongs to the client. A month after release is for layout corrections that showed up in real use, not for a second project slipped in as a fix.
- 1Check: The price does not promise someone else’s result or hide integrations
- 2Check: The scope is a list, not a paragraph that says turnkey
- 3Check: Copy and access have a date, not “when we have time”
- 4Check: Domain and mail are in the client’s name
- 5Check: The certificate opens without a browser warning
- 6Check: A backup exists before edits on the live site

03Access, hosting, the month after
- The price does not promise someone else’s result or hide integrations
- The scope is a list, not a paragraph that says turnkey
- Copy and access have a date, not “when we have time”
- Domain and mail are in the client’s name
- The certificate opens without a browser warning
- A backup exists before edits on the live site
- The admin makes clear what can be changed alone
Price
Grows from scenarios and integrations. A package called “just a site” cannot be compared without a list.
Hosting
Backup, access, and domain mail matter. The cheapest plan often has no real support.
After release
A month of layout fixes with one person. Later maintenance is its own routine.
Timing
Holds when copy and access exist. Without them the calendar is a wish.
04What to finish before launch day
- 1
Collect access
Domain, DNS, hosting, mail, and ad accounts if they are needed on launch day.
- 2
Test the live path
HTTPS, the form, mail, and a phone call from a real device, not only the developer’s computer.
- 3
Hand over the admin
A short note: what to change, what to leave alone, and where to write if something shifts.
- 4
Keep the month of fixes
A list of layout notes. New wishes are written separately and estimated separately.
- 5
Split the scope
Pages, forms, integrations, content entry, analytics. Each line is in or out.
An estimate without a scope is not a price. It is a conversation.
siteapp
05Questions that usually come up
Why do prices differ so much?
Because the scope differs: content, forms, catalog, payment, sync, support. Compare lines, not the total. On “A startup site MVP: what belongs in the first release” the same rule applies: if it is not written in the scope, it is not part of the first release.
Can you name a price before the brief?
You can name what the price depends on. A fixed sum without a scope should not be treated as an agreement. On “A startup site MVP: what belongs in the first release” the same rule applies: if it is not written in the scope, it is not part of the first release.
What is in the month after launch?
Layout fixes and small page states. New sections and integrations are not hidden there. On “A startup site MVP: what belongs in the first release” the same rule applies: if it is not written in the scope, it is not part of the first release.
Who owns the domain?
The client. A domain and mailbox on someone else’s account are hard to recover later. On “A startup site MVP: what belongs in the first release” the same rule applies: if it is not written in the scope, it is not part of the first release.
Fits a calm launch
A short scope, copy is ready, the domain is yours, and integrations are absent or described as fields.
Moves the date
No access, copy “after the layout”, payment and 1C “along the way”, and several people accept edits.
Send what already exists: domain, copy, who answers requests, and whether payment or accounting is required. That set shows what belongs in the first launch and what only sounds small.
Your case
Talk through this for your site
One person takes the job from the brief to launch: format, scope, the page itself and where the request goes. Leave your name, phone, email and a short note — the reply stays in plain language, without a fixed price before the scope is clear.


