Sure. But we need to go through the differences in web and mobile functionality first to choose the best technology combination. For example React for web and React Native for mobile or something.

Yes. But keep in mind that it's Facebook for 300 dollars.

20- 35 USD per hour depending on the skills required. Now Let's talk about the number of hours you need to have the work done.

No. We tried when we were a young inexperienced company. The outcome was always disappointing - we had to rewrite the template by 99%.

Today we develop custom products only.

Yes. As a first step, we'll make an audit of what screens are missing, and what business logic gaps the designs contain. So be ready to rework it a bit to adjust to technical requirements.

Yes, you can do it on a part-time and full-time basis. The minimum engagement period is 500 hours.

If the project we are estimating is supposed to be done turn-key - our PM will be there 100%, as this is the only scenario we can guarantee that we will meet the estimate.

If you hire a team on an outstaffing contract - we do not include PM in the monthly price, however, some PM will still curate our developers and make sure they behave due to our standards.

Now, when we talk about the Time and Material contract - this is where we have a lot of communication and changes, so we include 5-10% of the manager's time in a preliminary estimate.

Sure. Feel free to cut the scope, but not hours each feature is estimated.

No, and no one can. Engineers are not magicians. But let's see, if we can build something you can show publicly in a month or two. And then add features every 2 weeks for example...

Nope. But we have partners who do.

We maintain our apps when it comes to tech matters. But if we are talking about a call center - we have partners who do.

Let's discuss it in direct messages. There are many options, including SWIFT payments, SERA transfers, Transferwise etc.

Spoiler: Paypal and Stripe are not among them, sorry.

Mostly startups with 5-50 team members. Sometimes charities. Sometimes middle size production companies. What is important, is that they are happy with our service.

Sure. The phases are the following:

• Research and Business analysis
  
  
• UI/UX design
  
  
• Test plan and Acceptance criteria
  
  
• Iterative development
  
  
• Iterative delivery
  
  
• Final release
  
  
• Support and maintenance.
  
  

Sure, if the technology used is in our expert area. The algorithm is the following:

• NDA
• BA Audit by our experts
• Estimate against the list of tasks
• Priority setting session
• Iterative delivery

If we are not familiar with the technology you use, we'd be happy to recommend you one of our trusted partners who can help you.

The product development process is an assembly line. And the business analysis and proper research is a description of the way, this assembly line shall look like. No business analysis = unpredictable results and waste of money. Ready to risk?

No. We tried when we were a young inexperienced company. The outcome was always disappointing - we had to rewrite the template by 99%.

Today we develop custom products only.

Yes. As a first step, we'll make an audit of what screens are missing, and what business logic gaps the designs contain. So be ready to rework it a bit to adjust to technical requirements.

We have a post-release guarantee.

But if you need maintenance as a service - we have 2 scenarios.

Scenario A (1000-1500 hours project) - a fixed monthly package. Please note, that the first 2 months after release this package will be bigger.

Scenario B (1500+ hours projects made on a Time and Materials basis) - we continue project support on a Time and Materials basis on demand.

Short answer:

Weekly or monthly.

Full answer:

Each project has its own set of outcomes, which can be delivered (codebase, designs, specifications, user stories, test plans, etc.)

For the majority of them, we work together with the Client's product team, as client interim approval is required in each of them.

Once any of the project outcomes is ready - we deliver them to you. If they are paid of course).

Such a big thing as a codebase can be delivered once a month if we work in our repository, usually after the demo and payment. In case we work in a Client's repository - the code is already there. But we make sure we have a security deposit to prevent any mischief.

Additionally, when the project is released, we deliver all the documents and outcomes related to the product, as it is usually prescribed in the NDA.

If the project we are estimating is supposed to be done turn-key - our PM will be there 100%, as this is the only scenario we can guarantee that we will meet the estimate.

If you hire a team on an outstaffing contract - we do not include PM in the monthly price, however, some PM will still curate our developers and make sure they behave due to our standards.

Now, when we talk about the Time and Material contract - this is where we have a lot of communication and changes, so we include 5-10% of the manager's time in a preliminary estimate.

Easy. We have such an option for an outstaffed/dedicated team and outstaffing agreements. But some of our managers anyway will support the project as an additional point of contact.

No, and noone can. Engineers are not magicians. But let's see, if we can build something you can show publicly in a month or two. And then add features each 2 weeks for example...

Yes, in many cases we assemble a team specifically for the project need. Recruitment and staff placement is part of our services. But if the question was - Can you hire a team for me and disappear - then the answer is No.


If recruitment activities take place we suppose minimum 6 months engagement for each recruited resource.

For Outstaffing and Dedicated Team, and Mostly Time and Materials contracts - yes.

For a Fixed price projects team assigning stays on our side.

For such cases we estimate your idea. When you'll see idea's value against time and money it takes - cooperatively we take a decision what to do with it.

In any case, we'll complete a sprint, and then change the strategy (or no).

In software engineering, a functional requirement defines a system or its component. It describes the functions a software must perform. A function is nothing but inputs, its behavior, and outputs. It can be a calculation, data manipulation, business process, user interaction, or any other specific functionality which defines what function a system is likely to perform.


Non-functional Requirements allows you to impose constraints or restrictions on the design of the system across the various agile backlogs. For example, the site should load in 3 seconds when the number of simultaneous users is> 10000. Description of non-functional requirements is just as critical as a functional requirement.

Umm...I hope we will be able in one year, but not today.

Yes.

Idea description - Research -Solution composition - Requirements and scope documentation - Estimation - Implementation - Release.


So come to us with what you have and we will help you to validate the idea. Once the business analysis and research are done, you'll get a clear strategy and technologies offered, as well as an approximate cost and timeline.


If we agree on that - we describe a product in detail, collect the requirements and acceptance criteria, freeze a project scope and cost. Now, finally, it's time for coding!

Yes. But keep in mind that it's Facebook for 300 dollars.

We have an internal security protocol, which covers physical and intellectual security aspects. Each employee must follow this protocol. If you want to read it - please contact alexandra@redcat.dev.


If you want to sign an additional agreement with an executive of your project - we can do this as well.

No, and so does any other development studio.

Bug-free code is impossible to write from the first attempt. That is the reason Scrum, Agile, Kanban, Best practices, and the rest of the guides were created.

But we write code in a transparent well-commented manner, following the standards of the industry. Also, we make proper research preparation before the first line of the code is written.

Additionally, regular code reviews and cross-reviews, and educational programs are our investment in code quality.

In software engineering, a functional requirement defines a system or its component. It describes the functions a software must perform. A function is nothing but inputs, its behavior, and outputs. It can be a calculation, data manipulation, business process, user interaction, or any other specific functionality which defines what function a system is likely to perform.


Non-functional Requirements allows you to impose constraints or restrictions on the design of the system across the various agile backlogs. For example, the site should load in 3 seconds when the number of simultaneous users is> 10000. Description of non-functional requirements is just as critical as a functional requirement.

We have an internal security protocol, which covers physical and intellectual security aspects. Each employee must follow this protocol. If you want to read it - please contact alexandra@redcat.dev.

Just a few ideas:

• No hiring expenses and legal mess
  
  
• Lower development budget
  
  
• You can concentrate on business decisions, not code lines.
  
  
• The company you hire specializes in startup product development.