Contact
Send the store,
and the symptom.
A senior engineer reads every enquiry. You get a technical reply — what we think is happening and what we would look at first — usually within two working days.
- Reply time
- ≤ 2 working days
- First step
- Technical audit
- Read by
- A senior engineer
- Time zone
- Flexible overlap
01Project brief
03What to include
The more specific the symptom, the faster and more useful our reply.
A message that says "our site is slow" takes a back-and-forth to turn into something actionable. A message that says "PDP LCP is 4.6 seconds on mobile since we added a reviews app, and we can't touch the theme until after Q3 peak" lets us reply with a real answer on the first pass.
Useful things to name: the store URL, roughly how much traffic or revenue runs through it, the platform (Shopify or Shopify Plus), what changed right before the symptom appeared if you know it, and any hard constraint — a launch date, a code freeze, a budget ceiling. You do not need all of this to reach out; the form above only requires a name, email and the symptom itself.
04After you send it
- 01
A senior engineer reads it, not a sales queue
Your brief goes straight to the engineer who would run the work. There is no intake form that gets triaged by someone non-technical first.
- 02
We reply with a technical read, not a pitch
Expect a specific response — what we think is happening, what we'd check first, and whether an audit or a call is the right next step — not a generic 'let's hop on a call'.
- 03
If a call is useful, we book one
Calls happen when there is a decision to make together. It is run by the engineer, is technical from the first minute, and can conclude that you don't need us.
- 04
If not, you still get the answer
Sometimes the right answer fits in an email — a config change, an app to remove, a setting that was misconfigured. You get that either way.
05Ways to engage
- 01
Technical audit
A standalone, fixed-price review of your theme, app stack and performance. You get the findings document regardless of what you do next.
- 02
Fixed-scope project
A defined build, migration or feature, scoped and priced after the audit, delivered against an agreed architecture and render budget.
- 03
Monthly retainer
Ongoing engineering, CRO and support for stores that need a senior engineer on call without re-scoping every request from scratch.
- 04
Emergency support
For live-store incidents — broken checkout, failed sync, launch-day regression — with a same-working-day response window agreed up front.
06Response time
07Questions
Contact
Prefer to start with an audit?
Say so in the brief above. You will get the findings document either way, whether or not the engagement goes further.