Move Forward. Scale upwards. With the right team, right software.

Building a right software helps you reduce operational costs by 28%, a study says. Make the right choice.

Read more about Right Choices Does our Services seem right for your business?

Development at a large Scale

Expertise moves mountains. Coordination moves multiple mountains.

Get the best of your investment by building a team that can move mountains when its necessary. Expertise plays an important role in helping your business grow beyond boundaries. Help us get you there.

Read more about our Services

Agility - A shoulder for your business burden

When your business landscape changes often, the software has to change often as well.

Get more mileage for the spend that you do with our agile teams.

Our Agility - A Speciality

Your industry - our industry

Different industries do not intimidate us. We strive to be a different gameplayer - a wizard who takes the best options from everything and puts it to use.

We have worked with many industries ranging from finance to startups to manufaturing factories to saas businesses. We always learn and put some of the best practices into use in other industries. This has been our magic and will be our magic.

Read more about Industries we cover

Want to be nimble? — Go Microservices!

When your business landscape changes often, the software has to change often as well.

Get more mileage for the spend that you do with our agile teams.

Our Agility - A Speciality

Recent Posts

Wednesday, December 5, 2018

Product Roadmaps in the Self-driven Car Age

Leandro Pinter started as a graphic designer. Moved into software development, consultancies and Digital Agencies. Worked on CBA, ING – Agile Delivery & Transformation and Tyro, the leading the Digital & Data engineering.

The Roadmaps were initially created to inform stakeholders when major upgrades were coming so they could plan their purchases months in advance.

The characteristics of a Product Road Map are:
  • Deliverables
  • Dates
  • Priorities
  1. Ensure team’s focus on the highest business value first 
  2. A way to see and track commitments

  1. Output focused
  2. Data’s seen as hard commitment
  3. Tied to Annual planning
  4. It implies certainty
  5. Misused as a release plan
  6. It doesn’t embrace learning
An alternative to traditional Product Roadmap

“A product Roadmap describes how you intend how you intend to achieve your product vision”

Product Roadmap Components

Company/Product Vision & Strategy
Product Vision is your high level, ultimate view of where the company or business line is going. Product strategy is a sequence of product or releases we plan to deliver on the path to realise the product vision somewhere between 3-5 years out
  1. Qualitative and inspiring 
  2. Set by leadership
Company/Product Goals

This is first Business Goal you have to achieve on the way to your longer term vision
  1. The most important challenge that will help you get closer to your vision 
  2. Somewhere between 1-2 years out

Themes are the key areas the team decided to explore in order to achieve the Company Goals

  1. Hypothesis/Problem Statement – if we solve this problem or prove this hypothesis we will be closer to achieving our company goals 
  2. Outcomes – the most important part of the roadmap – it describes quantitatively what we hope to achieve by solving this problem

Product Roadmaps


  • Tie to Company Vision 
  • Focus on delivering value 
  • Commit to outcomes 
  • Get customers excited 
  • Create alignment to goals 
Should not

  • Make promises your team can’t deliver 
  • Require wasteful upfront design and estimation 
  • Be conflated with a Release Plan
How to get started
  • Understand your context 
  • Get buy-in from key stakeholders 
  • Start small and experiment 
  • Measure & Learn

Vision & Goals

  • Tie your Roadmap to your company
  • Commit to Outcomes rather than outputs
  • Broad timeframes over commitment
  • A Roadmap is not a Project Plan
  • Empower your teams

Friday, October 19, 2018

Agile Makes Work Faster

Agile Software Development is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s).

  • Individuals and Interactions over processes and tools
  • Working Software over comprehensive documentation
  • Customer Collaboration over contract negotiation
  • Responding to Change over following a plan

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the primary measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly

Studies shows that agile projects can be faster. Janet Gregory, authors of agile testing made a bold statement that “agile means faster” is just a myth. But Matthew Heusser stated that, “comparing an agile team that can't get something done in a year to a more traditional team that can is a false comparison. In a year, the traditional team will have 12-and-a-half requirements done, a mess on the floor and nothing to ship”.

There are four reasons to make Agile projects can slow down. They are:
  1. The wrong people: Remove people from the team who aren’t following good engineering discipline or are making things more complex.
  2. Putting the process first: Establish open communication and self-organizing and empowered teams.
  3. Using the wrong technologies: give teams authority to make technology decisions, and allow technology choices to be reversed if they hinder delivery.
  4. Making the architecture too complex: Keep your software as simple as possible, refactor.

Monday, October 16, 2017

Rails 204 Status Change - What does it mean?

Note: This is a change that is present in the latest Rails version 5. Versions before the 5 will throw an error "MissingTemplate" exception.

In Ruby on Rails 5, there is a change that is particularly important. Rails server issues a HTTP code of 204 No Content when you request a POST method without a template but the action for the same is present. This happens only when the HTTP Verb is POST and it doesn't happen for GET requests.

This is the sample code for the action which will be called as POST:

def create
  @user =[:user])

So how does this help you?

  1. Now you can write your own POST actions which can be called via Ajax calls which will automatically get a success response because of the 204 http code and you can let your javascript handle the changes on the UI.
  2. GET via browser will throw an error. This is because Rails assumes that you have to have a template for showing some content to the user.

Any disadvantages?

  1. Your html page after the POST request will be still the same and the page won't transition to a new page. This means that it will look like nothing has been done by the server and the user might be confused if its a form POST.

Thanks for your support and appreciation.

4 Hours
Average weekly hours saved for each user for our customers
4 Solutions
Different solutions that help our customers within our engagement
11 New Customers
Average yearly happy and new customers

Do you want to talk to us?

Connect with us

We are open to talking about any requirements that you have. Send us a message!


No: 18, Jai Nagar 2nd Street, Valasaravakkam, Chennai - 600087

Work Time:

Monday - Friday from 9am to 7pm