People often ask me: "How much does it cost to build a system?" The honest answer is that it depends on what the system has to do. I don't build template business-card sites or landing pages. My projects are web applications with business logic, CRM, ERP and payment integrations, AI assistants and RAG over documents, and complex Telegram Mini Apps. Two projects both called "customer portal" can differ in scope tenfold.
So instead of a price list I ask for a short brief, and then I send a concrete proposal. This article explains what to put in the request and what you get back.
Why there is no fixed price list
The cost of a complex project is driven not by screens but by what sits behind them: how many systems need connecting and how good their APIs are, which roles and permissions exist, the security and personal-data requirements, the expected load, and whether there is legacy code to understand before changing it. A price list "from N" either underprices a complex project or overprices a simple one. Both are bad for the client.
What to write in the request
You don't need a forty-page specification. It is enough to answer a few questions in your own words:
| Question | Example answer |
|---|---|
| What business problem are we solving? | Managers spend two hours a day copying orders from the website into the CRM |
| Who are the users and what roles do they have? | Customers, sales managers, warehouse, accounting |
| Which systems need integrating? | A WordPress site, KeyCRM, BAS accounting, LiqPay payments |
| What already exists? | The site and CRM work, API access is available, the previous contractor disappeared |
| How do we know the project succeeded? | No manual copying, payments reconciled automatically every day |
| Constraints | Deadline before the season, data must stay in the EU |
Links to the current product, process diagrams, sample documents or screenshots help a lot. The request form on the site lets you pick the service and an approximate budget range. The range is not a commitment, but it helps me suggest the right approach: a full system, a phased launch or an audit first.
What happens after the request
1. I read the brief and ask clarifying questions if needed.
2. A short call to go through processes and risks. We sign an NDA if needed.
3. You get a written proposal: scope, architectural approach, milestones with deliverables, timelines and the price of each milestone.
4. If there is too much uncertainty, I first propose a paid discovery or audit phase: understand the legacy code, verify the APIs, prototype the risky part. Its result is a precise plan that stays with you whether or not we continue.
How I price work
| Factor | Why it matters |
|---|---|
| Integrations | Every external system adds data mapping, error handling, reconciliation and monitoring |
| Roles and permissions | More roles means more scenarios, checks and tests |
| Data and security | Personal data, payments and access audits need dedicated work |
| AI components | Data preparation, quality evaluation, model cost control |
| State of existing code | Legacy code without tests or docs needs an audit before changes |
| Load | Traffic spikes, queues, caching, load tests |
I fix the price per milestone: each milestone has a concrete, verifiable result and is paid after acceptance. For long-running products there is a monthly engagement with an agreed scope.
What you get
Code in your repository, not mine. Documentation for the architecture, integrations and deployment. Tests for critical scenarios. Monitoring and accounts registered to your company. The goal is that the product can keep evolving with me or with another team, without depending on one person. For how I scope a first release, see https://zavada.dev/blog/how-i-scope-an-mvp.
When I'm not the right fit
If you need a simple landing page, a template online store with no integrations, or the cheapest option at any cost, a studio or a website builder is a better choice. I work where engineering quality matters: complex logic, data, money, AI and responsibility for production.
Conclusion
A good brief is five or six answers about the business problem, users, systems and success criteria. That is enough for me to come back with a concrete plan, milestones and a price instead of a vague range.
See the areas I work in: web applications https://zavada.dev/web-apps, AI solutions https://zavada.dev/ai-solutions and Telegram Mini Apps https://zavada.dev/telegram-mini-apps. When you are ready, fill in the request form: https://zavada.dev/contacts
Need a developer for the long run?
I can start now and work with you for months or years, not hand off after two weeks. Send me a message and we will talk through your project, requirements and next steps.