Home Approach

Approach

Understand, design, build. With your team.

We start with the business problem, test an approach on real examples, and put what works into use. Scope and support terms are defined in writing.

The approach

From the first example through support.

01

Understand the problem

We walk through a real example, tools, exceptions, and the result you need. I check feasibility, available data, and whether AI is useful.

02

Design and scope

I propose an approach that fits the need. Scope, reviews, success criteria, price, timeline, and support are defined in writing.

03

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.

04

Setup

I connect the agreed tools, provide operating instructions, and define a clear way to report an issue.

05

Support and changes

We agree on support for the delivered scope, its duration, and billing. Future changes are scoped separately.

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

Implementation, then support we agree together.

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.

Is the first conversation free?

Yes. We spend 30 minutes discussing your situation and whether I can help. Any detailed assessment and implementation follow under a written proposal.

Can we work together remotely?

Yes. I’m based in French Polynesia and available for remote engagements with US small businesses, in English or French. We agree on meeting times and communication before starting. For businesses in French Polynesia, on-site work is available by agreement.

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

What problem would you like to solve?

Tell me about your business, what gets in the way, and the result you need. The first 30-minute conversation is free. We’ll see whether I can help and where to start.

Let’s talkBook a free first conversation

Scope, timeline, price, and the expected outcome are defined in writing.