The analysis is done, the decision has been taken, and what is needed now is someone to do the work. The work starts from what is written down: requirements, data model and acceptance criteria first, not afterwards.
The same analyst-developer does the work from start to finish. From requirements to a working solution and on to handover, one person is accountable, so the description and the build do not drift apart.
If what is in front of you is replacing an old system and moving the data across, that is a job of its own with its own logic: System replacement and data migration.
The code lives in version control, changes go through review and automated tests, and deployment runs in a CI/CD pipeline. The data model, the interface descriptions and the decision log are written while the work happens, not at the end. The same goes for logging and monitoring: when something goes wrong, the trace has to be readable six months later too. A current toolchain and a tidy repository are the reason the next person can carry the work on instead of starting from zero.
The source code and the documentation stay with you. You can change partner at any time.
Development work is agreed in a written offer stating scope, timeline, assumptions, acceptance criteria and price. Acceptance, warranty and rights to the work are governed by our General Terms and Conditions. In brief:
The exact wording is in the General Terms and Conditions and in the contract. This list is a summary, not contract text.
Secure development is a way of working: authentication and permissions from the start, input validation, secrets kept out of the code, dependencies kept current, and logging done so that afterwards you can tell what happened and who did what. These decisions are cheap to make in the first sprint and expensive to make after go-live. For attack testing and penetration testing we bring partners in, and we agree that before the work starts.
The founding analyst has 13+ years of practice with systems, data models and interfaces in banking, telecom, IT consulting and logistics. The technical side has been a daily part of that work: designing data models, writing queries and data-quality checks, describing interfaces and checking how they behave.
The way the work is organised follows from that. One person accountable, a written scope, agreed acceptance criteria, a warranty, and transfer of rights. Qualification: BCS Foundation Certificate in Business Analysis. Working languages Estonian and English.
We write in Estonian first. The pieces below have not been translated yet and open in Estonian.
Each of these is a starting point; we settle its scope in conversation and fix it in a written offer. The steps can be taken separately, or one after another in a logical sequence.
A fixed-scope written assessment of an existing solution. Suits you before a larger development decision, a change of partner, or a takeover.
What it includes:
A working sample solution for a narrow, agreed case, using your data. It answers the question of whether the idea works, before a budget is built on top of it.
What it includes:
From requirements to a working solution, and on to handover. One person accountable across the whole chain, a written scope, and agreed acceptance criteria.
What it includes:
Development capacity in your team in an agreed volume, when priorities shift as you go and work has to be taken off a queue.
What it includes:
Write down what exists and what is missing. We talk the scope through and send a written offer. We reply within one working day, and the first discussion is free.
