Picture the owner of a 25-person company with no IT staff deciding to put AI to work this week. The people who already run the business do the few parts that need them, and we take care of the rest.
So the answer is no. Planning the work and running your first workflows involve nobody technical. Connecting a workflow to a business system needs one person who can approve access to that system, and that is usually someone you already have.
Planning takes the people who know the work.
Fully Powered Planner is where your company decides what each team and role should be able to do with AI. It runs in a web browser with nothing to install. The owner, the operations lead and whoever knows each team’s work best name the teams, list the work each team repeats and choose what to build first. Only the people in your business hold that knowledge, which is why the plan starts with them.
Running a workflow takes the AI you already use.
A workflow carries how your company does a piece of work: the steps, the rules, the judgment calls and what good output looks like. It runs in the AI your team already uses, whether that is ChatGPT, Claude, Copilot or Gemini, so there is no new system to buy or look after. At handover, the person who does the work runs it on a real case with us.
From the first day, the workflow works from what your team already has: files, the reports your systems export, and what the people who do the work tell us when we ask them. Someone exports a report they already know, hands it to the workflow and checks what comes back.
Your business confirms that its AI workspace is approved for the information the workflow uses. Is our data safe? sets out where that information goes at each step and who decides.
Connecting a system takes whoever approves access to it.
A workflow does far more when it reads straight from a business system and leaves its work where your team will pick it up. That is what a connector does, and Fully Powered Connectors is our name for those connections and for the work of choosing them and setting them up.
To connect a workflow to your accounting system, your CRM or another account, you need the person who administers that account, who is often the owner or the office manager. They approve access in the account’s settings, and we explain in plain words what they are approving: what the connection can read, what it can change and who acts on its output.
We set the connection up as part of building the workflow, wherever a connector for that system already exists. What gets connected is agreed when we scope the work, and we never promise a new connector. Until a connection is approved, the workflow keeps running from exports with the same rules and tests. How a workflow works across your business systems shows one invented company’s connections in detail.
Here is who does what at a 25-person firm.
Illustrative example with invented data. Calder Street Architects, an invented 25-person architecture practice. Its office manager administers the firm’s accounting account.
Calder Street has no IT staff. The principal wants a clear view of unpaid invoices every Monday, which the office manager pulls together by hand. The firm starts from the weekly receivables summary workflow template and adapts it to its own rules.
| Stage | Who is involved | Their part, and how long it takes |
|---|---|---|
| Plan in Fully Powered Planner | The principal and the office manager | An afternoon together naming the firm’s teams, listing the work each one repeats and choosing the weekly receivables summary to build first. |
| Run from exports | The office manager | A few minutes each Monday. She exports the open-invoices report she already uses, hands it to the workflow in the firm’s Claude workspace and reads the summary before it goes to the principal. |
| Connect the accounting system | The office manager, as the account’s administrator | One short call. A connector for the firm’s accounting system already exists, and connecting it was agreed in scoping. We show her what the connection can read, she approves access in the account’s settings, and we set it up. The Monday export step goes away. |
Each person who takes part already has the knowledge or the access their step calls for, and we build the rest.
Bring the person who approves your accounts to the fit call.
On a fit call we look at the work you want to start with, the systems it touches and where it sits in your plan. If a workflow may reach into one of your systems, bring whoever administers that account, so the person who will say yes hears the answers.
Your team stays on the platform it already has, at the pace you set, and your organization keeps control of how the work gets done. That is how you get 10X the ROI of your existing AI with no IT staff at all.
Bring one piece of work your team repeats every week, and the person who holds the keys to the system it lives in.