Contact
Describe what you need, with as much concrete detail as possible. I reply to messages myself, with no sales layer between you and the person who'll look at your request, whether it's a fault to deal with right now or a project still being scoped.
What to prepare before writing
-
Describe the situation
What isn't working, or what you're trying to build. The more concrete the description, the more concrete the reply can be.
-
State the platform involved
PrestaShop, WooCommerce, Shopify or custom development: it directly shapes how I approach the request and what I check first.
-
Say if it's urgent
A shop that's down isn't handled the same way as a project planned over several weeks. Say so clearly in your first message, with roughly when the problem started.
-
Leave a way to reach you quickly
Email and phone if possible, to avoid unnecessary back-and-forth on points that are simple to clarify.
-
Attach access if you have it
Read-only access to the admin or server often makes a situation clearer, faster, than a long written description.
How to reach me
-
Email
Suited to a detailed request, with screenshots, access details or documents to attach directly to your message.
-
Phone
Suited to an emergency or a quick exchange, before putting the details in writing afterwards to keep a clear record.
Frequently asked questions
What's the best way to contact you?
Do I need a spec document already?
Do you respond to requests from agencies?
What happens after my first message?
Can I contact you for a simple question, without a specific project?
Do I need to already know which service I need before writing?
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.