Skip to main content

Our guarantee

What we are willing to be held to, in writing, before you pay anything.

Most of what follows is unusual to put in writing, which is exactly why it is here. A business owner deciding whether to trust a software company has almost nothing to go on — so these are the terms we are willing to be held to, before you pay anything.

  • If a stage does not work, we refund its fee

    We take on work to cut what your business spends in money, hours or people, or to let it handle more without adding either. Before each delivery stage — a module or a phase — we agree what that stage is meant to move, and what you need to do for the measure to mean anything. If something on your side slips, that stage's review date moves with it; the guarantee does not lapse. If the thing we agreed to move has not moved by that review date, we refund the one-time fees you paid us for that stage of work — not everything else on the engagement, and not the recurring fees for keeping it running. The claim is yours to make once, within 30 days of that review date. We would rather return a fee than keep money for a system that did not earn it.

    How that works

    • Before any delivery stage starts — a module or a phase — we write down the one thing that stage is meant to reduce: the hours a task takes, the number of people on a process, a cost line you can point at, and what it measures today.
    • That baseline comes from your own records, not from our estimate, and you keep a copy of it.
    • The same note names the stage that measure is agreed against, so the amount at stake is settled before anything is built — our one-time fee for that stage, not the recurring fee for keeping it running. One stage's fee is the most any single review can put back; the whole engagement is never at stake at once.
    • That note also records what has to happen on your side for the measure to mean anything — data migrated by an agreed date, an agreed number of people trained, the old parallel process switched off. If one of those has not happened, that stage's review date moves by the time that item was late, and only for that item. Your right to the refund does not lapse, and the refund is not voided.
    • We check each stage together on its own review date, once the system has been running long enough for the answer to mean something. The refund for that stage can be claimed once, within 30 days of that date. Each stage carries its own window, so a later stage is never closed by an earlier one.
    • You keep everything built either way. A refund does not come with us taking the work back.
    • After a refund, the backup, the closing report and the alerting for that system keep running for 90 days, so you have time to move without a gap. After that they continue only under the recurring service. Nothing is held back in the meantime — your full export is yours on request from the first day.
  • An asset on your books, not a bill with nothing behind it

    We do not sell anything whose only effect is to add a line to your expenses. What we build is meant to become part of what the business is worth — the process it runs on, the history it holds, the thing a buyer or a bank would count. Keeping a live system running does cost something on a cycle, and we quote that separately and say what it buys, rather than folding it into the build and waiting for you to notice. If we cannot explain how a piece of work pays for itself, we will tell you not to buy it.

    How that works

    • Every service page states the before and after in mechanics — what happens today, and what happens instead — so you can do the arithmetic on your own numbers rather than trusting ours.
    • We publish no percentages, no savings figures and no return-on-investment claims. We do not hold that data for your business, and a number we made up would be worth less than nothing.
    • The recurring service is priced on the pricing page with what each part of it buys — hosting, the daily backup and closing report, alerting, updates and support — so you can see the ongoing cost before you commit to the build.
  • Run it on your own server if you want

    Your data can live on hardware you own, in your own office or your own cloud account, with us holding no copy of it. Some businesses need that for regulation, some for a client contract, and some simply because it is theirs. It is a deployment choice, not a premium tier — inshaAllah your data stays yours, and where it sits is your decision rather than ours.

    How that works

    • Role-based access and a full audit trail either way, so you can see who changed what and when.
    • If you host it yourself, we will tell you plainly what that requires of you — a machine that stays on, someone to apply updates — rather than letting you discover it later.
  • A backup and a closing report, every day

    For every system we run that holds your business data, a daily backup and the day's closing report are sent out automatically — to your own server, your cloud drive, or simply your inbox, whichever you choose. The backup means a copy of your business exists somewhere we do not control. The closing report means the owner sees the day without asking anyone for it.

    How that works

    • The backup is a file you can open and restore without us. A backup only your vendor can read is not a backup.
    • If a day's backup or report does not go out, an alert goes out instead — silence is never treated as success.
    • This is part of the recurring service that keeps a live system running, priced on the pricing page. It is not a separate line added later, and there is no charge at the moment you need a restore.
    • If we refund a stage, the backup, the closing report and the alerting run on for 90 days and then continue only under the recurring service. That is time to move, not a notice period — nothing is withheld during it, and your export is available throughout.
  • Leave whenever you like, with everything

    You can cancel or move to another provider at any time, and take a complete, readable export of your data with you — not a locked file that only works in our software. Nobody should stay with a vendor because leaving is expensive. If you go, we would rather you go cleanly and speak well of us afterwards.

    How that works

    • The export is in open formats a competitor can import, and we will hand it over without a final invoice attached to it.
    • No notice period is used to hold your data, and no part of your history is treated as ours.

Common questions

Yes. Before each delivery stage we agree in writing what that stage is meant to reduce — hours on a task, people on a process, or a cost line — record what it measures today from your own records, and note what you need to do for the measure to mean anything. If it has not moved by that stage's review date, we refund the one-time fees you paid us for that stage of work — not everything else on the engagement, and not the recurring fees for keeping it running. The claim can be made once, within 30 days of that review date, and you keep everything that was built. If something on your side has not happened, that review date moves with it rather than the guarantee lapsing.

Yes. It can run on hardware you own or in your own cloud account, with no copy held by us. It is a deployment choice rather than a more expensive tier, and we will tell you up front what hosting it yourself asks of you.

At any time, with a complete export in open formats another provider can import. No notice period is used to hold data back, and the export is not attached to a final invoice.

Daily, sent automatically to your own server, cloud drive or inbox, along with the day's closing report. The backup is a file you can restore without us, and a failed backup raises an alert rather than passing silently. If we refund a stage, backups and the report run on for 90 days and then continue only under the recurring service.

These terms are part of the agreement you sign, not a marketing page. If anything here is not in the contract we send you, tell us — it should be.