What size of organisation do you work with?

Enterprise practice work — integration, orchestration and bespoke builds — suits mid-to-large organisations, typically those running several business systems that need to talk to each other and having someone internally accountable for the outcome. Smaller businesses are better served by an INNOVATECH™ Managed Services membership, and businesses that need hosting alone are better served by Yamahost. We will tell you which of the three you belong in.

How do you price enterprise work?

From a scoped architecture, never from a feature list. An assessment is priced as a fixed piece of work. What follows is priced either as a fixed-scope build with a written change process, or as dedicated engineering capacity per period against a backlog you prioritise. A number quoted before the estate is understood is a guess, and guesses get paid for by somebody later.

Do you work on retainer?

Yes, in two forms. Dedicated engineering capacity gives you an agreed capacity per period against your own priorities. Operational retainers cover running an integration backbone or an application we built, under an agreed service level. Both are optional — handover is designed so that keeping us is a commercial choice rather than a technical necessity.

Which industries do you work in?

The work is defined by the shape of the problem more than the sector: multiple business systems that do not talk to each other, a process that is a competitive advantage, or a product that needs building. That pattern shows up in financial services, logistics, retail, professional services and the public sector. Where a sector carries specific regulatory obligations, those become design constraints from the assessment onwards.

Who owns the code and the intellectual property?

The client owns the intellectual property in commissioned work, stated in the engagement agreement. Pre-existing components and open-source libraries remain under their own licences, and we list which those are before the build starts rather than at handover. Where a venture is co-built with a partner, ownership is agreed in a separate agreement before development begins.

Do you sign non-disclosure agreements?

Yes, as a matter of course, and before any detail is shared. Send yours and we will sign it, or ask and we will send ours. Client information is not used to inform our own ventures — that separation is contractual, not merely cultural.

How is our data handled during a project?

Under POPIA, and by design rather than by policy statement. Personal information is classified during data modelling; access is least-privilege and logged; production data is not copied into development environments without masking; and retention and deletion paths are built rather than promised. Where data residency is required, infrastructure is deployed in-region.

What happens to our systems if we stop working with you?

You keep running. Handover includes source code, infrastructure-as-code, runbooks, architecture documentation and a working local development environment, and it is delivered as part of the engagement rather than at the end of the relationship. If we have done our job, leaving is a commercial decision with no technical hostage attached.

Can you work alongside our in-house development team?

Yes, and it is one of our four engagement models. Our architects design and review while your team builds, which suits organisations with engineering capability that need senior architecture rather than more hands. Where we build alongside your team, ownership of each component is agreed up front so accountability does not blur.

What support is available after go-live?

Stabilisation is planned into every engagement, because the first two weeks of real use find things no test environment will. After that, support is either an operational retainer under an agreed service level, or handover to your team with runbooks and documentation. Both are supported; neither is assumed.

How long does a typical engagement take?

An integration assessment runs two to three weeks. A first production slice typically follows four to eight weeks later. Full migration off legacy middleware is measured in quarters and runs alongside the existing path rather than replacing it on a date. A bespoke build depends on scope, but we deliver in two-week increments with something usable at the end of each.

Do you still offer web hosting, domains and IT support?

Yes, in two places. Hosting and domains on their own are sold under our Yamahost brand at transparent Rand pricing. Bundled managed services — website, hosting, email, domains, maintenance and support on one subscription — are the INNOVATECH™ Managed Services memberships, from R299 a month, managed in the client portal at innovatechgroup.co.za.

How do we get a proposal?

Start with an enquiry and a first call. If there is a fit, we propose an assessment, and the proposal for the work itself follows the assessment rather than preceding it. That order exists so the proposal describes your estate rather than our assumptions about it.

Frequently asked questions

How we work, what things cost, who owns what, and where hosting went. If your question is not here, ask it directly.

Ask a question See the pillars

Working with InnovaTech Group

The questions below are the ones that come up most in first conversations, answered as directly as we would answer them on a call. Questions specific to a service live on that service's page: integration questions on the integration page, build questions on the custom engineering page, membership questions on the managed services page.

About engagements

What size of organisation do you work with?: Enterprise practice work — integration, orchestration and bespoke builds — suits mid-to-large organisations, typically those running several business systems that need to talk to each other and having someone internally accountable for the outcome. Smaller businesses are better served by an INNOVATECH™ Managed Services membership, and businesses that need hosting alone are better served by Yamahost. We will tell you which of the three you belong in.
How do you price enterprise work?: From a scoped architecture, never from a feature list. An assessment is priced as a fixed piece of work. What follows is priced either as a fixed-scope build with a written change process, or as dedicated engineering capacity per period against a backlog you prioritise. A number quoted before the estate is understood is a guess, and guesses get paid for by somebody later.
Do you work on retainer?: Yes, in two forms. Dedicated engineering capacity gives you an agreed capacity per period against your own priorities. Operational retainers cover running an integration backbone or an application we built, under an agreed service level. Both are optional — handover is designed so that keeping us is a commercial choice rather than a technical necessity.
Which industries do you work in?: The work is defined by the shape of the problem more than the sector: multiple business systems that do not talk to each other, a process that is a competitive advantage, or a product that needs building. That pattern shows up in financial services, logistics, retail, professional services and the public sector. Where a sector carries specific regulatory obligations, those become design constraints from the assessment onwards.

Contracts, IP and data

Who owns the code and the intellectual property?: The client owns the intellectual property in commissioned work, stated in the engagement agreement. Pre-existing components and open-source libraries remain under their own licences, and we list which those are before the build starts rather than at handover. Where a venture is co-built with a partner, ownership is agreed in a separate agreement before development begins.
Do you sign non-disclosure agreements?: Yes, as a matter of course, and before any detail is shared. Send yours and we will sign it, or ask and we will send ours. Client information is not used to inform our own ventures — that separation is contractual, not merely cultural.
How is our data handled during a project?: Under POPIA, and by design rather than by policy statement. Personal information is classified during data modelling; access is least-privilege and logged; production data is not copied into development environments without masking; and retention and deletion paths are built rather than promised. Where data residency is required, infrastructure is deployed in-region.
What happens to our systems if we stop working with you?: You keep running. Handover includes source code, infrastructure-as-code, runbooks, architecture documentation and a working local development environment, and it is delivered as part of the engagement rather than at the end of the relationship. If we have done our job, leaving is a commercial decision with no technical hostage attached.

Delivery and support

Can you work alongside our in-house development team?: Yes, and it is one of our four engagement models. Our architects design and review while your team builds, which suits organisations with engineering capability that need senior architecture rather than more hands. Where we build alongside your team, ownership of each component is agreed up front so accountability does not blur.
What support is available after go-live?: Stabilisation is planned into every engagement, because the first two weeks of real use find things no test environment will. After that, support is either an operational retainer under an agreed service level, or handover to your team with runbooks and documentation. Both are supported; neither is assumed.
How long does a typical engagement take?: An integration assessment runs two to three weeks. A first production slice typically follows four to eight weeks later. Full migration off legacy middleware is measured in quarters and runs alongside the existing path rather than replacing it on a date. A bespoke build depends on scope, but we deliver in two-week increments with something usable at the end of each.
Do you still offer web hosting, domains and IT support?: Yes, in two places. Hosting and domains on their own are sold under our Yamahost brand at transparent Rand pricing. Bundled managed services — website, hosting, email, domains, maintenance and support on one subscription — are the INNOVATECH™ Managed Services memberships, from R299 a month, managed in the client portal at innovatechgroup.co.za.
How do we get a proposal?: Start with an enquiry and a first call. If there is a fit, we propose an assessment, and the proposal for the work itself follows the assessment rather than preceding it. That order exists so the proposal describes your estate rather than our assumptions about it.

Still have a question?

Ask it directly — you will get an answer from a person within one business day, including when the answer is that we are not the right supplier.

Ask InnovaTech Group