01
The beginning
A short diagnosis of the process and business goal.
Systems – questions and answers
Custom systems — questions about costs and implementation
A good start requires a clear goal, a process owner and access to the people who do the day-to-day work.
02
Stages
Scope divided into working, verifiable parts.
03
After implementation
Care, measurement of effect and conscious development.
01Questions about systems
What to prepare for the first interview?
All you need is an example of a process that is not working well today: a sheet, a form, a diagram or a description of the last few cases. You don't need the complete specification.
New design
Prepare an example of current work, users, expected outcome, and tools that are expected to remain.
Existing system
Provide the version, hosting, number of users, custom extensions and the area that needs to be changed.
Questions and answers
Before making a decision
Do you need to replace all the tools you use?
NO. It is often better to leave specialized systems and combine them into a coherent process.
How is the valuation created?
After recognizing the goal and scope, we prepare a stage or variants. A quote without understanding the data and exceptions would appear to be accurate.
Is it possible to transfer data from the old system?
Usually yes, but first we assess their quality, completeness, format and ordering rules.
Will I get access to the code and documentation?
The scope of transfer of sources, rights, documentation and access should be clearly described in the contract. We set it before we start cooperation.
How to avoid downtime during startup?
We prepare a test copy, migration test and acceptance criteria. The switchover date and return plan depend on the process; absence of interruption cannot be guaranteed without analysis.
Can the system work with a store or accounting?
Yes, if appropriate exchange mechanisms are available. You need to check the API, formats, permissions and scope of data on both sides.
How to take future changes into account?
We design module boundaries and the data model, and document dependencies. We evaluate subsequent functions in terms of their impact on existing processes, instead of adding them without review.
Is the sample system a finished product?
NO. The scenarios on the page show the types of applications. We confirm the availability of existing modules and the required scope of adjustment individually.
What determines the implementation time?
From the scope of the first stage, data quality, integration, number of exceptions and availability of people for decisions and tests. We set the schedule after recognizing these dependencies.
What costs beyond construction need to be taken into account?
Licenses, hosting, backups, maintenance, external services and development. We separate one-off and recurring costs and state the assumptions about user numbers and workload.
Who checks the system before launch?
We perform technical verification, while designated users work through the agreed scenarios. Acceptance testing should also cover errors, reversals and corrections to data.
Can different people see different data?
Yes. We design roles and rules for access to records, fields and activities. View restriction does not replace permission control on the data side.
Does the migration include photos and documents?
It may include them, but you'll need to identify the files, formats, and associations. The trial import checks both the number of records and the ability to open the correct attachment.
Do you adopt existing solutions?
We first check source code, access, documentation, licenses and recovery options. The findings allow us to plan maintenance or modernization.
Let’s start with a conversation
Does your case not fit into the short answer?
Send us a description of the process and your main question. We will establish what information is needed to provide a meaningful answer.
Ask a question about the system