Request
Describe the task briefly. Prefer a call or messenger — that works too. We reply during working hours.
Process
Clarity first, code second
We do not start “designing overnight because it is urgent”. We lock the task, scope and money, then move by stages. Fewer surprises for both sides.
Briefing
We map the process, constraints, timeline and what already exists: site, spreadsheets, legacy software, chat threads.
Prototype and estimate
We lock scope, stages and cost. No hidden modules that “you will definitely need later”.
Development
We show intermediate builds. Changes follow agreed stages — not endless “just in case” calls.
Launch
Move to your hosting or ours, check forms, analytics, access, and a short guide for the team.
Support
Bug fixes, small improvements, advice. The system should not freeze on delivery day.
What we need from you
A short task description, examples of sites or tools that work for the job, access to the current site if any, company details, a responsible contact. For accounting — how you track stock, deals and money today: even a spreadsheet or “in the senior manager’s head”.
How we align
Prototype or screen list — before full layout. Intermediate builds on a staging URL. Changes inside a stage stay in the estimate. Mid-flight scope change — we re-estimate, calmly.
How we hand over
Checklist: forms, analytics, access, basic guide. For systems — staff roles and data migration if it was in the estimate. Code and access are yours. We do not hold the site hostage.
Warranty and support
Defects on our side are fixed after launch. We usually include a warranty window for bugs. New features — separate estimate. Support can be a package or on demand.
Request
Describe the task — we reply with timeline and budget range
Name, phone or email. No long brief needed — we will clarify on a call or by email.