Study
We study the current process and formulate the target one. Sometimes it turns out that software does not solve the problem at all.
The project is split into self-contained stages. Each is accepted separately, and after any of them you can stop without losing what is already done.
We study the current process and formulate the target one. Sometimes it turns out that software does not solve the problem at all.
The structure of the system, the data model, external links, draft interfaces.
In short cycles, showing a working part every two weeks.
Scenario and load checks written up so they can be repeated on every version.
Data migration, staff training, work in trial mode.
Fixes, refinements and growth once the system is already in use.
The study takes two to four weeks, and a working first version appears no sooner than three months later. Exact figures we give once the study is done.
We study the way you work and estimate the return from automating it. It is paid for as a stage in its own right.
A working interface mock-up you can click through. Discussing it is cheap, unlike discussing finished code.
We show the result as we go rather than presenting everything at once on acceptance day.
Trial operation, corrections against your comments, handover of documentation and rights.
Features added just in case eat up the budget of the first version. Experience shows that a sizeable share of the capabilities ordered up front is never used once. It is cheaper to ship a narrow working version, watch how people actually behave and build the rest later.
To the client. We hand over the source code and documentation and fix the rights in the contract. This matters on principle: development after which you cannot change contractor ties a company down for good.
Often it does, and we say so plainly even though the opposite suits us better. Writing your own is worth it when the process really is unusual, or when the amount of reworking of a ready product exceeds building from scratch.
By working in stages with a fixed price for each. After the study the picture becomes clear, and the scope of the first release can always be trimmed, with part of it left for later. You can stop between stages without losses.
Describe the process you want to automate. We will start with a study, which sometimes shows that development is not needed.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.