Roles and screens plan
A scheme of who sees and does what in the application, which you approve before development.
Cookies on this site
The site stores what it needs itself: your theme, your animation setting and this choice. Analytics, marketing and external services switch on only with your consent. You can change your mind at any time. More about cookies
A web application is a service where people sign in under a role, enter data and see the result: a client account, an order system, internal records. We name the price in writing after a short brief, before you pay.
A scheme of who sees and does what in the application, which you approve before development.
An application that opens on a phone and a computer from a link, with no installation.
Sign-in under a role: each user sees only what they are meant to see.
Data exchange with spreadsheets, mail, messengers or an accounting system, if you need it.
After full payment everything passes to you with a description of how the application is built.
We find out who will use the application and what task it solves. We send you the estimate.
We draw the screens and the user’s path. You approve the scheme before development.
We build the application in parts. You review each on a test version and accept it.
We publish, train the people who will work in it and hand over code and access.
A website shows information, while an application works with data: the user signs in, enters something, changes a status or downloads a report. Examples: a client account, an order system, supply tracking, a staff portal.
The application opens in the browser of a phone or computer, with nothing to install from a store. If you need an icon on the home screen and a place in the app stores, that is a different service: a mobile app.
Two of our own products are built as web applications. They are our developments, not client orders, and you can open them yourself.
We do not name application prices at random: one application has three screens and one role, another has ten roles and a link to an accounting system. First a short brief: who uses it, what they do, what data is needed and which services to connect. After it you get a written estimate with the sum in drams, the stages and the term.
The price depends on the number of roles and screens, integrations, languages and whether AI is needed. You pay in stages, for accepted work.
After full payment the code and access belong to you, and any developer can carry the application on. If you need fixes and updates after launch, you can take them under support.
It depends on roles, screens and integrations, so we name the price in writing after a short brief, before you pay. We promise no figures in advance.
A website shows the same information to everyone. In an application a person signs in under a role and works with data: files, marks, reads a report.
No. A web application opens in the browser. In SnabKontrol a foreman marks cargo just by pointing the camera at a QR sticker, with no registration.
Yes, but first we look at what the site is built on and how to fit an account in. We discuss it at the brief.
Yes, for example reading invoices and delivery notes from a photo, as in SnabKontrol and Dokver. Whether you need it, we decide at the brief: AI adds work.
A description of how the process runs now: who does what, where the data is kept, where time is lost. Sample documents and spreadsheets help.
Talk to us
Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.
Animation is off because your system asks for reduced motion.