Keeping the people and the knowledge.
In 2017, Amit purchased a startup called Orchestrator 365, which worked closely with IBM in Markham. He retained the staff and their knowledge. He identifies this work as an early foundation for Julie and its focus on using compute to help make decisions.
Choosing the weekly flyer specials.
For a retailer with weekly spending of $7 million, according to Amit, the software brought together sales data, supplier information, store inventory and historical patterns. Cultural events and shopping data also informed recommendations about which products to feature in the weekly flyer.
Amit recalls that a run took about five days to return its results. In his account, the recommendations improved sales and enabled the retailer to reduce a planning team that had numbered more than 40 people. The retailer is not named here.
Putting idle computing capacity to work.
The acquisition fit the way Amit’s operations already used technology. At night, when call activity fell and computers were less heavily used, substantial computing capacity sat idle. He was looking for ways to make that capacity productive outside calling hours.
Computers could transcribe calls and run intensive processes such as retail decision analysis during those quieter periods. Orchestrator 365 added a use for computing resources that were already part of the wider business.
In Amit’s account, using equipment across more hours helped offset the high cost of the infrastructure, including equipment acquired through leases. The fit connected technology ownership and leasing costs with additional productive use.
A recommendation that started a debate.
One week, during an Indian festival, the software recommended featuring Pepto-Bismol alongside the Indian food promotion. The unexpected pairing prompted a substantial debate.
The retailer decided to follow the recommendation. Amit recalls that it proved to be a strong sales week for the product. It remains a memorable example of a recommendation the team initially questioned.
This is a historical retail-merchandising anecdote, not a health recommendation.
How the experience connects to Julie.
The lesson was to bring relevant business information together, examine recommendations and compare them with real outcomes. Amit sees this experience as part of the thinking behind Julie.
This historical retail system is separate from Julie’s current answering-service scope. Explore the current page to discuss what is being developed and whether there is a fit.
About this account
Acquisition, team retention, working relationship, processing time and outcomes are reported by Amit Kapoor. No formal IBM partnership, current affiliation, independently measured sales uplift or specific staffing reduction is asserted.