Home / What’s possible / Workflow automation
Workflow automation
Copying a request from a form into a spreadsheet, letting the right person know, checking three days later whether anyone followed up. These steps repeat every day, take up someone’s time and, one day, are bound to be forgotten.
One task starts, the rest runs on its own
The flow starts when a form is filled in, an order comes in or a document is uploaded. Information is written to the programs that need it, the right person is notified and overdue work gets a reminder. We first look at how work runs today and where it gets stuck, then build the flow around that.
Who is it for?
Teams that enter the same information into more than one program by hand, businesses that lose requests between email and messages, companies where approval and follow-up steps depend on individual people, and those who prepare the weekly report by hand every time.
Which tasks can be automated?
- Recording and routing requests from forms
- Moving information between programs
- Email, SMS and WhatsApp notifications
- Approval flows
- Deadline and follow-up reminders
- Creating quotes and documents
- Preparing regular reports
- Syncing between spreadsheets and databases
- Alerts when something goes wrong
Who stays in control?
Automation takes on repetitive work; it doesn’t make decisions. Steps that need approval wait for your team, and if the flow gets stuck somewhere, it notifies the person responsible. We decide together which steps run on their own and which wait for approval.
An off-the-shelf tool or a custom flow?
For simple flows between common programs, off-the-shelf automation tools are often enough. They’re quick to set up, and the initial cost stays low.
If the programs you use have no ready-made connection, the flow has many steps or the data has to stay on your own server, a custom setup is the better choice. We look at which one suits you together, before you decide.
What affects the price?
The price depends on the number of flows and their steps, the programs to be connected, the approval process and whether an off-the-shelf tool or a custom setup is used. Once we’ve studied the process, we send a quote with a clear scope.
Frequently asked questions
Which tasks are suited to automation?
Tasks that follow rules, repeat often and carry information from one program to another. Steps that need a human decision stay in the flow but are tied to an approval.
Will it work with the programs I use?
That depends on the connections the programs allow. If there’s no direct connection, a flow can also be built through files or email. We look at it together before setup.
What happens if a flow breaks?
When an error occurs, the flow stops and notifies the person responsible; no information is lost. The logs show when and where it got stuck.
Can we start with a small task first?
Yes, and that’s the approach we recommend. We start with the single flow that takes the most time and expand once we’ve seen it works.
Will my team have to learn a new program?
Usually not. The flows run between the programs your team already uses.
Do you work with off-the-shelf automation tools?
If they do the job, yes. If they aren’t needed, or the data must not leave your systems, we set up the flow to run on your own server.
What about personal data?
We decide together which data goes to which program and where it is stored, in line with GDPR, Turkey’s KVKK or whichever rules apply to you.
Can we change the flow later?
Yes. The flow is updated as the way you work changes. We set it up so your team can make simple changes themselves.
Are there monthly costs after setup?
For most setups, yes. Subscription fees for off-the-shelf tools or server costs vary with usage. We list them separately in the quote.
How long does setup take?
It depends on the number of flows and connections. We share a clear timeline with the quote.
Who owns the code?
We discuss code ownership based on the scope of the work and put it in the agreement.
How is the system handed over to us?
We agree on how the handover will work at the start of the project. We hand it over after teaching your team how to use it.
How long is support provided?
We provide support for bugs and issues for the first six months after delivery. After that, it depends on the contract.