One process
From 50 million tomans
Usually up to 100 million
One clear path: a form, roles, statuses, and a compact report.
- One main job
- Approval and history
- A limited report
Price
These numbers start the conversation. They are not the contract.
They are not a monthly subscription. After a request, we look at the work and price that scope. It may sit near this range, or move because of connections, data, and the delivery date.
One department
From 100 million tomans
Usually up to 200 million
A few connected jobs in one unit. Sales, stock, admin, or HR.
- Several related processes
- Reports for that unit
- Training for the users in scope
Several departments
From 200 million tomans
Usually up to 400 million
Units whose work is tied together. Purchasing into stock, stock into sales.
- Flow between units
- A management report
- Shared data
Several parts in one program
From 400 million tomans
Usually up to 800 million
More users, and a few connections to the programs you already have.
- Several parts
- Finer access
- A staged go-live
A process base or the main system
From 700 million tomans
Up past 2 billion, depending on the phase
A large job. First we have to know whether building it beats extending what you already run.
- A review before any commitment
- Phased delivery
- Connecting the current system may cost less
A very large job
After a review
A price of its own
When data sensitivity, the number of units, or the users do not fit the levels above.
- A separate review
- A separate architecture
- Price after the scope
How payment works
- Half at the contract, before building starts
- A quarter at mid-build, tied to a delivery the contract names
- A quarter when handover matches the criteria that were accepted
Usually separate
Servers, domains, SMS, email, model usage, licenses, hardware, and a heavy data move. If any of that is inside the price, the proposal for that project says so.
We do not name the contract price on the phone, before we have seen the work.