Send the problem in writing.
Say what should happen and what happens now. You do not need to identify the cause. Within two business days you get a written reply with the next step.
The intake form
You send
- What should happen.
- What happens now, or what does not exist yet. No diagnosis needed.
- The systems involved, and links if you have them: Shopify, Meta, Google Workspace, your CRM, your database, whatever is in play.
You get back
- Within two business days, a written reply with the next step.
- For a defined job, a plan and a fixed price, with what is included, what is left out, and how the result will be verified before it is called done.
- When the cause is not yet clear, the questions or the short, priced investigation needed to get there.
Prefer plain email? Write to [email protected] with the same three things.
Before you send
What will it cost?
A fixed price after a written plan. When the cause is not yet known, a short investigation is priced first, on its own, only where it is really needed. Ongoing engineering is priced monthly after an assessment.
Is there a minimum project size?
No. Small first jobs are welcome. A small, well-defined job gets the same written plan and fixed price before any work starts.
When do you charge for investigation?
Only when the cause, or the size of the job, genuinely cannot be known from your description. The investigation is short and bounded, and it is priced on its own before it starts. Simple, well-understood requests are planned and priced directly, with nothing to pay first.
Can you work on something another developer, or an AI tool, built?
Yes, after an initial look at its behavior, dependencies and access. You get the repair or development plan in writing.
What happens afterward?
Handoff in writing, an agreed correction period, and optional ongoing engineering if you want the system looked after.