Do you need admin access?

Usually not. Most workflows run with a limited set of permissions. If something genuinely needs more, we will tell you what it is, why it is needed, and what the alternative would cost — and you can say no.

Will an automation contact our customers without us knowing?

Only if you set it up that way. Outbound messages are switched on deliberately, using wording you approve, and you can require that a person reviews every message before it is sent.

What if the automation makes a mistake?

We assume it will at some point, so anything sensitive is built to require a person's approval before it happens. When we first turn a workflow on, your team reviews what it produces before it runs on its own.

What happens if we stop working with you?

You remove the connections from your own software settings, which stops the automations. Anything created inside your systems while they were running — records, documents, invoices — is yours and stays where it is.

Can you work around our own security requirements?

Tell us about them during the analysis. If you operate under client confidentiality, health information rules, or obligations in your own customer contracts, we will either build around them or tell you honestly that a workflow is not a good fit.

Security & privacy

Your business data stays under your control.

You would be letting an outside company near the systems that run your business. That deserves a straight answer rather than a page of badges — so here is what we ask for, what we do not, and how you switch it all off.

The short version

The free analysis needs no access at all.
We ask only for what an approved automation needs.
Your passwords stay with you.
Connections can be turned off by you.
We can sign an NDA before we talk details.
You approve what the automation can and cannot do.

What we always do

Write down what each automation needs access to, before we connect anything
Use the official, supported way of connecting to your software
Let you approve each connection from your own account
Show you where the off switch is for every connection
Sign an NDA before we discuss the details of your business
Tell you when something is a bad idea

What we never do

Ask for your passwords or ask you to share a login
Ask for full administrator access as a default
Send messages to your customers that you have not approved
Connect a system without showing you what it will do first
Make turning us off depend on getting hold of us
Claim certifications we do not hold

In detail

How we handle access, explained plainly.

We look at the work before we look at your systems

Nothing gets connected to talk to us. The first conversation is about how your business runs and which parts of it are repetitive. We only discuss access later, once you have decided there is something worth building.

We ask only for the access the approved automation needs

Before anything is connected, we write down which systems the automation touches and what it needs to do in each one — read a calendar, create an invoice, file a document. We ask for permission for those things and not for the rest of your account. You see that list in writing before you approve any connection.

We use official, supported connections

Where a business system offers a supported way for other software to connect to it, that is what we use. Those connections are built to be permission-limited and to be switched off by the account owner. If a system does not offer one, we will tell you rather than working around it with something fragile.

Your passwords stay with you

We will not ask you to email us a password or share a login. Where the software supports it, you sign in to your own system and approve a specific connection, and your provider issues a credential for that connection alone. If anyone ever asks you for a password on our behalf, it is not us.

Access can be turned off

Most business software lets the account owner see connected applications and remove them. Where that is the case, you can switch us off yourself, without asking us first. At the end of a build we hand you a short document listing every connection and where to find the switch, so shutting something down never depends on reaching us.

You approve what the automation can and cannot do

For every workflow we agree, in advance and in writing, which actions are allowed to happen automatically and which require someone on your team to review and approve first. Sensitive actions — sending contracts, issuing refunds, deleting records — default to requiring a person. You can tighten those limits at any time.

We can work under an NDA

Talking honestly about how your business runs means talking about customers, pricing, and where things go wrong. If you would rather have that protected in writing first, say so and we will sign a mutual non-disclosure agreement before the conversation. We are happy to use your document rather than ours.

What we do not claim

We do not hold SOC 2, HIPAA, GDPR, or ISO certification, and we will not tell you otherwise.
No system is completely secure, including ours. Anyone who tells you differently is selling something.
What is technically possible depends on your software. Some systems offer fine-grained permissions and clear controls; others do not. We will tell you which you are dealing with.

If your business has formal compliance obligations, bring them up early and we will be straight with you about whether a workflow is a good fit.

An example

What an access request looks like.

Before anything is connected, you get a list like this — one row per system, in plain language. You approve them one at a time, and you can say no to any of them.

Example of what each connected system would and would not allow
System	What it can do	What it cannot do
Calendar	See when you are free, add and update appointments	Read your email, open your contacts, change account settings
CRM	Read and add contacts, log activity, update a deal's stage	Export the whole database, delete records, manage users
Accounting	Prepare draft entries and invoices, check payment status	Move money, change bank details, approve payments
Email	Read incoming messages in a specific folder, send approved templates	Send anything you have not approved, or reach addresses you exclude

An illustration. Your own list is written against your workflows and your systems, and what is possible depends partly on what each system allows.

You stay in control

Automation should handle the repetitive work, not run your business.

Some steps are safe to run on their own, like filing a document or preparing a draft. Others should never happen without a person, like sending a contract or issuing a refund. You decide which is which, and we set those limits before anything goes live.

Step 1

The automation prepares the work

It gathers the information and gets the task ready to go.

Step 2

An employee reviews it

Your team sees exactly what was prepared, before anything happens.

Step 3

An employee approves it

Nothing sensitive moves forward until a person says so.

Step 4

The system carries it out

The approved action is applied in your software.

Questions

The questions owners actually ask.

No. The analysis is a conversation about how your business runs. Nothing needs to be connected, and you do not need to share any logins to have it.

Have a question that is not here? Ask it during the analysis, or before it.

Get a free workflow analysis

Want an NDA signed first?

Say so when you get in touch and we will have a mutual non-disclosure agreement in place before the conversation. Your document or ours — either is fine.

Get a free workflow analysis (818) 855-5875

A written list of the repetitive work in your business
An honest answer on what could realistically be automated
And what should be left alone, and why
Yours to keep, whether or not we work together