Project audit and plan
Define a complex project before investing in development.
- Review 1 business process
- Requirements and constraints
- Phased plan and budget estimate
- Recommendations document; no development
Estimate: 3-5 working days
CODEV_TIM · TASHKENT
We first identify where data, time and control are lost. Then we validate one limited pilot on real scenarios before expanding the system.
from 1 500 000 UZS · scope and estimate agreed before work
Start with your task; a finished specification is optional. We agree the estimate before development.
PROJECT / PRACTICE
Financial ERP connects leads, contracts, delivery, tasks and finance. The case study includes eight real system screens.
About this project →Define a complex project before investing in development.
Estimate: 3-5 working days
Keep customers, enquiries and next actions in one workflow.
Estimate: 15-25 working days
2 agreed revision rounds. Additional work requires approval of its price first. Domain, hosting, paid APIs, licences and professional translation are billed separately. Timelines start once scope is agreed and materials are received.
Tell me about your business. I'll suggest scope, stages and a budget.
We agree deliverables, timeline, cost and payment stages.
I share progress. We check agreed scenarios on mobile and desktop.
We launch, then I hand over code, access and instructions. Support is optional.
This offer covers development around your workflow. We first check whether existing tools can solve the problem. If custom software is needed, we start with a limited pilot rather than promising a whole-business replacement at one price.
One process, up to five employees, customer records, stages and tasks, two access roles and one basic report. Scope and timeline follow a process review. Migration, complex integrations and additional processes are separate.
Agree the scenarios: who creates a customer, changes a stage, assigns a task and reads a report. Demonstrate the pilot on those scenarios, collect feedback and accept the limited stage before expanding.
A structured spreadsheet can be estimated after reviewing columns, relationships and quality. Message history is not automatically a clean database. Migration rules, access and reconciliation are agreed first.
CONTACT / DIRECT
A website, bot or business workflow - let's start with your task.