Contact¶
For engagement enquiries, scoping conversations, or partnership discussions:
What to send¶
A first message that answers three questions accelerates everything that follows:
- What you are trying to do. The functional outcome, not the technology. ("Stable outbound IP for a remote workforce hitting GitHub and AWS" beats "We need a VPN.")
- The scale and constraints. Approximate user count, traffic profile, jurisdictions in scope, regulatory regime if applicable, infrastructure preferences (cloud, on-prem, hybrid).
- The shape of engagement you have in mind. Custom build, customization of an existing framework, managed operations, or "we don't know yet, want a scoping conversation."
We respond within two business days with either a scheduling proposal for a scoping call or a written follow-up if the scope is small enough to handle async.
What happens next¶
- Scoping call under NDA, typically 60-90 minutes. We review the requirement, sketch the architectural shape, identify the open questions.
- Written specification, produced over 1-2 weeks under a separately-quoted scoping engagement. The specification is the contract for any subsequent build engagement.
- Build engagement, fixed-price against the specification, executed under the engineering framework documented elsewhere on this site.
What we don't do over email¶
- Send proprietary detail, design documents, or sample code before NDA.
- Quote pricing against a verbal description. Pricing requires the written specification.
- Engage with introducers expecting commission on customer payments. We pay reasonable referral fees on signed contracts; we do not pay finders for introductions.