Skip to content
moyeu moyeu

Custom Development

Software built around how you already work.

Most businesses end up bending their process to fit software written for someone else. We build the other way round — starting from what your people actually do, and handing over something they can use on day one.

The work we take on.

Business systems, not apps. If a spreadsheet, a group chat and someone's memory are currently holding a process together, that is the shape of the problem we are good at.

  • The spreadsheet that became a system

    A file that started as one person’s tracker and now runs a department — until two people open it at once. Inventory, scheduling, job costing, approvals.

  • Getting paid, and knowing you were

    Billing, collections and reconciliation for businesses whose invoicing lives in three places and agrees in none of them.

  • Operations you can see

    Dashboards and reporting built on your own numbers, so a question about last month takes a minute rather than an afternoon of exports.

  • Moving off something you have outgrown

    Migrations off legacy software or a vendor you cannot reach, including getting your existing tools to talk to each other.

Whether this is worth a conversation.

We would rather say this on a web page than six weeks into a project.

A good fit

  • You already run the process by hand, and it works — it just does not scale.
  • Someone on your side can make decisions without a committee.
  • The problem costs you real money or real hours today, and you can say roughly how much.

Not us, honestly

  • The process does not exist yet and the software is meant to invent it.
  • You are looking for a technical co-founder or an equity arrangement.
  • You need it live next month. Discovery alone takes longer than that.

How an engagement runs

Discovery, build, handover.

Three stages, and you can stop after the first one with something useful in hand.

  1. 1

    Discovery

    We work out what it actually is.

    A short, fixed-price engagement on its own. We sit with the people who do the work, map the process as it really runs, and write it down. You leave with a written scope, wireframes and a fixed quote for the build.

    Those documents are yours whether or not you build with us. If the answer turns out to be "buy something off the shelf", we will say so.

  2. 2

    Build

    You see it working, not reported on.

    We ship to a staging site you can open from the first fortnight, and every fortnight after. Your staff use it long before launch, which is when the awkward truths about a process surface.

    The fixed quote from discovery holds. If scope changes, it changes because you asked, and you see the new number before we start.

  3. 3

    Handover

    It is yours, including the parts you cannot see.

    Source code, database, deployment and documentation, in your accounts and your name. We train your staff on it the same way we do for the register — at your desk, not over a chatbot.

    No lock-in clause and no proprietary runtime. You can hire anyone to carry it on, and we would rather you stayed because the work is good.

What it costs depends on the work

We price each build against its own scope rather than a rate card. Discovery is quoted as a fixed price once we understand roughly what you need, and it ends with a fixed quote for the build itself — so you approve a number before any of it starts, and that number does not move unless you change what you asked for.

What it has to do
How many workflows the system covers, and how much of the business runs through it.
What it has to talk to
Existing systems, payment providers, government or supplier formats — each connection is work, and some are more work than the rest of the build.
What has to come with you
Years of records in spreadsheets or an old system have to be cleaned and moved. This is routinely the most underestimated part of a project.
Who has to use it
How many people, in how many roles and locations, and how much has to work when the connection does not.

We do not quote a build before discovery. Anyone who gives you a number for an unscoped project has either padded it heavily or is about to discover why they should have.

What we have built

Two systems, both in daily use.

We would rather show you two things we actually shipped than a wall of logos. Both of these are ours end to end, and you are on one of their websites now.

Point of sale and inventory

cadran

An offline-first register for a sporting-goods retailer. It keeps selling through brownouts and syncs when the line returns, tracks stock across branches, and closes the day without a spreadsheet.

  • Offline-first register
  • Multi-branch stock
  • Day-end reporting
It is the product this site sells

School management

rayon

Enrollment, tuition payments, student records and report cards in one system, with a separate portal for administrators, staff and parents.

  • Online enrollment
  • Payments and balances
  • Parent portal
See rayon

Tell us what is not working.

A paragraph is plenty. What the process is, who does it now, and what it costs you when it goes wrong.

Goes to us, and nowhere else. We do not sell or share your information — ever.