Creating the future together with Founders

Types of projects we do

We all started with a dream. We see a problem, or we see something that could be improved and we set for ourselves the goal of making it happen. Improve a process, make people lives better, help animals, save money, make money. Whatever your particular dream and vision is, you're here, because you are looking for a technological solution to materialize it. An app to make it happen.

So, let's get one thing clear from the start: We know technology. There are various known solutions to common problems that can be solved with software. This is what engineering is about. Therefore, given enough time and money, it is entirely possible to get a good app out there. However, sucess requires more than just a piece of software. There are many variables that must work together to make an idea into a startup into a successful, profitable business. And since we've been working with Founders forever, we know some of these. And we'll help you make it happen.

  • + Node + MySQL
  • + HTML5 Bootstrap based interfaces
  • + Firebase apps
  • + Cloud hosting and DB
  • + Native iOS, Android
  • + Microservices
  • + Template-based design
  • + Mobile and web based consumer apps
  • + Marketplace apps
  • + Backend development
  • + Cloud operations
  • + Product design
  • + Startup strategy


Minimal Viable Product. Our first concern is to get a real, usable product as good as possible as fast as possible. Of course, these are relative terms, some industries have very high competition and very high user expectations, and thus, "good enough" might mean a LOT of effort, but if your product is on a new, innovative segment, it's possible and even desirable to launch with some rough edges and start testing as soon as possible.

In any case, "minimal viable" means a complete product that satisfies the very core need of the market you're trying to attack. Still, testing as soon as possible is critical, since as is often the case with new products, we're dealing with a high level of uncertainty, and the sooner we can get solid answers from the users, the better.

To maximize our gains in these areas, and minimize our work and error potential, we favor using as many ready-made and tested components or stacks or backends, as is reasonably possible, instead of building out everything from scratch, except in the case where the main product we're talking about has such unique characteristics that it's just not feasible to use pre-made parts to assemble it.

The incremental approach

In short, this means to break up a large goal into sub-component goals, meaningful objectives by themselves, that can be completed with less effort and allow us a pause to assess the current situation before proceeding further. Like chapters of a book, each stage should convey a sense of completion by itself, even if it is part of a larger story.

In particular, we want to avoid the trap of building too much, without properly vetting it by real-life use. Often, there's a disparity between what we humans think it's best, and what reality shows us, so the strategy here is to take smaller steps and immediately send the results for real world validation, thus correcting course as needed with the findings.

To be clear, this is not about building independent parts of the overall solution, but rather, building complete mini-solutions while heading to the final goal.

The rollout phase

So for each one of our previously achieved development stages, we will consider, depending on the app, the client, the users and the overall strategic situation, to get the app into the hands of its real, final users. The important thing here, is that even if we are 100% confident on the quality and suitability of the job we'd done together with the client, we still need an incremental approach to rollout.

The rationale behind this is to limit our risk exposure by avoiding the possiblity of letting an undetected problem pass, and reach 100% of our users, which will then be affected by whatever it is. So instead of assuming us to be fool-proof, we'll instead assume that there will be issues, and we'll let into the app only a handful of users at first, then carefully observe and monitor the situation, before allowing a larger number of users in, and so on.

Our warranty

You should know that all of our development work comes with a 3 month warranty against programming defects, that they will get corrected at no extra cost, once reported. A "defect" is a deviation from the functionality stated in the SRS or a badly performing one, technically speaking. For example, "The app will return the number of customers active within the year specified in the search field" but in actuality, you discover, after 1 month, that the search in question returns ALL customers, regardless of the year that they were active. So, this is a "programming defect" and you can report it for correction.

The warranty DOES NOT cover changes in external circumstances, new business goals on the part of the client, or issues outside of our control. For all of those cases, as well as the situation when a problem is discovered after a lot of time has passed, we will remain available to assist you by any of our support options available at the time.

For now, the important take away for you, as our client, is that we'll remain committed to deliver you working solutions, and we'll stay reachable afterwards to help you with whatever new developments might arise in the future.

Evaluate, to plan for next steps

We firmly believe that the path to success is one of continuous improvement, and in that sense, what worked yesterday, might not be the best fit for tomorrow, therefore, actionable knowledge is critical to future performance.

Once we're satisfied with our current results, it'll be time to think about implementing monitoring strategies to track key metrics related to the original goals of the project. In this way, we will be better able to advice you on the path to take with a follow-up, or even a completely new project; either way, supported by evidence as much as possible, instead of only intuition.

Focus on key metrics

There are many things to track, but the idea here is to engage resources to track first the things that are likely to have the biggest impact on our goals.

Interpret correctly

We will assist you not only in obtaining relevant numbers but in deriving well thought and evidence-based, documented conclusions from them, to enable proper and justified future decisions.