Questions, answered
Straight answers about how we work, how we keep AI under control and what it takes to get started.
Working with Keepflow
You're a new company. Why should we work with you?
You don't have to take our word for it. We start with one workflow, agree what success looks like before we build, and only expand once it has proven useful. The demonstrations on this website show how we think about AI, rules and people.
How do we start?
Tell us about one process where work gets stuck. We'll look at it with you and recommend a small first workflow with a clear scope and cost.
What happens after launch?
We monitor the workflow, fix issues, review how it's performing against what we agreed, and recommend improvements. You decide whether to expand.
Do you only build automation?
Yes, automation is what we offer today. We're planning a managed support service, Keepflow Teams, for work that still needs people, but it isn't available yet.
AI and safety
Will the AI make decisions on its own?
No. The AI interprets messages and documents. Business rules that you agree decide what happens next, and anything sensitive, unusual or high-stakes goes to a person.
What if the AI gets something wrong?
We design for it. Low-confidence results are handed to a person instead of guessed, sensitive actions need approval, every automated step is logged, and we test edge cases and failures before launch.
How do you handle safety-sensitive situations?
With fixed rules, not AI judgement. When a message suggests a safety issue, automation stops, a pre-approved message is sent, and a person is alerted straight away. The AI doesn't improvise advice.
Will customers know they are talking to an automated system?
We recommend being open about it, and always offering a route to a person.
Systems and data
Do we need to replace our current systems?
Usually not. We build around the tools you already use, such as your inbox, CRM, spreadsheets and calendar, and only suggest something new when it clearly helps.
Which tools do you work with?
It depends on what you already use. Typical building blocks include workflow tools such as n8n or Make, language models accessed through a secure server, text-messaging providers such as Twilio, CRMs such as HubSpot, calendars, and Microsoft 365 or Google Workspace.
Where do API keys and credentials live?
On secure servers, never in a website or browser. Each workflow gets only the access it needs.
What happens to our data?
We agree up front what data a workflow uses, where it's processed and who can access it, and keep it to what's necessary.
Pricing and control
How is pricing structured?
It depends on the scope of the workflow and the support you need afterwards. We agree the scope and cost with you before any work starts.
Can we pause or switch off an automation?
Yes. Every workflow we build can be paused, and we agree a fallback process so nothing gets lost while it is off.
Still have a question?
Ask us directly. We’ll give you a straight answer.