What we have delivered

Three deliveries. The telecom client, JCA, is named with its permission; the card payments client cannot be.

MyTelecom

The commission engine of JCA, a Vodafone Business partner

Context: JCA, a telecom distribution partner in Portugal that pays a network of independent agents.
The problem: Commissions were settled outside the systems that ran the business. Each settlement period had to be closed by hand, and claw backs and self billing each carried their own rules.
What we did: We built MyTelecom and ran it for years: commission plans, settlement runs and agent statements.
Where it stands: Served the operation for years. Retired in September 2026, after the last client moved to ShapeFlow (next case).

ShapeFlow

Context: The same operation at JCA: the application running the business could no longer be extended, with live customers and live commercial data on it.
The problem: The old system could not take the next set of requirements, and it could not be switched off either: it was the operation.
What we did: We designed ShapeFlow as the new generation, migrated the historic data, and planned a cutover in which MyTelecom kept serving until ShapeFlow answered for everything.
Where it stands: In production. The operation runs on ShapeFlow today, and reconciliation against the operator file is built and tested on its real data.

Payments

Context: A card payments programme. Neither the client nor the employer can be named, so this case carries no logo and no quote.
The problem: Payment flows inside an existing production estate, under the rules of the card scheme and of the institution, with no room for a rewrite.
What we did: Design and delivery of the card payment processing components, inside the estate that was already there.
Where it stands: Delivered and in production. The detail stays closed.

Tell us what you are running and where it hurts.