I don't know / Custom
Not sure what you need? Describe your business need.
preliminary project review-first engagement: describe your business challenge and we will help define the right solution together.
Pricing
Preliminary project review requiredThese are non-binding starting calibrations in KZT. Modules, integrations, workload, external services and preliminary project review can change the estimate; the preliminary total is calculated from the current published catalog rules.
Timeline
Preliminary project review and technical scope definition: 3–7 calendar days.
Professional base included where applicable
- Requirements normalization
- Architecture baseline
- Core data model
- Backend/API foundation
- Database foundation
- Basic security
- Error handling
- Basic QA
- Deployment handoff
- Health and logging baseline
- Technical handoff
Modules to validate in Configurator
- Preliminary project review session
- Smart Brief
Example logical architecture
Business need → structured project review → architecture concept → deterministic estimate
Transparent project estimates without hidden coefficients
Estimates use only the published and verified catalog; draft pricing is never shown to customers.
External provider costs are separate and shown when applicable.
Have a project in mind? Let’s define the right next step.
Describe the business need and we will help define the approach, project scope, and initial budget.