Development outsourcing
Outsourcing development means you hand over a whole area while we answer for the scope, the deadlines and the result at acceptance. What is left to you is making decisions about the product rather than managing contractors.
Outsourcing is taken up for two reasons. Either there is no in-house team and setting one up for a single area is expensive and slow. Or the team exists but is busy with something else while the task will not wait. In both cases you are buying not people but a closed area: with responsibility for the deadlines, for the scope and for everything working at acceptance.
Failures in outsourcing are almost always about the same thing. The client hands the task over turnkey and disappears for three months, and then it turns out that the wrong thing was built. That is not how we work: one person on your side has to answer questions and make decisions about the product. An hour of their time a week saves weeks of rework.
The second thing worth stating up front is that change is inevitable. Over the course of a project the scope always shifts: something turned out to be unnecessary, something else surfaced along the way. So we work in iterations with a demo every two weeks and record changes in writing, along with their effect on the timeline and the price. A surprise at the end of the project suits us as little as it suits you.
And third: outsourcing should not end in dependence on the contractor. Code, infrastructure and documentation accumulate on your side from the first stage rather than arriving as a single archive on the last day. If you one day decide to run the area yourself or to move it to another team, that should be a decision rather than a problem.
Any area can be handed over in full: web development, mobile apps, design, the backend or the infrastructure. If you do have a team and only lack people, see outstaffing. If it is unclear what is happening with a running product, start with an audit or IT consulting. How this looks over a long distance can be seen in the Silent Notary and SignItNow cases and in the ecosystem projects: the wallet, the exchange, the staking platform.
What the service covers
Any combination of the items below can be taken on its own.
We take it in full: discovery, design, development, infrastructure, launch and support. We answer for the result rather than for individual roles.
A line-up chosen for the task: developers, a designer, a tester, an infrastructure engineer, a lead. It changes during the project if the needs change.
A plan by stage, acceptance criteria, a demo every two weeks. It is visible what is done and what comes next.
Changes to the scope are recorded in writing along with their effect on the timeline and the price, before we start doing them.
A description of the architecture and the decisions, deployment instructions, walkthroughs for your team. It accumulates during the project rather than being written in the final week.
On-call duty, fixes and further development under a separate agreement.
How we work
The goal, the constraints, what already exists, where the risks are. The output is a specification, a plan by stage and an estimate.
We pick the people for the task, set up access and environments and agree the rhythm and who makes the decisions.
Two-week iterations with a demo, each of which can be seen live.
Verification against criteria agreed in advance, transfer of the result to your side.
Documentation, training for your team, on-call duty and development.
Frequently asked questions
In outsourcing we answer for the result in full: the scope, the deadlines, the acceptance. In outstaffing we place people inside your team, while you run the project and answer for the result.
It depends on how well defined the task is. A clear scope is priced fixed by stage. Where the scope will change along the way, an hourly arrangement with a cap per stage and written changes is the more honest one.
A demo every two weeks, access to the task tracker and the repository, a report by stage. You can look at the product itself and not only at the reports.
That is normal and happens almost every time. We record the change in writing, show its effect on the timeline and the price, and only then take it on.
The team is distributed and its working hours overlap with European ones. We communicate in Russian, English and German.
Everything is set by the contract, and we put it in writing at the specification stage, before the work starts. During the project the team works either on our infrastructure or on yours: the choice depends on the complexity of the project and on whether you already have infrastructure in place. Every approved stage is transferred to your servers and your repository, so the work accumulates on your side from the first stage rather than arriving as an archive on the last day. Once the project is closed, all code, materials and documentation are handed over to you together with the rights to them.
You receive the code, the infrastructure and the documentation together with the rights to them. From there you can run the area yourself, leave support with us or move to another team.
Related services
Shall we discuss your task?
Tell us what needs to be done and we will come back with an estimate, the team composition and a plan for the first two weeks.