Working together

How a Project Starts: From Workflow Brief to Pilot Decision

Understand what to share in an automation enquiry, how a pilot can be scoped, and which deliverables help you decide whether to proceed.

If your team is considering automation, the useful starting point is a description of the work people do today. Tell me what arrives, what someone does with it, and where the process becomes slow or unreliable. You can make an initial enquiry before choosing a tool or writing a technical specification.

I work across AI, data engineering, document workflows, and web automation. A project enquiry helps establish whether the problem fits that experience and whether a small, testable first step makes sense. The scope below is a proposed way to begin. Deliverables, availability, fees, and responsibilities need agreement for each engagement.

What to put in your first message

Describe the current workflow in a few sentences. Include the systems involved, approximate frequency or volume if you know it, and the result you want. Explain what happens when something goes wrong and who has to repair it.

For example, a useful brief could say, “Our team copies invoice totals from supplier PDFs into a spreadsheet. Layouts vary, and someone checks every row before import. We want to test whether extraction can reduce the amount of checking.” This is an illustrative brief, rather than a client result.

A description of document types or a redacted schema is enough to start a conversation. Keep confidential files, credentials, customer records, and regulated data out of the contact form. Access and permitted sample handling can be agreed separately if needed.

Turn the brief into a question a pilot can answer

A pilot needs a bounded decision. For document extraction, that might be whether required fields can be recovered on a reviewed sample with an acceptable amount of manual correction. For recurring website reports, it might be whether the system detects an introduced failure and delivers an actionable report once.

I would first identify the input, intended output, current baseline, and the person who will assess the result. A dependency such as access to an API or an agreed set of labels belongs in the scope before implementation begins.

Agree the deliverables before building

A practical scoping note can record the following agreement.

Scope itemWhat to make explicit
InputWhich websites, document families, or systems are included
OutputA report, structured records, a working integration, or a review interface
AcceptanceWhat evidence the team needs to make a decision
ReviewWho checks ambiguous results and how corrections are recorded
BoundariesExcluded formats, integrations, environments, or production responsibilities
HandoverCode, configuration, instructions, unresolved issues, and ownership

Set acceptance criteria before evaluating the final sample. Otherwise it is too easy to adjust the definition of success around the result that happens to appear.

What the pilot should leave you with

The deliverable should make the next decision easier. A useful handover includes the tested workflow, results and failures, instructions for repeating the evaluation, and a list of dependencies for production. The conclusion may be to proceed, narrow the scope, collect better data, or keep part of the work manual.

Production deployment needs its own agreement on monitoring, access, recovery, running costs, and ongoing support. Discuss these responsibilities when scoping the work so the pilot has a clear endpoint.

Where Websiteli fits

My Websiteli project describes a Swiss service focused on websites, automation, analytics, and related AI work. This personal site brings that work together with my engineering portfolio and research. In an enquiry, say which project or workflow brought you here. The contracting arrangement and delivery scope can then be clarified for the proposed engagement.

For hiring or research collaboration, use the same contact page and state that purpose in your message. My profile and CV provide background for those conversations.

Describe the workflow you want to improve

Share the current process, the systems involved, and what a useful first result would look like. The contact form supports an initial request and offers direct email as an alternative.

Describe your project