What it costs
and what it is made of.
The figures below are the ranges a conversation starts from. We work out the exact estimate after the brief and show it line by line. It can then be cut: we will tell you which items cost the most and what you can launch without.
Packages
The price covers the whole project. After the brief we send an estimate broken down by task.
Start
A landing page, a simple bot, an automation script
5–10 working days
- One product: a landing page, a bot or a script
- Design from scratch or adaptation of your mockup
- Responsive from 320 px and a dark theme
- Enquiry form with a Telegram notification
- Analytics and goal tracking
- Deployment, domain, SSL
- One month of free fixes
Business
A web app, a Mini App, integrations
3–6 weeks
- Everything in “Start”
- Up to 15 screens or a catalogue with filters
- Admin panel for content
- Two integrations: payments and CRM
- Roles and a user account area
- Automated tests for the critical paths
- Load check before launch
- One month of support after launch
Enterprise
A system built for load, several teams, an SLA
from 6 weeks
- Everything in “Business”
- Architecture designed for load
- Queues, caching, horizontal scaling
- SSO and granular permissions
- Deployment inside your own perimeter
- Security audit before launch
- SLA and on-call incident cover
- Code walkthrough for your team
What each package includes
with no asterisks or footnotes.
| What is included | Start | Business | Enterprise |
|---|---|---|---|
| Development | |||
| Prototype before front-end work starts | Prototype before front-end work starts: included | Prototype before front-end work starts: included | Prototype before front-end work starts: included |
| Design | Template or your mockup | Bespoke | Bespoke + design system |
| Number of screens | up to 6 | up to 15 or a catalogue | no limit |
| Responsive from 320 px | Responsive from 320 px: included | Responsive from 320 px: included | Responsive from 320 px: included |
| Dark theme | Dark theme: included | Dark theme: included | Dark theme: included |
| Admin panel for content | Admin panel for content: not included | Admin panel for content: included | Admin panel for content: included |
| User account area and roles | User account area and roles: not included | User account area and roles: included | User account area and roles: included |
| Multiple languages | Multiple languages: not included | one extra language | Multiple languages: included |
| AI and automation | |||
| API integrations | 1 | up to 3 | no limit |
| Automation scenarios | 1 process | up to 5 processes | orchestration |
| AI agent with a knowledge base | AI agent with a knowledge base: not included | one scenario | several roles |
| Answer quality dashboard | Answer quality dashboard: not included | Answer quality dashboard: included | Answer quality dashboard: included |
| Local model inside your perimeter | Local model inside your perimeter: not included | Local model inside your perimeter: not included | Local model inside your perimeter: included |
| Security | |||
| Dependency scanning for CVEs | Dependency scanning for CVEs: included | Dependency scanning for CVEs: included | Dependency scanning for CVEs: included |
| Testing against the OWASP Top 10 | Testing against the OWASP Top 10: not included | Testing against the OWASP Top 10: included | Testing against the OWASP Top 10: included |
| Role-based access checks | Role-based access checks: not included | Role-based access checks: included | Role-based access checks: included |
| AI red teaming | AI red teaming: not included | on request | AI red teaming: included |
| Compliance with 152-FZ | basic | Compliance with 152-FZ: included | Compliance with 152-FZ: included |
| Activity log for audits | Activity log for audits: not included | Activity log for audits: not included | Activity log for audits: included |
| Support | |||
| Free fixes after launch | 1 month | 1 month | 3 months |
| Monitoring and alerts | basic | Monitoring and alerts: included | 24/7 |
| Incident response time | next working day | 4 hours | 1 hour under SLA |
| Source code handover | Source code handover: included | Source code handover: included | Source code handover: included |
| Documentation | README | README + API | full + runbooks |
| Training for your team | Training for your team: not included | 2 hours | full course |
Three offers
that do not fit the ladder.
The audit, the agent rollout and the maintenance retainer follow their own logic, and you can take any of them without a project.
Audit
A penetration test, AI red teaming and a prioritised report
5–7 working days
- Manual testing against the OWASP Top 10
- Dependency and secret scanning
- Report with CVSS scores, PoCs and a remediation plan
- A one-page summary for management
- One free re-test
AI rollout
Building and integrating an agent for one process
3–8 weeks
- Payback calculation before the start
- Knowledge base and tool connections
- Rules for escalating to a human
- Quality evaluation on a labelled set
- Prompt injection testing
- Conversation dashboard and spend control
Subscription
Maintenance, improvements, monitoring
month to month
- 20 hours of development a month
- 24/7 monitoring and alerts
- Dependency updates and patches
- Incident response within 2 hours
- Unused hours roll over for a month
- Cancel at any time
Whether this earns money
or only looks modern.
Put in your own numbers. The calculation is linear and deliberately cautious: it gives an order of magnitude, and the brief gives the rest.
The fully loaded hourly cost with taxes and overheads, including the workplace and idle time.
The calculation assumes automation takes over 70% of the routine and that a human still does the rest. It is deliberately cautious; in real rollouts the share tends to be higher. Hours are per person and get multiplied by the headcount.
The calculation is indicative. We give an exact estimate after the brief.
What moves
the estimate.
- 01
Number of integrations
Every external system brings its own limits, its own outages and its own documentation. One integration adds 15–40 hours of work.
- 02
Readiness of content and access
The most common reason a deadline slips is waiting on copy, photos and CRM credentials. It affects the price indirectly and the launch date directly.
- 03
Load and resilience requirements
100 users and 100,000 are different architectures. Redundancy and queues add work before the first line of business logic.
- 04
Regulatory requirements
152-FZ, database localisation, ad labelling, audit logs. Cheaper to build in from the start than to rework after launch.
- 05
Urgency
A compressed deadline means several engineers working in parallel and overtime. The surcharge is 20–40%, and it appears in the estimate on a line of its own.
Asked most often
before starting.
How do you calculate the cost?
What is the payment schedule?
Why are you cheaper than a traditional studio?
Can the estimate grow during the project?
What happens to the price if the project has to stop?
What affects the price most?
Need a figure
accurate to the task?
Fill in the brief. In working hours we come back with a task-level estimate and a timeline within two hours, and the estimate is free.