Case Study – JobProgress

An Advanced & All-in-one Cloud Based Business Productivity Platform!!

JobProgress is an on-demand business productivity platform for Home Improvement Contractors featuring Automated Estimates & Proposals, Customized Workflow, Field Management, Growth, Productivity, etc. Being a scalable and flexible product, it supports the ability to build and grow a profitable business regardless of the size.

Core Idea of the Project

Core Idea of the Project

In 2014, one of the co-founders of JobProgress approached us with the innovative idea of creating an advanced CRM or we can say a productivity platform for the home improvement contracting businesses to effectively manage their sales, operations, workflow, performance, leads, estimations, proposals, contracts, and many more. He wanted an app that serves the diverse purposes of the contractors globally regardless of their size – big or small and makes a real impact on their business.
Goals Set to Logiciel

Goals Set to Logiciel

As we had to create an app from scratch, we had to prepare everything – Design, Database, Frontend, Backend, and Cloud Infrastructure but, most importantly we needed a high level documentation defining all the project specifications.


Designing a comprehensive and fully customized cloud-based platform with intuitive and highly interactive UI/UX.


Enabling office and field workers with fast & centralized access to the most updated information.


Bringing various services together to build a cohesive ecosystem for Home Improvement Contractors through multiple service integrations.

Product Discovery

Getting an in-depth grasp of the project’s objectives, scopes, and restrictions:
To understand the core requirements of the client we did a lot of collaborative team meetings and whiteboard sessions where we were brainstorming, mindmapping, expressing potential solutions, sketching the plan roughly, and exploring the design space.
Following Proof of Concept – the project implementation approach, we created and refined several wireframes to pin down the project specifications including tech stack and architecture.
Product Discovery


We then moved forward to create a prototype – a small working model of the required software with high fidelity screen designs. Because there are several design aspects that can’t be adequately defined and explained by static artifacts like wireframes and mockups, we were looking forward to know how the product will work and feel with an interactive prototype.

The first prototype was very close to what the client was expecting hence, our design team again did frequent brainstorming sessions and collaborated with our client to build a more user-centric design that completely meets their expectations. Later on our team kept on testing and refining the prototypes until an acceptable design was achieved to set the right flow from one screen to another.

Finally they succeeded in designing the desired prototype with expected functionality and interactivity.

MVP Development

After verifying the idea’s feasibility with POC and building a prototype demonstrating the required UI/UX design, the next milestone was designing an MVP – a product version with only the minimum capabilities, features, and functionalities needed for product’s desirability and viability verification.

Our aim was to build a quick, efficient, well-designed, and market-ready MVP on which we could develop the final version of the software. Following the build, measure, and run approach, we initiated this phase with defining the product’s value proposition and tech stack while mapping out the user flow.

Then we focused on prioritizing the essential features that were Customer & Job Manager, Estimates & Proposals & Workflow for the MVP and developed it accordingly. When the MVP was ready we got it through QA testing to determine possible functionality and usability challenges.

The initial testing was done by the client itself as he had a huge experience in the home improvement industry and was capable of providing fair feedback keeping actual struggles of the users in mind. The second testing was done by the limited set of real users – “contractors” to evaluate if the product solves their actual pain points as expected and can thrive in the market.

The MVP launch was a great success as we got a really good response from the customers with a series of suggestions on existing user experience as well as additional features. This is where we created a dedicated team for the project and got down to sprint-by-sprint development to work on the received feedback and add more features.

Growth Phase

Growth Phase

Since, JP is a subscription-based cloud platform that enables contractors to select features and add users or employees as per their business needs, a lot of customization requests started to arise right after the final product was launched in the market. This is where the growth phase of this project started with key challenges and growing maintenance requirements.

Key Challenges

Rapid Iteration

Since the client was highly focused to deliver maximum value to its customers – which perhaps is one of the important reasons of the product’s success, he was constantly listening to their feedback, suggestions, and preferences. And, our team was actively shaping the product roadmap on a continuous basis with those emerging requirements in mind.

With the shifting priorities as per the users’ feedback, tasks’ priorities were also shuffling every month and the sprints were not bringing expected results. All this was inevitably leading to a widening of the project scope.

API Integrations & Optimization

While there were only a few integrations in the MVP, implementation of 40+ APIs was required in the growth phase, extracting, transforming, and making data compatible with a centralized location was not that simple. Data Inconsistencies were appearing and it was creating complex integration scenarios. The integration and optimization process required extensive planning, consideration, construction, and testing to ensure seamless connections.

With the shifting priorities as per the users’ feedback, tasks’ priorities were also shuffling every month and the sprints were not bringing expected results. All this was inevitably leading to a widening of the project scope.

Evolving Requirement of Support & Maintenance

Aggressive Development Plan

Till this time we had the complete understanding of the product and its market hence, our product development plan got more strategic and aligned.


With time the number of end users got increased and we had to optimize the app according to the growing usage. Some other upgrades included – refining web pages or screens, customizing pages as per the users’ needs, integrating new APIs.