Question 1

How much does project development cost?

Accepted Answer

The cost depends on scope and complexity. After a call and business analysis we prepare an estimate broken down by stages and fix it in the contract — no hidden fees or surcharges along the way.

Question 2

How long does it take to launch?

Accepted Answer

An MVP usually takes 4 to 10 weeks. We fix the exact timeline after the analysis stage and architecture approval.

Question 3

Can you join an existing project?

Accepted Answer

Of course. We run a technical audit of the code and infrastructure, then either strengthen your team or take over the project entirely.

Question 4

How does the team work on a project?

Accepted Answer

Each specialist is responsible for their own part: design, development, testing or infrastructure. Team leads assign and review their tasks, and your personal manager runs the whole process. You don’t have to coordinate anyone — you deal with one person.

Question 5

What if a specialist leaves in the middle of the project?

Accepted Answer

We replace them quickly, and we try to anticipate such situations in advance. The same goes for someone who struggles with a task: first we help and advise, and if the situation is difficult, we bring in another specialist. You won’t have to search for or negotiate with anyone new.

Question 6

Can I meet the team?

Accepted Answer

Of course. You can also talk to the specialists during the work, but you don’t have to: your personal manager, your digital concierge, takes care of everything.

Question 7

Why do I need a manager if I can hire freelancers directly?

Accepted Answer

Our specialists are managed by experienced leads who know their craft well. Working with freelancers directly, it’s easy to run into misunderstandings and lengthy explanations of your domain, you need a separate contract with each one, and if someone leaves mid-project, you have to find a replacement yourself. We take all of that on.

Question 8

How does payment work?

Accepted Answer

Payment is split into stages based on finished functional parts of the product. We agree on the amounts and schedule with you so they fit your budget and are convenient. The prepayment is 10–15% of the estimated budget: with it we plan the project and prepare the documentation — the roadmap, calendar plan, payment schedule, architecture, user flows and developer tasks.

Question 9

What if the project goes over budget or past the deadline?

Accepted Answer

The budget can’t exceed the estimate — it is fixed in the contract. If a deadline is missed through our fault, we pay a penalty for the delay.

Question 10

Can I add new features during the work?

Accepted Answer

Yes. The cost depends on what exactly you want to add: we estimate the change, agree on the price and timeline with you, and only then add it to the plan.

Question 11

Can we start with a small task to try working together?

Accepted Answer

Of course. A small task is a good way to see how we work before taking on a larger project.

Question 12

Do you work with companies, sole proprietors and foreign businesses?

Accepted Answer

Yes. The company is registered in Armenia and abroad, so we work equally easily with Russian and international clients. We sign a contract and provide all the documents your accounting team needs.

Question 13

I only have an idea, no specification. Where do we start?

Accepted Answer

With business analysis. We figure out your needs and choose a way to build it that fits your budget, timeline and other requirements. We write the technical specification ourselves based on the analysis.

Question 14

How will I see what’s happening with the project?

Accepted Answer

All tasks and their statuses are visible on the task board, and overall progress on the timeline. On top of that, every two weeks we show finished functionality at a demo.

Question 15

How much of my time will it take?

Accepted Answer

Very little: to tell us about your ideas and to review the finished work. The rest of the time, the only interruptions will be clarifying questions from the manager if something is unclear.

Question 16

How quickly does the manager reply?

Accepted Answer

During working hours, within minutes; outside working hours, within an hour. At night, whenever possible.

Question 17

How do you check quality before delivery?

Accepted Answer

Everything is tested before delivery, and we agree on the scope of testing with you. For a simple product, smoke tests run by the developers themselves are enough. For critical features — for example, anything involving payments — we bring in QA engineers and penetration testers. Then comes alpha testing together with you and beta testing with a control group of users from the waitlist. After launch we collect feedback and ship fixes and updates.

Question 18

What if I don’t like the result?

Accepted Answer

Before development starts, we show you approximate visuals of the product and approve them with you. During the work, everything is reviewed and checked against the technical specification approved at the start. If a mistake is ours, we fix it free of charge. If you want new features, we add them for an additional fee.

Question 19

Can I later hand the project over to my own team or another contractor?

Accepted Answer

Yes, of course. We will prepare all the project documentation and help with the handover.

Question 20

How are my data and access credentials protected?

Accepted Answer

We follow information security standards, and we can sign an NDA before discussing project details.

Question 21

Will you support and develop the product after launch?

Accepted Answer

Yes. Any product that people use is constantly updated, and yours is no exception. We handle administration, technical support and releasing updates.

Question 22

Have you worked on projects in my industry?

Accepted Answer

If it’s a popular niche, our specialists have most likely worked in it. But tasks are set by a systems analyst: they decide exactly how the product should be built, and developers and designers bring it to life. If the analyst hasn’t worked in your niche, they will ask clarifying questions, listen to what you tell them about it and study all the nuances on their own to write the technical specification correctly.

Document workflow automation service