What you get

Portal Engine

Exclusive rights to the portal and its source code belong to the customer.   The portal is installed on a leased web server. We take care of setting up and maintaining the server.

Portal Engine

Development team

It is from the team that 40% of the startup's success depends. It is their hands that make the project. The quality of the team's work will primarily affect how fast your startup will "run": it will stumble at every step or will overcome all the difficulties that arise. And they in any case will be and must be ready for this.

Development team

Our experience

A startup is always a high risk and a lot of pitfalls. In the project, in addition to participation as simple developers of engines, we offer our experience and options for solving emerging problems. Most errors can be avoided if the necessary measures are taken in time.

Our experience

Product Management

We do not need projects "in the table". We offer customers to jointly plan the future of the product and develop it based on feedback from the market. They planned, implemented, received feedback, made conclusions and entered a new cycle

Product Management

How we work

        

In our work we use 2 approaches: a flexible development methodology and an incremental model. Each has its pros and cons. It is better to apply a flexible model to most projects.

Agile

Стандартный

Sense

Agile:

The project is implemented in the form of iterations. Each iteration - this is the formation of the task, the implementation and implementation in operation. There is no general detailed plan for the whole project

Standart:

In the incremental model, the overall planning of the project is first done, and then the project is implemented in stages with the demonstration of the intermediate results in the form of releases.

Process

Agile:

Concept - Rough estimation - Initial site - TOR and refinements - TOR and rework with parallel implementation, etc.

Standart:

The project concept - Rough estimation - Writing a complete TOR - Detailed assessment - Implementation by stages - Commissioning

When should use

Agile:

It is impossible to plan the whole project in advance. In the course of the project, much will change and it makes no sense to plan ahead. You need to be prepared for any changes.

Standart:

We can fairly well imagine the details of the whole project, but there may be some deviations from the planned plan.

Sequential project implementation

We create portals for a very specific period and quite a certain budget without additional hidden costs, provided that you know exactly and specifically what you want to end up with.

Creating a portal is not an assembly on WordPress from ready-made modules, but a full-fledged engine development process – from creating a technical task to beta testing and commissioning.

Initial estimate by calculator

We have a ready-made calculator template for assessing the creation of a portal, you just need to choose / decide what you want to see on your web service. You will have an understanding of how the project budget

Design concept development

At this stage it is important to have an understanding on the main key issues: goals, composition and structure, marketing, target audience, etc. The concept is the entry point to the project

Creating a technical assignment (TK) with layouts

This includes creating the structure of the portal, working through usability through prototyping, creating specifications on the pages of the site, developing general requirements, designing key technical solutions

Detailed rating

Based on the technical specifications, a detailed assessment of your project is made. Here you will know the budget and terms of development of the portal defined in the terms of reference.

Contract

Coordination and registration of the contract for the development of the portal. Payment by stages, your rights to the site, technical task, schedule, estimate, procedure for implementation and acceptance of the site

Portal development in stages

Project implementation. You will see transparently the development process – all the tasks at the stage, time consumption, project schedule. Weekly calls. Project acceptance by stages

Our guarantees and project risk reduction

Reducing the risks of the project at different stages of the project is one of our main priorities. To do this, we use the following tools:

Warranty for errors

No project after startup is perfect. Errors still arise even in products that have long been in the market. We give a guarantee in 3 months to correct our errors in the code (not in the data that is entered in the database!).

Thus, after full acceptance of the work in case of errors within 3 months from the date of delivery - we solve the errors that have arisen by mistake for free.

Work by stages

Work by stages

Each stage is tested and delivered to the customer in full. This allows you not to create a gap between the expectations of the customer and the actual state of affairs of the project.    

Mockups

Mockups

Prototype pages simplify communication and understanding with the customer. The visual language is clear to all. In this way, we minimize the risk that the customer wanted one, but got a completely different one.    

Startup development

Startup development

We help the main basic elements of the startup to work on the customer. We absolutely do not want to participate in a project that initially could not take off - and very often the customer does not understand its target audience and its needs at all.

Inconvenient questions

Inconvenient questions

Very often the founder of the startup avoids some questions, because they are complex and unpleasant. For example, legal complaints, fraud partners, the risk of changing the contractor. We try to identify these issues and demand their solution in the early stages.

About company

Our market-kit

(downloadPDF, 3MB)

Our team

Руслан

Ruslan

CEO

Екатерина

Kate

PM

Станислав

Stas

PM

Дмитрий

Dmitry

PM, Lead web-developer

Владимир

Vladimir

PM

Александр

Alex

Web-developer

Максим

Max

Lead web-developer

Олег

Oleg

Web-developer

Алина

Alina

Web-developer

Екатерина

Kate

PM, Usability

Иван

Ivan

Mockups, CSS&HTML

Виталий

Vitaly

Mockups

 

26

Out team
 

89825

Development hours
 

30722

Closed tickets
 

103

Projects

Project interaction details

Remote interaction

Remote interaction

                                    

We are a distributed team. The main interaction occurs via Skype, telegrams and e-mail. Exchange of documents - through the RF mail. If necessary, meetings are possible in Moscow. Usually this is necessary 1 time for initial acquaintance and introduction of the project cases.

Project milestones

Project Control Points

                                        

This is the delivery of the project stages. Each stage is given with a full test cycle. The result of the stage is demonstrated to the client on the test server.

Project artefact's access

Accessing project artifacts

                                        

Artifacts are a test site for a project, a project development plan, status status for project budget elements, documentation, layouts, etc. All this is available online for the customer so that the current status of the project can be more thoroughly examined at any time. Openness is one of our top priorities.

Resolution of operational issues

Solutions to operational issues

                                        

In case of problems, the reaction speed is very important. Of course, we do not work around the clock, but we still try to speed up the process of processing urgent messages. To do this, we give several contacts to different people on the project - phones, skype, email, telegrams. An important point - our people often work on weekends - this minimizes the risk that no one will be in place at the time of the problem.

Reporting

Reporting

We make weekly reports on the current status of the project. We indicate that we did what we plan to do and the current project bottlenecks.

TOR - evaluation - work

TOR - evaluation - work

                                        

We are working on a simple scheme. The task is created first. Usually we create a task, not a customer. And it's not free. Next, we evaluate the requirements in the task in the regulatory hours. If the budget and timing are right, then we start working. The payment is based on the estimated hours, not actually spent, which gives you the opportunity to fix the budget.

What about reworks?

What about reworks?

We usually proceed from the following rule: if the modifications are small, then we make them within the current task. If the average or major improvements - it's the topic of a separate task and they are paid separately. We believe that this is a fair scheme, which excludes the possibility of unnecessary pressure of the parties on each other.

Our main principle of work

Consistent achievement of the goal through open cooperation

 Ruslan Ryanov

Sequence - we follow our development process and do not deviate from it due to the immediate desires of the project participants. It is consistent coherent actions that ultimately lead to a real result.

Openness allows us to work with the customer more easily. These clear clear expectations for the project, the constant availability of project artifacts, are frequent cut-offs for the result of the project. The more open the process - the less there is the need to believe in the word.

The goal is what is at the bottom of the project. We focus on it in any decisions taken on the project.

Consistent achievement of the goal through open cooperation

Consistency - we follow our development process and do not deviate from it due to the immediate desires of the project participants. It is consistent coherent actions that ultimately lead to a real result.

Openness allows us to work with the customer more easily. These clear clear expectations for the project, the constant availability of project artifacts, are frequent cut-offs for the result of the project. The more open the process, the less there is the need to believe in the word.

The goal is what is at the bottom of the project. We focus on it in any decisions taken on the project.

Ruslan Rayanov

Work geography

Pricing

We estimate work in hours, we agree cost estimate and schedule

Determine the amount of work in the form of a technical task, evaluate it in hours and agree on the cost estimate and the calendar plan.

Estimated hour varies from 1100 to 1500 rubles per hour - depending on the level of developers on the project.

Start project

Fist step is concept creation

Creating a project concept. We propose to do this together, and not just fill a generalized brief.

By clicking the Submit form button (widget at the bottom right), you agree to the processing of your personal data entered.

Leave your contact

Our specialist will contact you to draft an online project (preferably via Skype, not by phone).

If it is more convenient for you to discuss the questions by phone, please call

+ 7 (900) 908-88-33

Business center Flagman