Atlassian Experts Service by TechTime Initiative Group


Here you'll find some basic info on how we do things


NZ$120.00/hour “on-site/on-call rate”
NZ$1,120.00/day “day rate” for full day workshops and travel outside Greater Wellington area

NZ$90.00/hour “consultancy rate” (with "Advice Only" Contractplease enquire)
NZ$64.00/hour “off-site rate” (with Support and Maintenance Contract
please enquire) 

Support & Maintenance package structure

In our added-value support & maintenance our role is "Expert on Call" - we fit between the Client's ServiceDesk, their DBAs and similar teams (if required) and Atlassian as a vendor.

Our usual terms for support & maintenance agreement are:

  • base "maintenance" component: pre-paid $256/VM/month equivalent to 4h of off-site work (i.e. $64/h, via remote access) includes reviewing logs for any strange/new exceptions, performance tuning, keeping non-production environments in sync with production, active tracking of updates from Atlassian and plugin vendors in non-production environment keeping it up-to-date and thus being ready to do the upgrade of prod at any time, adjusting monitoring settings, memory settings and doing performance tuning. In a nutshell - keep the overall system running and prepared for an upgrade. These hours are intended to be used up fully every month.
  • 24/7 "standby" component: $90/h, from 4h/month pre-approved to be used in case of a failure or out-of-business hours upgrades/maintenance. These are not rolling over from month to month and are effectively a risk mitigation payment (risk for you that it may fail, risk for us that you may need us to work on a weekend or at 2am). Our generic agreement stipulates zero or more extra hours we can spend on restoring the system in case of failure without requesting an explicit approval (at 2am in the morning) so the 4 hour cap doesn't stop us if the failure does happen.
  • "general support/being available" component: - pre-paid hours the Client can use for anything at $64/h, capped at a certain number of hours per months, not rolling over. The intent here is to let the client use them (or lose them) for non-project tasks every month.

A typical package is priced at $1000+GST per month and includes:

  • 1 VM = $256 per month
  • 4h 24/7 = $360 per month (these are not rolling)
  • 6h of "regular work" hours = $384 per month (these are not rolling)
  • provision for any hours beyond the above to be pre-approved as separate SOWs

Upgrade Call-out Service

Priced at $1440, this is an equivalent of 16h on-site or 22.5h off-site and includes up to 2 environments.

We strongly recommend to have a test environment and perform the upgrade there first using your production data restored from a backup, to see how long the upgrade will take for your data set and hardware configuration and eliminate possible data issues, incompatibilities with plugins and custom add-ons.

We also encourage our customers to have a week in between for your team to have a chance to get used to new features and do a bit of the UAT.

During that week we log all the issues you've discovered and aim to deal with them before the production installation.

Additional environments can be added for $720. If the complexity of your setup may prevent us from performing this service on the fixed-cost basis we will advise you immediately.

Questions to Ask Your Team

  1. Can remote access (ssh or Remote Desktop) be provided to TechTime? Access can be limited to specific static IPs.
  2. What versions of Atlassian products are being used? What versions are desired?
  3. What platform is in use in production: OS, distributive and version. Is it running on a physical host or a VM?
  4. Who is looking after this host/VM? What if something needs changing (memory, HDD space)? Will it be possible to give TechTime admin-level access?
  5. What DB is currently used? Who handles DB-related questions ie access, running SQL statements if required?
  6. Are backups up to date and where can they be found?
  7. Do you already have a test environment? If not, would a temporary cloud instance in Amazon EC2 be acceptable (i.e. how sensitive is your data)?
  8. Do the environments have access to Internet either direct or through proxy? If through proxy, what are the proxy details.
  9. Does the existing license make you eligible for the upgrade or will you need to renew?
  10. What, if any, are the important plug-ins being used?
  11. What, if any, customisations have been applied to your Atlassian product and will need to be migrated?
  12. Do you have a test plan?
  13. When approximately is this upgrade expected to be performed?
  14. What downtime/outage procedures are observed, who has to be notified/updated on progress.
  15. Are there any documents/agreements that we need to sign (NDA/contracts)? Are there any security checks/requirements TechTime needs to fulfill before we can take on this project?
  16. Who will be supporting the installation after the upgrade?