The problem with a buy-now-pay-later button is everything behind the button. For DivideBuy, the British lender, retailers arrived with different versions of Magento, incompatible plugins, and sometimes no Magento at all. The shopper wanted installments. The lender needed eligibility checks. Someone had to make the machinery agree. Sigma Infosolutions built connections for product synchronization, verification, credit scoring, and automatic repayments, alongside a custom CRM. Its case study reports delivery in six months. A small payment option had required a rather large act of coordination.
- Builds and maintains commerce, lending, and enterprise software.
- Combines custom engineering with its LendFoundry lending platform.
- Its practical appeal: connecting existing systems and changing them in stages.
That coordination is a useful way into Sigma. The company’s menu includes cloud, analytics, Salesforce, product engineering, and AI. But lists conceal the interesting part. A store and a lender can have the same underlying headache: each piece of software works until it must communicate with another piece. Sigma sells the engineering that makes those handoffs possible.
A payment button with a six-month backstory
Founded in 2004, Sigma names three co-founders on its current leadership page: Sandeep Phophaliya, responsible for business development; Pranav Panpalia, engineering; and Anubha Phophaliya, product. The division of responsibilities suits a firm that must translate a commercial request into functioning software. Its customers include retailers, financial businesses, and technology companies with systems to build or improve.
Sandeep Phophaliya
Pranav Panpalia
Anubha PhophaliyaDivideBuy makes the distinction clear. The assignment included business rules deciding who qualified, along with connections that collected monthly installments. For merchants outside Magento, Sigma added a way to import eligible products into a Magento store. The work crossed commerce and financial operations. Buyers considering a specialist store designer or their own developers should ask whether those connections are inside the proposed scope.
Change one storefront. Keep the business.
Consider another assignment: a California retailer selling glow products and light-up merchandise. Two storefronts shared a Magento environment. The main one needed a faster, more manageable frontend. Its companion needed to stay on Luma, Magento’s existing theme. Replacing everything would have expanded the assignment before solving the immediate problem.
Sigma moved the primary storefront to Hyvä Themes and Hyvä Checkout while preserving the shared platform, records, integrations, and second storefront. The company reports approximately 25% more orders afterward and a 29% shorter purchase journey. Those are observations from its case study, rather than controlled evidence that a theme change alone produced the gains.
The transferable idea is scope discipline: identify what must change and what must survive. This approach depends on the existing platform being worth retaining and extensions remaining compatible. A broken underlying architecture would call for a different plan. Sigma’s August 2024 Hyvä partnership gives this particular practice a formal technology relationship behind it.
The price of staying connected
There is a useful price anchor in a different retailer’s account. In April 2020, Flashing Blinky Lights creative director Martha Garcia told Clutch that spending with Sigma had exceeded $100,000. Work included Magento development and migration. This describes an engagement that began in 2018, not a current fixed price for a new website.
“We have very little to worry about thanks to their communication and organization.”
Martha Garcia · Flashing Blinky Lights · 2020
Garcia praised planning and status updates, while wanting less reliance on third-party resources. Her advice included being available at night because working hours overlapped poorly. Communication takes time, and that time belongs in the project budget. A buyer who needs constant collaboration during one local workday should settle the schedule before signing.
A lending product inside the services firm
Sigma also has something a conventional development shop need not have: a lending platform. LendFoundry, described as its division, offers loan origination and servicing software. A company-hosted release dates its public launch at LendIt USA to April 2016. The SaaS model lets a lender adopt existing infrastructure rather than commission every component.
The distinction matters commercially. Sigma earns through engineering work and continuing maintenance relationships; LendFoundry adds software delivered as a service. Its API documentation separates functions such as payments, accounting, and loan management. For a buyer, the question becomes which workflows an existing platform can cover and which require customization.
That creates two routes through the same supplier. A lender with familiar origination and servicing needs can evaluate LendFoundry first. A business with unusual retailer connections can discuss custom engineering, as DivideBuy did. The procurement exercise should separate software fees, implementation work, external services, and continuing support. Otherwise, a comparison between a platform subscription and a development proposal can obscure how much work each actually covers.
A published implementation for an unnamed personal-loan provider reports 40% less collections and servicing effort, plus fewer support requests. Those results are specific to that engagement. The underlying appeal is easy to understand: loan operations need reporting, payment handling, and a clear audit trail long after an application is approved.
Even Christmas has an integration problem
Retail supplies an earthier example. Taste of Germany needed an online platform for German and Central European foods, with hundreds of products and seasonal demand around Oktoberfest and Christmas. Sigma built on BigCommerce, adding catalog tools, payments, and shipping connections. The company reports 29% more orders during the first holiday season after launch.
Here, design included the decidedly unglamorous work of getting delivery options and stock information to behave. That is where Sigma sits in the market: an implementation and engineering partner around established platforms. Its BigCommerce agency partnership, announced in August 2024, complements its Magento work rather than requiring every merchant to choose the same system.
A person still owns the result
Sigma’s current pitch puts AI near the front. Its responsible-AI policy is more useful than the slogan: client-facing AI-assisted work receives human review, and client data cannot train public models. Its careers material describes individualized learning through Sigma Academy. Both commitments concern how people supervise changing tools.
For a prospective customer, copy the process visible in the projects: map dependencies, define the migration boundary, test the connections, and agree who maintains them afterward. Ask for demonstrations using your own operational exceptions. The successful button is the one whose surrounding systems can handle what happens next.