Draft.
These terms are stated in plain language for review by Fully Powered AI and its adviser before they go live; the signable agreement follows.
What "working" means.
"Working" means your team runs the workflow in its own ChatGPT, Claude, Copilot or Gemini workspace, with information it can already bring into it: files it already handles, exports its systems give, and connections the platform already supports and you have already approved. A person reviews what it produces.
"Working" does not mean a custom connection to your systems, unattended or scheduled running, or rollout beyond the people at the handover. Each is separately agreed work.
The 3-Day Workflow Sprint implements the agreed procedure after the suitability check, not an absolute promise to automate a document as written; minor clarifications are settled with your expert as the build goes, and defects in the written procedure are flagged to you. The 2-Week Team Sprint implements the one procedure chosen with its owner from those written and agreed.
Acceptance: when it is done.
Success criteria are written down before the build and agreed with your approver. Correctness and benefit are tested separately.
The build uses invented examples. Checking uses your real examples: your own person runs them in your account while Fully Powered AI watches, and Fully Powered AI never receives them. The checking set includes realistic exceptions, ambiguous inputs, and cases where the right behaviour is to stop and ask. Your expert marks each checked result right, wrong or uncertain, and sees every miss.
A handful of passing tests shows behaviour on those cases; it does not establish reliability on every case. So the handover notes state the supported scope, when the workflow must hand off to a person, and the manual fallback.
The engagement is accepted when the criteria are met and the intended user has run the workflow on real work, meaning the most recent real instance you have, run by the user in your own workspace. Where the work arrives unpredictably, the first live occurrence is observed at a follow-up check; acceptance does not wait for it.
If checking what the workflow prepares takes as long as doing the work, we say so and stop.
If the chosen workflow proves unsuitable, we agree with you which of three things happens: another workflow, a simpler solution, or stopping, in which case Fully Powered AI settles it with you directly. Never a substitute presented as the original promise met.
Support after handover.
At handover you name the owner of the approved procedure. The handover notes cover how to run the workflow, how to check its output, what it does not cover, how to ask for a change, and what to do by hand if it fails. The agreement sets out the rights to use and adapt the delivered capability.
Five business days of support after the 3-Day Workflow Sprint's handover, and ten after the 2-Week Team Sprint's. Inside the window Fully Powered AI corrects delivery defects: the workflow not doing what was agreed and accepted.
A new step, rule, output, data source or team is a new requirement, quoted separately as new work, inside the window or after it.
This is support, stated and bounded. What protects you is the suitability check before any work starts, the criteria agreed before the build, and this window. If an engagement goes badly, Fully Powered AI deals with that with you directly, case by case.
Your information and use rights.
Your information and know-how remain yours. The agreement sets out your rights to use and adapt the deliverables and any included Fully Powered AI technology.
Fully Powered AI retains its underlying technology, general methods, reusable templates and testing tools.
Your confidential information is never reused or shown as an example without your written permission. Every example on this site is an invented one, and it says so.
Improve & expand.
An ongoing relationship can include reviewing results, refining workflows, maintaining existing capabilities and developing new ones. It may be agreed from the outset or after an introductory sprint. Scope, fees and included services are set out in the agreement.
Three definitions, in every agreement:
- Defect correction: making the workflow do what was agreed and accepted; included in the support window.
- Maintenance: keeping it doing that when something around it changes, such as a platform update, an export format or a change of system; when a dependency changes, the commitment is to check and retest, not a promise that nothing will need changing.
- New requirement: a new step, rule, output, data source or team; quoted as new work.
Every quote is a fixed fee for an agreed scope and states how long it stands. An expired quote is requoted, never honoured by default. No fee is billed by the hour, and no fee is tied to your savings.
A past client's next workflow is a scoped quote, never a second entry offer; the 3-Day Workflow Sprint is not credited toward the 2-Week Team Sprint, and a 3-Day client whose work proves to need mapping is offered a 2-Week Team Sprint, once.
What is not included.
The 3-Day Workflow Sprint
- Substantial mapping, redesign or documentation (that is the 2-Week Team Sprint).
- A new system connection.
- Unattended or scheduled runs.
- Anything sent or changed without a person's approval.
- A second procedure.
- Any promise of accuracy beyond the reported test results.
- Any promise of a financial result.
The 2-Week Team Sprint
- A second built workflow.
- A second team or area.
- New system connections.
- Unattended or scheduled runs.
- Rollout or training beyond the people at the handover.
- Any promise of a financial result.
Neither engagement requires you to hand information to Fully Powered AI. The work is done in your systems and your accounts; you install what is built; production data is never needed to build it. Before the 3-Day Workflow Sprint you send a couple of documented procedures and a couple of examples you choose, never production data or sensitive records.