Question 1

How do you work alongside an existing engineering team?

Accepted Answer

Either way round. Sometimes I own the problem — discovery, workflows, knowledge, prompts, testing — while your engineers own the implementation, which is how the production support agent in Chapter 01 was built. Sometimes I own the architecture and write the code, which is how the ownership determination engine in the same chapter is being built. I will tell you which one a given problem needs.

Question 2

What does a first project look like?

Accepted Answer

A short scoping conversation, then a discovery pass over one real workflow — the one you already suspect is wasting the most time. That produces a written assessment of whether it should be automated and how, which is useful whether or not you continue.

Question 3

What do you need from me to start?

Accepted Answer

Access to the real process rather than a description of it: a sample of actual tickets or documents, whoever currently does the work for an hour, and a clear statement of what must never be decided without a human.

Question 4

How quickly do you reply?

Accepted Answer

I answer project enquiries myself, usually within two working days.

Question 5

What won't you do?

Accepted Answer

I won't build automation that makes a compliance, funds or eligibility decision without a person in the loop. I will automate everything that prepares that decision. I also won't quote a system I haven't scoped.

Question 6

Availability and rates?

Accepted Answer

Part-time and project-based only — I am currently engaged and not available full-time. Remote, any timezone by agreement. Rates on request, once I know the scope.

Writing