Contact
Tell us what you’re deciding, or what’s breaking.
You don’t need a budget, a specification or any technical vocabulary. Describe it the way you would to a colleague.
What happens next
A reply from the engineer
Whoever reads your message is the person who would do the work.
A short call
We ask what you use day to day and what it costs you when it goes wrong. No slides.
Something in writing
What we’d do, what it would cost, and what could go wrong.
Your decision
The document is yours either way, including if you take it elsewhere.
Direct
- Email[email protected]
- Who repliesThe engineer
Already have a developer and want a second opinion on something they proposed? That’s a good reason to write, and usually a short conversation.