Five services, one accountable team.
Tap a service to see what it includes, what you receive and how the work runs.
Web platforms
For when customers or staff depend on a web system every day — and the current one is slow to change, hard to trust or doesn’t exist yet.
Discuss a web platformWhat’s included
- Architecture and technical design
- Frontend and backend development
- Automated tests and code review
- Deployment, hosting and monitoring
You receive
- D1A production application, running on infrastructure you own
- D2Source code and full repository access
- D3Technical and handover documentation
How the engagement runs
- Step 1Discovery1–3 weeks
- Step 2Build in iterationsdemo every 3–7 days
- Step 3Launchwith handover
- Step 4Supportoptional
Mobile applications
For when your customers or field teams need the product in their pocket — working with the same data and rules as everything else you run.
- Includes
- React Native (cross-platform) or native apps, API integration, store release
- You receive
- Apps published under your developer accounts, source code, release notes
- Engagement
- Same rhythm as web: discovery, iterations, launch, optional support
Backend & integrations
For when data is retyped between systems, reports don’t agree, or a new product has to talk to the platforms you already run.
Includes
API design and development, integrations with payment, ERP and CRM platforms, data modelling and migration.
You receive
Documented APIs, source code, and a runbook for each integration — what it does, how it fails, how to fix it.
Next step
Send us the list of systems involved. We’ll come back with questions before any estimate.
Discuss an integrationProduct discovery & UX
For when the idea is clear but the product isn’t — and building the wrong thing would cost more than finding out first.
| 01Interviews | 02Flows | 03Prototype | 04Scope | |
|---|---|---|---|---|
| You bring | Access to the people who use, sell or support the product | Decisions on what matters first | Time for two or three feedback sessions | Budget and timeline constraints |
| You get | A findings summary: who the users are and what they need | Agreed user journeys and wireframes | A clickable prototype tested with real users | A prioritised backlog and an estimate you can plan with |
Typical length: 1–3 weeks · Can be booked on its own
Book a discovery phaseSupport & continued development
For live products that need someone responsible: fixing what breaks, keeping dependencies current and shipping planned improvements.
- Monitoring and incident response
- Dependency and security updates
- Planned features from a shared backlog
- Taking over systems built by other teams
01Web platformsFor when people depend on a web system every day — and the current one is slow to change or doesn’t exist yet.
- Architecture and technical design
- Frontend and backend development
- Automated tests and code review
- Deployment, hosting and monitoring
- A production application you own
- Source code and repository access
- Technical and handover documentation
- Discovery 1–3 weeks
- Build in iterations demo every 3–7 days
- Launch with handover
- Support optional
02Mobile applicationsThe product in your customers’ pockets, using the same data and rules as everything else.
03Backend & integrationsWhen data is retyped between systems or a new product must talk to the ones you run.
04Product discovery & UXFinding out what to build before building it.
05Support & developmentSomeone responsible for the live product.
Pick the shape that fits the work.
| Fixed-scope project | Dedicated team | Support retainer | |
|---|---|---|---|
| Best when | The goal and scope are clear enough to estimate | Scope will evolve and you need steady capacity | The product is live and needs ongoing care |
| Scope | Agreed up front; changes go through a written change request | Re-prioritised with you every iteration | A shared backlog of fixes and improvements |
| Pricing basis | Fixed price per milestone | Monthly, per team member | Monthly retainer |
| Team | Put together for the project | The same people every month | Named engineers who know your system |
| Reporting | A demo at each milestone | A demo every 3–7 days | Monthly summary |
Fixed-scope project
- Best when
- Scope is clear enough to estimate
- Scope
- Agreed up front; changes in writing
- Pricing
- Per milestone
- Reporting
- Demo at each milestone
Dedicated team
- Best when
- Scope will evolve; you need capacity
- Scope
- Re-prioritised every iteration
- Pricing
- Monthly per person
- Reporting
- Demo every 3–7 days
Support retainer
- Best when
- The product is live
- Scope
- Shared backlog of fixes
- Pricing
- Monthly retainer
- Reporting
- Monthly summary
Questions clients ask first.
Not covered here? Ask directly; the answer goes into this list if others need it too.
Ask a questionCan you take over an existing codebase?
Yes. We start with a short audit of the code, infrastructure and documentation and tell you plainly what state the system is in, what needs fixing first and what it will take — before you commit to anything. Then we take over development and support step by step, without interrupting your business.
Who owns the code?
You do — the repository, the accounts and the documentation. Source code, infrastructure accounts, access credentials and technical documentation are transferred to you, and you keep full access during and after the project.
How do you estimate a project?
By scope. We break the work into parts, estimate each one with the engineers who will build it, and give you a range rather than a single number, with the assumptions behind it. The range narrows after discovery, and any change in scope is agreed in writing before work on it starts.
Will you sign an NDA before we talk?Will you sign an NDA first?
Yes. If you prefer, we sign a non-disclosure agreement before you share any details of your project.
Which languages can we work in?
Uzbek, Russian and English — for calls, documents and the product itself. If your product needs another language, we can build it in that language too.