Contact
Tell us what is breaking.
The more specific you are, the more useful the first reply will be. Mailbox counts, current platform, deadlines and the thing you are actually worried about all help.
Send us the details
Fields marked with an asterisk are required. Nothing here goes to a mailing list.
What happens next
- Reply within one working day From a person who has read your message, not an autoresponder with a ticket number.
- A 30-minute call We ask about the environment and the constraint you are actually under. No deck, no pitch.
- A written summary What we understood, what we would recommend, and roughly what it costs — in writing, whether or not you proceed.
Something urgent?
Existing clients with a live outage should use the support line in your service agreement — that routes straight to on-call. This form is for new enquiries and reaches us during office hours.
hello@queuebytes.comPrefer to look around first?
Before you write
Answers to the usual first questions.
How do you price work?
Projects are fixed-price after a paid discovery phase — we will not quote a migration blind. Support is a monthly per-user or per-device fee with the inclusions written out, so there are no surprise line items.
Do you work with businesses that already have an IT team?
Frequently. We take specialist projects — a migration, an audit, an integration — or the repetitive load, so internal staff can focus on the work only they can do.
What size of business do you work with?
Typically 20 to 500 staff. Below that, a full support agreement is often more than you need and we will say so. Above it, we usually work alongside an existing internal function.
How quickly can you start?
Discovery usually begins within a week or two. Migrations are scheduled around your business calendar — we would rather wait for the right weekend than force a cutover into a bad one.
Do we get locked into your tooling?
No. Documentation, source code, admin credentials and signing keys are yours. If you leave, you leave with a working handover — that is written into the agreement.
What if something goes wrong during a cutover?
There is a documented rollback path with agreed trigger criteria, decided before the window opens. If we hit a trigger we roll back and reschedule rather than improvising under pressure.