Before a contract is written

A site or a workspace, an app, online sales, a bot, sync between systems, summaries, CRM, the cloud, an access review, and a review before anything is written. After launch we can stay on for ongoing support.

It makes sense when the process no longer fits in a spreadsheet or a chat: a live stream of requests, several systems, people in the field, a storefront, internal training. A napkin sketch works too, if a narrow first release is needed.

After the review we name a range for the first system, not for “the whole possible product.” Then a fixed fee for an agreed scope, payment by stage, or monthly ongoing support. The first conversation costs nothing.

A narrow landing page or a bot takes a few weeks. A workspace or a shop takes about one to two months. Several systems and roles take longer. We name the time once we have seen what is already in place.

Leave the task in the form, or write to hello@qazoryx.group. If a call is easier, put a phone number in the request. We will add a Qazoryx number once it is confirmed.

Yes, if it is needed. One-off edits are possible, and so is ongoing support with an agreed response time. We set the format apart from development.

Yes. A contract for the work is the usual order. We sign a non-disclosure agreement before we discuss the inside of the process.

Yes. First we look at the code, the access, and what must not be touched. Then we say what we extend, and what is simpler to replace.

Yes. Calls and messages cover most of the work. We go on site only when readings cannot be taken, or the system cannot be started, any other way.

A fixed fee for an agreed scope, portions as stages are ready, or monthly if the work is long. We choose the method before the start and write it into the contract.