Project enquiries
New consultancy work, Salesforce engagements, agentic AI builds, automation projects. Describe the problem, not the solution; the solution is the part we'll work out together.
No chatbots, no ticket portals. One guided form, or one email address if you prefer. Either way it lands with one person: the one who built whatever you're writing about.
A subject-line convention keeps a one-person inbox honest. Use these and nothing gets lost.
New consultancy work, Salesforce engagements, agentic AI builds, automation projects. Describe the problem, not the solution; the solution is the part we'll work out together.
Questions before buying, help after buying, licence issues, bug reports. Include your Windows version and what you expected to happen versus what did.
Data access, correction, or deletion requests under UK GDPR, including waitlist removals. The privacy policy explains exactly what's held and why.
The best enquiries read like a problem statement, not a job spec. These questions guide you there; answer what you know, skip what you don't. Only email and the first question are required.
Your enquiry is in the inbox and will be read by the engineer. Expect a reply within two working days.
Whatever it is, a half-formed idea counts. Half-formed ideas are where the interesting systems start.