Frequently Asked Questions

Welcome to our FAQ corner! You're about to get answers to these questions:

1. How much does it cost to build an app?

2. How long does it take to build an app?

3. How do I know it's safe to share my app idea with you?

4. Which are the steps to build an app?

5. What project documentation do you require from potential clients?

6. What type of projects are you looking for?

7. How do I select the team for my project?

1. How much does it cost to build an app?

Building a website or an app may cost you anywhere between 5k and 500k euro. Why this broad range? At Around25, we are looking to fit the solution into your budget, not the other way around. So it all depends on how much you want to invest in your product.

The cost of building your app is the result of several meetings where we agree on project documentation, visual assets (clickable prototypes or screen designs), and custom estimation.

Please refer to our No guesstimate. Your Guide to Spot-on Product Development ebook to learn more about pricing models, documentation, and stages of product development.

2. How long does it take to build an app?

The most accurate answer is it takes between 3 and 6 months to build an MVP.

For bigger projects than MVPs, there are several stages to go through before providing a clear answer.

Before we can answer How long it takes to build an app?, we need to answer What are you building?, or How does each screen work?. For that, we go through a scoping process with you, which involves:

  • discussions
  • writing wireframes
  • getting a high-level estimation from our team
  • refining the estimation
  • follow-up calls for touch-ups.

Only then can we truly provide a proper answer to the "How long does it take to build an app?" question.

It's also really important how far along with the project you are. If you only have the app idea, this adds several weeks to your timeline because you need a discovery workshop.

You can always book a meeting to discuss more on this topic, on our Calendly call scheduler. Click here to chat with Paul Chirila (Around25 CEO).

Bonus: Check this infographic and side-by-side case study to see how we help clients maintain a predictable timeline and budget. Or click on the box below to see what they have to say about our work:

3. How do I know it's safe to share my app idea with you?

Before you share in-depth insights about your business idea, or give access to any provisions you own, we sign a standard mutual NDA (Non-Disclosure Agreement). This happens at the very beginning of our collaboration with a potential client, before sharing any sensitive information from one side to the other.

Only then can both parties agree on the custom estimation and quote our team delivers for you.

It works as a fair exchange: you entrust us with the success of your project, we 'transfer' Intellectual Property of our expertise to you.

4. Which are the steps to build an app?

Generally, building an app involves these steps:
  • Idea validation and product discovery research
  • Specs hand-off and discussion
  • Design
  • Development
  • Testing
  • Deployment
  • Maintenance.

As digital partners, we give the pre-development stages as much attention as the software development itself.

That's how we can help you avoid these potential issues:

  • Losing thousands of dollars on nice-to-have features that are not supported by in-depth discovery/research, on assumptions, and on change requests/edits;
  • Poor customer satisfaction and guidance;
  • Lack of clarity.

If you've never built an app before, you can head over to this app development guide.

Another good practice is to search client reviews on B2B directories like Clutch. Click on the box below to read our clients' reviews on Clutch:

5. What project documentation do you require from potential clients?

Building a successful product starts with minimal documentation related to the data and functionality of the app, which is a document describing:
  • user flows
  • screens and style guides for the user interface (UI)
  • mindmaps.

These will help you build a clickable/tappable prototype of the interface design, which is at the basis of project documentation. The prototype helps you get an accurate development budget, while preventing major changes later on during development.

No prototype for the UI means a weak or non-existent project documentation, which led - in some cases - to 220% more money spent on development, as we found .

Bonus: Check these 2 sample documents to get an idea about building project documentation:

  1. How to build project documentation (access document).
  2. How to build wireframes (access document).

Do you have a product idea but haven't figured out how to create a project documentation? Don't worry, we can offer templates, resources, cues, key advice, and good case practices. Email us here and let us know how we can help.

6. What type of projects are you looking for?

We choose projects where we spot potential for long-term collaboration and traction on the market. Projects that challenge us, that fuel our curiosity for new technologies and for new approaches to software development.

We are looking for projects that tell us we will work hard for the best technical solutions; that we'll be put to the test. Because it means we'll go all in and you can trust a team that cares.

To paraphrase Kobe Bryant, if you have a project and we're saying «Okay, I can do that», that's not the project we want. If we see projects that make us say «I dont' know how to do that» - "those are the things we want because through that curiosity you'll reach a level that you didn't think was possible."

7. How do I select the team for my project?

After signing the NDA, these are the steps you should take to pick a developer/team of developers?
  • Ask for CVs or developer profiles to get detailed information about their technical expertise (technologies, libraries, frameworks) and past projects.
  • Schedule a technical call where developers can present you a code sample and walk you through it (this way you can see they think and work).
  • Set up a one-week trial for the developer(s) to work hands-on for the project.


  1. For non-technical founders, we suggest you bring in a technical consultant to help you with testing, interview questions and feedback.
  2. Before the interviews, we advise that you specify which frameworks, technologies, libraries, SDKs, third-parties you need on the project, just so we can provide the best-suited developer profiles for you to choose from.

Still have questions? Head straight to our contact page, write us an email here to get a quote, or click below to read what our clients say.

Have an app idea? It’s in good hands with us.

Contact us
Contact us