Tell me what your team does by hand.
The more specific you are about the workflow, the more useful my first reply will be. If it turns out an agent isn't the right answer, I'll say so.
Project enquiry
Details
Response time
Within one business day
Location
Remote, working with teams worldwide
Availability
Open to new work
What happens next
- 01You send the workflowA paragraph is enough: what happens today, how often, and which tools are involved.
- 02We talk for thirty minutesFree, no deck. I'll ask about the data, the edge cases and what happens when it fails.
- 03You get it in writingIf it's a fit I send a scoped plan with a price. If it isn't, I'll tell you what I'd do instead.
What happens next
The things people ask first
What happens after I send this?
I read it myself and reply with either a few questions or a time to talk. If it is clearly not something I should take on, you get that answer too, rather than being left waiting for a reply that never comes.
How quickly will I hear back?
Usually within one business day. If it will be longer than that, you will get a note saying so instead of silence.
What should I put in the first message?
The task someone does by hand today, roughly how often, and which tools are involved. That is enough to tell you whether it is worth a conversation. Rough information is genuinely fine at this stage.
Is the first call free, and is it a sales pitch?
Free, and not a pitch. Thirty minutes to understand the workflow and tell you honestly what I would do. Plenty of those calls end with me suggesting something other than an agent.
I don't have a spec. Is that a problem?
No, that is the normal starting point. Describing what hurts is more useful than a spec written in advance. The written scope comes out of the conversation, not the other way round.
Can we agree an NDA before I share details?
Yes. Say so in the form or the first reply and we sort the paperwork first. Nothing sensitive needs to be in the initial message anyway.