PROCESS · NO BLACK BOX

You always know what's done and what's next.

Five stages, 2-week sprints with a live demo, a report every Friday and tracker access from day one. Below is what it looks like from the inside.

sprint with a demo: 2 weeks
weekly report: Fri 17:00
chat reply: ≤ 2 hrs
of your time per sprint: ~1 hr

FIVE STAGES

What happens at each stage — and what you get at the end

01 · Brief and call1 day

We get to grips with your business, audience and constraints. No presentations — 20 focused minutes.

WE DO

Read the brief and your current website
Prepare 5–7 clarifying questions
Hold a 20-minute call

YOU DO

Fill in the brief or message us on Telegram
2–3 examples of websites you like

OUTPUTbrief.pdfcall notes

02 · Estimate and contract1–2 days

A line-by-line estimate: what is included, what isn't, what can be postponed to phase two. The amount is fixed in the contract.

WE DO

An estimate with a range and work lines
Sprint plan and demo dates
Contract, NDA if needed

YOU DO

Approve the scope
Sign the contract and pay 30%

OUTPUTestimate.xlsxcontractroadmap

03 · Prototype and design1–3 weeks

Structure and prototype first — cheap to change. Then the design of key pages and a UI kit for development.

WE DO

Site map and wireframes
Design of key pages, 1–2 concepts
UI kit: colours, typography, components
Mobile versions

YOU DO

Texts and photos (or delegate them to us)
Two rounds of revisions — collected into a single list

OUTPUTFigma prototypeUI kitdesign acceptance act

04 · Development with QA2–8 weeks

2-week sprints. Each ends with a demo on staging — you see a live website, not screenshots.

WE DO

Nuxt frontend, Laravel admin panel
Testing of every sprint
A staging demo every 2 weeks
A report every Friday

YOU DO

30 minutes for a demo every 2 weeks
Access: domain, payment, CRM

OUTPUTstaging URLtest casesreports

05 · Launch and warranty1 week + 30 days

Final regression against the checklist, migration to your hosting, admin panel training. Then a 30-day warranty.

WE DO

60–150 point regression
Analytics and Search Console setup
Migration and DNS
Admin panel video guide

YOU DO

Accept the website against the checklist
Pay the final 30%

OUTPUTchecklist.pdfinstructionsaccess and repository

ANATOMY OF A SPRINT

Two weeks of development — day by day

with youdevelopmentQA

Mond1

Planning 30 minTasks kickoff

Tued2

Development

Wedd3

DevelopmentTest cases

Thud4

Development

Frid5

Code reviewWeekly report

Mond6

Development

Tued7

DevelopmentTesting

Wedd8

RegressionFixes

Thud9

Deploy to stagingSmoke test

Frid10

Demo 30 minSprint report

Your time is about 1 hour per 2 weeks: a 30-minute demo and answers to questions in chat. Feedback from the demo goes into the next sprint plan.

REPORTING AND COMMUNICATION

A report every Friday. Not "everything is on track"

weekly-report · week 6Fri, 17:00 · Telegram + email

## Done[PASS] Cart and checkout — on staging[PASS] LiqPay: test payments go through[PASS] 7 bugs from the previous demo fixed

## Next week[TODO] Nova Poshta integration (branches + parcel lockers)[TODO] "Delivery" and "Payment" pages

## Risks[WARN] Texts for "Delivery" not yet received — needed by Wed, otherwise a 2-day slip

budget: 58% / plan 60%timeline: on scheduleopen bugs: 3 minor

An example of the real report format. We write about risks before they become problems.

Shared Telegram chatdaily

Questions, approvals, quick fixes. A reply within 2 hours during working hours.

Sprint demoevery 2 weeks

30 minutes on Google Meet: we show the live result and collect feedback.

Weekly reportFri, 17:00

Done, plan, risks, budget. Short, in a single message.

Tracker accessalways

You see every task and its status in real time.

Tools

Access is on your accounts or with a guest login

GitHubCode and pull requests. The repository is on your account.

Linear / JiraTasks, sprints, bug reports. We work in yours if you have one.

FigmaPrototypes, design, UI kit. Comments right on the mockup.

PlaywrightAutomated tests for cart, payment, forms — in CI.

Vercel / VPSStaging for every pull request, production on your hosting.

SentryWe see production errors before your customers do.

DEFINITION OF DONE

When a task counts as "done"

Not "I committed it". A task closes only after all the items — this is written into the contract as the acceptance criterion.

7/7 · ready to merge

Let's start with stage 01.

A 5-minute brief — and an estimate with a price and timeline range within 1 business day.

Fill in the brief Telegram Payment stages