Take a peek at our work process

Have a quick chat with us and tell us about your next big idea.


Receive a pricing quote from us in less then an hour. If you have complete technical specification of the project we will take time to study it and come back to you with detailed proposal.

What if I don’t have technical specifications?

Once we have complete understanding of the project we can start the development cycle – design of the wireframes and actual coding. Cycle contains multiple milestones, which are check-in points that occur roughly every two weeks. Milestones give you a chance to review the progress that we’ve made so far, give feedback to your team, and confirm the scope of upcoming work.

We will schedule a weekly call with you to ensure that project is on track
We will send you updates via email at least twice a week
At the end of every milestone we will send you work to review. It’s important that you review milestones promptly in order to keep your project on schedule.

After the development cycle is finished, we’ll do a final pass to make sure that everything is polished and high quality.

For most people this is just a start – as the project grows we will consult you along the way, scale the product and enhance it’s features.


Development cycle

Each project is unique, but any one of them can be split into parts (customer dashboard, admin dashboard, etc.) – each part containing multiple layers (design, front-end development, back-end development, etc.). We treat each part as a milestone, while layers could be made in parallel.

Ground Rules

Lets reach an agreement before the process started

Number of the revisions to the work done is limited to 2. While using your product in the middle of development cycle you may find that there are parts of your product that you would like to change or make additions to. We’re happy to perform revisions to work that is part of the initial project scope, but we need to limit revisions in order to guarantee that projects are delivered in a timely fashion. Work that is not part of the initial scope of a project may require additional payment for us to deliver it.

Examples of revisions:
Adding new field to the checkout page
Storing additional user data for users who have logged in via Facebook
Slightly changing the layout of a profile page

We have too much experience at what we do and only 1 out of 10 projects goes without any revisions. The time for revision is reserved into 2 week milestone cycle.


A bug is any functionality in your product that does not work as specified in your project proposal. We are committed to building you an incredibly high quality product, and part of that means making sure that your product has as few bugs as possible. Revisions to intended functionality and feature additions do not qualify as bugs but can be handled through our revision process.

Examples of bugs:
Information that is intended to be saved on your server is lost
A part of your product that should be available for all users is only accessible by some users
A page consistently lags when you scroll it or interact with elements on the page
A screen in an app displays properly on an iPhone 6 but not on an iPhone 5
Examples of changes that do not qualify as bugs:
Addition of profile pictures to user profiles when the initial spec did not include pictures
Layout changes for the home screen of the product
Simplifying a photo posting flow based on user feedback

We would be happy to work with you on any project – big or small. But the majority of our projects are very complex and people are confused of how technical specifications should look like for such projects. Proper technical specifications include general logic of how how parts of the project are connected, as well as feature description of each part. It may also include wireframes, database structure and server infrastructure. This insures that we don’t have any misunderstandings and you get a high quality product in the end.

Our technical writer would be happy to help you getting this done!