Six stages, and two of them are places to walk away

Three things, priced separately. A fixed-price review that maps your systems and produces a costed plan you keep, whoever builds it. A build, fixed against what the review scoped. Then month-to-month support. No licence and no per-message charge: the infrastructure runs in your own cloud account and you pay that bill directly, at cost. We will not publish a build price, because scope is discovered rather than specified, and a number quoted before seeing your systems is one we would have to renegotiate later.

Once the first flows are running, adding a partner on a document type you already handle is designed to take days rather than weeks: the mapping is configuration and the plumbing exists. A partner with an unfamiliar format, or one that runs its own certification cycle, moves on their timetable rather than ours. That is worth knowing up front rather than in week three. On a new project the first flow runs in production within weeks of the build starting.

You own it. It is built inside your own cloud account, defined as infrastructure code in your repository, and the field mapping is data in your own database rather than a proprietary format on our server. Nothing lapses and nothing stops working if you stop paying us. A hosted integration platform runs your order flow in the vendor’s tenancy, and leaving it means rebuilding every flow somewhere else.

Almost certainly. Each connection is designed against that system’s own interface rather than picked from a list of prebuilt adapters. The question is whether the system has a documented way in: an API, a file exchange, a database view, an export. Nearly all of them do. Where one is genuinely closed we say so early, and the review costs a fraction of finding out later.

Monitoring runs around the clock and retries are automatic, so most overnight failures clear themselves and nothing queued is lost. There is no person answering the phone at 3am. This is a small, senior-led firm, and pretending otherwise is the kind of promise that gets found out at the worst moment. Ownership covers the gap: the system runs in your account, so your team can search by your own order number and fix a data problem without waiting on us. If you need a staffed overnight desk, buy that from a larger provider.

In your own cloud account, in Australia — Sydney by default. Because the account is yours, the residency question has a shorter answer than usual: the data never moves to our infrastructure, because there is no our infrastructure in the path. Every payload is archived in that same account so you can search what a partner actually sent you. We hold no IRAP assessment and no government security certification, and we will say so plainly if that is what you need.

As the person who decides how the systems should fit together, while your team or incumbent keeps running what they run. That works best when the boundary is explicit from the start — who owns which account, who is called when something breaks, which changes need a conversation first. We write that down in the first week. Replacing an incumbent who is doing a reasonable job is rarely the recommendation.

GTSR Solutions is an Australian private company and invoices in AUD with the ABN shown — ABN 54 697 553 870, ACN 697 553 870. Engagements run on a short written services agreement covering scope, price, ownership of the code and accounts, liability, and how either side ends it. Support is month to month with thirty days’ notice. There is no offshore entity and no third party in the contracting chain.