// terms of service

How projects work: scope, price, support, ownership

Effective 7 October 2026. These terms describe how Oleksandr Shylo (“MakeFlows”, “I”) works with clients (“you”). The written scope we agree for each project is the contract; where it says something different from this page, the written scope wins.

1. Scope and price

Every project starts with a free discovery call or a written brief. I reply with a written scope: what will be built, which tools, what “done” looks like, the timeline and a fixed price.
Prices on the site (“from $150”, “from $200” …) are starting points for the simplest version of each service. The number in the written scope is the one that applies.
Payment terms (deposit, milestones, final payment) are stated in the written scope or the platform we work through (Upwork, Fiverr) and follow that platform’s rules where applicable.

2. Timeline

Typical delivery is 2–3 days for a single-flow automation and 5–10 days for multi-tool or AI projects. The timeline in the written scope starts when I have the access and inputs listed there. Delays caused by missing access, credentials or answers extend the timeline by the same amount.

3. What you provide

Access to the tools involved (Make.com / n8n workspace, CRM, Google account, Telegram bot token, etc.), ideally through your own accounts so ownership is never in question.
Test data I can use safely, and a person who can answer questions within a business day.
Subscriptions and usage fees for third-party services (Make.com operations, n8n hosting, OpenAI/Anthropic API, Google Workspace, Telegram, CRM seats) are yours; they are not part of my price unless the scope says so.

4. Review, changes and acceptance

You review the build against the written scope. Fixes to anything that does not match the scope are included.
Changes to the scope itself (new steps, new tools, new rules) are quoted as a separate fixed-price task — before I build them, never after.
The project is accepted when the scope checklist is met, or 7 days after delivery if I have not heard back, whichever comes first.

5. Handoff and support

Handoff includes a walkthrough video and step-by-step documentation of what was built and how to change the common things yourself.
30 days of free support after acceptance covers defects in what I built and questions about it. It does not cover changes in third-party services (a CRM renaming a field, an API deprecation) — those are quoted as small fixed-price tasks.

6. Ownership

After final payment, you own the deliverables: scenarios, workflows, code, prompts, documentation and the credentials created for the project. There is no lock-in and no hosting dependency on MakeFlows. I keep the right to reuse generic techniques and to describe the project in my portfolio in anonymised form unless you ask me not to in writing.

7. Confidentiality

Anything you share for a project — data, credentials, business details — is used only for that project and is not shared with third parties beyond the services the project itself requires. If you need a signed NDA, send yours or ask for mine before we start.

8. Reliability and liability

Automations depend on third-party platforms that change, rate-limit and sometimes go down. I build with error handling and alerts where the scope allows, but I cannot guarantee the uptime of services I do not control. My liability for any project is limited to the amount you paid for that project; I am not liable for indirect losses such as lost profits or lost data held in third-party services.

9. Cancellation

Either side can stop a project in writing. Work completed to that point is paid for at the pro-rata share of the fixed price and handed over as-is.

10. Law

These terms are governed by the laws of Ukraine, without prejudice to mandatory consumer or platform rules that apply to you. Disagreements are first resolved by talking; both sides commit to a good-faith attempt before anything else.