Web application
A service in the browser: roles, flows, data. This is not a set of pages, and we price it that way.
Guide from 1 200 000 ₸
Not an offer. The quote comes after the brief.
We work across Kazakhstan remotely. We do not promise a visit or an office in the city: a call and online delivery are enough.
We build the web application around the flow. We do not promise a stack until it is in the brief.
Who it is for
- services with a client account
- internal teams with roles
- companies that have outgrown a brochure site
- projects with repeated operations
What is included
- a role map: who sees what
- one end-to-end flow from sign-in to result
- statuses and notices that earn their place
- a first version you can put in front of users
How we proceed
- 1We describe the roles and the main flow.
- 2We build the screens for that flow.
- 3We add statuses and permissions.
- 4We walk the path with you on test data.
Questions
Which stack?
We name it after the brief. Before that we do not promise a platform.
Is it a site or a product?
If there are roles and repeated operations, it is an application. A card site is a different job.
Can we start with one flow?
Yes. That is the point. A second flow is not hidden in the first quote.
Where is the data?
In your system. Export and access are agreed separately.
Nearby tasks
The same format in other cities
Cities of republican significance are already on the map. Click a region to show its cities. Drag the map and zoom with the wheel.