Tell us what the system does and what is going wrong.

What to include

The more of this you can answer up front, the more useful our first reply will be. Anything you do not know yet is fine to leave out.

• ▪What the system does, and roughly how long it has been running.
• ▪The stack, as far as you know it. A language, a framework version and a database is plenty.
• ▪What you want to happen: something new built, something slow made fast, something old made safe to change, or a manual step automated.
• ▪Whether there is a deadline forcing the timing, such as an end-of-support date.
• ▪Who would be involved on your side, and whether they have capacity.

What happens next

We read it and reply within 24 business hours, usually sooner. The first reply is a real response to what you sent, not a request to book a call so somebody can ask you the same questions again.

If we do not think we are the right team for the work, that will be in the first reply too, along with what we think you should be looking for instead.