Contact · One inbox

Reach the engineer.

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.

01 / WHAT GOES WHERE

Same address, clear subject.

A subject-line convention keeps a one-person inbox honest. Use these and nothing gets lost.

Projects

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.

Subject: "Project enquiry"
Reply: typically within 2 working days
Products

WorkRecap support

Questions before buying, help after buying, licence issues, bug reports. Include your Windows version and what you expected to happen versus what did.

Subject: "WorkRecap support"
Reply: typically within 2 working days
Legal

Privacy requests

Data access, correction, or deletion requests under UK GDPR, including waitlist removals. The privacy policy explains exactly what's held and why.

Subject: "Privacy request"
Reply: within one calendar month (usually far sooner)
02 / THE ENQUIRY FORM

Help me say yes quickly.

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.

Received, properly.

Your enquiry is in the inbox and will be read by the engineer. Expect a reply within two working days.

Honest expectations
  • Every message gets read; most get replies within two working days
  • If it's not a fit, you'll be told so, quickly and with a pointer elsewhere
  • This is an after-hours practice becoming a product business: quality over speed, always
  • No obligation survives an enquiry; nothing is binding until a written scope is agreed
  • Prefer plain email? theunisj@nightowlit.co.uk reaches the same person

The inbox is open.

Whatever it is, a half-formed idea counts. Half-formed ideas are where the interesting systems start.