mysu.
Index // Selected work

Proven outcomes.

Selected work  //  05 projects
01JSI Ledger02themysu.com03Harbr04ResGo05Capilingua
01 / Engineering

JSI Ledger

2
weeks from brief to live

The problem

Vouchers were written by hand and carried no numbers, so there was no way to show an accountant or an auditor that a set was complete. Receipts ended up separated from the payments they belonged to. Month end meant a day of gathering it all back together before any of it could be sent.

What we did

We built the controls in, rather than bolting process on top. Voucher numbers are issued by the database under a row lock, so the sequence has no gaps and no duplicates even when several people record at once. Every voucher is issued in both directors’ names and carries both signatures. The receipt photo is bound into the same PDF as the payment it evidences. Once a voucher has been sent, nothing can delete it: a mistake is voided with a reason and stays in the record, and an append-only log keeps the history. Then we automated the month: one tap collects the period, generates the Excel ledger and every voucher PDF, flags any payment still missing its receipt, and emails the complete pack to the accountant. Installs on any phone, in English and Sinhala.

The result

A day of month-end work became one tap. The company can now hand an accountant or an auditor a complete numbered set of records, with the receipt for every payment attached to it.

02 / DTC & Commerce

themysu.com

4
ways to pay, one checkout

The problem

Shopify was charging for the platform, then again for every app bolted onto it to make it work: content, email, tracking, payments. Selling internationally from Sri Lanka also needs local payment methods that no off-the-shelf checkout supports together. Changing a product page meant waiting on a developer.

What we did

A complete overhaul. We rebuilt the storefront on our own stack and put a backend behind it, so content, order tracking, payments and customer email all run from one place. Four payment methods sit behind a single checkout. The team publishes and edits its own pages with no developer in the loop.

The result

Off the subscription stack and onto infrastructure we own outright, with the whole operation, from a product page to a shipping notification, running in one system.

03 / Data & Audit

Harbr

2
months to launch

The problem

Billing and day-to-day operations ran across separate spreadsheets that had never been joined up. Getting a straight answer about the state of the business meant collecting figures by hand, and what you got back depended on which sheet you started from.

What we did

We built the platform end to end, the interface and the data layer underneath it. Figures are captured where the work happens rather than re-entered afterwards, so the number on the report is the number in the system.

The result

Operations and billing now run in one place, and the whole business works from the same figures. Live two months after the first brief.

04 / Engineering

ResGo

60%
reduction in no-shows

The problem

For most restaurants, reservations are still fragmented: a phone ringing through service, a paper diary at the host stand, and marketplace platforms that charge per cover and keep the guest relationship for themselves.

What we did

We operated as ResGo's product and engineering team. We shaped the proposition with the founders, designed the guest and operator experiences, built the platform, and carried it through to launch. One accountable team across the entire arc.

The result

Live in production and serving restaurants, on an architecture designed to grow from a single venue to many without rework. More than 7,000 guests seated through it, including at award-winning venues.

05 / Engineering

Capilingua

0
extra admin staff, even as intake grew

The problem

As the school grew, friction compounded. Course administration lived across spreadsheets, enrolment was manual, and every new intake added overhead that scaled with headcount rather than with software. Off-the-shelf platforms forced them into a generic mould.

What we did

We worked directly with leadership and teaching staff, translating pedagogy into product workflows: course and cohort management aligned to level progression, lesson materials organised the way teachers actually plan, and separate experiences for students, teachers and admins.

The result

Capilingua now runs courses, assessment and administration on one platform built for its own way of teaching. Administrative overhead no longer grows with every intake, so they can expand without adding headcount.