A real example
We walk through the information received, tools, actions, exceptions, and expected result.
Home Approach
Approach
A precise task, a usable solution, clearly defined support.
From a real example through maintenance, responsibilities and working terms are defined before we begin.
The approach
From the first example through support.
A written proposal
The task, software, reviews, success criterion, price, timeline, and support are defined before work begins.
Build and trial
I build the solution and we test it on real cases. If a fixed rule is enough, AI is not the starting point.
Setup
I connect the agreed tools, provide operating instructions, and define a clear way to report an issue.
Maintenance and changes
Support for the delivered scope and future changes are separated in the agreed terms.
Before we build
We start with one focused engagement.
Scope, timeline, price, and the expected outcome are defined in a written proposal. We expand only when it is useful.
Clearly bounded support
Setup and maintenance are part of the engagement.
Before work begins, we define what is covered, for how long, and how requests are handled. The proposal separates initial setup from support, which may be billed as a recurring service.
Hosting, third-party subscriptions, AI usage, access handover, and end-of-service terms are also made explicit.
Within agreed support
- Fixes within the delivered scope
- Agreed operational checks
- Maintenance of covered connections
- Planned usage support
Scoped separately
- A new business process
- A new tool or integration
- Major rework after an external change
- A major increase in volume or scope
Before we talk
Questions you might be asking.
Do we need to change our software?
We start with the tools you use and check connection options before deciding.
Do we need to learn how to build agents?
No. Setup includes the guidance your team needs to use the solution and review its output.
Does the agent act without approval?
Automatic actions and required approvals are agreed according to the process and its level of risk.
Where does the solution run?
Depending on the need, it can run in your environment or in a hosted service. Access and responsibilities are defined before setup.
What happens if it stops working?
Support defines a reporting channel, the correction scope, and written intervention terms.
How is support billed?
The written proposal separates initial setup from support, including its duration, coverage, and terms.
What if our process changes?
We separate maintenance of the existing solution from changes that need a new estimate.
Your next step
Which task would you rather not do by hand again?
Describe what comes in, what you do today, and the result you need. We will work out what can be handled for you.
Your task does not look like any of these examples? Describe it anyway.
Describe my taskBook a 30-minute call
Scope, timeline, price, and the expected outcome are defined in writing.