Skip to content

Built to be maintained, not to be shown off.

Code another team can pick up, an architecture explainable on one page, and tests that actually run on every release.

Request consultationCase studies

What you get

  • Rigid legacy systems replaced without halting operations
  • Data scattered across apps finally converges
  • Small changes no longer take weeks
  • Code and documentation handed over in full — nothing locked in

Capabilities

What this covers

Legacy Modernisation

Replaced piece by piece, without halting operations.

  • Operations keep running throughout the replacement
  • Each migrated part goes into use immediately, rather than waiting for everything
  • Can be stopped midway without discarding what has already moved
  • Old data moves too, instead of being stranded in a dead system
  • Documentation written from scratch for the parts that never had any

Typical scope

  • Legacy modernisation

    The old system is replaced piece by piece while still running, until the last part has moved.

    • Operations never stop during the replacement
    • Can be halted midway without discarding what has moved
    • Old data moves too, rather than being stranded

    Typical duration: 3–12 months

  • Technical audit of a running system

    A full read of a running system: code quality, unmaintained dependencies, security gaps, running costs, and which parts are genuinely dangerous to touch.

    • A system map a non-technical person can read
    • Which parts are dangerous to touch, and why
    • Dependencies that are unmaintained or vulnerable

    Typical duration: 2–3 weeks

  • Incremental legacy modernisation

    Moving a legacy system piece by piece while the old one keeps running — rather than rewriting everything and hoping the switchover survives one weekend.

    • The old system keeps running throughout
    • Each stage delivers value on its own, not at the end
    • A rollback path at every stage

    Typical duration: 4–12 months, in stages

Request consultation

Talk to us about scope and pricing.

Project Rescue

Taking over code the previous vendor walked away from.

  • Two costed options, not one recommendation that happens to favour us
  • The code is actually run, not merely read
  • Whatever still works is kept — not everything is thrown away
  • Passwords, domains, and server access recovered as well
  • The report can be used to hold the previous vendor to account

Typical scope

  • Abandoned project assessment

    The code the previous vendor left behind is dissected and run, producing two costed options: continue, or rewrite specific parts.

    • Two costed options, not a single recommendation
    • The code is actually run, not merely read
    • A list of lost access: domains, servers, passwords

    Typical duration: 2 weeks

  • Stalled project rescue

    Taking over a stalled project: establishing what is genuinely finished, what can be salvaged, and the shortest path to something usable.

    • An honest assessment: how much is genuinely done
    • What is worth salvaging and what is cheaper to discard
    • The shortest path to something usable

    Typical duration: 2-week assessment, then staged

Request consultation

Talk to us about scope and pricing.

Android & iPhone Apps

One app for both platforms, maintained by one team.

  • A single codebase for Android and iPhone
  • Still usable when the signal drops, syncing on reconnect
  • Notifications, payments, and maps wired into your systems
  • Support until it clears App Store and Play Store review
  • Download size kept small so older handsets stay usable

Typical scope

  • Field team app

    An app for technicians, field sales, or couriers working where there is no signal — reports sync once back in range.

    • Fully usable with no signal at all
    • Photos, signatures, and location points captured too
    • Syncs by itself once reconnected

    Typical duration: 4–5 weeks

  • Mobile app, base package

    An Android and iPhone app from a single codebase, supported until it clears App Store and Play Store review.

    • One codebase for both platforms — no doubled maintenance
    • Tested on real devices, not only a simulator
    • Supported until it clears app store review

    Typical duration: 6–8 weeks

  • Mobile application build

    Android and iOS from one codebase, with offline mode where fieldwork demands it, and a release path that does not wait on a vendor.

    • One codebase for both platforms
    • Offline mode with sync when signal returns
    • Store registration under your own name

    Typical duration: 10–18 weeks

Request consultation

Talk to us about scope and pricing.

Desktop Applications

Installed on the machine, running even when the network is down.

  • Fully operational offline, catching up automatically on reconnect
  • Connected to printers, scales, and scanners on the desk
  • One application across Windows, macOS, and Linux
  • Updates install themselves across every branch
  • On-device data stored encrypted

Typical scope

  • Offline-first point of sale

    A point-of-sale application that keeps its own data locally and catches up with head office once the network returns.

    • Fully operational without internet
    • Connected to receipt printers, cash drawers, and scanners
    • Catches up with head office by itself on reconnect

    Typical duration: 4 weeks

Request consultation

Talk to us about scope and pricing.

Custom Applications

Systems shaped around how you actually work.

  • Shaped around the process you already run rather than forcing your team to change
  • Small releases every two weeks, so direction can change while it is still cheap
  • Per-role access rather than one shared account for everyone
  • Code and documentation handed over in full — another team can pick it up without us
  • Tests handed over too, and actually run on every release

Typical scope

  • Discovery & blueprint

    Two weeks to lock the specification, architecture, release order, and final numbers — before a line of code is written.

    • A specification any vendor could price, not only us
    • An architecture explainable on a single page
    • A release order: what goes live first

    Typical duration: 2 weeks

  • Custom web application

    An internal tool, customer portal, or operations console shaped around how you work, not the other way round.

    • Designed around the process you already run
    • Per-role permissions, not one shared account
    • Code and documentation handed over in full

    Typical duration: 6–16 weeks

  • Back-office system

    Inventory, orders, payroll, and approval flows in one connected system.

    • Tiered approvals with a stand-in when someone is away
    • Stock recorded per location, not as one combined figure
    • Change history preserved — who changed what, and when

    Typical duration: 8–20 weeks

  • Two-sided marketplace

    A platform matching two sides, holding funds until the deal completes, then settling payment and ratings.

    • Funds held until both sides confirm completion
    • Matching buyers and sellers by your own rules
    • Ratings and transaction history that cannot be faked

    Typical duration: 12–24 weeks

  • Internal operations system build

    A system that follows how you actually work — rather than a way of working you must change to fit software bought off the shelf.

    • Follows your workflow rather than forcing it to change
    • An admin panel so rules change without calling us
    • Numbers visible daily, not at month end

    Typical duration: 8–20 weeks

Request consultation

Talk to us about scope and pricing.

Subscription Platform

A product that bills itself every month, with an owner’s panel included.

  • Sign-up, plans, and quotas running by themselves
  • Recurring billing through Indonesian payment providers
  • An admin panel to change pricing and plans without code
  • Revenue, usage, and per-user cost reporting
  • A referral programme ready to switch on

Typical scope

  • Subscription platform

    A product that bills for itself: multi-tenant, tiered plans, quotas, and recurring billing that runs unattended.

    • Each customer’s data kept strictly separate
    • Plans, quotas, and usage limits configurable without code changes
    • Recurring billing, including failed cards and renewal reminders

    Typical duration: 10–20 weeks

  • Multi-tenant SaaS platform build

    A complete subscription platform: tenant data separation, plans and quotas, billing, an admin panel, and audit trails — with separation that is tested rather than assumed.

    • Tenant separation that is tested, not assumed
    • Plans, quotas, and recurring billing
    • Upgrades and downgrades with proration

    Typical duration: 12–24 weeks

Request consultation

Talk to us about scope and pricing.

System Integration

Systems that never spoke to each other finally do.

  • Two systems that never spoke now exchange data by themselves, with nobody copying in between
  • Failures are reported, not swallowed until a discrepancy surfaces months later
  • Failed transfers retry themselves; whatever still fails queues for a person to handle
  • Every exchange logged and inspectable by your own team
  • Documentation handed over so the integration never becomes a black box

Typical scope

  • System integration

    Two systems that never spoke are made to exchange data automatically, with nobody copying in between.

    • Runs automatically, with nobody triggering it
    • Failures are reported, not swallowed
    • Failed transfers retry themselves

    Typical duration: 1–2 weeks

  • System integration

    Connecting systems never designed to talk — accounting, warehouse, payments, logistics, government portals — with safe failure handling and retries.

    • Two-way, not a periodic export
    • Safe retries: one event is never recorded twice
    • Alerts when a connection breaks rather than silent failure

    Typical duration: 3–6 weeks per connection

Request consultation

Talk to us about scope and pricing.

Data & Analytics

Scattered numbers become one screen you can actually read.

  • Figures from several sources unified into one screen every division agrees on
  • One agreed definition per figure, so meetings stop arguing about them
  • Refreshes itself — nobody copies anything by hand at the start of each month
  • Personal data masked where the report does not genuinely need it
  • Your team taught to recognise when a figure deserves doubt

Typical scope

  • Management dashboard

    Figures from three separate data sources merged into one screen every division agrees on.

    • Three data sources unified
    • One agreed definition for each figure
    • Refreshes itself; nobody copies anything by hand

    Typical duration: 3 weeks

  • Decision dashboard

    Bringing numbers from separate systems into one view you can trust — with each figure’s definition written down, so meetings stop arguing over whose version is right.

    • Every figure defined and agreed upfront
    • A single source rather than copies chasing each other
    • Refreshed automatically, not rebuilt monthly

    Typical duration: 4–6 weeks

Request consultation

Talk to us about scope and pricing.

Corporate Websites

Fast sites that turn visitors into conversations.

  • All text, images, and pages editable by you without calling a developer
  • Ready to be found by search engines from day one
  • Displays properly on phones, not only on large screens
  • Enquiries land on a screen someone actually reads, not an inbox that gets missed
  • Two languages side by side, each written natively

Typical scope

  • Company site + content panel

    A company website with an admin panel, so text, images, and pages can be changed without calling a developer.

    • All text and images editable by you
    • Ready to be found by search engines from day one
    • Displays properly on phones, not just large screens

    Typical duration: 2–3 weeks

Request consultation

Talk to us about scope and pricing.

Technology Advisory

Technology direction settled before money is spent.

  • Technology aligned with business goals
  • Objective IT infrastructure audit
  • Clear digital transformation roadmap
  • Optimised cloud and software licence costs
  • Vendor and technology selection grounded in facts
  • Security and compliance risk mitigation

Typical scope

  • Technical session

    A one-hour meeting to map the problem, the available options, and a rough sense of cost and time.

    • A written summary after the meeting
    • A rough estimate of cost and time
    • A recommendation for the cheapest sensible first step

    Typical duration: 60 minutes

  • Monthly support & SLA

    Fixes, security updates, monitoring, and further development with a written response time.

    • A written response time, not a verbal promise
    • Security updates applied without being asked
    • Monitoring that tells us before you notice

    Typical duration: Monthly

  • Scoping workshop

    Two days with your team turning "we need a system" into something estimable: who uses it, what must happen, what is deliberately excluded, and what it will roughly cost.

    • A requirement list that can actually be estimated
    • An explicit list of what is NOT being built — equally important
    • A cost range plus what would widen it

    Typical duration: 2 days

  • Fractional technical leadership

    Technical leadership present a few days a month: judging vendor proposals, blocking decisions that get expensive later, and translating technical matters into business decisions.

    • Judging vendor proposals from your side of the table
    • Blocking decisions that get expensive later
    • Translating technical matters into decisions

    Typical duration: Ongoing

Request consultation

Talk to us about scope and pricing.

Related work

View all

Questions we are asked most

When is building better than buying off the shelf?

When off-the-shelf software forces your team to change how it works and the part that matters most simply is not there. If what you need already exists on the market, buying is almost always cheaper — and we will say so, even when that means there is no work in it for us.

How does the build run?

Small releases every two weeks, not one large handover at the end. You see what works from early on and can change direction while it is still cheap. Scope changes are written down with their cost and time attached — we do not quietly do extra work and invoice for it later.

How many rounds of changes do we get?

Corrections to anything that departs from what was agreed are unlimited and unbilled — that is our responsibility. What is bounded is added scope, and that is costed openly by the day. Promising "unlimited revisions" without drawing that line is a promise that always ends badly for one side.

How long until we can use it?

A custom web application runs six to sixteen weeks, a subscription platform ten to twenty, and a back-office system eight to twenty. The exact figure is locked after a two-week diagnosis rather than guessed at the outset.

Do we own the source code?

Yes, entirely, on full payment — including the right to modify it and pass it to another party. Third-party open-source components remain under their own licences, and we hand over that list alongside the work.

Which systems can be connected?

Almost anything with an open interface: accounting systems, ERPs, CRMs, payment gateways, shipping providers, and online stores. For legacy systems that offer none, we build a connecting layer of our own — which is in fact the work we are asked for most.

How long does one connection take?

One to two weeks per connection, at a fixed USD 2,100. What drives the timeline is not the number of systems but how well documented the system on the other side happens to be.

Do we receive documentation?

Yes: what is exchanged, when it runs, what happens on failure, and how to inspect it yourselves. Without that, an integration becomes a black box only we can repair — and that is not the working relationship we want.

How we engage

Choose the engagement that fits where you are

Not every piece of work belongs in a big project. These four are what we normally use — scope and duration agreed before anything starts.

  • Rapid assessment

    Find out what is actually broken before committing a large budget.

    1–2 weeks

    • Interviews with the people who actually run the process
    • A count of the hours and money currently being lost
    • Findings ranked by real cost, not by volume
    • A staged recommendation with time and cost estimates

    Best when: You know something is wrong, but not yet which part is costing you most.

  • Fixed-scope project

    The outcome, the date, and the scope agreed up front.

    4 weeks – 8 months

    • A written scope, a delivery date, and agreed acceptance criteria
    • A demo every two weeks — you watch progress instead of waiting for news
    • Testing plus hand-over of the code and its documentation
    • A warranty period for fixes after the system goes live

    Best when: The need is already clear and you want budget certainty.

  • Dedicated team

    Our team works full time for you, following your priorities.

    From 3 months

    • A standing team: engineering, testing, and one accountable lead
    • You set the priorities, reviewed every two weeks
    • Working Indonesian hours, adjustable to your time zone
    • Scaled up or down month by month

    Best when: The roadmap is long and priorities will still shift along the way.

  • Monthly retainer

    A live system kept running, updated, and watched.

    Monthly, cancel any time

    • Monitoring, backups, and security updates
    • A fixed block of hours each month for fixes and small features
    • An agreed response time when something goes wrong
    • A monthly report on what was done and what needs deciding

    Best when: The system is live and you would rather not wait until it breaks.

  • The code and documentation become yours
  • An NDA from the first conversation
  • A post-release fix warranty
  • Progress reported every two weeks
  • No vendor lock-in — another team can take over
Request consultation

Talk through custom software for your organisation

One conversation is enough to know whether this is worth doing now or later.

Request consultation