How we work
Three formats, one way of doing things. Here is how they differ, how each one goes, and what stays the same in all of them.
The formats side by side
Not sure? Tell us the task: we will suggest a format and explain why.
| Project (outsourcing) | Team (staff augmentation) | Audit and consulting | |
|---|---|---|---|
| What it is | A defined result: we take the task from understanding to launch and support. | Our engineers join your team and work in your process and your tools. | A review of code, architecture, security or infrastructure: findings ranked by importance, and what to fix first. |
| When it fits | You need a system or a part of one, and your own team is missing or busy. | You have a product and a process, and you lack hands or rare expertise. | You need to know where a system stands before deciding what to do with it. |
| Who leads | We lead the work and show you the result at every stage. | You lead: the engineers take tasks from your backlog. | We run the review within the agreed limits and access. |
| How the price is set | The scope and the price of each stage are agreed after a short introductory talk. | A monthly rate per engineer. | A fixed price, agreed in advance. |
| What you have at the end | A working system with documentation, tests and monitoring, and support if you want it. | More capacity and the skills you were missing, inside your own team. | A written report with findings and priorities, and a plan you can act on. |
How each one goes
The steps are the same every time, so you always know where things stand.
Project
-
Understand
Who will use the system, what must never break, what already exists.
-
Design
Architecture, data and interfaces, agreed before the code.
-
Build
Short iterations you can see and try, with tests and review.
-
Harden
Security, load and failure checks, monitoring and backups.
-
Support
Updates, fixes and the next features after launch.
Team
-
Request
The roles and skills you need, and how your team works.
-
Selection
We propose engineers for your stack.
-
Introduction
You talk to them and decide yourself.
-
Work
They join your tasks, your tools and your meetings.
-
Review
We check regularly that it works for you, and change what does not.
Audit
-
Scope
What we look at, and the access we need.
-
Review
Code, architecture, security or infrastructure.
-
Report
Findings ranked by importance, and what to fix first.
-
Walk-through
We go through it with your team and answer questions.
-
Next
You fix it yourselves, with us, or as a project.
In any format
What does not depend on how we work together.
-
Three languages
We work in Armenian, Russian and English.
-
Time zone
Armenia, UTC+4: the working day overlaps with Europe, the Middle East and Central Asia.
-
Honest scope
We say at the start what we do not do, and what we would do differently.
-
Written down
Whatever we build or review is documented, so that your team can pick it up.
What we commit to
-
The code is yours
The code and the rights to it pass to you on payment.
-
NDA first
If you need one, we sign an NDA before discussing the details.
-
The first conversation is free
And so is our view on how to approach the task.
How we start
No long forms and no sales funnel.
-
You write
A few lines about the task are enough.
-
We ask
We reply with the questions we need to understand it.
-
We propose
A format, the next steps and how the price will be set.
Questions
Can we start small?
Yes. An audit or one stage of a project is a good first step: you see how we work before committing to more.
Can your engineers join a team we already have?
Yes, that is the Team format: they work in your process and your tools, on your tasks.
How is the price set?
A project: the scope and the price of each stage, agreed after a short introductory talk. A team: a monthly rate per engineer. An audit: a fixed price, agreed in advance.
What if the task is outside your eight directions?
We say so at the start, and do not take it just to take it.
Tell us about your task
A few lines are enough. We will read them and reply with our questions.