The most common question we get: “How much will this cost?” The honest answer: there’s no single price — but there are clear benchmarks and factors any experienced 1C developer can use to estimate within 1–2 days. Here’s how it works.
Why there’s no fixed price
Customizing 1C isn’t “buying a box.” Every project is a blend of:
- scope: adding a button vs building a 20-document module;
- complexity: one catalog vs integration with 3 external APIs;
- 1C version: Trade Management 11.5 vs ERP 2.5 — a 2–3× labor difference;
- source base quality: clean standard vs “homebrew from 2014.”
That’s why any experienced contractor runs an estimation pass first (usually free, 1–3 days), and only then quotes a price.
Three types of work and their cost
95% of projects come down to these three. Use them as your benchmark:
| Type | Duration | Hourly (USD) | Typical budget (USD) |
|---|---|---|---|
| Report or print form | 1–3 days | 25–40 | 150–400 |
| Document or module | 1–3 weeks | 25–40 | 800–4,000 |
| API integration | 2–8 weeks | 30–50 | 2,000–12,000 |
25–50 USD/hour is the middle of the Uzbek market. Below 20 — usually inexperienced freelancers or pirates. Above 60 — a premium integrator or expat consulting. Teamly operates at 30–40 USD/hour.
5 factors that shift the price
- How clear the brief is. Vague “something like what that other client has” inflates estimates 1.5–2× — we price the risk in.
- How many touch points with the database. A single button on a catalog = 4 hours. Same button plus impact on 6 reports = 20 hours.
- Whether data migration is needed. Moving historical balances from Excel into the new schema is often pricier than the module itself.
- How training is delivered. Recording a video tutorial — 1 hour. Running 3 live workshops for 40 people — 20 hours.
- Warranty and support scope. Usually 3 months free, then monthly hour packages.
Estimation example: a real task
Client: electronics distributor, 30 sales managers. Wants to automate sending an SMS to customers when order status changes.
Breakdown:
| Step | Hours |
|---|---|
| Discussion, SMS gateway pick (Eskiz.uz) | 4 |
| General integration module | 10 |
| ”Status change” event handler | 6 |
| Configuration (templates, send filters) | 8 |
| Testing with real numbers | 4 |
| Documentation + one training session | 4 |
| Total | 36 |
At 35 USD/hour that’s ≈ 1,260 USD. Timeline — 2 weeks.
How to bring the budget down
- Write the brief down. Even 2 pages of “what should work” cuts the estimate 20–30%.
- Start with an MVP module. Often 40% of features deliver 80% of the value.
- Don’t build on top of a homebrew base. Sometimes it’s cheaper to clean up the base configuration first.
- Fix the budget, not the scope. Work inside X hours and prioritize — tackle what matters most.
Avoid this. A contractor who quotes a firm price after one phone call is either missing the mark or baked in a huge buffer. Normal practice — 1–3 days to estimate.
Frequently asked
Can we do fixed-price? Yes, with a clear brief. Without one — time & material only. We value transparency: if we finish in fewer hours, you pay less.
What does the warranty cover? Fixing any bugs in our code for free within 3 months. New features are not included.
How much is post-launch support? From 300 USD/month (10-hour package) to 1,500 USD/month (50 hours + dedicated engineer).
Can we pay in som? Yes, at the Central Bank rate on the invoice date.
How current are these numbers? The above are Teamly’s actual rates as of early 2026. Market rates adjust every 6–12 months.
Free estimate on your task. Describe what you want — we’ll respond in 1–2 days with an hour-by-hour breakdown and timeline. No strings attached.
Also read: Custom 1C in Uzbekistan, Tashkent construction-materials wholesaler case study.
