01
Discover
Map the operation as it runs today: the people, the steps, the exceptions, and the systems already in place.
Output Problem definition, constraints, success measures
Custom software / full lifecycle
Software built around the way your operation actually works.
Codewin is a Malaysian software studio. We design, build and operate custom systems for teams whose work depends on them, and we stay across the whole lifecycle: from the first conversation about the problem through to the years of operation that follow.
Built on a decade of engineering leadership across payments, fintech and platform teams. Registered in Malaysia (SSM RA0136810-W), based in Klang, Selangor.
01 / Services
One connected lifecycle
We work across every stage. The people who scope the problem stay through architecture, delivery and operation.
02
Design
Shape the workflows and interfaces around how the job is actually done, for operators, field staff and back office.
Output Workflow and interface design
03
Architect
Make the decisions that are expensive to change later: data model, service boundaries, integrations, failure handling.
Output Architecture and technology choices
04
Build
Deliver in usable increments, tested where it matters, reviewed, and integrated with the systems around it.
Output Working software, shipped continuously
05
Launch
Move to production carefully: environments, data migration, monitoring, and a rollback path that has been tried.
Output Production release
06
Operate
Watch it run. Fix what breaks, measure what matters, and keep the system maintainable, or hand it over cleanly.
Output Monitoring, support, iteration
02 / Approach
How we work
Five principles that hold across the whole lifecycle, whatever a project is built with.
- 01 Discover
- 02 Design
- 03 Architect
- 04 Build
- 05 Launch
- 06 Operate
Most clients do not arrive with a specification. They arrive with an operation that has outgrown its spreadsheets, and a process that only works because someone remembers how. Our job is to turn that into software the team can rely on, and keep relying on.
01
Understand the operation before designing the interface
The screens come after we understand the work. A dashboard that does not match how staff actually operate is just a nicer place to be confused.
02
Make the important technical decisions early
Data model, service boundaries, integration points. These are cheap to decide well at the start and costly to unwind later.
03
Deliver usable increments
You should be able to put something real in front of staff within weeks, not wait months for a single launch.
04
Design for production, not only launch
Monitoring, logging, backups and a way to recover are part of the build, not a task for afterwards.
05
Leave systems maintainable and observable
Conventional choices, written documentation, clean handover. Your team should be able to run and extend the system without us.
Typical stack
chosen per project, never for novelty
03 / Selected work
Systems running in production
Two recent builds, both live. Each was taken from the operational problem through to a system staff use every day.
Solar plants are maintained across many sites at once: inverter faults, string underperformance, inspection rounds, corrective jobs. That work was tracked in spreadsheets and group chats.
GridSense is the engineering portal that replaced it. Field staff log faults and inspections from site, the office plans preventive maintenance and assigns work, and every asset carries its own history. Field and office roles have separate access.
- System architecture and data model
- Front-end and back-end build
- AWS deployment and environments
- Ongoing operation and iteration
A public market event sells pre-orders online for weeks, then runs walk-up sales on the day across dozens of booths staffed by volunteers.
Bhūmiḥār 2.0 covers both phases. An admin portal manages orders, booths, activities and staff. On the day, booth staff scan customer QR codes to release pre-orders or check guests into activities, and a point-of-sale flow takes walk-up payment by DuitNow before handover.
- Platform architecture
- Admin portal, booth and point-of-sale interfaces
- QR issuing and scan flow
- AWS Amplify delivery
04 / About
About Codewin
Codewin is a software studio for operations that run on systems where being wrong has real consequences: money moved, fuel dispensed, orders reconciled.
A project usually starts where a spreadsheet, a manual process, or an ageing tool has quietly become a liability. Codewin takes it from there: mapping how the operation actually runs, designing the system around it, building it, and staying on to keep it running in production.
Behind the studio is a decade of payments and platform engineering, on systems that handled real money and real traffic every day. That standard, correct by default, observable, and safe to change, carries into every project regardless of its size.
Codewin works with a small number of clients at a time. There is no account layer and no junior bench: the people who scope the work are the people who build and run it.
- Experience
- 10+ years, including 5 in payments and fintech
- Focus
- Business-critical systems, across the full SDLC
- Background
- Payments, fintech and platform engineering. Computer Science, University of Toronto
- Registered
- SSM RA0136810-W, Klang, Selangor
- Availability
- Accepting new projects
05 / Contact
Tell us what is difficult, slow or still held together by spreadsheets.
A short description of the process you are trying to improve is enough to start. We reply within one working day and will tell you honestly whether we are the right fit for it.