Blog
All articlesFAQ: Everything About Development at Webzella — Timelines, Pricing, Tech, and Getting Started
We've gathered answers to the key questions clients ask before starting. How the first contact works, what makes up the price, why we choose React + FastAPI, and what to do if you only have an idea so far.
How We Work
How does the first contact work? What do you need from a client to get an estimate?
The first step is a 20–30 minute call or a Telegram chat. You don't need a finished spec. It's enough to describe the task in your own words: what hurts, which process you want to automate, or what kind of website you need. After that, we ask clarifying questions and send a preliminary estimate with a timeline and budget range within 1–2 business days.
Do you work alone or with a team?
Webzella's format is solo development with specialized professionals brought in for specific tasks. One person is responsible for architecture, code, and communication with you — the founder. This removes middlemen and extra markups. If a task needs an additional specialist, we bring in trusted partners we've worked with on previous projects, but responsibility for the result always stays with us.
What does the development process look like step by step?
We follow a transparent process:
- Brief and task clarification (call or chat).
- Technical specification and fixed estimate. You know exactly what you're getting and what it costs.
- Contract signing and advance payment based on the fixed project cost.
- Development in sprints. Every 1–2 weeks we show interim results (demo).
- Testing and handover. We check scenarios according to the estimate together with you, make business-logic adjustments, and transfer access.
- Support. Warranty period under the contract and further development by agreement.
Can your developer join the client's existing team?
Yes, we work in an outstaffing or part-time format. If you have a product team but lack hands on the backend (FastAPI) or frontend (React), we can integrate into your processes: work on your tasks in Jira/Trello and join regular calls.
How is progress monitored? Are there demos and a tracker?
Yes. You get access to the task board of our Webzella Planner and see the status of every task. Every 1–2 weeks we hold a demo call where we show what already works. No "black boxes" — you see progress in real time.
Pricing and Estimates
How is a fixed estimate formed and what does it include?
The estimate is formed after the technical specification is written. We write it ourselves after gathering all needs and requirements on the first calls. It includes: architecture design, frontend and backend development, server and hosting setup, integrations (CRM, payments, 1C), basic testing, and documentation. The spec is handed over after contract signing and advance payment. A fixed estimate means the final price won't change as long as the scope of work stays the same.
What happens if new requirements appear during the project?
If requirements change, we don't add costs retroactively. We document the change in a separate agreement and show how the new requirements affect timeline and budget. You can also see this in Webzella Planner. You decide: do it now, later, or drop it. It's an honest process with no surprises.
How does the calculator on the website work — can I trust it?
The calculator gives a preliminary price based on average data from similar projects. It's a reference point so you understand the order of prices. The exact figure only appears after discussing the task and writing the spec. If the calculator showed one amount and it grew after discussion, we'll explain exactly which task details affected the price.
Is there a minimum project budget?
We work with projects from 50,000 RUB. If your task is below this amount, we'll honestly say that an off-the-shelf solution is more profitable for you (for example, setting up a SaaS service), and we'll recommend which one.
How does payment work — stages, prepayment, postpayment?
Standard scheme: 30–50% prepayment to start, then milestone payments. We work officially and issue receipts after payment is received. For example: start → prototype → beta → handover. This way you pay for real results, not promises.
Timelines
How long does a typical project take?
It depends on complexity:
- Landing page or simple website: 1 to 3 weeks.
- Telegram bot or request automation: 1 day to a week.
- CRM integration (1C, YCLIENTS) or a personal account on a multi-page website: 6 to 10 weeks.
- Complex system with an AI agent: from 3 months.
What affects timelines and how are they fixed?
Timelines are affected by: spec readiness, the speed of feedback from your side, the complexity of integrations, and the volume of data to migrate. Timelines are fixed in the contract. If we delay delivery due to our fault, we acknowledge it and compensate (for example, with a free support period). If the delay is due to waiting for your feedback, the timeline shifts accordingly.
What happens if the client delays feedback?
We understand that a business has other priorities. The contract specifies an SLA for feedback (for example, a response within 2 business days). If your delay exceeds this period, we revise the schedule and warn you about the shift. There are no penalties for this — only honest planning.
Technology and Security
Why React + FastAPI and not an off-the-shelf solution?
Off-the-shelf (WordPress, Tilda, ready-made SaaS) is good for standard tasks. But when you need unique logic, integration with legacy systems, or control over data — custom wins. React + FastAPI is a stack we fully control: from architecture to security. We covered this in detail in the article ["Tilda, WordPress, or React+FastAPI: Where Your Website's Security Actually Lives"](link to the article).
How is security ensured and how do you comply with 152-FZ?
We design systems with 152-FZ requirements in mind: data is stored on servers in Russia, access is segregated, encryption in transit (HTTPS/TLS) and authentication are used. We don't use third-party plugins with unknown code — only vetted libraries. Security is architecture, not a "plugin you bought."
Where are servers located? Can I host in Russia?
Yes, we host projects on Russian servers (Beget, Yandex Cloud) or on your own hardware or a server you choose. If you have requirements for a specific provider, we take them into account.
Who owns the code and data after the project is handed over?
You do. After full payment, you receive exclusive rights to the code and all data. We don't keep you "hooked": you can take the code, deploy it on your own server, and work with any contractor. The only thing we reserve is the right to mention the project in our portfolio (unless you object).
What about support after launch — warranty, bug fixes, development?
We provide a 3-month warranty for fixing bugs caused by our side. After that, support is by agreement: a fixed package of hours per month or pay-as-you-go. Development (new features) is discussed separately.
Integrations and AI
Which systems do you integrate with?
We work with: CRM (Bitrix24, amoCRM), 1C, YCLIENTS, payment systems (YooKassa, Tinkoff, Stripe), messengers (Telegram, MAX), analytics services (Yandex.Metrica, Google Analytics). If a needed integration doesn't exist, we'll build it via API.
What is "AI agent training" in practice? What tasks does it solve?
It's not "magic" but specific scenarios:
- Auto-replies to requests with context awareness (not just a template, but understanding the question).
- Request classification (urgent/not urgent, spam/client).
- Manager assistance: generating draft replies based on a knowledge base. We train the agent on your data (chat history, knowledge base) and embed it into existing processes. It doesn't replace people — it removes routine.
Can a specific process be automated (example)?
Yes. For example: a client submits a request on the website → the system creates a deal in the CRM → assigns a task to a manager → sends a confirmation to the client in Telegram. All without human involvement. We covered such scenarios in the article ["Business Automation Without a Corporate Budget"](link to the article).
Trust and Legal
Do you sign contracts and NDAs?
Yes, we work only under a contract. We sign an NDA if the project involves sensitive data. All terms (timelines, estimate, code rights) are documented.
Do you work with international clients?
Yes, we work with clients from the CIS and Europe. Communication is in Russian and English. Payment is in rubles or in foreign currency, depending on jurisdiction.
Do you have a portfolio/reviews?
We have 2 completed cases and client reviews. The full portfolio is in the "Implemented Systems" section. We don't publish everything, but we're happy to show relevant examples on a call.
Getting Started
What do I need to do to start?
- Message us on Telegram, email, MAX, or call.
- Describe the task in 2–3 sentences.
- Have a 20-minute call.
- Receive a preliminary estimate.
- Sign the contract and start.
What if I only have an idea, no spec?
That's fine. We'll help you formulate the task and write the spec together. The first call is free and non-binding. If the idea is raw, we'll honestly say what needs to be worked out before development starts.
How do I get in touch and how fast do you respond?
Telegram: @webzella_it, Email: mail@webzella.com. We respond within 2–4 hours during business hours. If you write at night, we'll reply in the morning.
Didn't find your question? Message us on Telegram — we'll answer personally.
Build an estimate or message us — we'll discuss the task.
Webzella services
Read also
Tilda, WordPress, or React+FastAPI: Where Your Website's Security Actually LivesA turnkey website in a weekend sounds tempting. But once it starts taking payments and storing customer data, "fast and cheap" turns into hidden risks. We break down why security is an architecture, not a plugin, and compare Tilda, WordPress, vibe coders, and custom React+FastAPI.
Why a Website Won't Open on iPhone but Works on Android: A Real-World Breakdown of CDN and TLS 1.3The site works, the server is fine, the logs are clean, but half the clients on iPhone either can't load it or see a non-working image. We break down a real-world case: what CDN, TLS 1.3, and RKN whitelists have to do with it.Business Automation Without a Corporate Budget: Where to Start So You Don't Regret It"Digital transformation" sounds like something out of a McKinsey report. In reality, for a business with 10–50 employees, it means one thing: stop doing manually what a system can do. We break down which processes to automate first, how much it costs, and when custom React + FastAPI beats an off-the-shelf solution.