The software part of our first client project took three months. The adoption part took a year.
I did not know this when we started. Nobody had told us. Every consulting deck talks about deliverables and timelines. Almost none of them talk about the twelve months that follow go-live, where the real project actually happens.
The first client
Our first Proeffico client was a laminate manufacturer in Hapur, Uttar Pradesh.
Second-generation son of a family-run business. He had watched his father run the company on notebooks, files, and memory for decades. He wanted to change how they saw their own operations.
We built the platform from scratch. My first hires were freshers. I coded parts of it myself. I designed the database schema. We were three people and one idea and one client who was giving us a chance.
We went live.
And then the floor went on strike.
Not against the software
The strike was not against the software.
It was against what the software revealed.
Roles that had been quietly overlapping for years were suddenly visible. Inventory that had been "adjusted" at month-end was now logged in real time. The plant was seeing itself for the first time.
That is what real adoption looks like. It is not a training session. It is a mirror the organisation was not ready for.
The 11 months we did not build
For the next eleven months we did not build many new features.
We travelled to Hapur on need basis. We sat with the shop floor. We sat with the finance team. We rewrote reports until the plant head could read them at 7 AM without a coffee. We co-located our team locally so that anyone with a question could walk to them.
We took every piece of feedback and turned it back into the product. That is how the product actually got built.
The second-generation son believed from month one. His father, the first generation of the business, said we were a waste of money for the first eleven months.
Month twelve
In month twelve, the father got the report he had been silently asking for, without knowing he wanted it. Movement of goods. Leakages. Patterns in the data. All in one place.
He stopped calling us a waste.
They are still using the platform four years later.
What four years taught us
Here is what those four years taught me about building for real Indian businesses.
The 50% has no glamour. No case-study PDFs. No investor slides. It is a Wednesday morning call with a plant head. It is a workshop with 40 supervisors who have never used a screen at work. It is rewriting an alert message for the seventh time until it stops being ignored.
But the 50% is where the software stops being a product and starts being value.
The line that carries all of it
The tech is the pilot. The human is the project.
If you are only measuring your rollout by go-live date, you are measuring 20% of it.
If you are planning a rollout
Four things that would have saved us months of pain in year one:
- Sit on the floor before you build. Minimum 40 hours on-site before the design freeze. The domain is not on the diagram.
- Co-locate through go-live. Put your engineers physically inside the customer's office for the first 30 days after launch. Every doubt gets answered by walking three metres.
- Expect the mirror moment. The rollout will reveal accountability gaps that were quietly ignored for years. It is the sign the tool is working.
- Win the senior stakeholder last. The buyer will believe day one. The founder / father / plant head takes months. Ship the report they never asked for but always wanted.
Read more
Have an ongoing rollout that looks amazing in the demo and is breaking in production? Book a working session with our team.
Saurabh Agarwal
Founder & CEO, Proeffico Solutions. Proeffico builds AI products (VIZO361, MaximPro, ZIVUX, MAFLO) and delivers digital transformation for Indian and Gulf enterprises. ISO 27001:2022 certified.
