> automation & integration studio
Untangle the work between your tools.
We map how work moves through your team, pick the tool that fits each step, and wire it into one flow that starts on a trigger, checks itself and reports back.
the same untangling, in
- before
- starts when someone remembers
- after, starts when
- a new brief arrives
- built in
- 2 checks, one retry loop
- ends with
- a report, every run
Modelled on an ad-creative pipeline we built: a new brief triggers research, copy, images, two checks, delivery and a report, as one run.
- before
- starts when someone remembers
- after, starts when
- a new order comes in
- built in
- 1 check, 1 decision
- ends with
- a report, every run
Illustration: payment is checked, then stock decides the route. In stock goes to picking, label and courier; out of stock goes to a reorder and a note to the customer.
- before
- starts when someone remembers
- after, starts when
- an invoice arrives
- built in
- 2 checks, one retry loop, 1 decision
- ends with
- a report, every run
Illustration: an invoice is read, checked against three records at once, and matched. Small amounts post straight to the ledger; large ones wait for a manager.
- before
- starts when someone remembers
- after, starts when
- the shift ends
- built in
- 1 check, one retry loop
- ends with
- a report, every run
Illustration: three inputs from site become one day report. Once the foreman approves it, payroll, invoicing, the project log and stock all update at once.
- before
- starts when someone remembers
- after, starts when
- an application arrives
- built in
- 1 check, 1 decision
- ends with
- a report, every run
Illustration: each application becomes a profile and is screened. A fit goes to a recruiter, an invite and the calendar; the rest get a polite decline.
- before
- starts when someone remembers
- after, starts when
- a ticket opens
- built in
- 1 check, 1 decision
- ends with
- a report, every run
Illustration: a ticket is classified. Known issues get a checked answer automatically; new ones go to a person. Either way the reply, the CRM and the help docs stay in step.
Read the six example workflows as text
- Marketing: starts when a new brief arrives
- trigger (a new brief arrives) → forums + ad intel → research → copy → review (check) → images → visual QA (check) with a loop back to images → assets + tracker + publish → report.
- E-commerce: starts when a new order comes in
- trigger (a new order comes in) → payment (check) → stock (decision: in stock goes to pick list, backorder goes to reorder) → pick list + reorder → label + customer note → courier → report.
- Finance: starts when an invoice arrives
- trigger (an invoice arrives) → extract → PO + supplier + tax ID → match (check) with a loop back to supplier → amount (decision: over limit goes to manager, under limit goes to ledger) → manager (check) → ledger → payment + archive → report.
- Construction: starts when the shift ends
- trigger (the shift ends) → timesheets + site photos + deliveries → day report → foreman (check) with a loop back to day report → payroll + invoice + project log + stock → report.
- Recruiting: starts when an application arrives
- trigger (an application arrives) → profile → fit (decision: fit goes to recruiter, no fit goes to decline) → recruiter (check) + decline → invite → calendar → report.
- Support: starts when a ticket opens
- trigger (a ticket opens) → known (decision: known goes to answer, new goes to agent) → answer + agent → policy (check) → reply → CRM + help docs → report.
01 / the difference
Same four tools. One version needs a person at every arrow.
Most teams already own good tools. What is missing is the connection between them, so a person carries the data across by hand.
By hand
todayreads the enquiry in the inbox
- 3 times retyped
- 4 stops waiting on a person
- 0 record of what happened
Automated
afterenquiry arrives, the run starts on its own
- 0 times retyped
- 1 approval by a person
- 1 report per run
02 / anatomy of an automated workflow
Every automation is the same six parts.
Once you can name the parts, you can see which of your own steps fit. Select a part, or let it play.
- what it does
- Something happens and the run starts without anyone pressing a button.
- for example
- An email lands, a form is sent, a deal changes stage, or the clock reaches 08:00.
- usually built with
- Webhooks, schedules, inbox rules
03 / what to automate
Not every step should be automated the same way.
We sort each step of your flow into one of three lanes before choosing any tool.
Automate fully
Same input, same output, every time. No judgement involved.
- Moving data between systems
- Reminders and follow-ups
- Status updates
- Assembling a weekly report
- Creating records from a form
Automate with a check
A tool does the work, then a rule or a person confirms it before it goes further.
- Drafting replies
- Qualifying leads
- Sorting documents
- Generating images and copy
- Reading invoices
Keep with a person
The decision is the job. Automation only prepares what the person needs.
- Pricing and discounts
- Final approvals
- Hard client conversations
- Hiring decisions
04 / process
Four steps, in this order, every time.
We do not start with a tool. We start with how the work moves today.
Map
We sit with the people who do the work and write down every step, handoff and tool.
you getA map of the flow as it runs today, knots marked.Pick
For each step we compare a feature you already own, an automation platform, an AI model and plain code, then recommend one.
you getA comparison per step and one recommendation. No vendor ties.Wire
We connect the chosen tools into one run, with a check between steps so a bad result stops early.
you getA working pipeline in your own accounts, plus a runbook.Report
Every run ends with a log you can read and a cost report. A failing step shows up by name.
you getA history of every run and its cost. You own all of it.
05 / worked example
From new enquiry to paid invoice.
Select a step to see how it runs by hand, what we would weigh, and what we would likely choose. Notice how often the answer is not AI.
- A form that writes straight to the CRM
- An email parser in an automation platform
- An AI model that reads free-text emails
A form for new enquiries; AI reading only for emails that still arrive as free text.
The cheapest thing that works goes first. AI is used only where the input is messy.
An illustration. Your flow, your tools and the right picks will differ, which is what the mapping step is for.
06 / services
Three things we do.
Each one can be a project on its own. Most clients start with the first.
Procedure to pipeline
We take a written procedure, or one that lives in people's heads, and turn it into a run that does the routine parts on its own.
Tool selection and integration
We compare the options for each step, recommend one, and connect it to what you already use. We sell no licences and take no commissions.
Checks and cost reports
Quality checks between steps, retries with a limit, and a cost report after every run, so the automation stays auditable.
Automation you cannot audit is a liability.
Every run writes down what happened at each step, which tool did it, and whether the check passed. This sample follows a creative-production pipeline we built for a performance-marketing team.
| step | stage | tool | result |
|---|---|---|---|
| 1/5 | research | browser agent | PASS |
| 2/5 | copy | writing tool | PASS |
| 3/5 | images | image generator | RETRY |
| 4/5 | checks | reviewer | PASS |
| 5/5 | publish | ad platform | READY |
07 / questions
Asked before every project.
What does Untanglery do?
Untanglery is an automation and integration studio. We map how work moves through a team, choose the right tool for each step, and connect those tools into one workflow that starts on a trigger, checks its own results and writes a report after every run.
Is this an AI agency?
AI is one of the tools we use, and often a good one. But many steps are better served by a feature you already own or a simple connection between two apps. We recommend whatever does the step reliably at the lowest running cost.
Which tools do you work with?
Whichever fit. We start from what you already use and add something new only when the comparison shows it earns its place. We have no reseller agreements.
Which kinds of work can be automated?
Steps with the same input and output every time, such as moving data between systems, reminders and status updates, can run fully on their own. Steps that need judgement, such as drafting replies or qualifying leads, run with a check by a rule or a person. Decisions like pricing and final approvals stay with a person, and automation only prepares what they need.
Who owns the result?
You do. The pipeline runs in your accounts, and you keep the repository, the runbook and the run history.
What if a step cannot be automated well?
Then we say so and leave it with a person. A flow with one honest manual step beats a fully automatic one that fails quietly.
Where do we start?
With a flow review: you walk us through one process that hurts, and we tell you where the knots are and whether it is worth untangling. Email info@solvedge.ee or use the contact form.
08 / book a flow review
Bring one process that hurts.
Tell us what it is and which tools it touches. We reply with a time to walk through it together.
info@solvedge.ee