What should I include in the first message?
Describe what keeps breaking, slowing people down, confusing customers, changing between staff, or falling back on manual work. Include who it affects and what would become easier if it was fixed.
Contact
Bring the messy operational problem.
You do not need a polished brief. A rough description of what keeps drifting, changing between staff, or falling back on manual work is enough to start.
Enquiry
Talk through what is out of kilter.
Use this for workflow inconsistency, customer onboarding, waiver systems, access workflows, software gaps, hardware handoffs, staff training, supplier friction, or admin overload.
Before You Send It
What to include in the first message.
You do not need to package the problem neatly. The rough version is usually more useful.
Do I need a formal brief?
No. A rough description is enough. Plain language is better than guessing the technical answer too early.
Can I contact Off Kilter about a custom workflow or software idea?
Yes, especially if the idea comes from a real operating problem. The first step is still to explain the problem, not just the feature you think might solve it.
What happens after I send the enquiry?
Off Kilter reviews the message and follows up if the problem looks like a fit. If a problem session makes sense, the session is booked and paid before the call.