Terms of Work

Transparent collaboration terms: workflow format, payment, timelines, revisions, warranty and communication.

Workflow Format

The work process includes the following stages:

  1. Brief — discussion of the task, requirements and goals
  2. Estimate — analysis of scope, timelines and cost
  3. Agreement — approval of spec, timelines and payment terms
  4. Implementation — development with regular status updates
  5. Testing — functionality check and bug fixes
  6. Launch — deployment and project handover
  7. Support — maintenance and development (by agreement)

Payment

Payment options depend on the project type:

  • Development: 50/50 (advance + final payment) or by milestones (advance + payment upon completion of each stage)
  • Support: monthly, fixed amount or hour package
  • Small tasks: hourly or as a package (e.g., 5–10 hours)

Work starts upon receiving advance payment and written confirmation of scope (email, Telegram).

Timelines

Typical completion timelines:

  • Technical audit: 2–4 days
  • Simple website: 7–14 days
  • Complex projects: 2–6 weeks (depends on scope)

Urgent tasks: +25% to cost, timeline depends on current queue and task complexity.

What affects timelines?

Timelines depend on scope of work, feature complexity, need for integrations, availability of materials and feedback. Exact timelines are discussed during project estimation.

Revisions

Within the agreed spec, 1–2 revision iterations are included. Further changes are discussed separately.

New scope includes:

  • Adding new screens or pages
  • Changing functionality logic
  • New integrations with external services
  • Changes not described in the original spec

Cosmetic changes (colors, spacing, texts) are usually included in revisions if they don't change the structure.

Warranty

Bug fix warranty: 14–30 days after project delivery. Critical bugs are fixed within 24 hours.

Functionality changes, new features and improvements after warranty period — separate task, estimated and paid separately.

What is considered a bug?

A bug is an error in functionality that was implemented according to the spec. If functionality doesn't work as described in the spec, it's a bug. If you need to change behavior or add a new feature — that's new scope.

Communication

Main communication channels: Telegram or email (your choice).

Status update frequency: once every 1–2 days or upon completion of stages (depends on project). For urgent tasks — more often, by agreement.

For documentation and formal questions, email is preferred; for urgent questions — Telegram.

Materials and Access

To start work, we need:

  • Link to current website or mockup
  • Task list or description of required functionality
  • Access (for audit or work with existing project): SSH, FTP, admin panel, database access (if needed)
  • Examples of similar solutions or references (if available)
  • Desired timelines and priorities

If something is missing — I'll tell you what else might be needed.

What's NOT Included by Default

The following services are not included in basic development cost and are paid separately (if needed):

  • Content and copywriting — writing texts, selecting images
  • Paid services — API subscriptions, plugins, software licenses
  • Licenses — purchase of CMS, plugin, template licenses
  • Promotion and advertising — SEO, contextual advertising, SMM
  • 24/7 support without SLA — round-the-clock support with guaranteed response time (if needed, we discuss separately)

If any of this is needed — we'll discuss separately and include it in the estimate.

Send me a message and share the link + a short task description — I'll reply with an estimate and timelines.

Contact →