Skip to content

Software products and modernization

New products built. Legacy systems brought up to date.

We build SaaS products, apps, portals and the internal tools your business runs on, and modernize the legacy systems holding it back: spreadsheets, paper forms and ageing software nobody wants to touch. Price and launch date are fixed before we start.

Two kinds of project

Build something new, or fix what you have.

  • 01

    Build new

    Products you sell, and software for work your business still does by phone, paper or spreadsheet.

    • SaaS products with sign-up, billing, admin and data kept separate per customer
    • Customer apps and self-service portals
    • Internal tools for sales, operations and approvals
    • Dashboards and reports that managers actually open
    • Mobile apps for staff in branches and in the field
  • 02

    Modernize

    Software that still runs the business but is slow, fragile or impossible to change.

    • Spreadsheets and paper processes turned into proper systems
    • Old desktop or server software rebuilt for the web and mobile
    • Data moved out of legacy databases, checked and reconciled
    • APIs added so old systems can work with new ones

Typical builds

Examples by industry, not a limit.

IndustryTypical build
Banks, microfinance lenders, insurersCustomer apps and portals, loan and claims workflows, internal tools around the core system
Property developersBuyer portals, instalment schedules, sales and unit tracking
Retail and distributionOrdering, inventory, delivery tracking, point of sale with KHQR
FactoriesProduction tracking, attendance, compliance and audit records
Hospitals, clinics and private schoolsPatient and student records, scheduling, fees, parent messages

Modernization

Replacing an old system without stopping the business.

Most old systems hold years of rules nobody wrote down. We replace them a piece at a time, so the business keeps running on the day you switch.

  1. Map what exists

    We read the code, the database and the workarounds your staff use, and write down what the system really does.

  2. Replace in slices

    The new system takes over one part at a time. The old one keeps running alongside until each part is proven.

  3. Move the data

    Records are migrated and reconciled, and your team signs them off before anything is switched off.

  4. Switch over safely

    Each cut-over is planned for a quiet period, with a tested way back if anything goes wrong.

Fixed price, fixed date

How we can quote firm.

A paid scoping phase, a shared toolkit for the integrations we build again and again, and AI-assisted development let us estimate tightly. The process keeps the estimate honest.

  1. Scoping

    Two weeks, US$3,000. Requirements, existing systems and a clickable prototype of the key screens.

  2. One price, one date

    Both are written into the contract before the build starts.

  3. Two-week cycles

    You see working software at the end of every cycle, not a status report.

  4. Changes quoted first

    Anything new is priced in writing before work starts, so the total never drifts quietly.

  5. Launch and handover

    Go-live on the agreed date, training for your team, and documentation your IT staff can use.

Integrations

Connected to what you already run.

  • Core banking and bank APIs

    Account data, payouts, statements

  • KHQR and Bakong

    Payments, reconciliation, point of sale

  • ERP and accounting

    SAP, Dynamics, Odoo, QuickBooks

  • Telegram and Messenger

    Notifications, approvals and customer chat

  • Legacy databases

    SQL Server, Oracle, MySQL and older formats

Pricing

Ranges now, one number after scoping.

Scoping2 weeks
US$3,000
Build or modernizationFixed after scoping
US$30,000–120,000
Maintenance and hostingMonthly
US$1,500–5,000

Questions we hear

Bring the system you keep putting off.

Two weeks of scoping turns it into a plan, a fixed price and a launch date.