What can we work on?

SmartFlowX can help with AI consulting and strategy, reviewing how your work gets done, building automation and AI agents, connecting systems, private or internal AI, and maintaining the systems we deliver. We’ll agree on the work and outputs around what you need.

Getting started, cost and timing

Before we start, we’ll agree on the problem and goal, scope, expected outputs, cost, estimated timing, what each of us is responsible for, delivery and support. Work starts once we’ve agreed on these.

Cost depends on how complex the work is, how much we need to build, infrastructure, outside services, security needs and support. If you see a price on the site, it’s a base or starting price rather than necessarily the final price for your project. We’ll confirm that once the scope is clear. Outside services and infrastructure may cost extra.

Timing depends on the scope, access we need, whether your data and infrastructure are ready, and how quickly we both move things along. Changes to the scope or delays in sharing information can shift the schedule. If you ask for something outside the agreed scope, we’ll review and agree on any change in cost or timing before doing it.

Your part and responsible use

You’re responsible for making sure the information, data and access you provide are accurate and lawful, and that using them follows the laws and policies that apply to your organisation. Access to internal systems should stay limited to what the project needs. You must use the outputs lawfully and responsibly; illegal activity, abuse and unauthorised access aren’t allowed.

Outside tools and AI

A project may rely on other companies’ services, such as servers, APIs, AI models, messaging or hosting. Their providers set the terms, prices and availability. If a service changes or stops, we may need to change how the system is built.

AI outputs can need human review or approval and won’t always be correct. We’ll decide how independently the system works and where people need to approve actions based on the project’s risk. People still need to make responsible decisions.

Ownership, confidentiality and showing the work

We’ll set ownership and usage rights for custom code, documentation, settings, agents, models and system design in your project agreement. Other companies’ tools and libraries stay under their owners’ licences.

I’ll only use the information you share for what our project needs. I won’t use it publicly or in a case study without coordinating with you. With your permission, and without revealing confidential information, I may show the project as an example of my work.

Support, responsibility and stopping a project

If we agree on support, it can cover system health checks, fixes within the project’s scope, necessary updates and service monitoring. New features or major changes are separate work or cost extra unless we agree otherwise.

Results can depend on things outside the project’s direct control, including data quality, API changes, service outages and how people use the system. That’s why a specific business result isn’t guaranteed unless we explicitly agree to it in a contract. We’ll also set the terms for stopping or cancelling a project, including the cost of work already done, in its agreement.

Changes to this page

I may update this page when services or legal requirements change. The latest version will be here. Updates don’t replace earlier project agreements, except where they can legally apply.