Process
How we work: fixed prices, named people, weekly demos
This page is the contract in plain English: how a project runs, what you see each week, what we promise and what happens when something changes.
Six stages, each with your sign-off
Discovery
1-2 weeks
We interview your team, review analytics and competitors, and agree what the site must do for the business.
- Research notes and goals
- Sitemap and page list
- A written estimate with a fixed price
Your sign-offYou approve the scope and the price, or stop here and keep the work.
Structure
1-2 weeks
Wireframes for every page template, with real headings and content priorities instead of lorem ipsum.
- Clickable wireframes
- Content outline per page
- Navigation and URL plan
Your sign-offYou approve the structure before any visual design starts.
Design
2-3 weeks
Art direction, page designs and a component library, reviewed in weekly demos.
- Desktop and mobile designs
- Component library in Figma
- Two or three revision rounds, per product
Your sign-offYou approve the final designs. Later changes go through a change note.
Build
2-6 weeks
Front end, CMS and integrations on a live staging link you can open any day.
- Staging site updated daily
- CMS with your content model
- Weekly demo recordings
Your sign-offYou approve each template on staging.
QA and content
1 week
We test against the published checklist and help load and proofread the final content.
- QA report against the checklist
- Accessibility and performance results
- Editing guide and walkthrough
Your sign-offYou approve the launch candidate.
Launch and care
30 days
Launch on your accounts, redirects and Search Console checks, then 30 days of monitoring.
- Launch checklist signed off
- 30 days of monitoring
- 60-day bug warranty
Your sign-offYou confirm handover, and the warranty period starts.
How we build: UX/UI design and Next.js
Design and the technical stack are part of every product, not extras you buy separately. A landing page, an online store and a web app all go through the same UX/UI design work and the same build standard: Next.js by default, or the stack you prefer.
UX/UI design starts with structure. We plan each page or screen around the decision your buyer has to make, test the flow in wireframes with real headings, then design desktop and mobile layouts and a component library in Figma. You approve each step before the next one starts.
The build is Next.js and TypeScript by default, or the stack you pick from the list below, hosted on your own accounts. Pages are rendered on the server, so they load fast and search engines read them in full. Content lives in a headless CMS or in Markdown, depending on the product, and the code is mainstream enough for any React or Vue team to maintain.
If you need research before design, the UX research add-on ($2,500) adds user interviews and usability tests on a clickable prototype. It is already included in every web app.
- Wireframes with real content before any visual design
- Custom desktop and mobile design, no templates
- A component library your team can reuse
- Next.js by default, or the stack you prefer, checked against the published QA list
- Code, designs and hosting in your accounts
Stack we build on
- Languages
- TypeScript
- JavaScript
- Node.js
- Python
- SQL
- Bash
- Front end
- React
- Next.js
- Vue 3
- Nuxt
- Astro
- Tailwind CSS
- shadcn/ui
- Radix UI
- Framer Motion
- TanStack Table
- React Hook Form
- Zod
- Pinia
- Zustand
- D3
- Chart.js
- Content and i18n
- MDX
- Nuxt Content
- Fumadocs
- Markdown in Git
- Remotion
- i18next
- vue-i18n
- Back end and APIs
- NestJS
- Express
- Hono
- Next.js route handlers
- Server Actions
- REST
- OpenAPI
- WebSockets
- Data
- PostgreSQL
- Drizzle ORM
- MongoDB
- DynamoDB
- Redis
- pg-boss
- SQLite
- S3
- Cloudflare R2
- Cloud and infrastructure
- Vercel
- AWS Lambda
- AWS API Gateway
- AWS CloudFront
- AWS EventBridge
- AWS Step Functions
- AWS SQS
- AWS SNS
- Terraform
- Docker
- GitHub Actions
- GitLab CI
- Quality and observability
- Playwright
- Vitest
- Jest
- Cypress
- Testcontainers
- Supertest
- OpenTelemetry
- Sentry
- Prometheus
- Vercel Analytics
- Speed Insights
- AI
- Anthropic Claude API
- Claude on AWS Bedrock
- Google Gemini API
- OpenAI API
- MCP servers
- RAG with embeddings
- LLM agents with tool use
- AI vision and OCR
- prompt-injection guarding
- llms.txt
- agent-ready sites
- AI crawler analytics
- Security and supply chain
- SBOM
- CycloneDX
- SPDX
- CVSS
- EPSS
- CSAF
- purl
- dependency scanning
- secret management
- WAF
- rate limiting
- Payments
- Stripe
- Paddle
- LiqPay
- monobank acquiring
- Fondy
- WayForPay
- Portmone
- Privat24
- NBU QR payments
- Apple Pay
- Google Pay
- Auth and sign-in
- Auth.js
- Google sign-in
- Microsoft Entra ID
- Discord sign-in
- Keycloak
- AWS Cognito
- OAuth 2.0
- OpenID Connect
- Email and notifications
- Resend
- nodemailer
- SendGrid
- Telegram bots
- Viber
- Microsoft Teams
- TurboSMS
- Integrations
- Cloudflare Turnstile
- reCAPTCHA
- hCaptcha
- n8n
- Salesforce
- Elasticsearch
- OpenSearch
- Typesense
- Google Maps
- Leaflet
- Google Calendar
- Nova Poshta
- Ukrposhta
- GitHub API
- Azure DevOps API
- Catalog APIs
- BoardGameGeek
- Discogs
- TCGdex
- Rebrickable
- Numista
- Comic Vine
- Open Library
Our 14 commitments
A fixed price, in writing
Every product has a published starting price. After discovery you get one written number for the agreed scope, and that number is what you pay.
Changes are priced before any work
New ideas are welcome. Each one gets a written change note with its price and its effect on the timeline, and nothing starts until you approve it.
A reply within 4 business hours
Messages sent Monday to Friday get an answer from a person on your project within 4 business hours, Kyiv time. Not an autoresponder, an actual answer or a time for one.
A credit if we deliver late
Each milestone has a date in the contract. If we miss one for reasons on our side, we credit 5% of that milestone's fee for every week of delay.
The people on the call build your site
The designer and developer you meet in discovery are named in the proposal and do the work. If we ever need to swap someone, you approve the replacement first.
You own everything from day one
Domain, hosting, repository, CMS and design files are created in your accounts, or moved there before launch. We work as invited users, so you can remove us at any time.
Nothing moves on without your sign-off
Every stage ends with a review against a published QA checklist and your written approval. After launch, bugs in what we built are fixed free for 60 days.
Your rankings are protected in a redesign
Redesigns include a redirect map for every indexed URL, Search Console checks on launch day and 30 days of monitoring, with fixes included.
You can edit the site yourself
Content lives in a CMS your team can use without us. Handover includes a recorded walkthrough and a written editing guide for your pages.
Support with published prices
After launch you can pick a monthly support plan with listed hours and response times, or none at all. There are no hidden recurring fees.
You see progress every week
A weekly video demo, a live staging link that is always current, a shared task board and one short written update every Friday.
You can leave after paid discovery
Discovery is a small, separately priced first step. You keep its research, sitemap and estimate, and you are free to stop there or take them to another team. The written proposal arrives within 3 working days of the discovery call.
No templates, no theme marketplace
Every layout is designed for your content and your buyers. We show the sketches, wireframes and decisions behind each page, so you can see the work.
A written continuity plan
Backup power and connectivity for every team member, a named backup person for every role, and all project data in your accounts. The plan is part of the contract.
When something changes
Projects change, and that is fine. When you ask for something outside the agreed scope, we send a change note within one business day: what it is, what it costs, and how it moves the timeline.
Nothing in a change note starts until you approve it in writing. Small changes inside an approved design are not change requests; they are part of the revision rounds.
Change-request rates
| Change | Price | How it works |
|---|---|---|
| Change request, design | $90 per hour | Estimated in hours before you approve it |
| Change request, development | $95 per hour | Estimated in hours before you approve it |
| Extra section, page template, source or screen | From $250 | Depends on the product's size unit, shown in the calculator |
| Extra language | 12% of base + extra size | Same rule as the calculator |
| Rush delivery | +20% or +40% | Priority or rush schedule |
| Content changes after launch | Free | You edit them yourself in the CMS |
Our published QA checklist
- Latest two versions of Chrome, Safari, Firefox and Edge, plus iOS Safari and Android Chrome
- WCAG 2.2 AA: keyboard paths, focus order, contrast, labels and screen reader checks
- Lighthouse on mobile and desktop for every template, with the scores in the QA report
- Core Web Vitals inside the good thresholds on a throttled mobile profile
- Every form tested for validation, error messages, spam protection and delivery
- Redirects, canonical tags, sitemap, robots rules and structured data validated
- Content proofread in every language the site ships in
- Analytics events fired and checked against the measurement plan
What you'll see each week
Weekly video demo
A 20-minute walkthrough of what changed, recorded so people who missed it can watch later.
Live staging link
The site as it is today, on a private URL that updates with every change we push.
Shared task board
Every task, its owner and its status, in a board you can open any time.
Friday note
One short written update: what shipped, what is next, and any decision we need from you.
Payments
Discovery is invoiced up front, on its own. The fixed build price it produces is split into milestone invoices, each tied to a stage you have signed off. Typical split: 30% at kickoff, 40% at design sign-off, 30% at launch.
Invoices are in USD or EUR, paid by bank wire or Stripe. Bank details and payment terms are written into the contract.
Leaving and refunds
You can stop after paid discovery and keep everything it produced. After that, you can end the contract at any stage boundary and pay only for stages you have signed off.
We never use countdown offers or pressure tactics. If we are not the right team, we will say so and suggest who might be.