Skip to main content
Custom Software

Software that fits how you already work.

Tell us what you need on WhatsApp. We will say whether to build it, or use something that already exists.

Someone explaining a workflow beside a laptop

Signs off-the-shelf software is not enough.

If two of these sound familiar, custom software is worth a conversation. If not, we will tell you plainly.

  • Your data is spread across spreadsheets

    Stock in one file, orders in another, reports rebuilt at every month end. One typo quietly breaks the numbers in the other files.

  • The subscription grows, the features sit unused

    Ready-made apps bill per user, often in dollars, while much of the menu is never opened by your team.

  • Your team types the same data again and again

    Orders from WhatsApp get retyped into a system, then into a report. The hours go into moving data rather than doing the work.

What we can build for you.

The six shapes small and mid-sized businesses ask for most. What you need does not have to match one exactly.

A dashboard of sales charts on a laptop screen

Internal tools and admin dashboards

One place for stock, orders, schedules or customer data, with different access for each role on your team.

Booking and scheduling systems

Calendars, slots and payments that follow your own business rules.

Integrations between apps

Connecting the apps you already use, as long as each one has a documented API.

Apps for your customers

A member portal, a catalogue, or an order-status page your customers open on their phones.

Reports that build themselves

Sales and operations figures gathered automatically, without an Excel export every week.

Automation and AI

Repetitive work, like answering the same questions or tidying incoming data, runs on its own while your team still checks the results.

Start here

Tell us first. No technical terms needed.

Fill in what you know. The button opens WhatsApp with the message already laid out, and every field can stay empty.

  • We reply in working hours, Monday to Saturday, 09.00 to 18.00 WITA.
  • A free 30-minute consultation by phone, WhatsApp, Google Meet or Zoom.
  • If a ready-made app is enough for you, we will recommend that instead.
What you want built

Optional. It helps us prepare the right questions.

One or two sentences is enough.

This button opens WhatsApp. You can still edit the message before sending it.

After your message arrives.

Nothing is signed before you have read a written estimate.

A hand arranging app flow sketches on a planning wall
  1. We ask what is missing

    Over chat first, so the consultation is not spent on basic questions.

  2. A 30-minute consultation

    You walk us through the workflow, and we map which parts genuinely need building.

  3. Written estimate within 2 working days

    A feature list, a schedule and a fixed price. No invoice until you agree.

  4. Built in milestones

    Usually 30%, 30%, 30%, then the last 10% 30 days after launch. You see each stage before paying for the next.

  5. Handover

    The source code, accounts and documentation are handed over in your name after the final milestone payment.

Cost

The price is set after the consultation.

Two projects can be very different sizes, so one figure here would mislead. The price is written down and fixed before we start.

What decides the cost

  • The number of screens and features
  • The number of user roles and their access
  • Other apps that need connecting
  • Existing data that needs moving

2 working days

Written estimate after the consultation

4 instalments

Paid per milestone, not all up front

100%

Of the source code is yours, after the final milestone payment

Read the written guarantees
Guarantees, Not Promises

Four contractual guarantees built into every quote

Custom software has uncertainty. These four don't.

Written estimate within 2 working days

At most 2 working days from the consultation, in plain language. If we run late, your estimate goes first, and you stay under no obligation.

The code and IP are yours

Code, repository, server and domain move into your name once the final milestone is paid. Nothing is locked, and you are free to switch developers.

Paid per milestone, free to stop at each one

Usually 30-30-30-10, with the last 10% held until 30 days after launch. Stop after any milestone: what was delivered is yours, and the next one is not billed.

30-day bug-fix guarantee after launch

Bugs from our work in the first 30 days are fixed free. After that, an optional Care Plan or pay per fix.

Four guarantees. Written. In your contract.

Program code on a monitor

We build software of our own, too.

The same team runs Dagangku AI, our own software product. So we also handle the servers, fixes and user questions that come after launch.

Your project is built directly by our engineers in Bali, not handed off to someone else.

Questions people usually ask.

Yes, and that is exactly what it is for. Tell us the problem and how you work today. If a ready-made app turns out to be enough, we will recommend it, and you pay nothing.

No. The 30-minute consultation is free, and so is the written estimate. The first invoice only comes after you approve the estimate.

Because two projects can be very different sizes even when they share a name. The price is written in the estimate after the consultation, and it is fixed. Any change along the way is written down with its cost and schedule before it is built. Payment is per milestone, and you may stop after any milestone is delivered: what has been delivered is paid for and is yours, and the next milestone is not billed.

It depends on the size, and the schedule is written in the estimate. As a rough guide, an internal tool for one workflow usually takes 4 to 8 weeks, and a system with several integrations 2 to 4 months.

You do. During the project you have read access to the repository. The source code, hosting accounts, domain and documentation are handed over in your name after the final milestone payment, so you are free to continue with any developer.

It starts with one message.

Tell us the problem. What kind of software, we can work out after.