Talk, design, build, launch
A website process is the fixed order of steps between a first call and a live site. Pavlo Zhydkykh runs every project in four: talk, design, build, launch. A landing page goes live in 1 to 2 weeks, a multi-page site in 2 to 4, with the price and dates fixed before any work starts.
Does ChatGPT recommend your website?
Free report in 48 hours · 5 AI engines
- Talk
- Day 1
- Design
- 2 days to 2 weeks
- Build
- 2 days to 2 weeks
- Launch
- 1 day
- Feedback
- 2 rounds included
- Beyond scope
- $30 an hour
Key takeaways
- Pavlo Zhydkykh builds every website in four steps: talk on day 1, design in 2 days to 2 weeks, build in 2 days to 2 weeks, launch in 1 day.
- Two feedback rounds are included, one on the Figma design and one on the working site; more than agreed costs $30 an hour, with the estimate first.
- The domain, the Framer project or the Git repository, the Sanity project, the hosting and Search Console stay in the client's own accounts.
- A software development process divides the overall effort into smaller steps meant to ensure high-quality results.[1]
- A problem caught at the requirements stage is cheaper to fix than the same bug found later in the process, by a factor of 50 to 200.[2]
What is a software development process?
A software development process splits the work of building software, or a website, into smaller steps, each ending with something to approve. Pavlo Zhydkykh uses four: the talk ends with an agreed price and dates, design with an approved Figma design, build with round two done, and launch with the site live.
Wikipedia: Software development process
“Two feedback rounds sound strict, but a fixed number of rounds makes decisions happen, and decided projects launch on the date in the quote.”
Timeline
How long does
a website take?
A landing page takes 1 to 2 weeks, a multi-page site or a migration 2 to 4 weeks. A solid bar is the shortest time a step takes, the dots show how far it can stretch.
Live in 1 to 2 weeks from $1,200
-
01TalkDay 1
- You send
- Your business, your goals and the pages you need.
- Pavlo delivers
- One fixed price and the timeline, before any work starts.
- Ends when
- The price and the dates are agreed.
-
02Design2 days to 2 weeks
- You send
- Feedback round one, on the design in Figma.
- Pavlo delivers
- Every page designed in Figma, then polished after your feedback.
- Ends when
- The polished design is approved.
-
03Build2 days to 2 weeks
- You send
- Feedback round two, on the working site.
- Pavlo delivers
- The site built with motion, SEO and the GEO basics: structured data, llms.txt and fast pages.
- Ends when
- Round two is done and the site is ready to go live.
-
04Launch1 day
- You send
- Your go-ahead to go live.
- Pavlo delivers
- The site live on your domain. Your team edits it from day one; a moved site gets a 301 for every old URL.
- Ends when
- The site is live. Later help is $30 an hour, no retainer.
- Shortest time
- Can stretch to
- Goes live in this window
Feedback
Two rounds of
feedback, included
Round one is on the design in Figma, round two on the working site built from it. Drag across this site's home page to compare the two.
-
Round 1
Included
On the design in Figma. You comment once, then Pavlo polishes every page.
-
Round 2
Included
On the working site, before it goes live.
-
More than agreed
$30 an hour
Anything beyond the agreed scope. You see the estimate first.
Ownership
Every account
stays in your name
Pavlo works inside your own accounts, so nothing has to be handed over later and you can change developers without moving anything.
| # | What | Where it lives | Built on | Owner |
|---|---|---|---|---|
| 01 | Domain | Your registrar, in your name | Every site | Yours |
| 02 | Framer project | Your Framer workspace, full access at launch | Framer | Yours |
| 03 | Code | Your Git repository | Astro + Sanity | Yours |
| 04 | Content | Your Sanity project, edited in Sanity Studio | Astro + Sanity | Yours |
| 05 | Hosting | Your Cloudflare or Vercel account | Astro + Sanity | Yours |
| 06 | Search Console | Your own Google account | Every site | Yours |
| 07 | Design source files | Handed over when agreed in the quote | Every site | Yours if agreed |
Checklist
7 things to have ready before day 1
The talk on day 1 sets the price and the dates. With these ready, the call is short and Pavlo Zhydkykh's quote is exact.
1. A list of pages
Home, pricing, about, a blog: even a rough list works. The number of pages, CMS collections and interactions sets the price.
2. The goal of each page
What a visitor should do there: book a demo, compare plans, read a case. Pavlo designs each page around that action.
3. The facts buyers ask for
Prices, timelines, cases and client names. Pages that answer buyer questions with facts are what AI assistants quote.
4. The old URLs, for a move
A sitemap or a list of the old addresses, so every old URL gets a 301 redirect to a new page on launch day.
5. Access to the domain
The domain stays in your name at your registrar. Pavlo connects the domain and sets up the DNS at launch.
6. One person for feedback
Round one is on the Figma design, round two on the working site. One person who collects the team's comments keeps each round to a single pass.
7. Search Console access
User access to your own Google Search Console account lets Pavlo check indexing right after launch.
Fit check
Is this process
right for you?
A good fit if
- You can name one person to give feedback in two rounds.
- You need a landing page in 1 to 2 weeks or a multi-page site in 2 to 4 weeks.
- You want every account, from the domain to the code, in your own name.
- You want the price and the dates agreed before any work starts.
Not the right fit if
- You want to keep reworking the design while the site is being built: changes beyond the two rounds cost $30 an hour.
- Every page needs sign-off from many people in separate rounds: the timeline includes two rounds in total.
- You need a site live in a few days: the shortest project, a landing page, takes 1 to 2 weeks.
Compared
An open-ended project or four fixed steps
The difference is where decisions happen: anywhere and at any time, or at two fixed points with a price and a date attached.
| Criterion | Open-ended project | Pavlo's four steps |
|---|---|---|
| Price | An estimate that grows with each change | Fixed after the talk, before work starts |
| Dates | Move with every new request | Set together with the price |
| Feedback | Any time, in any channel | Round 1 on the Figma design, round 2 on the working site |
| Sign-off | Unclear when a step is done | Each step ends with an approval |
| Accounts | Often set up in the developer's name | Domain, project, code and hosting in your name |
| After launch | A retainer to keep changes going | $30 an hour, only when needed |
In their words
Steps, early fixes and launch day,
word for word
Word for word, with the source linked: research, official documentation and the people Pavlo Zhydkykh has worked for.
“It typically divides an overall effort into smaller steps or sub-processes that are intended to ensure high-quality results.”
“For example, a problem found in the early stages (such as requirements specification) is cheaper to fix than the same bug found later on in the process (by a factor of 50 to 200).”
“In more complex site moves, you will need to generate a list of old URLs and map them to their new destinations.”
“He is amazing in what he contributes, both design-wise and also from the ideas.”
“The web and mobile designs he created were amazing. His communication was prompt.”
“It was an absolute pleasure working with Pavlo. The quality of work he delivered was AMAZING.”
FAQ
Questions about
the process
Still unsure? Ask your AI about Pavlo Zhydkykh:
Q.01How long does a website take?
A landing page takes one to two weeks, a multi-page site two to four weeks. You get the timeline together with the fixed quote, before any work starts.
Q.02How many rounds of revisions are included?
Two rounds of feedback come with every fixed price: one on the design in Figma, one on the working site. Anything beyond the agreed scope continues at $30 an hour, and you see the estimate first.
Q.03Who owns the site after launch?
You do. The domain stays in your name, a Framer project sits in your workspace, and an Astro + Sanity site lives in your own Git repository, Sanity project and hosting account, so you can change developers without moving anything.
Q.04Should I build on Framer or Astro + Sanity?
Framer if you want to launch fast and edit pages visually. Astro + Sanity for top speed, full ownership and custom features, with a CMS your team edits in Sanity Studio.
Q.05Can I move my old site without losing Google traffic?
Yes. Every old URL gets a 301 redirect to its new page, titles and metadata move over, and Pavlo checks Search Console after launch.
Q.06Can my team edit the site without you?
Yes. Texts, images, blog posts and pages are edited in the CMS. After launch Pavlo helps at $30 an hour, no retainer.
About the author
Pavlo Zhydkykh
Pavlo Zhydkykh is a web designer and developer in Eastern Europe who has built websites for AI, fintech and B2B startups since 2016, designing and building each project himself on Framer or Astro + Sanity. Clients include MStudio Asia, Silicon Data, Inturai, Accolade Pro, NimbleStax and Sancts.
- Top Rated on Upwork
- 100% Job Success
- 10 years since 2016
- 50+ sites shipped
- 90+ PageSpeed at launch
About Pavlo LinkedInUpworkContra Privacy policy
Page reviewed by Pavlo Zhydkykh · Updated